Bug#1120749: marked as done (upgrade-reports: mxrepo.com/mx/repo trixie/main amd64 ddm-mx all 25.11.01 is not (yet) available (404 Not Found)

This is a multi-part message in MIME format...

------------=_1763240223-469654-0
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"

Your message dated Sat, 15 Nov 2025 20:53:55 +0000
with message-id <0c1b6fb11476d156204de9419a17421ac8c02278.camel@adam-barrat=
t.org.uk>
and subject line Re: Bug#1120749: upgrade-reports: mxrepo.com/mx/repo trixi=
e/main amd64 ddm-mx all 25.11.01 is not (yet) available (404  Not Found
has caused the Debian Bug report #1120749,
regarding upgrade-reports: mxrepo.com/mx/repo trixie/main amd64 ddm-mx all =
25.11.01 is not (yet) available (404  Not Found
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


--=20
1120749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D1120749
Debian Bug Tracking System
Contact [email protected] with problems

------------=_1763240223-469654-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.debian.org; 15 Nov 2025 19:59:32 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
	(2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-13.6 required=4.0 tests=BAYES_00,
	BODY_INCLUDES_PACKAGE,HAS_PACKAGE,KHOP_HELO_FCRDNS,RCVD_IN_PBL,
	RCVD_IN_VALIDITY_CERTIFIED_BLOCKED,RCVD_IN_VALIDITY_RPBL_BLOCKED,
	RCVD_IN_VALIDITY_SAFE_BLOCKED,RDNS_DYNAMIC,SPF_SOFTFAIL,
	XMAILER_REPORTBUG autolearn=ham autolearn_force=no
	version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 36; hammy, 128; neutral, 46; spammy,
	1. spammytokens:0.943-+--H*r:bugs.debian.org
	hammytokens:0.000-+--XDebbugsCc, 0.000-+--X-Debbugs-Cc,
	0.000-+--trixie, 0.000-+--UD:ftp-master.debian.org,
	0.000-+--ftp-master.debian.org
Return-path: <[email protected]>
Received: from 80-218-20-141.dclient.hispeed.ch ([80.218.20.141]:52449 helo=[127.0.0.1])
	by buxtehude.debian.org with esmtp (Exim 4.96)
	(envelope-from <[email protected]>)
	id 1vKMQl-001iuh-30
	for [email protected];
	Sat, 15 Nov 2025 19:59:32 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: CAlbrecht <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: upgrade-reports: mxrepo.com/mx/repo trixie/main amd64 ddm-mx all 25.11.01 is not (yet) available (404  Not Found
Message-ID: <176323676391.6523.1437209938769053029.reportbug@localhost>
X-Mailer: reportbug 13.2.0
Date: Sat, 15 Nov 2025 20:59:23 +0100
Delivered-To: [email protected]

Package: upgrade-reports
Severity: important
X-Debbugs-Cc: [email protected]

(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

My previous release is: <codename or version from which you are upgrading>
I am upgrading to: <codename or version of the release you are upgrading to>
Archive date: <Timestamp, available as project/trace/ftp-master.debian.org
     on your mirror or .disk/info on your CD/DVD set>
Upgrade date: <Date and time of the upgrade>
uname -a before upgrade: <The result of running uname -a on a shell prompt>
uname -a after upgrade: <The result of running uname -a on a shell prompt>
Method: <How did you upgrade?  Which program did you use?>

Contents of /etc/apt/sources.list:


- Were there any non-Debian packages installed before the upgrade?  If
  so, what were they?

- Was the system pre-update a 'pure' system only containing packages
  from the previous release? If not, which packages were not from that
  release?

- Did any packages fail to upgrade?

- Were there any problems with the system after upgrading?


Further Comments/Problems:


Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
depending on your shell) from before and after the upgrade so that we
know what packages were installed on your system.

------------=_1763240223-469654-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 1120749-done) by bugs.debian.org; 15 Nov 2025 20:54:04 +0000
X-Spam-Checker-Version: SpamAssassin 4.0.1-bugs.debian.org_2005_01_02
	(2024-03-25) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-5.5 required=4.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,HAS_BUG_NUMBER,SPF_HELO_NONE,
	SPF_PASS,URIBL_BLACK autolearn=ham autolearn_force=no
	version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 19; hammy, 150; neutral, 92; spammy,
	0. spammytokens: hammytokens:0.000-+--XDebbugsCc,
	0.000-+--X-Debbugs-Cc, 0.000-+--trixie, 0.000-+--H*u:Evolution,
	0.000-+--H*F:D*adam-barratt.org.uk
Return-path: <[email protected]>
Received: from adsbarratt.vs.mythic-beasts.com ([2a00:1098:86:f9::1]:60038)
	by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
	(Exim 4.96)
	(envelope-from <[email protected]>)
	id 1vKNHY-001xc2-01
	for [email protected];
	Sat, 15 Nov 2025 20:54:04 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;
	d=adam-barratt.org.uk; s=ab20190809; h=MIME-Version:Content-Transfer-Encoding
	:Content-Type:References:In-Reply-To:Date:To:From:Subject:Message-ID:Sender:
	Reply-To:Cc:Content-ID:Content-Description:Resent-Date:Resent-From:
	Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:
	List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive;
	bh=7qcsnnMBC9KRy3le67Gad7hSWgcLua7A/UJUXuJyBxA=; b=o9Ywotjq4RfIZ5n44aAx1uIQUW
	DPunQXT66PYu/NTA+H8WGiUjlMumDSPyz2sATcfLaBSQPSrf+N7vNK3t/fKbA6GK6sd4tABtcnh48
	CqHOCgCzhBlKVNh4TaSMKTt+Q1lkLVfbRkw7AtnERym3KRkSb9qNXxlCMGzgHMOvg1QzUw89SM3Fj
	j4CDrHUEKqtVjVuEwgxt9Z4YKuAIDEXFxwgCQB77C9C8x42dDmyVxGG6JzLzly2vBT1r1safy13u6
	g4fyrcSUqQ/TKWk9eznpekjHwrEw4V3FY1aMU5c4maVccRYXV0Ev6A6TSiaHsRl9EjrIZlGXHa0lP
	Lpex9P8g==;
Received: from bb.adam-barratt.org.uk ([188.64.38.69]:55998 helo=darzee)
	by adsbarratt.vs.mythic-beasts.com with esmtps (TLS1.3:ECDHE_SECP256R1__ECDSA_SECP256R1_SHA256__AES_256_GCM:256)
	(Exim 4.96 #2 (Debian))
	(envelope-from <[email protected]>)
	id 1vKNHP-000K0X-2Q;
	Sat, 15 Nov 2025 20:53:55 +0000
Received: from localhost ([::1])
	by darzee with esmtp (Exim 4.96)
	(envelope-from <[email protected]>)
	id 1vKNHP-0007yC-0i;
	Sat, 15 Nov 2025 20:53:55 +0000
Message-ID: <0c1b6fb11476d156204de9419a17421ac8c02278.camel@adam-barratt.org.uk>
Subject: Re: Bug#1120749: upgrade-reports: mxrepo.com/mx/repo trixie/main
 amd64 ddm-mx all 25.11.01 is not (yet) available (404  Not Found
From: "Adam D. Barratt" <[email protected]>
To: CAlbrecht <[email protected]>, [email protected]
Date: Sat, 15 Nov 2025 20:53:55 +0000
In-Reply-To: <176323676391.6523.1437209938769053029.reportbug@localhost>
References: <176323676391.6523.1437209938769053029.reportbug@localhost>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.46.4-2 
MIME-Version: 1.0
X-ADSB-Scan-Signature: d919dff3d466f03f7835fbf92b66793d

mxrepo.com is not in any way associated with the Debian project, and we
can do nothing about whether anything is or is not available from it.

Closing this report, as there's nothing actionable.

Regards,

Adam

On Sat, 2025-11-15 at 20:59 +0100, CAlbrecht wrote:
> Package: upgrade-reports
> Severity: important
> X-Debbugs-Cc: [email protected]
>=20
> (Please provide enough information to help the Debian
> maintainers evaluate the report efficiently - e.g., by filling
> in the sections below.)
>=20
> My previous release is: <codename or version from which you are
> upgrading>
> I am upgrading to: <codename or version of the release you are
> upgrading to>
> Archive date: <Timestamp, available as project/trace/ftp-
> master.debian.org
> =C2=A0=C2=A0=C2=A0=C2=A0 on your mirror or .disk/info on your CD/DVD set>
> Upgrade date: <Date and time of the upgrade>
> uname -a before upgrade: <The result of running uname -a on a shell
> prompt>
> uname -a after upgrade: <The result of running uname -a on a shell
> prompt>
> Method: <How did you upgrade?=C2=A0 Which program did you use?>
>=20
> Contents of /etc/apt/sources.list:
>=20
>=20
> - Were there any non-Debian packages installed before the upgrade?=C2=A0
> If
> =C2=A0 so, what were they?
>=20
> - Was the system pre-update a 'pure' system only containing packages
> =C2=A0 from the previous release? If not, which packages were not from
> that
> =C2=A0 release?
>=20
> - Did any packages fail to upgrade?
>=20
> - Were there any problems with the system after upgrading?
>=20
>=20
> Further Comments/Problems:
>=20
>=20
> Please attach the output of "COLUMNS=3D200 dpkg -l" (or "env COLUMNS
> ...",
> depending on your shell) from before and after the upgrade so that we
> know what packages were installed on your system.
>=20
>=20
------------=_1763240223-469654-0--