Bug#887425: marked as done (upgrade-reports: fails in keys in trusted.gpg)

"Debian Bug Tracking System" <[email protected]> Thu, 24 Jul 2025 00:43:02 +0000
Newsgroups gmane.linux.debian.user.testing
Message-ID <[email protected]>
This is a multi-part message in MIME format...

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

Your message dated Thu, 24 Jul 2025 02:41:52 +0200
with message-id <[email protected]>
and subject line Re: Bug#887425: upgrade-reports: fails in keys in trusted.=
gpg
has caused the Debian Bug report #887425,
regarding upgrade-reports: fails in keys in trusted.gpg
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
887425: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D887425
Debian Bug Tracking System
Contact [email protected] with problems

------------=_1753317782-1548797-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at submit) by bugs.debian.org; 16 Jan 2018 11:44:02 +0000
X-Spam-Checker-Version: SpamAssassin 3.4.1-bugs.debian.org_2005_01_02
	(2015-04-28) on buxtehude.debian.org
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=4.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	FOURLA,FREEMAIL_FROM,HAS_PACKAGE,HELO_MISC_IP,NML_ADSP_CUSTOM_MED,RCVD_IN_PBL,
	RCVD_IN_SBLXBL,RCVD_IN_SBLXBL_CBL,RDNS_NONE,SPF_SOFTFAIL,TXREP,
	XMAILER_REPORTBUG,X_DEBBUGS_CC autolearn=ham autolearn_force=no
	version=3.4.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 23; hammy, 146; neutral, 38; spammy,
	1. spammytokens:0.953-+--H*r:bugs.debian.org
	hammytokens:0.000-+--H*M:reportbug, 0.000-+--H*MI:reportbug,
	0.000-+--H*x:reportbug, 0.000-+--H*UA:reportbug, 0.000-+--inrelease
Return-path: <[email protected]>
Received: from [188.170.192.234] (helo=[127.0.1.1])
	by buxtehude.debian.org with esmtp (Exim 4.89)
	(envelope-from <[email protected]>)
	id 1ebPes-0001EK-58
	for [email protected]; Tue, 16 Jan 2018 11:44:02 +0000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Stanislav <[email protected]>
To: Debian Bug Tracking System <[email protected]>
Subject: upgrade-reports: fails in keys in trusted.gpg
Message-ID: <151610304012.9171.15518829966857929911.reportbug@stas-debian>
X-Mailer: reportbug 7.1.8
Date: Tue, 16 Jan 2018 14:44:00 +0300
X-Debbugs-Cc: [email protected]
Delivered-To: [email protected]

Package: upgrade-reports
Severity: important

Dear Maintainer,

After upgrade my system from Stretch to Buster I always see this messages:
W: http://security.debian.org/dists/buster/updates/InRelease: The key(s) in the
keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported
filetype.
W: http://deb.debian.org/debian/dists/buster/InRelease: The key(s) in the
keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported
filetype.
W: http://deb.debian.org/debian/dists/buster-updates/InRelease: The key(s) in
the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported
filetype.
W: http://packages.microsoft.com/repos/vscode/dists/stable/InRelease: The
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an
unsupported filetype.

MOreover, now I am unable to upgrade my system from Synaptic or Applications
but looks like updating from the terminal works relatively well.


I am really sorry if I send it to the wrong address.





-- System Information:
Debian Release: buster/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 4.14.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8), LANGUAGE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

------------=_1753317782-1548797-0
Content-Type: message/rfc822
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Received: (at 887425-done) by bugs.debian.org; 24 Jul 2025 00:41:56 +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=-108.6 required=4.0 tests=BAYES_00,DKIMWL_WL_HIGH,
	DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FROMDEVELOPER,
	HAS_BUG_NUMBER,SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY,
	USER_IN_DKIM_WELCOMELIST autolearn=ham autolearn_force=no
	version=4.0.1-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 18; hammy, 150; neutral, 37; spammy,
	0. spammytokens:
	hammytokens:0.000-+--Hx-spam-relays-external:sk:stravin,
	0.000-+--H*RT:sk:stravin, 0.000-+--Hx-spam-relays-external:311,
	0.000-+--H*RT:311, 0.000-+--H*RT:108
Return-path: <[email protected]>
Received: from stravinsky.debian.org ([2001:41b8:202:deb::311:108]:34542)
	from C=NA,ST=NA,L=Ankh Morpork,O=Debian SMTP,OU=Debian SMTP CA,CN=stravinsky.debian.org,[email protected] (verified)
	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 1uek1z-006UmP-2y
	for [email protected];
	Thu, 24 Jul 2025 00:41:55 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=debian.org;
	s=smtpauto.stravinsky; h=X-Debian-User:In-Reply-To:Content-Type:MIME-Version:
	References:Message-ID:Subject:To:From:Date:Reply-To:Cc:
	Content-Transfer-Encoding:Content-ID:Content-Description;
	bh=/C/4CJ6MNpD3zeNbP7CY4wAbVH8Iooh/zxbdzDYOrJQ=; b=XFyWMDOgQQW4E2oyB6KiNaldaa
	wKLn7jPqwc9dFdkBtVarViHPVNjFB5M3r7bXHS8nBfAx3IzUWqkLrJ4OltazvjSzLTMFQgx0otmsY
	mS2WLcRe9UNmee8Ia1fihnbvZxQJpGy9B6bC0hj+EL/aHuWQuql4A5KeVyj4n8OiiI0RVs9fdn9uo
	DacvBKeSbuiLV0th8f3dp74Hc4su8znKJniASqdbUnSwQrHMA+zP4TsErE7fsU+xQxMakNscc+eR9
	EXRbAoHJtCDu7v8cGsvB6kr+B0obhQ02vDxWjldQttkYetuBi3RVv8Ym2I0a5mTPkcn5CxQWhHrca
	7nc01Y+Q==;
Received: from authenticated user
	by stravinsky.debian.org with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256)
	(Exim 4.94.2)
	(envelope-from <[email protected]>)
	id 1uek1y-008xjc-2V; Thu, 24 Jul 2025 00:41:54 +0000
Date: Thu, 24 Jul 2025 02:41:52 +0200
From: Chris Hofstaedtler <[email protected]>
To: Stanislav <[email protected]>, [email protected]
Subject: Re: Bug#887425: upgrade-reports: fails in keys in trusted.gpg
Message-ID: <[email protected]>
References: <151610304012.9171.15518829966857929911.reportbug@stas-debian>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <151610304012.9171.15518829966857929911.reportbug@stas-debian>
X-Debian-User: zeha

On Tue, Jan 16, 2018 at 02:44:00PM +0300, Stanislav wrote:
> Package: upgrade-reports
> Severity: important
> 
> Dear Maintainer,
> 
> After upgrade my system from Stretch to Buster I always see this messages:
> W: http://security.debian.org/dists/buster/updates/InRelease: The key(s) in the
> keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported
> filetype.
> W: http://deb.debian.org/debian/dists/buster/InRelease: The key(s) in the
> keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported
> filetype.
> W: http://deb.debian.org/debian/dists/buster-updates/InRelease: The key(s) in
> the keyring /etc/apt/trusted.gpg are ignored as the file has an unsupported
> filetype.
> W: http://packages.microsoft.com/repos/vscode/dists/stable/InRelease: The
> key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file has an
> unsupported filetype.
> 
> MOreover, now I am unable to upgrade my system from Synaptic or Applications
> but looks like updating from the terminal works relatively well.

Sorry for the very late reply. It should be possible to recover from 
this by deleting /etc/apt/trusted.gpg, and if necessary, reinstall 
the vscode package.

Apart from that I'm not sure we can do something on the distribution 
side about this problem.

Chris
------------=_1753317782-1548797-0--