Package: ftp.debian.org
User: ftp.debian@packages.debian.org
Usertags: remove
Control: affects -1 src:theano src:deepnano src:keras
Control: reopen 1026539
Control: reopen 1027215
theano has been mostly abandoned upstream since 2018. (The Aesara fork
is not abandoned, but includes interface
Package: qa.debian.org
User: qa.debian@packages.debian.org
Usertags: udd
Bug titles containing non-ASCII characters work in the BTS:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=966851
but not in the UDD bug listings, or the autoremovals notices generated
from them:
https://udd.debian
Johannes Schauer wrote:
In particular, in the "CI" column, look for those rows where the first line
shows exactly "✔-" -- those packages have to be excluded. Failures are fine and
even both missing is fine but a checkmark followed by a minus triggers that
bug.
Neutral/missing ("⛔-") is also bad
Control: retitle -1 UDD/dmd: fails to load when debci data is missing
The problem isn't the number of packages, but some specific packages
that can't be displayed even when they are the only package requested:
https://udd.debian.org/dmd/?email1=&email2=&email3=&packages=node-file-entry-cache&ig
debcheck processes a single release per run, so in its current form
can't check this, or anything that requires comparing multiple releases.
(The oldlibs check looks for explicit Section: oldlibs labels.)
There is a separate tool on jenkins that does check this:
https://salsa.debian.org/qa/jen
Control: retitle -1 debcheck: :$arch and :native always appear broken
Since
https://salsa.debian.org/qa/qa/-/commit/526d2319174cb15111bb2d6c702f8e23ee7bd0d7
, arch-specific Depends don't crash debcheck, but do search for a
package named literally $package:$arch not just $package. As this does
This appears to be fixed, probably by
https://salsa.debian.org/qa/qa/-/commit/56fbe1b36e3a8ec9064cb9ce6cbcbfd5448feb61
(Fixed on qa.debian.org/dose/debcheck/...;
qa.debian.org/debcheck.php?... doesn't have a tracker link at all.
Should it?)
Control: tags -1 patch
If you'd prefer to just fix this without (for now) the broader rewrite,
https://salsa.debian.org/qa/qa/-/merge_requests/28 claims to do so; I
haven't tried it but it looks plausible.
Weirdly, this bug doesn't seem to affect everything with build profiles:
of my package
Package: qa.debian.org
User: qa.debian@packages.debian.org
Usertags: udd
Some packages' vcswatch pages have the error
fatal: could not read Username for 'https://salsa.debian.org': No such
device or address
(e.g. apertium-bel, python-asteval) or
remote: Retry later fatal: unable to acces
Package: qa.debian.org
User: qa.debian@packages.debian.org
Usertags: udd
Some packages have a dash in the watch column of
qa.debian.org/developer.php and this error message on tracker.debian.org:
uscan had problems while searching for a new upstream version:
In watchfile debian/watch, rea
Package: tracker.debian.org,debci
https://wiki.debian.org/ContinuousIntegration/RegressionEmailInformation
says autopkgtest failures trigger an automatic email.
When theano recently started failing [0] (#918090), no such email was
received, either to its maintainer list [1] or to me (subscrib
Package: tracker.debian.org
Severity: minor
Control: tags -1 patch
The 'all' bugs count double-counts 'patch' bugs (but not 'help' or
'newcomer' bugs, which also appear both there and in a severity
category), e.g. https://tracker.debian.org/pkg/debhelper
Can probably be fixed (though I haven'
Control: retitle -1 UDD/testing_autoremovals_gatherer.pl: includes
non-release-architecture Build-Depends
The autoremoval listing went away when beignet 1.2.0 (which no longer
depends on LLVM 3.7 on any architecture) reached testing, and inspection
of the tool's source
(https://anonscm.debian.org
[beignet] 1.1.2-4 had the problem, 1.1.2-5 doesn't, and is no longer listed for
autoremoval):
beignet now *is* listed for autoremoval, for (a different) LLVM 3.7 bug,
though I haven't had another warning email (yet).
1.1.2-5 dropped the LLVM 3.7 dependency on release architectures, but
kept
Package: qa.debian.org
Severity: minor
User: qa.debian@packages.debian.org
Usertags: udd
When a package has recently migrated, one may receive an autoremoval
warning that lists the new version of the package, but a problem only
the old version had.
Example (1.1.2-4 had the problem, 1.1.2-
15 matches
Mail list logo
