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)
Your message dated Sat, 15 Nov 2025 20:53:55 +0000
with message-id <0c1b6fb11476d156204de9419a17421ac8c02278.camel@adam-barratt.org.uk>
and subject line 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
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 owner@bugs.debian.org
immediately.)
--
1120749: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120749
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: upgrade-reports
Severity: important
X-Debbugs-Cc: christoph.albrecht@jrs.net
(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.
--- End Message ---
--- Begin Message ---
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: christoph.albrecht@jrs.net
>
> (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.
>
>
--- End Message ---
Reply to: