public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Thomas Lamprecht <t.lamprecht@proxmox.com>
Subject: Re: [pve-devel] applied: [PATCH proxmox-widget-toolkit 1/1] apt: drop ChangeLogUrl
Date: Tue, 14 Nov 2023 08:04:30 +0100	[thread overview]
Message-ID: <1699945124.to5foxnfgj.astroid@yuna.none> (raw)
In-Reply-To: <bd223d1a-1b86-46d6-b76a-836f70a2c79e@proxmox.com>

On November 13, 2023 6:18 pm, Thomas Lamprecht wrote:
> Am 04/07/2023 um 11:45 schrieb Fabian Grünbichler:
>> it's not returned anymore by the corresponding backends, since fetching
>> changelogs is now fully delegated to `apt`.
>> 
>> Signed-off-by: Fabian Grünbichler <f.gruenbichler@proxmox.com>
>> ---
>> 
>> Notes:
>>     could benefit from a Breaks on old versions of pve-manager/pmg-api ,
>>     but not strictly required, it will simply allow attempting to fetch
>>     changelogs for packages where the backend already said there is none
>> 
>>  src/node/APT.js | 8 ++++----
>>  1 file changed, 4 insertions(+), 4 deletions(-)
>> 
>>
> 
> applied, thanks!
> 
> Not directly related, but I get 404 not found for all Debian origin updates that
> are currently pending on a Proxmox VE 8 VM of mine (e.g., for ffmpeg)

yes, this is an (old) known issue also reported on the Debian side since
ages - the security repo doesn't get the changelogs published like the
other ones, only when packages are folded into the next point release
are they available via apt. sometimes it manages to pick it up locally
(from /usr/share/doc/$package/changelog.Debian.XX) *after* the upgrade,
but I haven't yet figured out what makes it do that only sometimes.




  reply	other threads:[~2023-11-14  7:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  9:45 [pve-devel] [PATCH pve-manager/pmg-api/proxmox-backup/pwt 0/4] APT changelog switch-over Fabian Grünbichler
2023-07-04  9:45 ` [pve-devel] [PATCH pmg-api 1/1] apt: use `apt changelog` for changelog fetching Fabian Grünbichler
2023-07-04  9:45 ` [pve-devel] [PATCH proxmox-backup " Fabian Grünbichler
2023-07-04  9:45 ` [pve-devel] [PATCH proxmox-widget-toolkit 1/1] apt: drop ChangeLogUrl Fabian Grünbichler
2023-11-13 17:18   ` [pve-devel] applied: " Thomas Lamprecht
2023-11-14  7:04     ` Fabian Grünbichler [this message]
2023-07-04  9:45 ` [pve-devel] [PATCH manager 1/1] apt: use `apt changelog` for changelog fetching Fabian Grünbichler
2023-11-14  8:30 ` [pve-devel] applied-series: [PATCH pve-manager/pmg-api/proxmox-backup/pwt 0/4] APT changelog switch-over Thomas Lamprecht

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1699945124.to5foxnfgj.astroid@yuna.none \
    --to=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.lamprecht@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal