[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1057893: marked as done (upgrade-reports: Discover will not update because of broken packages)

Your message dated Sun, 10 Dec 2023 17:42:51 +0100
with message-id <02125223-cdcd-4f25-ae9d-ad604bb8b1f0@debian.org>
and subject line Re: Bug#1057893: upgrade-reports: Discover will not update because of broken packages
has caused the Debian Bug report #1057893,
regarding upgrade-reports: Discover will not update because of broken packages
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.)


-- 
1057893: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057893
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: upgrade-reports
Severity: normal
X-Debbugs-Cc: michelbinette1956@gmail.com

(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.

Contents of bug report :

<html>Package download failed:<br/><br/>E: http://deb.debian.org/debian
bookworm/main amd64 linux-image-6.1.0-14-rt-amd64 amd64 6.1.64-1 is not (yet)
available (403  Access denied - broken package [IP: 199.232.30.132 80])
E: http://deb.debian.org/debian bookworm/main amd64 linux-image-rt-amd64 amd64
6.1.64-1 is not (yet) available (403  Access denied - broken package [IP:
199.232.30.132 80])
</html>

--- End Message ---
--- Begin Message --- 
Hi,

Thanks for your report.

On 10-12-2023 12:41, Michel wrote:

<html>Package download failed:<br/><br/>E: http://deb.debian.org/debian
bookworm/main amd64 linux-image-6.1.0-14-rt-amd64 amd64 6.1.64-1 is not (yet)
available (403  Access denied - broken package [IP: 199.232.30.132 80])
E: http://deb.debian.org/debian bookworm/main amd64 linux-image-rt-amd64 amd64
6.1.64-1 is not (yet) available (403  Access denied - broken package [IP:
199.232.30.132 80])
</html>
This is on purpose. Our related announcement: https://lists.debian.org/debian-announce/2023/msg00005.html 

Paul

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
Reply to: