On 8/14/21, The Wanderer wrote:
> On 2021-08-14 at 19:06, Greg Wooledge wrote:
>
>> On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote:
>>
>>> I had enough trouble with this at the last Debian release,
>>
>> ... but not this time, right?
>
> Yes, this time; in fact...
>
>>> For anyone wh
The Wanderer wrote:
...
> I had enough trouble with this at the last Debian release, and came
> close enough to having trouble with it again this time, that I want to
> make sure the solution is available and findable for anyone else who may
> need it.
...
considering i use only testing in my ap
On Sun, Aug 15, 2021 at 04:40:31PM +0300, ellanios82 wrote:
>
> - bewildered , am getting stuff like this :
>
>
> GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY F942E0D4E1C726CD
>
- bewildered , am getting stuff like this :
GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY F942E0D4E1C726CD
.
what to try please ??
thanks
.
On 8/15/21 4:08 AM, Greg Wooledge wrote:
Why not simply "apt update"?
: i have myself muddled : am getting "NO_PUBKEY"
- what to try, please ?
thank you
regards
.
On Sat, 14 Aug 2021 20:02:51 -0400
The Wanderer wrote:
Hello The,
>As do I. It may be possible that this is what makes the difference.
I'm almost certain that is the root of it.
I recall having to do this at the previous Debian release. I forgot
that I'm now using a new machine built after t
On 2021-08-14 9:08 p.m., Greg Wooledge wrote:
> On Sat, Aug 14, 2021 at 08:52:19PM -0400, Polyna-Maude Racicot-Summerside
> wrote:
>> I got a series of line saying N and one saying E:
>>
>> N: Repository 'http://security.debian.org buster/updates InRelease'
>> changed its 'Suite' value from 'st
On Sat, Aug 14, 2021 at 08:52:19PM -0400, Polyna-Maude Racicot-Summerside wrote:
> I got a series of line saying N and one saying E:
>
> N: Repository 'http://security.debian.org buster/updates InRelease'
> changed its 'Suite' value from 'stable' to 'oldstable'
> N: Repository 'http://security.de
On 2021-08-14 7:45 p.m., The Wanderer wrote:
> On 2021-08-14 at 19:41, Greg Wooledge wrote:
>
>> On Sat, Aug 14, 2021 at 07:26:44PM -0400, The Wanderer wrote:
>
>>> The warnings I'd be OK with; I might even be OK with the errors,
>>> except for the fact that they point not to anything with usef
On 2021-08-14 7:06 p.m., Greg Wooledge wrote:
> On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote:
>> I had enough trouble with this at the last Debian release,
>
> ... but not this time, right?
>
>> For anyone who uses 'apt-get update' - and, I suspect, any other tool
>> than 'apt'
On 15-08-2021 10:02, The Wanderer wrote:
> On 2021-08-14 at 19:49, Brad Rogers wrote:
>
>> On Sat, 14 Aug 2021 19:28:32 -0400 Greg Wooledge
>> wrote:
>>
>> Hello Greg,
>>
>>> It will be interesting to see if anyone else reports the same
>>> problem you're seeing.
>>
>> I experienced it here.
>>
>
On 2021-08-14 at 19:49, Brad Rogers wrote:
> On Sat, 14 Aug 2021 19:28:32 -0400 Greg Wooledge
> wrote:
>
> Hello Greg,
>
>> It will be interesting to see if anyone else reports the same
>> problem you're seeing.
>
> I experienced it here.
>
> I usually use Synaptic to perform updates. Synapt
On Sat, 14 Aug 2021 19:28:32 -0400
Greg Wooledge wrote:
Hello Greg,
>It will be interesting to see if anyone else reports the same problem
>you're seeing.
I experienced it here.
I usually use Synaptic to perform updates. Synaptic put up the warning
message about the codename change, but I cou
On 2021-08-14 at 19:41, Greg Wooledge wrote:
> On Sat, Aug 14, 2021 at 07:26:44PM -0400, The Wanderer wrote:
>> The warnings I'd be OK with; I might even be OK with the errors,
>> except for the fact that they point not to anything with useful
>> information but to a place which doesn't actually
On Sat, Aug 14, 2021 at 07:26:44PM -0400, The Wanderer wrote:
> See bug #879786, and the various bugs that have been merged into it
> (listed near the very bottom, IIRC).
Man, some people have the most *bizarre* setups. And then when someone
points it out, they act all confused. :-/
Most of the
On Sat, Aug 14, 2021 at 07:12:30PM -0400, The Wanderer wrote:
> Maybe somehow I'm running an older apt-get version than what has the
> fix(es)? But as far as I know that's shipped in the 'apt' package, and I
> have that at version 2.2.4, which is what's currently in both stable and
> testing (unsur
On 2021-08-14 at 19:15, Greg Wooledge wrote:
> On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote:
>
>> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed
>> > its 'Codename' value from 'buster' to 'bullseye'
>> > N: This must be accepted explicitly before update
On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote:
> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed
> > its 'Codename' value from 'buster' to 'bullseye'
> > N: This must be accepted explicitly before updates for this repository can
> > be applied. See apt-se
On 2021-08-14 at 19:06, Greg Wooledge wrote:
> On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote:
>
>> I had enough trouble with this at the last Debian release,
>
> ... but not this time, right?
Yes, this time; in fact...
>> For anyone who uses 'apt-get update' - and, I suspect, an
On Sat, Aug 14, 2021 at 06:26:07PM -0400, The Wanderer wrote:
> I had enough trouble with this at the last Debian release,
... but not this time, right?
> For anyone who uses 'apt-get update' - and, I suspect, any other tool
> than 'apt' itself - to update the list of available packages from the
20 matches
Mail list logo
