Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.bugs.dist > #1171244 > unrolled thread
| Started by | наб <nabijaczleweli@nabijaczleweli.xyz> |
|---|---|
| First post | 2023-10-09 14:10 +0200 |
| Last post | 2023-10-09 16:40 +0200 |
| Articles | 3 — 1 participant |
Back to article view | Back to linux.debian.bugs.dist
Bug#1053710: lintian: Homepage: https://lintian.debian.org/ NXDOMAIN наб <nabijaczleweli@nabijaczleweli.xyz> - 2023-10-09 14:10 +0200
Bug#1053710: lintian: Homepage: https://lintian.debian.org/ NXDOMAIN наб <nabijaczleweli@nabijaczleweli.xyz> - 2023-10-09 15:20 +0200
Bug#1053710: lintian: Homepage: https://lintian.debian.org/ NXDOMAIN наб <nabijaczleweli@nabijaczleweli.xyz> - 2023-10-09 16:40 +0200
| From | наб <nabijaczleweli@nabijaczleweli.xyz> |
|---|---|
| Date | 2023-10-09 14:10 +0200 |
| Subject | Bug#1053710: lintian: Homepage: https://lintian.debian.org/ NXDOMAIN |
| Message-ID | <HmXfb-eBQk-1@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Source: lintian Version: 2.116.3 Severity: normal Dear Maintainer, $ apt info lintian Homepage: https://lintian.debian.org/ $ host lintian.debian.org Host lintian.debian.org not found: 3(NXDOMAIN) https://codesearch.debian.net/search?q=lintian.debian.org&literal=1&perpkg=1 shows that this is used heavily (I came across it on a mentors.d.n listing, for example). I don't see any off-line documentation listed in /u/s/doc/lintian, and indeed the tags ‒ which is what lintian.d.o was used most of all ‒ are available exclusively online via lintian-explain-tags and /usr/share/lintian/tags, which isn't really, uh, linkable. If maintaining lintian.d.o is too much of a maintenance burden (though I can't imagine why turning 1527 RFC822s in a consistent format into HTMLs once per release would be one), something should should be put in its place (indeed, generating a lintian-tags(7) is similarly trivial and autogenerates into a manpages.d.o entry). Best, наб -- System Information: Debian Release: 12.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_FIRMWARE_WORKAROUND, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information
[toc] | [next] | [standalone]
| From | наб <nabijaczleweli@nabijaczleweli.xyz> |
|---|---|
| Date | 2023-10-09 15:20 +0200 |
| Message-ID | <HmYkV-eCXd-3@gated-at.bofh.it> |
| In reply to | #1171244 |
[Multipart message — attachments visible in raw view] — view raw
Indeed, as I later noticed in https://salsa.debian.org/mentors.debian.net-team/debexpo/-/issues/160: archive.org says the last scrape of lintian.d.o was on 2023-09-13 and /succeeded/, so this is very recent breakage, to the extent that I wonder if this is purely a zone misconfiguration. To that end, src:lintian appears to contain a significant amount of lintian.d.o-specific data and what appears to be code. So ‒ is it just a zone misconfiguration?
[toc] | [prev] | [next] | [standalone]
| From | наб <nabijaczleweli@nabijaczleweli.xyz> |
|---|---|
| Date | 2023-10-09 16:40 +0200 |
| Message-ID | <HmZAl-eEPg-3@gated-at.bofh.it> |
| In reply to | #1171251 |
[Multipart message — attachments visible in raw view] — view raw
https://salsa.debian.org/dsa-team/mirror/domains sayeth
(commits that mention lintian, after 2014):
commit 19c1f45b63b0fe91222f2806bb1c81594d16d073
Author: Pierre-Elliott Bécue <peb@debian.org>
Date: Mon Sep 18 10:34:47 2023 +0200
RT9275: Drop CNAME lintian.debian.org
debian.org | 1 -
1 file changed, 1 deletion(-)
commit a6d86f260a79593abc7e84482657cc1af09f9430
Author: Aurelien Jarno <aurelien@aurel32.net>
Date: Fri May 7 00:04:45 2021 +0200
Move lintian.d.o to lintian-01
debian.org | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
commit 3768edf828b5f2c576ad401625c6ea137ede1b12
Author: Aurelien Jarno <aurelien@aurel32.net>
Date: Sat May 1 23:23:48 2021 +0200
Reserve IPs @ conova for lintian-01.d.o
1.0.1.4.c.d.8.a.6.1.2.0.a.2.ip6.arpa | 1 +
debian.org | 1 +
2 files changed, 2 insertions(+)
3768edf828b5f2c576ad401625c6ea137ede1b12 adds PTRs,
a6d86f260a79593abc7e84482657cc1af09f9430 replaces
lintian CNAME static
with
lintian CNAME lintian-01,
and naturally
19c1f45b63b0fe91222f2806bb1c81594d16d073 removes
lintian CNAME
entirely.
lintian-01.debian.org resolves and appears to nominally exist:
https://db.debian.org/machines.cgi?host=lintian-01
It responds to pings, but refuses 80 and 443.
Dialing static.d.o with Host: lintian.debian.org,
both klecker and mirror-csail respond with a generic "this is $HOST" page.
nagios.debian.org says lintian-01 is "UP" for 12 days,
and bases this on ping connectivity (which, I s'pose, makes it right).
https://munin.debian.org/debian.org/lintian-01.debian.org/index.html
says traffix in kilobytes per second all the way back to 2023-10-01,
and allthewhile 0 apache requests.
RT#9275 is inacessible to me, since guest logins to rt.d.o were removed,
so I'm unable to draw a conclusion.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.bugs.dist
csiph-web