podcastindex-db: 0-unstable-2025-04-27 -> 0-unstable-2025-04-29
the db just grew 5x in size... upstream website claims that this new count is correct, and is only a couple % larger than 3 days ago, implying that the old db snapshot was wrong somehow... in fact looking at `head` and `tail` of the new v.s. old indexes: - primary keys in old db: 6385082 - 7311215 - primary keys in new db: 1 - 7313345 so the old one was just WRONG somehow? and ACTUAL growth is about 1000 keys per day. TODO: add some safeguards to the update script, in light of this!
This commit is contained in:
@@ -13,14 +13,14 @@
|
||||
|
||||
stdenv.mkDerivation {
|
||||
pname = "podcastindex-db";
|
||||
version = "0-unstable-2025-04-27";
|
||||
version = "0-unstable-2025-04-29";
|
||||
|
||||
src = fetchFromGitea {
|
||||
domain = "git.uninsane.org";
|
||||
owner = "colin";
|
||||
repo = "podcastindex-db-mirror";
|
||||
rev = "354ad295ea6b46055e71405d77e841d20b265e8c";
|
||||
hash = "sha256-nhjZ2AIlDa7OX5/UFOqF5acyKT5wkdyD9/mpbp4bzvE=";
|
||||
rev = "2a87bdd92b71acd74527cee6715cfbb67331df8a";
|
||||
hash = "sha256-YyroE7+R/V290stXnYHwD65WwgsZj4KYzTzgClrLW1g=";
|
||||
};
|
||||
|
||||
dontBuild = true;
|
||||
|
Reference in New Issue
Block a user