Change Details

Now that the new listers have run a bit, some of those listers demonstrate issues caught by sentry. Some are already fixed in the repositories (cran [1]), some are tasks inputs to update (debian, gitea, ...) [2], others are plain tasks which no longer exists (gitea full task, ...) [3] Resolve those issues following the next-gen deployments. [1] https://sentry.softwareheritage.org/share/issue/500f1adcceed4897a7c580b62e7de7af/ [2] https://sentry.softwareheritage.org/share/issue/d15b817b882d4a28a1fbde27b5b5ba49/ [3] https://sentry.softwareheritage.org/share/issue/8a9ea56b626840d288c26e427a7addcd/

Now that the new listers have run a bit, some of those listers demonstrate issues caught by sentry: - [x] cran issue due to some parser error in date [1] (already fixed, needs deployement v0.9.0) - [x] task inputs needs some update [2] (debian) - [x] Task needs be disabled (incremental gitea listing no longer exist, this needs to be replaced by full listing when needed) [3] - [x] some debian repository (debian-security) needs code adaptation (v0.9.1) Resolve those issues following the next-gen deployments. [1] https://sentry.softwareheritage.org/share/issue/500f1adcceed4897a7c580b62e7de7af/ [2] https://sentry.softwareheritage.org/share/issue/d15b817b882d4a28a1fbde27b5b5ba49/ [3] https://sentry.softwareheritage.org/share/issue/8a9ea56b626840d288c26e427a7addcd/

Now that the new listers have run a bit, some of those listers demonstrate issues caught by sentry.: Some are already fixed in the repositories (cran [1])- [x] cran issue due to some parser error in date [1] (already fixed, some are tasks inputs to updateneeds deployement (debian, gitea, ...) [2], others are plain tasks which no longer exists (gitea full v0.9.0) task- [x] task inputs needs some update [2] (debian) - [x] Task needs be disabled (incremental gitea listing no longer exist, ...) [3]this needs to be replaced by full listing when needed) [3] - [x] some debian repository (debian-security) needs code adaptation (v0.9.1) Resolve those issues following the next-gen deployments. [1] https://sentry.softwareheritage.org/share/issue/500f1adcceed4897a7c580b62e7de7af/ [2] https://sentry.softwareheritage.org/share/issue/d15b817b882d4a28a1fbde27b5b5ba49/ [3] https://sentry.softwareheritage.org/share/issue/8a9ea56b626840d288c26e427a7addcd/