Source: tar
Version: 1.35+dfsg-3
Severity: wishlist
Hi,
I used
$ PGPASSWORD="udd-mirror" psql --port=5432 --host=udd-mirror.debian.net
--username=udd-mirror udd <<EOT
SELECT source,
vote,
maintainer,
vcs_url,
tags
FROM (
SELECT source, vote, MAX(testsuite) as testsuite, maintainer, vcs_url, tags
FROM (
SELECT source, vote, testsuite, maintainer, vcs_url, tags, row_number()
OVER (PARTITION BY source ORDER BY vote DESC) FROM (
SELECT DISTINCT p.source, p.package, s.maintainer, s.vcs_url,
CASE WHEN pop.vote IS NULL THEN -1 ELSE pop.vote END AS vote,
s.testsuite, d.tags FROM packages p
LEFT OUTER JOIN popcon pop ON p.package = pop.package
LEFT OUTER JOIN (SELECT source, maintainer, vcs_url, testsuite FROM
sources WHERE release = 'sid' ) s ON p.source = s.source
LEFT OUTER JOIN (SELECT package, array_agg(tag) AS tags FROM debtags
WHERE tag LIKE 'uitoolkit::%' OR tag LIKE '%x11%' GROUP BY package) d ON
p.package = d.package
WHERE p.release = 'sid'
) tmp1
) tmp2
GROUP BY source, vote, tags, maintainer, vcs_url
) tmp3 WHERE testsuite is NULL
AND VOTE > 1000
ORDER BY vote DESC, source
LIMIT 5;
EOT
source | vote | maintainer
| vcs_url
| tags
-------------+--------+----------------------------------------------------------------------------+-----------------------------------------------------------------+----------------------------------------------------------------------------------
debconf | 217976 | Debconf Developers
<[email protected]> |
https://salsa.debian.org/pkg-debconf/debconf.git |
{uitoolkit::ncurses,interface::x11,uitoolkit::TODO,uitoolkit::gtk,uitoolkit::qt}
zlib | 217757 | Mark Brown <[email protected]>
|
|
tar | 216067 | Janos Lenart <[email protected]>
| https://salsa.debian.org/debian/tar.git
|
sysvinit | 214097 | Debian sysvinit maintainers
<[email protected]> |
https://salsa.debian.org/debian/sysvinit.git |
libgcrypt20 | 212538 | Debian GnuTLS Maintainers
<[email protected]> |
https://salsa.debian.org/gnutls-team/libgcrypt.git -b branch1.6 |
to find out what most popular packages in Debian are not featuring some
autopkgtest. Since I somehow considered tar some feasible target to
write such a test I tweaked the build time test to hopefully work as
autopkgtest. I succeeded in my local chroot. To make sure it will
really work reliably I created a branch in Git[1] where I added this
test. My hope was an additional verification that it works in CI - but
this failed[2]. I admit I'm a bit clueless about
1. Why this test fails in Salsa CI while it succeeds locally
2. Whether this kind of test is really sensible since it includes
some automake created header files I have stolen from amd64
build[3] which definitely is a hack that might break for
a) upgrades
b) other architectures
3. Whether we might consider a more simple test just as starting
point.
Thus I did not created a MR and do not tag this bug patch leaving it for
further discussion. If you prefer I should rather fork your git
repository on Salsa and discuss things in some MR I'm fine with removing
that said branch. I just don't know your prefered way of communication
in your small packaging team.
Thanks a lot for maintaining tar
Andreas.
[1] https://salsa.debian.org/debian/tar/-/tree/autopkgtest?ref_type=heads
[2] https://salsa.debian.org/debian/tar/-/jobs/5494107
[3]
https://salsa.debian.org/debian/tar/-/blob/autopkgtest/debian/tests/headers.tar.xz?ref_type=heads
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (50, 'buildd-unstable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 6.3.0-2-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
