[Piuparts-reports] Cron <piupartsm at pejacevic> detect_archive_issues

[Cron Daemon]

Runtime: 00:00:02

Broken packages detected! The following packages have been moved to
/untestable and will be tested again in 1 days.

Broken packages are usually a temporary problem in the archive and are
caught by other tools like britney or https://qa.debian.org/dose/debcheck.html
If it is always the same package failing, it's likely to be an issue in the
package.

     84 https://piuparts.debian.org/sid-nodoc/untestable/tulip-dbg_4.8.0dfsg-2+b7.log
     83 https://piuparts.debian.org/sid-nodoc/untestable/libtulip-dev_4.8.0dfsg-2+b7.log
     76 https://piuparts.debian.org/sid-nodoc/untestable/python-kivy-examples_1.9.1-1.log
     45 https://piuparts.debian.org/sid-nodoc/untestable/python-sardana_2.2.2-3.log
      1 https://piuparts.debian.org/sid2experimental/untestable/libpetsc-real3.9-dev_3.9.1+dfsg1-1exp2.log
      1 https://piuparts.debian.org/sid2experimental/untestable/libpetsc-complex3.9-dev_3.9.1+dfsg1-1exp2.log
      1 https://piuparts.debian.org/experimental/untestable/libpetsc-real3.9-dev_3.9.1+dfsg1-1exp2.log
      1 https://piuparts.debian.org/experimental/untestable/libpetsc-complex3.9-dev_3.9.1+dfsg1-1exp2.log

Those problems were found in failed logs by grep'ing for these patterns:
        'E: Broken packages'
        'E: Unable to correct problems, you have held broken packages'
        'E: Error, pkgProblemResolver::Resolve generated breaks'