'sudo apt-get update' stall/error

[Emanuel Berg]

$ sudo apt-get update

... ?

Nothing happens, when I do C-c C-c it says on stderr:

  Got SIGINT, quitting.
  Traceback (most recent call last):
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 126, in 

  address = get_proxy_host_port_from_avahi()
File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 79, in 
get_proxy_host_port_from_avahi
  for line in p.stdout:
  KeyboardInterrupt

Ideas?

-- 
underground experts united
https://dataswamp.org/~incal

Re: 'sudo apt-get update' stall/error

[Reco]

Hi.

On Mon, Sep 06, 2021 at 01:43:03AM +0200, Emanuel Berg wrote:
> $ sudo apt-get update
...
>   address = get_proxy_host_port_from_avahi()
> File "/usr/share/squid-deb-proxy-client/apt-avahi-discover", line 79, in 
> get_proxy_host_port_from_avahi
...
> 
> Ideas?

apt purge squid-deb-proxy-client, for starters.

If you're using Squid as a proxy - just set the proxy in
/etc/apt/apt.conf, like this:

Acquire::http::Proxy "http://:3148";

If not - no further action is required.

Reco

Re: PSA: 'apt-get update' new-Debian-release error fix

[Cindy Sue Causey]

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 who uses 'apt-get update' - and, I suspect, any other tool
>>> than 'apt' itself - to update the list of available packages from the
>>> new release, you're at least moderately likely to see the update attempt
>>> fail with error messages like the following:
>>>
>>> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease'
>>> > changed its 'Codename' value from 'buster' to 'bullseye'
>>
>> You copied this from the NewInBuster wiki most likely.
>
> ...nope, I copied it from a terminal on my computer, where it had just
> been output on my initial 'apt-get update' attempt.
>
>> That's where I put it, when I ran into this issue two years ago, and
>> documented it there.  It's even the same mirror that I use (which is
>> no longer the default, hence it standing out).
>>
>> The issue did not happen this time around.  Instead of getting an
>> "E:" line (error), you only get a bunch of N: (warning) lines.
>>
>> You're trying to solve a problem that doesn't actually exist any
>> more.
>
> I would love for that to have been the case, but my experience does not
> reflect it being so.
>
> 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 (unsurprising given that they should currently be nearly
> identical).


Stuff's not totally caught up or something. I've encountered the
following a couple of times. The latest was while playing along with a
recent Debian-User Docker thread:

https://packages.debian.org/search?keywords=docker

That packages page says buster is stable and bullseye is still
testing. That's possibly (likely?) not the only place still showing
similar, too.

Yesterday I debootstrap'ed in anticipation of new and not so stable.
Only a couple font packages failed as no longer available, and the
rest were already hoarded locally here. My previous experience had
been that a LOT of packages are not available because Developers
haven't brought them up to speed. Examples there would be something
like GIMP and Inkscape.

This morning there were a lot of upgrades and incidental deletions
that were more as expected. Things are slowly rolling along and
catching up to speed, I guess. :)

OR not..

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

Re: debian11 early - apt-get update - At least one invalid signature [OK NOW] was encountered

[jeremy ardley]

On 16/08/2021 7:19 am, raf wrote:


It's working now on the original VM. Someone else reported
that keys have finally made it to a German mirror, solving
a similar problem for them. I guess I was having the same
A problem with the Australian mirror. But maybe that's just
a guess. The keys aren't actually new. But it sounds like
something to do with something taking a while to propagate
to mirrors.

cheers,
raf


I did speed checks and for me the Singapore mirror was a lot faster than 
Australian ones including ones in my city Perth.


I think there is some server speed selection in apt? So you may not be 
using the servers you think you are using.


Jeremy

Re: debian11 early - apt-get update - At least one invalid signature [OK NOW] was encountered

[raf]

On Sun, Aug 15, 2021 at 06:47:34PM +1000, raf  wrote:

> On Sun, Aug 15, 2021 at 08:24:13AM +0200, john doe  
> wrote:
> 
> > The below assumes that 'sources.list' is set only for bullseye
> > 
> > Some hints more than an answer:
> > - Try to remove the gpg keys in '/etc/apt' directory.
> > - Try to remove the Debian apt-keyring pkg ('$ apt-get --autoremove
> > purge  > 
> > $ apt-get update && apt-get full-upgrade
> > 
> > P.S.
> > 
> > I would first try the first step and see how it goes
> > 
> > --
> > John Doe

It's working now on the original VM. Someone else reported
that keys have finally made it to a German mirror, solving
a similar problem for them. I guess I was having the same
A problem with the Australian mirror. But maybe that's just
a guess. The keys aren't actually new. But it sounds like
something to do with something taking a while to propagate
to mirrors.

cheers,
raf

Re: PSA: 'apt-get update' new-Debian-release error fix

[songbird]

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 apt sources list and do not
reference bullseye or bookworm directly this is precisely the reason
why i use testing and follow it.  i don't care about specific 
version names.  having to figure this out is a PITA.

  definitely a BUG IMO.  yet another place where security has
made things worse for people who don't need it.

  i don't know if apt has been fixed or not to honor the
don't remove packages from the cache flag i have set, but the
last time i ran it ages ago it cleared things out i didn't 
want it to remove so i won't run it again.  i always use
apt-get.


  songbird

Re: PSA: 'apt-get update' new-Debian-release error fix

[Greg Wooledge]

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
> 
> 
> .
> 
>  what to try please ??

An MX Linux support forum, perhaps?  This isn't one.

Re: PSA: 'apt-get update' new-Debian-release error fix

[ellanios82]

 - 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

.

Re: PSA: 'apt-get update' new-Debian-release error fix

[ellanios82]

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

.

Re: debian11 early - apt-get update - At least one invalid signature was encountered

[raf]

On Sun, Aug 15, 2021 at 08:24:13AM +0200, john doe  
wrote:

> The below assumes that 'sources.list' is set only for bullseye
> 
> Some hints more than an answer:
> - Try to remove the gpg keys in '/etc/apt' directory.
> - Try to remove the Debian apt-keyring pkg ('$ apt-get --autoremove
> purge  
> $ apt-get update && apt-get full-upgrade
> 
> P.S.
> 
> I would first try the first step and see how it goes
> 
> --
> John Doe

Thanks, but removing keys from /etc/apt/trusted.gpg.d
didn't help. There is no apt-keyring package. And I
couldn't bring myself to uninstall the
debian-archive-keyring package because I assumed that
would make it impossible to ever install anything ever
again. There was an old debian-keyring package that I
removed. But nothing helped.

Never mind. On another VM with the same sized disk, an
upgrade of a fresh debian-10 install got past that
point happily, but then ran out of disk when it got to
the kernel. So it probably wouldn't have worked anyway
(but 1GB spare should have been enough). Another VM
with double the disk upgraded fine.

And the important VM that matters upgraded fine as
well. So it's OK now.

Although bind9 crashed in a heap and dumped core and
couldn't run, as soon as I got it to DNSSEC-sign all my
zones. I wasn't expecting bind9 to crash immediately on
debian stable!

And it overwrote my carefully crafted and documented
zonefiles. I wasn't expecting that either (having read
all the documentation on the subject).

But that's a discussion for a different mailing list,
unless someone here knows what the crashing is about
(bind9-9.16.15 + DNSSEC = firetrucks and sirens). :-)

I hope I won't have to wait too long for bind9-9.16.19.

cheers,
raf

Re: PSA: 'apt-get update' new-Debian-release error fix

[Brad Rogers]

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 the last release.   So glad
about your reminder.

I would have figured the solution out (I did last time, despite the
cryptic info in the man pages), but you saved me a few moments of mild
panic.

Thank you.

-- 
 Regards  _
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
I'm spending all my money and it's going up my nose
Teenage Depression - Eddie & The Hot Rods


pgpEtJCKK4K6k.pgp
Description: OpenPGP digital signature

Re: debian11 early - apt-get update - At least one invalid signature was encountered

[john doe]

On 8/15/2021 3:46 AM, raf wrote:

Hi,

Firstly, many thanks for debian-11. I've been looking
forward to the newer bind9 and its dnssec-policy
finally making it trivial to implement DNSSEC on a
stable system. Yay!

My problem: A day or two ago, I tried to upgrade to
debian-11 on a little VM on my laptop and I've run into
a problem.

I know it wasn't official yet, but I thought I could
get away with it. And I wanted to have done it once
before upgrading a more important VM. But I would like
to get this VM unbroken as well.

I wasn't as careful as usual with it (I didn't do the
backups mentioned in Release Notes section 4.1.1) but
I'm not sure if that would have helped.

I added the new the bullseye details to
/etc/apt/sources.list but I didn't comment out the
existing buster details at the same time. I think that
might have been my mistake. Then, I did apt update and
got GPG invalid signature errors.

And I still get them when I only have the buster
details in sources.list and when I only have the
bullseye details there. But before, everything
was fine.

With buster only:

   deb http://ftp.au.debian.org/debian/ buster main
   deb-src http://ftp.au.debian.org/debian/ buster main
   deb http://security.debian.org/debian-security buster/updates main
   deb-src http://security.debian.org/debian-security buster/updates main
   deb http://ftp.au.debian.org/debian/ buster-updates main
   deb-src http://ftp.au.debian.org/debian/ buster-updates main

apt update looks like this:

   Err:1 http://security.debian.org/debian-security buster/updates InRelease
 At least one invalid signature was encountered.
   Get:2 http://ftp.au.debian.org/debian buster InRelease [122 kB]
   Get:3 http://ftp.au.debian.org/debian buster-updates InRelease [51.9 kB]
   Err:2 http://ftp.au.debian.org/debian buster InRelease
 At least one invalid signature was encountered.
   Err:3 http://ftp.au.debian.org/debian buster-updates InRelease
 At least one invalid signature was encountered.
   Fetched 174 kB in 0s (452 kB/s)
   Reading package lists... Done
   Building dependency tree
   Reading state information... Done
   2 packages can be upgraded. Run 'apt list --upgradable' to see them.
   W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
http://security.debian.org/debian-security buster/updates InRelease: At least 
one invalid signature was encountered.
   W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
http://ftp.au.debian.org/debian buster InRelease: At least one invalid 
signature was encountered.
   W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 
http://ftp.au.debian.org/debian buster-updates InRelease: At least one invalid 
signature was encountered.
   W: Failed to fetch http://ftp.au.debian.org/debian/dists/buster/InRelease  
At least one invalid signature was encountered.
   W: Failed to fetch 
http://security.debian.org/debian-security/dists/buster/updates/InRelease  At 
least one invalid signature was encountered.
   W: Failed to fetch 
http://ftp.au.debian.org/debian/dists/buster-updates/InRelease  At least one 
invalid signature was encountered.
   W: Some index files failed to download. They have been ignored, or old ones 
used instead.

With bullseye only:

   deb http://ftp.au.debian.org/debian/ bullseye main contrib non-free
   deb-src http://ftp.au.debian.org/debian/ bullseye main contrib non-free
   deb http://security.debian.org/debian-security bullseye-security main 
contrib non-free
   deb-src http://security.debian.org/debian-security bullseye-security main 
contrib non-free
   deb http://ftp.au.debian.org/debian/ bullseye-updates main contrib non-free
   deb-src http://ftp.au.debian.org/debian/ bullseye-updates main contrib 
non-free

apt update looks like:

   Get:1 http://security.debian.org/debian-security bullseye-security InRelease 
[44.1 kB]
   Err:1 http://security.debian.org/debian-security bullseye-security InRelease
 At least one invalid signature was encountered.
   Get:2 http://ftp.au.debian.org/debian bullseye InRelease [113 kB]
   Get:3 http://ftp.au.debian.org/debian bullseye-updates InRelease [40.1 kB]
   Err:2 http://ftp.au.debian.org/debian bullseye InRelease
 At least one invalid signature was encountered.
   Err:3 http://ftp.au.debian.org/debian bullseye-updates InRelease
 At least one invalid signature was encountered.
   Fetched 153 kB in 0s (448 kB/s)
   Reading package lists... Done
   Building dependency tree
   Reading state information... Done
   1416 packages can be upgraded. Run 'apt list --upgradable' to see them.
   W: An error occurred during the signature verification. The repository is 
not updated and the previous index files will be used. GPG error: 

debian11 early - apt-get update - At least one invalid signature was encountered

[raf]

Hi,

Firstly, many thanks for debian-11. I've been looking
forward to the newer bind9 and its dnssec-policy
finally making it trivial to implement DNSSEC on a
stable system. Yay!

My problem: A day or two ago, I tried to upgrade to
debian-11 on a little VM on my laptop and I've run into
a problem.

I know it wasn't official yet, but I thought I could
get away with it. And I wanted to have done it once
before upgrading a more important VM. But I would like
to get this VM unbroken as well.

I wasn't as careful as usual with it (I didn't do the
backups mentioned in Release Notes section 4.1.1) but
I'm not sure if that would have helped.

I added the new the bullseye details to
/etc/apt/sources.list but I didn't comment out the
existing buster details at the same time. I think that
might have been my mistake. Then, I did apt update and
got GPG invalid signature errors.

And I still get them when I only have the buster
details in sources.list and when I only have the
bullseye details there. But before, everything
was fine.

With buster only:

  deb http://ftp.au.debian.org/debian/ buster main
  deb-src http://ftp.au.debian.org/debian/ buster main
  deb http://security.debian.org/debian-security buster/updates main
  deb-src http://security.debian.org/debian-security buster/updates main
  deb http://ftp.au.debian.org/debian/ buster-updates main
  deb-src http://ftp.au.debian.org/debian/ buster-updates main

apt update looks like this:

  Err:1 http://security.debian.org/debian-security buster/updates InRelease
At least one invalid signature was encountered.
  Get:2 http://ftp.au.debian.org/debian buster InRelease [122 kB]
  Get:3 http://ftp.au.debian.org/debian buster-updates InRelease [51.9 kB]
  Err:2 http://ftp.au.debian.org/debian buster InRelease
At least one invalid signature was encountered.
  Err:3 http://ftp.au.debian.org/debian buster-updates InRelease
At least one invalid signature was encountered.
  Fetched 174 kB in 0s (452 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  2 packages can be upgraded. Run 'apt list --upgradable' to see them.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://security.debian.org/debian-security buster/updates InRelease: At least 
one invalid signature was encountered.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://ftp.au.debian.org/debian buster InRelease: At least one invalid 
signature was encountered.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://ftp.au.debian.org/debian buster-updates InRelease: At least one invalid 
signature was encountered.
  W: Failed to fetch http://ftp.au.debian.org/debian/dists/buster/InRelease  At 
least one invalid signature was encountered.
  W: Failed to fetch 
http://security.debian.org/debian-security/dists/buster/updates/InRelease  At 
least one invalid signature was encountered.
  W: Failed to fetch 
http://ftp.au.debian.org/debian/dists/buster-updates/InRelease  At least one 
invalid signature was encountered.
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

With bullseye only:

  deb http://ftp.au.debian.org/debian/ bullseye main contrib non-free
  deb-src http://ftp.au.debian.org/debian/ bullseye main contrib non-free
  deb http://security.debian.org/debian-security bullseye-security main contrib 
non-free
  deb-src http://security.debian.org/debian-security bullseye-security main 
contrib non-free
  deb http://ftp.au.debian.org/debian/ bullseye-updates main contrib non-free
  deb-src http://ftp.au.debian.org/debian/ bullseye-updates main contrib 
non-free

apt update looks like:

  Get:1 http://security.debian.org/debian-security bullseye-security InRelease 
[44.1 kB]
  Err:1 http://security.debian.org/debian-security bullseye-security InRelease
At least one invalid signature was encountered.
  Get:2 http://ftp.au.debian.org/debian bullseye InRelease [113 kB]
  Get:3 http://ftp.au.debian.org/debian bullseye-updates InRelease [40.1 kB]
  Err:2 http://ftp.au.debian.org/debian bullseye InRelease
At least one invalid signature was encountered.
  Err:3 http://ftp.au.debian.org/debian bullseye-updates InRelease
At least one invalid signature was encountered.
  Fetched 153 kB in 0s (448 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  1416 packages can be upgraded. Run 'apt list --upgradable' to see them.
  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://security.debian.org/debian-security bullseye-security InRelease: At 
least one invalid signature was 

Re: PSA: 'apt-get update' new-Debian-release error fix

[Polyna-Maude Racicot-Summerside]

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 'stable' to 'oldstable'
>> N: Repository 'http://security.debian.org stretch/updates InRelease'
>> changed its 'Suite' value from 'oldstable' to 'oldoldstable'
>> E: Repository 'http://deb.debian.org/debian testing InRelease' changed
>> its 'Codename' value from 'bullseye' to 'bookworm'
> 
> Fascinating.
> 
>> Will be fixed in a dirty way (remove the offending non needed repository)
> 
> Why not simply "apt update"?
> 
I did apt update when I finally "catched" that it was apt-get update
that didn't allow interactive questions.

So doing *apt update* fixed it (saying Y helped too).

> Also, um... if you weren't planning to track bookworm-as-testing, you
> really should've removed that testing line before the bullseye release.
> 

That what I said when I talked about dirty way, removing *testing* but
*apt update* worked.
-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Re: PSA: 'apt-get update' new-Debian-release error fix

[Greg Wooledge]

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.debian.org stretch/updates InRelease'
> changed its 'Suite' value from 'oldstable' to 'oldoldstable'
> E: Repository 'http://deb.debian.org/debian testing InRelease' changed
> its 'Codename' value from 'bullseye' to 'bookworm'

Fascinating.

> Will be fixed in a dirty way (remove the offending non needed repository)

Why not simply "apt update"?

Also, um... if you weren't planning to track bookworm-as-testing, you
really should've removed that testing line before the bullseye release.

Re: PSA: 'apt-get update' new-Debian-release error fix

[Polyna-Maude Racicot-Summerside]

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 useful
>>> information but to a place which doesn't actually tell you anything
>>> helpful.
>>
>> Yeah, the DD who replied with "If you run it interactive, you get
>> asked directly" clearly had no idea
> 
> If I remember that exchange correctly, that seems to have been a case of
> confusion about which front-end was being used. If you run 'apt'
> interactively rather than for scripting purposes, I understand that you
> *do* get asked directly; if you run 'apt-get', however, you don't.
> 
Using *apt update* instead of *apt-get update* solved my problem
(without changing my sources.list files).

>> In any case, it sounds like your machines have some unique setup
>> that's triggering the symptoms in cases where other people won't
>> experience them.  For now, I'm going to assume that the problem is
>> unique to you, unless/until someone else reports it.
> 
> I'd be glad of that, but given the number of other people reporting the
> problem in that collection of bug reports, don't expect it to be the
> case; that was part of what led me to report the solution here in the
> form of a PSA, rather than bringing it up in some other way or just not
> mentioning it at all.
> 
>> Also, the fact that people apparently can't manage to find the
>> NewInBuster page that describes the symptom and its workaround (not
>> even with Google?) is sad.
> 
> I didn't even look this time, since I'd had to look so hard last time
> and found nothing anyway. I just ran 'reportbug apt', filtered the list
> of bugs for mention of 'secure', and looked at the first bug report -
> out of, IIRC, three or four - whose title seemed relevant.
> 

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Re: PSA: 'apt-get update' new-Debian-release error fix

[Polyna-Maude Racicot-Summerside]

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' itself - to update the list of available packages from the
>> new release, you're at least moderately likely to see the update attempt
>> fail with error messages like the following:
>>
>>> E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed 
>>> its 'Codename' value from 'buster' to 'bullseye'
> 
> You copied this from the NewInBuster wiki most likely.  That's where I
> put it, when I ran into this issue two years ago, and documented it
> there.  It's even the same mirror that I use (which is no longer the
> default, hence it standing out).
> 
> The issue did not happen this time around.  Instead of getting an "E:"
> line (error), you only get a bunch of N: (warning) lines.
> 
> You're trying to solve a problem that doesn't actually exist any more.
> 

Running Buster and having a the bullseye repository on my system (source
one only).
I kept source package repository for stretch, buster, bullseye and testing.

Seem to be testing changed from bullseye to bookwork that is complaining.

 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.debian.org stretch/updates InRelease'
changed its 'Suite' value from 'oldstable' to 'oldoldstable'
E: Repository 'http://deb.debian.org/debian testing InRelease' changed
its 'Codename' value from 'bullseye' to 'bookworm'
N: This must be accepted explicitly before updates for this repository
can be applied. See apt-secure(8) manpage for details.
N: Repository 'http://ftp.debian.org/debian bullseye InRelease' changed
its 'Version' value from '' to '11.0'
N: Repository 'http://ftp.debian.org/debian bullseye InRelease' changed
its 'Suite' value from 'testing' to 'stable'
N: Repository 'http://ftp.debian.org/debian bullseye-updates InRelease'
changed its 'Version' value from '' to '11-updates'
N: Repository 'http://ftp.debian.org/debian bullseye-updates InRelease'
changed its 'Suite' value from 'testing-updates' to 'stable-updates'
N: Repository 'https://www.deb-multimedia.org buster InRelease' changed
its 'Suite' value from 'stable' to 'oldstable'
N: Repository 'http://ftp.debian.org/debian buster InRelease' changed
its 'Suite' value from 'stable' to 'oldstable'
N: Repository 'http://ftp.debian.org/debian buster-updates InRelease'
changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
N: Repository 'http://ftp.debian.org/debian stretch-updates InRelease'
changed its 'Suite' value from 'oldstable-updates' to 'oldoldstable-updates'
N: Repository 'http://ftp.debian.org/debian stretch Release' changed its
'Suite' value from 'oldstable' to 'oldoldstable'

Will be fixed in a dirty way (remove the offending non needed repository)

-- 
Polyna-Maude R.-Summerside
-Be smart, Be wise, Support opensource development



OpenPGP_signature
Description: OpenPGP digital signature

Re: PSA: 'apt-get update' new-Debian-release error fix

[Weaver]

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.
>>
>> I usually use Synaptic to perform updates.  Synaptic put up the
>> warning message about the codename change, but I could find no way to
>> explicitly accept the changes in Synaptic.  As The Wanderer
>> suggested, I ran 'apt update' from a command line and followed the
>> prompts.
>>
>> I will add that my sources lists refer only to 'testing', and do not
>> use version codenames at all.
> 
> As do I. It may be possible that this is what makes the difference.

I always use distribution and never versioning, but have never
experienced this problem.
Cheers!

Harry

-- 
`Unthinking respect for authority is 
the greatest enemy of truth'.
-- Albert Einstein

Re: PSA: 'apt-get update' new-Debian-release error fix

[The Wanderer]

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.  Synaptic put up the
> warning message about the codename change, but I could find no way to
> explicitly accept the changes in Synaptic.  As The Wanderer
> suggested, I ran 'apt update' from a command line and followed the
> prompts.
> 
> I will add that my sources lists refer only to 'testing', and do not
> use version codenames at all.

As do I. It may be possible that this is what makes the difference.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: PSA: 'apt-get update' new-Debian-release error fix

[Brad Rogers]

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 could find no way to explicitly
accept the changes in Synaptic.  As The Wanderer suggested, I ran 'apt
update' from a command line and followed the prompts.

I will add that my sources lists refer only to 'testing', and do not use
version codenames at all.

-- 
 Regards  _
 / )  "The blindingly obvious is never immediately apparent"
/ _)rad   "Is it only me that has a working delete key?"
But they didn't tell him the first two didn't count
Tin Soldiers - Stiff Little Fingers


pgpRWfEt8GZ6y.pgp
Description: OpenPGP digital signature

Re: PSA: 'apt-get update' new-Debian-release error fix

[The Wanderer]

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 tell you anything
>> helpful.
> 
> Yeah, the DD who replied with "If you run it interactive, you get
> asked directly" clearly had no idea

If I remember that exchange correctly, that seems to have been a case of
confusion about which front-end was being used. If you run 'apt'
interactively rather than for scripting purposes, I understand that you
*do* get asked directly; if you run 'apt-get', however, you don't.

> In any case, it sounds like your machines have some unique setup
> that's triggering the symptoms in cases where other people won't
> experience them.  For now, I'm going to assume that the problem is
> unique to you, unless/until someone else reports it.

I'd be glad of that, but given the number of other people reporting the
problem in that collection of bug reports, don't expect it to be the
case; that was part of what led me to report the solution here in the
form of a PSA, rather than bringing it up in some other way or just not
mentioning it at all.

> Also, the fact that people apparently can't manage to find the
> NewInBuster page that describes the symptom and its workaround (not
> even with Google?) is sad.

I didn't even look this time, since I'd had to look so hard last time
and found nothing anyway. I just ran 'reportbug apt', filtered the list
of bugs for mention of 'secure', and looked at the first bug report -
out of, IIRC, three or four - whose title seemed relevant.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: PSA: 'apt-get update' new-Debian-release error fix

[Greg Wooledge]

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 separate instances in that bug report have something wrong
with them, like trying to use testing/updates for security after the
URL changed, or using Ubuntu repositories, so it's a bit hard to see
what's actually happening.

> 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 tell you anything helpful.

Yeah, the DD who replied with "If you run it interactive, you get asked
directly" clearly had no idea

In any case, it sounds like your machines have some unique setup that's
triggering the symptoms in cases where other people won't experience
them.  For now, I'm going to assume that the problem is unique to you,
unless/until someone else reports it.

Also, the fact that people apparently can't manage to find the NewInBuster
page that describes the symptom and its workaround (not even with Google?)
is sad.

Re: PSA: 'apt-get update' new-Debian-release error fix

[Greg Wooledge]

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 (unsurprising given that they should currently be nearly identical).

apt version 2.2.4 here.  It will be interesting to see if anyone else
reports the same problem you're seeing.  And, I suppose, to see whether I
experience the same problem myself when I do a straight buster-to-bullseye
upgrade with no testing in the middle.

Re: PSA: 'apt-get update' new-Debian-release error fix

[The Wanderer]

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 updates for this repository can 
>> > be applied. See apt-secure(8) manpage for details.
>> 
>> If you used the label 'buster' instead of 'stable' in your sources.list,
>> you may see complaints about a change in the 'Suite' value instead.
> 
> Hmm... after reading your message again, I think we're talking about
> two separate problems that have very similar symptoms.
> 
> I've never actually *heard* of your problem before, nor have I seen it.

See bug #879786, and the various bugs that have been merged into it
(listed near the very bottom, IIRC).

> In all cases, whenever I've had a machine that ran *only* stable
> releases, this symptom has never happened to me.  All
> stable-to-stable release upgrades have gone smoothly for me, at least
> as far as the "apt-get update" step goes.  I'm not sure what you're
> doing differently, or why it's not working properly for you.

Some of the discussion in the bug report seems to imply that this is
only expected to happen if you have a repository which has some aspect
which isn't properly configured as trusted on your system. I'm guessing
that the exact details of how I access the same repositories which would
normally be considered trusted makes them not be so.

> What *I* saw (and put on the wiki), was that a machine which ran
> buster *as testing* (i.e. was upgraded from stretch to testing, prior
> to buster's release) ran into the problem you describe, except that
> it said the suite name changed from "testing" to "stable".

That sounds like the situation I'm in; I typically dist-upgrade against
testing once a day during the weeks after a new release, and then about
once a week after that, till it's time to repeat the cycle with the next
release.

I've been running testing (specified by that name in sources.list)
for... long enough that I don't actually remember when I started; it was
probably over a decade ago.

That said, I *did* somewhat-recently (around the end of June, I think)
install a new machine to the same specifications as the old one - using,
IIRC, the then-release-candidate installer version - and immediately
switch it to target testing, using the same sources.list as on the
previous machine. I never ran this '--allow-releaseinfo-change' on the
new machine, although I had done it on the old; maybe somehow there's a
flag involved other than just the release info itself being different,
which hadn't been set previously on this new machine?

> When I upgraded my buster-to-testing-to-bullseye machine today, I did
> not see this same problem.  I got a bunch of warnings, and I
> *thought* I was seeing the same problem as last time, but it turns
> out I didn't actually have to run "apt update".  The "apt-get update"
> had worked in the first place.

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 tell you anything helpful.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: PSA: 'apt-get update' new-Debian-release error fix

[Greg Wooledge]

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-secure(8) manpage for details.
> 
> If you used the label 'buster' instead of 'stable' in your sources.list,
> you may see complaints about a change in the 'Suite' value instead.

Hmm... after reading your message again, I think we're talking about
two separate problems that have very similar symptoms.

I've never actually *heard* of your problem before, nor have I seen it.

In all cases, whenever I've had a machine that ran *only* stable releases,
this symptom has never happened to me.  All stable-to-stable release
upgrades have gone smoothly for me, at least as far as the "apt-get update"
step goes.  I'm not sure what you're doing differently, or why it's not
working properly for you.

What *I* saw (and put on the wiki), was that a machine which ran buster
*as testing* (i.e. was upgraded from stretch to testing, prior to
buster's release) ran into the problem you describe, except that it
said the suite name changed from "testing" to "stable".

When I upgraded my buster-to-testing-to-bullseye machine today, I did not
see this same problem.  I got a bunch of warnings, and I *thought* I was
seeing the same problem as last time, but it turns out I didn't actually
have to run "apt update".  The "apt-get update" had worked in the first
place.

Re: PSA: 'apt-get update' new-Debian-release error fix

[The Wanderer]

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, any other tool
>> than 'apt' itself - to update the list of available packages from the
>> new release, you're at least moderately likely to see the update attempt
>> fail with error messages like the following:
>> 
>> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed 
>> > its 'Codename' value from 'buster' to 'bullseye'
> 
> You copied this from the NewInBuster wiki most likely.

...nope, I copied it from a terminal on my computer, where it had just
been output on my initial 'apt-get update' attempt.

> That's where I put it, when I ran into this issue two years ago, and
> documented it there.  It's even the same mirror that I use (which is
> no longer the default, hence it standing out).
> 
> The issue did not happen this time around.  Instead of getting an
> "E:" line (error), you only get a bunch of N: (warning) lines.
> 
> You're trying to solve a problem that doesn't actually exist any
> more.

I would love for that to have been the case, but my experience does not
reflect it being so.

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 (unsurprising given that they should currently be nearly identical).

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: PSA: 'apt-get update' new-Debian-release error fix

[Greg Wooledge]

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
> new release, you're at least moderately likely to see the update attempt
> fail with error messages like the following:
> 
> > E: Repository 'http://ftp.us.debian.org/debian stable InRelease' changed 
> > its 'Codename' value from 'buster' to 'bullseye'

You copied this from the NewInBuster wiki most likely.  That's where I
put it, when I ran into this issue two years ago, and documented it
there.  It's even the same mirror that I use (which is no longer the
default, hence it standing out).

The issue did not happen this time around.  Instead of getting an "E:"
line (error), you only get a bunch of N: (warning) lines.

You're trying to solve a problem that doesn't actually exist any more.

PSA: 'apt-get update' new-Debian-release error fix

[The Wanderer]

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.


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
new release, you're at least moderately likely to see the update attempt
fail with error messages like the following:

> 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-secure(8) manpage for details.

If you used the label 'buster' instead of 'stable' in your sources.list,
you may see complaints about a change in the 'Suite' value instead.

The error message directs you to the apt-secure(8) man page. This man
page does document the reason why this error happens (although not in a
very clear or discoverable fashion), but provides no hint about how to
explicitly accept the change and allow the update to proceed.

That is apparently because the fancy new 'apt' front-end will detect
this situation and prompt you to accept the change interactively, but
none of the others necessarily will.


The actual solution will depend on which apt front-end you're using.

For the front-end which is also called 'apt', a simple 'apt update' will
apparently be enough; it will apparently prompt you to accept the change
interactively, and if you do so, will proceed accordingly.

For the 'apt-get' front-end, the necessary solution is to run the
command 'apt-get update --allow-releaseinfo-change'.

For other front-ends (aptitude, synaptic, others?), there are probably
commands which can make it possible to get past this, but I don't know
what any of them are.


There have been bug reports about this misdirecting documentation, and
the lack of any usefully-discoverable pointer to the actual solution,
dating back as far as 2017; the bug has been acknowledged, possible
solutions have been proposed, but nothing has apparently actually made
it into the release as of yet.

-- 
   The Wanderer

The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all
progress depends on the unreasonable man. -- George Bernard Shaw



signature.asc
Description: OpenPGP digital signature

Re: apt-get update release expired

[Raphaël POITEVIN]

Daniel Caillibaud  writes:
> Chez ovh c'est malheureusement assez fréquent (pb de certificat, pb de
> rafraîchissement, etc.),
> j'ai arrêté d'utiliser leur miroir depuis longtemps.

J’aurais pensé que c’était une réplication automatique.

OK je vais changer de miroir.

Merci,
-- 
Raphaël
www.leclavierquibave.fr

Re: apt-get update release expired

[Daniel Caillibaud]

Le 22/06/20 à 13:22, raphael.poite...@gmail.com (Raphaël POITEVIN) a écrit :
> Bonjour,
> 
> Un petit apt-get update && apt-get dist-upgrade de routine :
> 
> E: Release file for
> http://debian.mirrors.ovh.net/debian/dists/buster-updates/InRelease is
> expired (invalid since 3h 7min 14s). Updates for this repository will
> not be applied.
> 
> Avez-vous le même problème ?

Chez ovh c'est malheureusement assez fréquent (pb de certificat, pb de 
rafraîchissement, etc.),
j'ai arrêté d'utiliser leur miroir depuis longtemps.

-- 
Daniel

Accroche toi au terminal, j'enlève le shell…
Nojhan (Geekscottes)

apt-get update release expired

[Raphaël POITEVIN]

Bonjour,

Un petit apt-get update && apt-get dist-upgrade de routine :

E: Release file for
http://debian.mirrors.ovh.net/debian/dists/buster-updates/InRelease is
expired (invalid since 3h 7min 14s). Updates for this repository will
not be applied.

Avez-vous le même problème ?

Cordialement et merci,
-- 
Raphaël
www.leclavierquibave.fr

Re: error while doing apt-get update

[Tapas Mishra]

On Sat, Sep 7, 2019 at 4:45 PM Sven Joachim  wrote:

> So the file looks like this:
>
> ,
> | Origin: Debian
> | Label: Debian-Security
> | Suite: stable
> | Version: 10
> | Codename: buster
> | Date: Fri, 06 Sep 2019 11:51:20 UTC
> | Valid-Until: Fri, 13 Sep 2019 11:51:20 UTC
> | Acquire-By-Hash: yes
> | Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el 
> s390x
> | Components: updates/main updates/contrib updates/non-free
> | Description: Debian 10 - Security Updates
> `
>
> Which is definitely wrong for buster-updates, this is how an InRelease
> file from the security repository starts.
>
> It's hard to tell how this happened (file system corruption perhaps),
> but if you proceed with the update it should be corrected.
> Run "apt-get update --allow-releaseinfo-change" to do so.

Ok thanks for pointing that out apt-get update
--allow-releaseinfo-change did the trick.
But I want to understand what was wrong in previous file and what did
you noticed that
should have been there which was not there in my file.
--
Thanks and Regards
Tapas

Re: error while doing apt-get update

[Sven Joachim]

On 2019-09-07 15:50 +0530, Tapas Mishra wrote:

> On Sat, Sep 7, 2019 at 12:22 AM Sven Joachim  wrote:
>>
>>
>> This sources.list file looks good to me.
>>
>> > What should I  check?
>>
>> There should be a file
>> /var/lib/apt/lists/deb.debian.org_debian_dists_buster-updates_InRelease.
>> If it exists, can you please show its first 15 lines?
>>
> Hi you can see the whole file on this link
> https://pastebin.com/116phYnH

So the file looks like this:

,
| Origin: Debian
| Label: Debian-Security
| Suite: stable
| Version: 10
| Codename: buster
| Date: Fri, 06 Sep 2019 11:51:20 UTC
| Valid-Until: Fri, 13 Sep 2019 11:51:20 UTC
| Acquire-By-Hash: yes
| Architectures: amd64 arm64 armel armhf i386 mips mips64el mipsel ppc64el s390x
| Components: updates/main updates/contrib updates/non-free
| Description: Debian 10 - Security Updates
`

Which is definitely wrong for buster-updates, this is how an InRelease
file from the security repository starts.

It's hard to tell how this happened (file system corruption perhaps),
but if you proceed with the update it should be corrected.
Run "apt-get update --allow-releaseinfo-change" to do so.

Cheers,
   Sven

Re: error while doing apt-get update

[Eduardo M KALINOWSKI]

On 06/09/2019 13:29, Tapas Mishra wrote:
> Hi,
> I am getting some error while doing
> debian@debian:~$ sudo apt-get update
> [sudo] password for debian:
> Get:1 http://security-cdn.debian.org/debian-security buster/updates
> InRelease [39.1 kB]
> Hit:2 http://cdn-fastly.deb.debian.org/debian buster InRelease
> Get:3 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease [49.3 
> kB]
> Reading package lists... Done
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
> InRelease' changed its 'Label' value from 'Debian-Security' to
> 'Debian'
> N: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
> InRelease' changed its 'Version' value from '10' to ''
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
> InRelease' changed its 'Suite' value from 'stable' to 'stable-updates'
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
> InRelease' changed its 'Codename' value from 'buster' to
> 'buster-updates'
> N: This must be accepted explicitly before updates for this repository
> can be applied. See apt-secure(8) manpage for details.

This is a known issue when updating for the fist time, see
https://unix.stackexchange.com/questions/528751/cannot-update-apt-list-repository-no-longer-has-a-release-file


-- 
BOFH excuse #93:

Feature not yet implemented

Eduardo M KALINOWSKI
edua...@kalinowski.com.br

Re: error while doing apt-get update

[Tapas Mishra]

On Sat, Sep 7, 2019 at 12:22 AM Sven Joachim  wrote:
>
>
> This sources.list file looks good to me.
>
> > What should I  check?
>
> There should be a file
> /var/lib/apt/lists/deb.debian.org_debian_dists_buster-updates_InRelease.
> If it exists, can you please show its first 15 lines?
>
Hi you can see the whole file on this link
https://pastebin.com/116phYnH
---
Thanks & Regards
Tapas

Re: error while doing apt-get update

[Sven Joachim]

On 2019-09-06 21:59 +0530, Tapas Mishra wrote:

> I am getting some error while doing
> debian@debian:~$ sudo apt-get update
> [sudo] password for debian:
> Get:1 http://security-cdn.debian.org/debian-security buster/updates
> InRelease [39.1 kB]
> Hit:2 http://cdn-fastly.deb.debian.org/debian buster InRelease
> Get:3 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease [49.3 
> kB]
> Reading package lists... Done
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
> InRelease' changed its 'Label' value from 'Debian-Security' to
> 'Debian'
> N: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
> InRelease' changed its 'Version' value from '10' to ''
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
> InRelease' changed its 'Suite' value from 'stable' to 'stable-updates'
> E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
> InRelease' changed its 'Codename' value from 'buster' to
> 'buster-updates'
> N: This must be accepted explicitly before updates for this repository
> can be applied. See apt-secure(8) manpage for details.

This is rather strange.  The new values for these fields in the
buster-updates repository look correct, I wonder how the old ones got
there.

> debian@debian:/etc/apt$ cat sources.list
> #
>
> # deb cdrom:[Official Debian GNU/Linux Live 10.0.0 gnome
> 2019-07-06T10:51]/ buster main
>
> #deb cdrom:[Official Debian GNU/Linux Live 10.0.0 gnome
> 2019-07-06T10:51]/ buster main
>
> deb http://deb.debian.org/debian/ buster main
> deb-src http://deb.debian.org/debian/ buster main
>
> deb http://security.debian.org/debian-security buster/updates main
> deb-src http://security.debian.org/debian-security buster/updates main
>
> # buster-updates, previously known as 'volatile'
> deb http://deb.debian.org/debian/ buster-updates main
> deb-src http://deb.debian.org/debian/ buster-updates main
>
> # This system was installed using small removable media
> # (e.g. netinst, live or single CD). The matching "deb cdrom"
> # entries were disabled at the end of the installation process.
> # For information about how to configure apt package sources,
> # see the sources.list(5) manual.

This sources.list file looks good to me.

> What should I  check?

There should be a file
/var/lib/apt/lists/deb.debian.org_debian_dists_buster-updates_InRelease.
If it exists, can you please show its first 15 lines?

Cheers,
   Sven

error while doing apt-get update

[Tapas Mishra]

Hi,
I am getting some error while doing
debian@debian:~$ sudo apt-get update
[sudo] password for debian:
Get:1 http://security-cdn.debian.org/debian-security buster/updates
InRelease [39.1 kB]
Hit:2 http://cdn-fastly.deb.debian.org/debian buster InRelease
Get:3 http://cdn-fastly.deb.debian.org/debian buster-updates InRelease [49.3 kB]
Reading package lists... Done
E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
InRelease' changed its 'Label' value from 'Debian-Security' to
'Debian'
N: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
InRelease' changed its 'Version' value from '10' to ''
E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
InRelease' changed its 'Suite' value from 'stable' to 'stable-updates'
E: Repository 'http://cdn-fastly.deb.debian.org/debian buster-updates
InRelease' changed its 'Codename' value from 'buster' to
'buster-updates'
N: This must be accepted explicitly before updates for this repository
can be applied. See apt-secure(8) manpage for details.

debian@debian:/etc/apt$ cat sources.list
#

# deb cdrom:[Official Debian GNU/Linux Live 10.0.0 gnome
2019-07-06T10:51]/ buster main

#deb cdrom:[Official Debian GNU/Linux Live 10.0.0 gnome
2019-07-06T10:51]/ buster main

deb http://deb.debian.org/debian/ buster main
deb-src http://deb.debian.org/debian/ buster main

deb http://security.debian.org/debian-security buster/updates main
deb-src http://security.debian.org/debian-security buster/updates main

# buster-updates, previously known as 'volatile'
deb http://deb.debian.org/debian/ buster-updates main
deb-src http://deb.debian.org/debian/ buster-updates main

# This system was installed using small removable media
# (e.g. netinst, live or single CD). The matching "deb cdrom"
# entries were disabled at the end of the installation process.
# For information about how to configure apt package sources,
# see the sources.list(5) manual.

What should I  check?
I am using Debian 10 in a virtualized environment (Vmware 15 workstation)
---
Thanks

Re: Output from apt-get update.

[Greg Wooledge]

On Tue, Jul 02, 2019 at 03:10:06PM -0700, pe...@easthope.ca wrote:
> dalton has dnsmasq.  From distant recollection, name resolution failed when 
> the system was running and dnsmasq was not.  That motivated direct reference 
> to IP addresses.  To the best of my knowledge, an IP address should suffice 
> to 
> identify a server or possibly a cluster of them. 

An entry in /etc/hosts would probably be a better choice.  In the case
of HTTP requests, the hostname needs to be sent inside the request to
identify the correct virtual host.

(Now, maybe that particular mirror isn't on a virtual host, but in
general, most HTTP requests *should* be treated as virtual hosts.  Using a
raw IP address in the URL typically won't get you the right result.)

Re: Output from apt-get update.

[Dan Ritter]

pe...@easthope.ca wrote: 
> 
> The mainboard interface appears as eth0.
> "ip link show" reports eth0 is up.
> "ip addr show" reports an IPv6 address for eth0.  No IPv4 address.
> 
> ping to a neighbour reports 
>   connect: network is unreachable
>   
> Is IPv6 the default now?  Shorewall configuration needs updating?
> 

On a default Debian install, both IPv4 and IPv6 addresses will
be configured if detected: a DHCP request will be sent to obtain
an IPv4 address, and SLAAC will be used to get an IPv6 address.

It's normal for ip addr show eth0 to give you something like:

2: eth0:  mtu 1500 qdisc
pfifo_fast state UP group default qlen 1000
link/ether fc:ab:14:a9:92:db brd ff:ff:ff:ff:ff:ff
inet 10.2.0.2/16 brd 10.2.255.255 scope global eth0
   valid_lft forever preferred_lft forever
inet6 fe80::feaa:14ff:fea9:92db/64 scope link 
   valid_lft forever preferred_lft forever

which shows both IPv4 and IPv6 addresses assigned to eth0.

-dsr-

Correct: Re: Output from apt-get update.

[peter]

From: Francisco M Neto 
Date: Wed, 12 Jun 2019 07:27:28 -0300
> It's also worth checking if there's anything under
> /etc/apt/sources.list.d/

You're right.  If /etc/apt/sources.list.d/mythtv.list is disabled, 
apt-get update doesn't produce obscure complaints.  The complaints 
from apt-get could help by identifying the bad repository.

A D-link card gives a network connection.  The mainboard NIC alone is 
problematic.  ??

So the system working again, more or less.  I'm still wondering about 
IPv4 vs. IPv6 and ip vs. other stuff.

Thanks for the help,  ... P.


-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: Output from apt-get update.

[Matthew Crews]

On 7/2/19 5:18 PM, pe...@easthope.ca wrote:
> From: Francisco M Neto 
> Date: Wed, 12 Jun 2019 07:27:28 -0300
>> It's also worth checking if there's anything under
>> /etc/apt/sources.list.d/
> peter@imager:~$ ls /etc/apt/sources.list.d/*
> /etc/apt/sources.list.d/mythtv.list
> peter@imager:~$
> 
> With any luck, mythtv.list isn't involved in this conundrum.

Something tells me that it is worth a look. What are the contents of
/etc/apt/sources.list.d/mythtv.list ?

-Matt



signature.asc
Description: OpenPGP digital signature

Re: Output from apt-get update.

[peter]

From: Francisco M Neto 
Date: Wed, 12 Jun 2019 07:27:28 -0300
> It's also worth checking if there's anything under
> /etc/apt/sources.list.d/

peter@dalton:/etc/apt$ ls /etc/apt/sources.list.d/*
ls: cannot access '/etc/apt/sources.list.d/*': No such file or directory
peter@dalton:/etc/apt$

peter@imager:~$ ls /etc/apt/sources.list.d/*
/etc/apt/sources.list.d/mythtv.list
peter@imager:~$

With any luck, mythtv.list isn't involved in this conundrum.

The mainboard interface appears as eth0.
"ip link show" reports eth0 is up.
"ip addr show" reports an IPv6 address for eth0.  No IPv4 address.

ping to a neighbour reports 
  connect: network is unreachable
  
Is IPv6 the default now?  Shorewall configuration needs updating?

Online documentation still has numerous mentions of ifconfig.
https://wiki.debian.org/NetworkConfiguration is a prime example.

Here and there a remark that ip is the new tool replacing ifconfig and 
etc.  Difficult for a non-expert to decide when to use and old command 
and when a shiney new one.   8~(

Any further ideas?

Thanks,... P.



-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: Output from apt-get update.

[peter]

From: Matthew Crews 
Date: Wed, 12 Jun 2019 06:00:26 +0200 (CEST)
> What does your "/etc/apt/sources.list" file look like on your two machines?

Here they are.

# imager:/etc/apt/sources.list
# Security updates
deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free
# mirror.it.ubc.ca = 137.82.116.42
deb http://137.82.116.42/debian stretch main contrib non-free
deb-src http://137.82.116.42/debian stretch main contrib non-free
# stretch-updates, previously known as 'volatile'
deb http://137.82.116.42/debian stretch-updates main contrib non-free
deb-src http://137.82.116.42/debian stretch-updates main contrib non-free
# stretch backports
deb http://137.82.116.42/debian stretch-backports main contrib non-free
deb-src http://137.82.116.42/debian stretch-backports main contrib non-free

# dalton:/etc/apt/sources.list
# Security updates
deb http://security.debian.org/ stretch/updates main contrib non-free
deb-src http://security.debian.org/ stretch/updates main contrib non-free
# mirror.it.ubc.ca = 137.82.116.42
deb http://137.82.116.42/debian stretch main contrib non-free
deb-src http://137.82.116.42/debian stretch main contrib non-free
# debian.oregonstate.edu = 140.211.166.134
#deb http://140.211.166.141/debian jessie main contrib non-free
#deb-src http://140.211.166.141/debian jessie main contrib non-free
# Stable updates
deb http://137.82.116.42/debian stretch-updates main contrib non-free
deb-src http://137.82.116.42/debian stretch-updates main contrib non-free
# Stable backports
deb http://137.82.116.42/debian stretch-backports main contrib non-free
deb-src http://137.82.116.42/debian stretch-backports main contrib non-free

As I see, sources.list from the two systems are identical, except for comments.

> Its unusual to directly point to an IP address for the Debian repos, as
> opposed to point to the domain name.

dalton has dnsmasq.  From distant recollection, name resolution failed when 
the system was running and dnsmasq was not.  That motivated direct reference 
to IP addresses.  To the best of my knowledge, an IP address should suffice to 
identify a server or possibly a cluster of them. 

I don't understand the intent or meaning of the hypothetical long path cited 
repeatedly.  Eg.
root@imager:/home/peter# apt-get update
Get:1 file:/full/path/to/build/packaging/deb ./ InRelease
Ign:1 file:/full/path/to/build/packaging/deb ./ InRelease
Get:2 file:/full/path/to/build/packaging/deb ./ Release
Ign:2 file:/full/path/to/build/packaging/deb ./ Release
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
  ...

Whereas dalton just confirms the sources.list
root@dalton:/home/peter# apt-get update
Ign:1 http://137.82.116.42/debian stretch InRelease
Hit:2 http://137.82.116.42/debian stretch-updates InRelease
Hit:3 http://137.82.116.42/debian stretch-backports InRelease
Hit:4 http://137.82.116.42/debian stretch Release
Hit:5 http://security.debian.org stretch/updates InRelease
Reading package lists... Done
root@dalton:/home/peter# 

Any ideas about that?  Incidentally, what is "Ign"?

Thanks,... P.



-- 
https://en.wikibooks.org/wiki/Oberon
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: Output from apt-get update.

[Francisco M Neto]

On Wed, 2019-06-12 at 06:00 +0200, Matthew Crews wrote:
> On 6/11/19 7:28 PM, pe...@easthope.ca wrote:
> **SNIP*
> 
> What does your "/etc/apt/sources.list" file look like on your two
> machines?
> 
> Its unusual to directly point to an IP address for the Debian repos,
> as opposed to point to the domain name.

It's also worth checking if there's anything under
/etc/apt/sources.list.d/

-- 
[]'s,

Francisco M Neto 

GPG: 4096R/D692FBF0


signature.asc
Description: This is a digitally signed message part

Re: Output from apt-get update.

[Andy Smith]

Hi Peter,

On Tue, Jun 11, 2019 at 07:28:12PM -0700, pe...@easthope.ca wrote:
> E: Failed to fetch file:/full/path/to/build/packaging/deb/./Packages  File 
> not found - /full/path/to/build/packaging/deb/./Packages (2: No such file or 
> directory)
> E: Some index files failed to download. They have been ignored, or old ones 
> used instead.
> root@imager:/home/peter# 
> 
> The last two lines, "E: ...", appear to be error messages.  The two 
> systems have the same /etc/apt/sources.list.  Any ideas about the 
> difficulty in imager?

The second machine seems to have additional sources. They may be in
a file under /etc/apt/sources.list.d/ rather than in
/etc/apt/sources.list itself.

Cheers,
Andy

-- 
https://bitfolk.com/ -- No-nonsense VPS hosting

Re: Output from apt-get update.

[Matthew Crews]

On 6/11/19 7:28 PM, pe...@easthope.ca wrote:
**SNIP*

What does your "/etc/apt/sources.list" file look like on your two machines?

Its unusual to directly point to an IP address for the Debian repos, as
opposed to point to the domain name.



signature.asc
Description: OpenPGP digital signature

Output from apt-get update.

[peter]

On my workstation, apt-get echoes the locations from which package 
information is retrieved.  No problems evident.
root@dalton:/home/peter# apt-get update
Ign:1 http://137.82.116.42/debian stretch InRelease
Hit:2 http://137.82.116.42/debian stretch-updates InRelease
Hit:3 http://security.debian.org stretch/updates InRelease
Hit:4 http://137.82.116.42/debian stretch-backports InRelease
Hit:5 http://137.82.116.42/debian stretch Release
Reading package lists... Done
root@dalton:/home/peter# 

Another machine gives this output.
root@imager:/home/peter# apt-get update
Get:1 file:/full/path/to/build/packaging/deb ./ InRelease
Ign:1 file:/full/path/to/build/packaging/deb ./ InRelease
Get:2 file:/full/path/to/build/packaging/deb ./ Release
Ign:2 file:/full/path/to/build/packaging/deb ./ Release
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:5 http://137.82.116.42/debian stretch InRelease
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Get:3 file:/full/path/to/build/packaging/deb ./ Packages   
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages   
Hit:7 http://137.82.116.42/debian stretch-updates InRelease
Hit:8 http://security.debian.org stretch/updates InRelease 
Hit:9 http://137.82.116.42/debian stretch-backports InRelease  
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US  
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US  
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en 
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Hit:10 http://137.82.116.42/debian stretch Release 
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Ign:3 file:/full/path/to/build/packaging/deb ./ Packages
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Get:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Ign:6 file:/full/path/to/build/packaging/deb ./ Translation-en
Get:3 file:/full/path/to/build/packaging/deb ./ Packages
Err:3 file:/full/path/to/build/packaging/deb ./ Packages
  File not found - /full/path/to/build/packaging/deb/./Packages (2: No such 
file or directory)
Get:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Ign:4 file:/full/path/to/build/packaging/deb ./ Translation-en_US
Reading package lists... Done
E: Failed to fetch file:/full/path/to/build/packaging/deb/./Packages  File not 
found - /full/path/to/build/packaging/deb/./Packages (2: No such file or 
directory)
E: Some index files failed to download. They have been ignored, or old ones 
used instead.
root@imager:/home/peter# 

The last two lines, "E: ...", appear to be error messages.  The two 
systems have the same /etc/apt/sources.list.  Any ideas about the 
difficulty in imager?

Thanks, ... Peter E.

-- 
Composed and transmitted by software designed to avoid the 
complication and vulnerability of antivirus software.
Tel: +1 604 670 0140Bcc: peter at easthope. ca

Re: apt-get update error

[Cindy Sue Causey]

On 4/30/19, Curt  wrote:
> On 2019-04-29, Bob Bernstein  wrote:
>> Thank you guys!
>>
>> On Mon, Apr 29, 2019 at 03:36:24PM -0400, Greg Wooledge wrote:
>>
>>> This could have been communicated or handled a bit more > smoothly.
>>
>> Can I safely assume you are referring to how the organization handled it,
>> and not my email?
>>
>
> I believe the interpretation of Greg's statement in which you, Bob, are
> the target occurred only to you, Bob, and that the remark was intended
> solely to incriminate the authorities.
>
> So you can rest easy (until Greg contradicts me).
>
> ;-)


That was my brain's interpretation, too... with the further thought
process that NEXT TIME... those of us who follow Debian-Publicity and
similar could help out by forwarding the most important of those
updates over here to Debian-User

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with run on sentences *

Re: apt-get update error

[Curt]

On 2019-04-29, Bob Bernstein  wrote:
> Thank you guys!
>
> On Mon, Apr 29, 2019 at 03:36:24PM -0400, Greg Wooledge wrote:
>
>> This could have been communicated or handled a bit more > smoothly.
>
> Can I safely assume you are referring to how the organization handled it, and 
> not my email? 
>

I believe the interpretation of Greg's statement in which you, Bob, are
the target occurred only to you, Bob, and that the remark was intended
solely to incriminate the authorities.

So you can rest easy (until Greg contradicts me).

;-)

> All best,
>


-- 
The major, who had been a great fencer, did not believe in bravery, and spent
much time while we sat in the machines correcting my grammar. He had
complimented me on how I spoke Italian, and we talked together very easily. One
day I had said that Italian seemed such an easy language to me that I could not
take a great interest in it; everything was so easy to say. "Ah, yes," the
major said. "Why, then, do you not take up the use of grammar?" - "Another 
Country"

Re: apt-get update error

[Bob Bernstein]

Thank you guys!

On Mon, Apr 29, 2019 at 03:36:24PM -0400, Greg Wooledge wrote:

> This could have been communicated or handled a bit more > smoothly.

Can I safely assume you are referring to how the organization handled it, and 
not my email? 


All best,

-- 
"In our age there is no such thing as ‘keeping out of 
politics’. All issues are political issues, and politics 
itself is a mass of lies, evasions, folly, hatred, and 
schizophrenia."

 George Orwell "Politics and the English Language" (1946) 

Re: apt-get update error

[Francisco M Neto]

On Mon, 2019-04-29 at 15:31 -0400, Bob Bernstein wrote:
> -snip-
> deb http://deb.debian.org/debian/ jessie main contrib non-free
> 
> deb-src http://deb.debian.org/debian/ jessie main contrib non-free
> 
> deb http://security.debian.org/ jessie/updates main contrib non-free
> 
> deb-src http://security.debian.org/ jessie/updates main contrib non-
> free
> 
> deb http://deb.debian.org/debian/ jessie-updates main contrib non-free
> 
> deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-
> free
> -snip-

Those last two lines are not needed, and are what is probably
causing the errors in your update. 

Also, check this page: https://wiki.debian.org/LTS/Using


Cheers!
-- 
[]'s,

Francisco M Neto 

GPG: 4096R/D692FBF0


signature.asc
Description: This is a digitally signed message part

Re: apt-get update error

[Greg Wooledge]

On Mon, Apr 29, 2019 at 03:31:18PM -0400, Bob Bernstein wrote:
> W: Failed to fetch 
> http://deb.debian.org/debian/dists/jessie-updates/InRelease  Unable to find 
> expected entry 'main/source/Sources' in Release file (Wrong sources.list 
> entry or malformed file)

There is no more jessie-updates repository.  Just remove that line.

foo-updates is a repository that exists only while a stable release is
still supported and receiving point-release updates (like 8.3, 8.4, 8.5).
The foo-updates repository is a place where the updates that are GOING to
be in the next point release are available before the formal point release
happens.

Since jessie will never receive another point-release update, there is
no reason to have a jessie-updates repository.

So, the repository was removed, nuked, wiped out, obliterated, you have
no chance to survive make your time.

This could have been communicated or handled a bit more smoothly.

apt-get update error

[Bob Bernstein]

Greetings earthlings!

I am running an old Jessie I refuse to let go of, on an 
amd64. # uname -a
Linux debian.localdomain 3.16.0-7-amd64 #1 SMP Debian 3.16.59-1 (2018-10-03) 
x86_64 GNU/Linux

Here is the apt-get update output error:

W: Failed to fetch http://deb.debian.org/debian/dists/jessie-updates/InRelease  
Unable to find expected entry 'main/source/Sources' in Release file (Wrong 
sources.list entry or malformed file)

This is my sources.list. It represents my effort to 
invoke LTS for this Jessie. I can't see anything in it that even vaguely 
resembles the line above. 

-snip-
deb http://deb.debian.org/debian/ jessie main contrib non-free

deb-src http://deb.debian.org/debian/ jessie main contrib non-free

deb http://security.debian.org/ jessie/updates main contrib non-free

deb-src http://security.debian.org/ jessie/updates main contrib non-free

deb http://deb.debian.org/debian/ jessie-updates main contrib non-free

deb-src http://deb.debian.org/debian/ jessie-updates main contrib non-free
-snip-

Any and all contributions will be gratefully and thoroughly examined.

Thank you.


-- 
"In our age there is no such thing as ‘keeping out of 
politics’. All issues are political issues, and politics 
itself is a mass of lies, evasions, folly, hatred, and 
schizophrenia."

 George Orwell "Politics and the English Language" (1946) 

Re: [SOLVED] Re: apt-get update hangs forever

[Cindy-Sue Causey]

On 7/15/18, deloptes  wrote:
> Carl Fink wrote:
>
>> May we assume you tried switching repos? Because the only times I've
>> seen that, a particular repository was unreachable.
>
> no, I have not switched anything, but your answer helped me rewind the tape
> back and yes I have added one source (Signal) by myself and the stupid
> skype package adds it's source each time you install it, so I removed both
> and now it works. I would bet it hangs on the Signal source.
>
> thank you very much for the hint


There's also this that JUST occurred:

https://lists.debian.org/debian-announce/2018/msg3.html

+++ BEGIN QUOTE +++

The Debian project is pleased to announce the fifth update of its stable
distribution Debian 9 (codename "stretch"). This point release mainly
adds corrections for security issues, along with a few adjustments for
serious problems. Security advisories have already been published
separately and are referenced where available.

Please note that the point release does not constitute a new version of
Debian 9 but only updates some of the packages included. There is no
need to throw away old "stretch" media. After installation, packages can
be upgraded to the current versions using an up-to-date Debian mirror.

Those who frequently install updates from security.debian.org won't have
to update many packages, and most such updates are included in the point
release.

New installation images will be available soon at the regular locations.

+++ END QUOTE +++

It's possible a mirror was burping or something, too. That last line
is the hint there.

I'm on a brand new, 24-hour-old debootstrap that was 100% up-to-date,
*yes, including security releases (grin)*. I just  "apt-get updated".
It took about 4 hours and now says another 23MB of upgrades are needed
that quickly. :D

Just thought to check libreoffice, too, since I hadn't install it again and yet:

0 upgraded, 132 newly installed, 0 to remove and 38 not upgraded.
Need to get 132 kB/179 MB of archives.
After this operation, 578 MB of additional disk space will be used.

It sure pays to hoard previously downloaded dotDeb archive files when
you're on dialup!

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[SOLVED] Re: apt-get update hangs forever

[deloptes]

Carl Fink wrote:

> May we assume you tried switching repos? Because the only times I've
> seen that, a particular repository was unreachable.

no, I have not switched anything, but your answer helped me rewind the tape
back and yes I have added one source (Signal) by myself and the stupid
skype package adds it's source each time you install it, so I removed both
and now it works. I would bet it hangs on the Signal source.

thank you very much for the hint

regards

Re: apt-get update hangs forever

[Carl Fink]

On 07/15/2018 06:27 AM, deloptes wrote:

Hi
on one of my machines apt-get update hangs forever.


Get:32 http://ftp.at.debian.org/debian stretch/non-free i386 Packages [69.7
kB]
Get:33 http://ftp.at.debian.org/debian stretch/non-free Translation-en [80.6
kB]
0% [Working]

What can I do to understand the reason and to solve it?

thanks


May we assume you tried switching repos? Because the only times I've
seen that, a particular repository was unreachable.

--
Carl Fink  c...@finknetwork.com
Thinking and logic and stuff at Reasonably Literate
http://reasonablyliterate.com

apt-get update hangs forever

[deloptes]

Hi
on one of my machines apt-get update hangs forever.


Get:32 http://ftp.at.debian.org/debian stretch/non-free i386 Packages [69.7
kB]
Get:33 http://ftp.at.debian.org/debian stretch/non-free Translation-en [80.6
kB]
0% [Working]   

What can I do to understand the reason and to solve it?

thanks  

Re: apt-get update on sid: Hash Sum mismatch

[Felix Natter]

Sven Joachim <svenj...@gmx.de> writes:

> On 2018-04-14 17:24 +0200, Felix Natter wrote:
>
>> I shut down a virtualbox sid VM, and it turned out it was running
>> "unattended upgrades". On next start, apt-get update fails:
>>
>> =
>> Get:22 http://ftp2.de.debian.org/debian unstable/contrib amd64 Contents
>> (deb) [221 kB]
>> Err:13 http://ftp2.de.debian.org/debian unstable/non-free amd64 DEP-11 
>> Metadata> [...]
>> Is anyone else experiencing this?
>
> Yes, that is https://bugs.debian.org/895671.  Should be fixed with the
> next mirror push.

hello Sven,

this is fixed now, thanks for the confirmation :-)

Best Regards,
-- 
Felix Natter
debian/rules!

Re: apt-get update on sid: Hash Sum mismatch

[Jimmy Johnson]

On 04/14/2018 08:24 AM, Felix Natter wrote:

> apt-get update on sid: Hash Sum mismatch


That means try again later or try a different source. :)

Cheers!
--
Jimmy Johnson

Devuan Beowulf - TDE-Trinity R14.0.5 - AMD A8-7600 - EXT4 at sda8
Registered Linux User #380263

Re: apt-get update on sid: Hash Sum mismatch

[Sven Joachim]

On 2018-04-14 17:24 +0200, Felix Natter wrote:

> I shut down a virtualbox sid VM, and it turned out it was running
> "unattended upgrades". On next start, apt-get update fails:
>
> =
> Get:22 http://ftp2.de.debian.org/debian unstable/contrib amd64 Contents (deb) 
> [221 kB]  
>   
> Err:13 http://ftp2.de.debian.org/debian unstable/non-free amd64 DEP-11 
> Metadata> [...]
> Is anyone else experiencing this?

Yes, that is https://bugs.debian.org/895671.  Should be fixed with the
next mirror push.

Cheers,
   Sven

apt-get update on sid: Hash Sum mismatch

[Felix Natter]

Hello debian-users,

I shut down a virtualbox sid VM, and it turned out it was running
"unattended upgrades". On next start, apt-get update fails:

=
Get:22 http://ftp2.de.debian.org/debian unstable/contrib amd64 Contents (deb) 
[221 kB]

Err:13 http://ftp2.de.debian.org/debian unstable/non-free amd64 DEP-11 Metadata 

  
  Hash Sum mismatch
  Hashes of expected file:
   - Filesize:72292 [weak]
   - SHA256:64b9be98f14db2f20b9730981fc799db28903d53adec5e501ad25ffe965d5c7e
   - MD5Sum:138830c87e09a8e9a1b2f449c8687e13 [weak]
  Hashes of received file:
   - SHA256:997f4a6bd4e0a4bda048eec9f0ea3539d8995fe825417c9dfe6c70b5beb6f5fe
   - MD5Sum:3ce213b33bd27fa8b0b89bedf3e05dd3 [weak]
   - Filesize:72292 [weak]
  Last modification reported: Thu, 12 Apr 2018 15:29:53 +
  Release file created at: Sat, 14 Apr 2018 08:34:47 +
Fetched 76.6 MB in 52s (1,485 kB/s) 

  
Reading package lists... Done
E: Failed to fetch 
store:/var/lib/apt/lists/partial/ftp2.de.debian.org_debian_dists_unstable_non-free_dep11_Components-amd64.yml.xz
  Hash Sum mismatch
   Hashes of expected file:
- Filesize:72292 [weak]
- SHA256:64b9be98f14db2f20b9730981fc799db28903d53adec5e501ad25ffe965d5c7e
- MD5Sum:138830c87e09a8e9a1b2f449c8687e13 [weak]
   Hashes of received file:
- SHA256:997f4a6bd4e0a4bda048eec9f0ea3539d8995fe825417c9dfe6c70b5beb6f5fe
- MD5Sum:3ce213b33bd27fa8b0b89bedf3e05dd3 [weak]
- Filesize:72292 [weak]
   Last modification reported: Thu, 12 Apr 2018 15:29:53 +
   Release file created at: Sat, 14 Apr 2018 08:34:47 +
E: Some index files failed to download. They have been ignored, or old ones 
used instead.
=

I already switched from ftp.de.debian.org to ftp2.de.debian.org, and
did this:
$ sudo rm -rf /var/lib/apt/lists/*
(I made a backup copy)

but I get the same error.

Is anyone else experiencing this?

Many Thanks and Best Regards,
-- 
Felix Natter
debian/rules!

Re: Problem using "apt-get update"

[Richard Owlett]

On 02/24/2018 12:02 PM, Felix Miata wrote:

Richard Owlett composed on 2018-02-24 10:48 (UTC-0600):


I had just done a minimal (command line only) install of Stretch from
the first DVD of the complete set rather than using netinst to conserve
bandwidth. The install as usual was successful.



I wish to install a package from the repository - it's not on DVD1.
I added the line
deb http://ftp.us.debian.org/debian/ stretch main non-free contrib
to sources.list while commenting out the line referencing CDROM.



I attempted to run "apt-get update".
It *FAILED*
The message was the source I wanted was being ignored.



WHY?

  Mirror problems in .us.???


No. A typo in the following "apt-get install ..." line ;/




Do you get also get failure if you s/apt-get/apt/g ?

Re: Problem using "apt-get update"

[Richard Owlett]

On 02/24/2018 12:01 PM, Brian wrote:

On Sat 24 Feb 2018 at 11:55:29 -0600, Richard Owlett wrote:


On 02/24/2018 11:08 AM, Reco wrote:

Hi.

On Sat, Feb 24, 2018 at 11:06:53AM -0600, Richard Owlett wrote:

On 02/24/2018 10:56 AM, John Hasler wrote:

Verbatim command


apt-get update  (as per
<https://manpages.debian.org/stretch/apt/apt-get.8.en.html>)


verbatim message


The message started a recognizable abbreviation of "ignored".
For a character perfect quote - where would it be logged?


apt-get update > /tmp/somefile

Reco




OK, I mis-remembered which line had "Ign". Here is redo:

Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.us.debian.org/debian stretch InRelease
Hit:3 http://ftp.us.debian.org/debian stretch Release
Reading package lists...


So I redid the apt-get install which got me problem chasing,
(apt-get install xorg lightdm lvwm) whose captured output was:

Reading package lists...
Building dependency tree...
Reading state information...


That was followed by an uncaptured line saying:
E: Unable to locate package lvwm


lvwm doesn't exist.



Ba Baaa
Signed: He With Sheepish Look

Thanks all.

Re: Problem using "apt-get update"

[Felix Miata]

Richard Owlett composed on 2018-02-24 10:48 (UTC-0600):

> I had just done a minimal (command line only) install of Stretch from 
> the first DVD of the complete set rather than using netinst to conserve 
> bandwidth. The install as usual was successful.

> I wish to install a package from the repository - it's not on DVD1.
> I added the line
>deb http://ftp.us.debian.org/debian/ stretch main non-free contrib
> to sources.list while commenting out the line referencing CDROM.

> I attempted to run "apt-get update".
> It *FAILED*
> The message was the source I wanted was being ignored.

> WHY?
 Mirror problems in .us.???

Do you get also get failure if you s/apt-get/apt/g ?
-- 
"Wisdom is supreme; therefore get wisdom. Whatever else you
get, get wisdom." Proverbs 4:7 (New Living Translation)

 Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

Re: Problem using "apt-get update"

[Brian]

On Sat 24 Feb 2018 at 11:55:29 -0600, Richard Owlett wrote:

> On 02/24/2018 11:08 AM, Reco wrote:
> > Hi.
> > 
> > On Sat, Feb 24, 2018 at 11:06:53AM -0600, Richard Owlett wrote:
> > > On 02/24/2018 10:56 AM, John Hasler wrote:
> > > > Verbatim command
> > > 
> > > apt-get update  (as per
> > > <https://manpages.debian.org/stretch/apt/apt-get.8.en.html>)
> > > 
> > > > verbatim message
> > > 
> > > The message started a recognizable abbreviation of "ignored".
> > > For a character perfect quote - where would it be logged?
> > 
> > apt-get update > /tmp/somefile
> > 
> > Reco
> > 
> > 
> 
> OK, I mis-remembered which line had "Ign". Here is redo:
> > Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
> > Ign:2 http://ftp.us.debian.org/debian stretch InRelease
> > Hit:3 http://ftp.us.debian.org/debian stretch Release
> > Reading package lists...
> 
> So I redid the apt-get install which got me problem chasing,
> (apt-get install xorg lightdm lvwm) whose captured output was:
> > Reading package lists...
> > Building dependency tree...
> > Reading state information...
> 
> That was followed by an uncaptured line saying:
> E: Unable to locate package lvwm

lvwm doesn't exist.

-- 
Brian.

Re: Problem using "apt-get update"

[Richard Owlett]

On 02/24/2018 11:08 AM, Reco wrote:

Hi.

On Sat, Feb 24, 2018 at 11:06:53AM -0600, Richard Owlett wrote:

On 02/24/2018 10:56 AM, John Hasler wrote:

Verbatim command


apt-get update  (as per
<https://manpages.debian.org/stretch/apt/apt-get.8.en.html>)


verbatim message


The message started a recognizable abbreviation of "ignored".
For a character perfect quote - where would it be logged?


apt-get update > /tmp/somefile

Reco




OK, I mis-remembered which line had "Ign". Here is redo:

Hit:1 http://security.debian.org/debian-security stretch/updates InRelease
Ign:2 http://ftp.us.debian.org/debian stretch InRelease
Hit:3 http://ftp.us.debian.org/debian stretch Release
Reading package lists...


So I redid the apt-get install which got me problem chasing,
(apt-get install xorg lightdm lvwm) whose captured output was:

Reading package lists...
Building dependency tree...
Reading state information...


That was followed by an uncaptured line saying:
E: Unable to locate package lvwm

Color me more confused ;<

Re: Problem using "apt-get update"

[John Hasler]

The messages emitted by apt-get update are cryptic and undocumented, but
see

<https://wiki.debian.org/ftp.debian.org>
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Re: Problem using "apt-get update"

[Brian]

On Sat 24 Feb 2018 at 17:31:21 +, Brian wrote:

> On Sat 24 Feb 2018 at 11:06:53 -0600, Richard Owlett wrote:
> 
> > On 02/24/2018 10:56 AM, John Hasler wrote:
> > > Verbatim command
> > 
> > apt-get update  (as per
> > <https://manpages.debian.org/stretch/apt/apt-get.8.en.html>)
> > 
> > > verbatim message
> > 
> > The message started a recognizable abbreviation of "ignored".
> 
> "ign" means there have been no changes in the file - so it won't
> be downloaded again. Nothing to worry about.

Or maybe not ( when I use a search engine instead of my imagination). 

-- 
Brian.
 

Re: Problem using "apt-get update"

[Brian]

On Sat 24 Feb 2018 at 11:06:53 -0600, Richard Owlett wrote:

> On 02/24/2018 10:56 AM, John Hasler wrote:
> > Verbatim command
> 
> apt-get update  (as per
> <https://manpages.debian.org/stretch/apt/apt-get.8.en.html>)
> 
> > verbatim message
> 
> The message started a recognizable abbreviation of "ignored".

"ign" means there have been no changes in the file - so it won't
be downloaded again. Nothing to worry about.

-- 
Brian.

Re: Problem using "apt-get update"

[Abdullah Ramazanoglu]

On Sat, 24 Feb 2018 11:06:53 -0600
Richard Owlett  wrote:
> On 02/24/2018 10:56 AM, John Hasler wrote:
--8<--
>> verbatim message  
> 
> The message started a recognizable abbreviation of "ignored".
> For a character perfect quote - where would it be logged?
> 
>> and verbatim sources.list, please.  
> 
> Here it is
--8<--
> > http://ftp.us.debian.org/debian/ stretch main non-free contrib deb

It could be due to archive signature being incorrect or something. You
can *force*-override this with [ trusted=yes ] in the "deb" line, as in;

deb [ trusted=yes ] http://ftp.us.debian.org/debian/ stretch main
non-free contrib

But it is strongly recommended against using this arbitrarily. (I use
it for home-grown local archives only)
-- 
Abdullah Ramazanoglu

Re: Problem using "apt-get update"

[Reco]

Hi.

On Sat, Feb 24, 2018 at 11:06:53AM -0600, Richard Owlett wrote:
> On 02/24/2018 10:56 AM, John Hasler wrote:
> > Verbatim command
> 
> apt-get update  (as per
> <https://manpages.debian.org/stretch/apt/apt-get.8.en.html>)
> 
> > verbatim message
> 
> The message started a recognizable abbreviation of "ignored".
> For a character perfect quote - where would it be logged?

apt-get update > /tmp/somefile

Reco

Re: Problem using "apt-get update"

[Richard Owlett]

On 02/24/2018 10:56 AM, John Hasler wrote:

Verbatim command


apt-get update  (as per 
<https://manpages.debian.org/stretch/apt/apt-get.8.en.html>)



verbatim message


The message started a recognizable abbreviation of "ignored".
For a character perfect quote - where would it be logged?


and verbatim sources.list, please.


Here it is

# 


# deb cdrom:[Debian GNU/Linux 9.1.0 _Stretch_ - Official i386 DVD Binary-1 
20170722-12:45]/ stretch contrib main

# deb cdrom:[Debian GNU/Linux 9.1.0 _Stretch_ - Official i386 DVD Binary-1 
20170722-12:45]/ stretch contrib main
deb http://ftp.us.debian.org/debian/ stretch main non-free contrib
deb http://security.debian.org/debian-security stretch/updates main contrib
deb-src http://security.debian.org/debian-security stretch/updates main contrib

Re: Problem using "apt-get update"

[John Hasler]

Verbatim command, verbatim message and verbatim sources.list, please.
-- 
John Hasler 
jhas...@newsguy.com
Elmwood, WI USA

Problem using "apt-get update"

[Richard Owlett]

I had just done a minimal (command line only) install of Stretch from 
the first DVD of the complete set rather than using netinst to conserve 
bandwidth. The install as usual was successful.


I wish to install a package from the repository - it's not on DVD1.
I added the line
  deb http://ftp.us.debian.org/debian/ stretch main non-free contrib
to sources.list while commenting out the line referencing CDROM.

I attempted to run "apt-get update".
It *FAILED*
The message was the source I wanted was being ignored.

WHY?

Re: apt-get update error

[Frank]

Op 08-02-18 om 22:27 schreef Sven Hartge:

Forest Dean Feighner  wrote:

On Thu, Feb 8, 2018 at 3:36 PM, Greg Wooledge  wrote:

On Thu, Feb 08, 2018 at 03:26:40PM -0500, Forest Dean Feighner wrote:



W: http://security.debian.org/debian-security/dists/stretch/updates/InRelease:
The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
not readable by user '_apt' executing apt-key.



-rw--- 1 root root   32 Feb  6 17:58 trusted.gpg


Synaptic strikes again. :(



Ah, so the error is from using Synaptic rather than from the update of
libtasn1-6?



That's the only recent update I've done and I didn't realize Syaptic would
write the file.


The problem is from synaptic creating /etc/apt/trusted.gpg with too
narrow permissions,


Actually, it's not synaptic that's doing that, but the executable 
software-properties-gtk when it's called by synaptic. So if you run that 
separately, you'll also end up with a messed up /etc/apt/trusted.gpg file.


https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=867681

Regards,
Frank

Re: apt-get update error

[Sven Hartge]

Forest Dean Feighner  wrote:
> On Thu, Feb 8, 2018 at 3:36 PM, Greg Wooledge  wrote:
>> On Thu, Feb 08, 2018 at 03:26:40PM -0500, Forest Dean Feighner wrote:

>>> W: 
>>> http://security.debian.org/debian-security/dists/stretch/updates/InRelease:
>>> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
>>> not readable by user '_apt' executing apt-key.

>> > -rw--- 1 root root   32 Feb  6 17:58 trusted.gpg
>>
>> Synaptic strikes again. :(

> Ah, so the error is from using Synaptic rather than from the update of
> libtasn1-6?

> That's the only recent update I've done and I didn't realize Syaptic would
> write the file.

The problem is from synaptic creating /etc/apt/trusted.gpg with too
narrow permissions, a file which is no longer used by apt (instead all
keys are in /etc/apt/trusted.gpg.d)

You can just delete /etc/apt/trusted.gpg or change the permissions to
644 (instead of 600 now).

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Re: apt-get update error

[Forest Dean Feighner]

Ah, so the error is from using Synaptic rather than from the update of
libtasn1-6?

That's the only recent update I've done and I didn't realize Syaptic would
write the file.

Thanks Greg


On Thu, Feb 8, 2018 at 3:36 PM, Greg Wooledge  wrote:

> On Thu, Feb 08, 2018 at 03:26:40PM -0500, Forest Dean Feighner wrote:
> > W:
> > http://security.debian.org/debian-security/dists/stretch/
> updates/InRelease:
> > The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> > not readable by user '_apt' executing apt-key.
>
> > -rw--- 1 root root   32 Feb  6 17:58 trusted.gpg
>
> Synaptic strikes again. :(
>
>

Re: apt-get update error

[Greg Wooledge]

On Thu, Feb 08, 2018 at 03:26:40PM -0500, Forest Dean Feighner wrote:
> W:
> http://security.debian.org/debian-security/dists/stretch/updates/InRelease:
> The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
> not readable by user '_apt' executing apt-key.

> -rw--- 1 root root   32 Feb  6 17:58 trusted.gpg

Synaptic strikes again. :(

apt-get update error

[Forest Dean Feighner]

Greetings All,

After updating libtasn1-6 last night I've started getting and an apt-get
update error.

W:
http://security.debian.org/debian-security/dists/stretch/updates/InRelease:
The key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is
not readable by user '_apt' executing apt-key.
W: http://ftp.us.debian.org/debian/dists/stretch-updates/InRelease: The
key(s) in the keyring /etc/apt/trusted.gpg are ignored as the file is not
readable by user '_apt' executing apt-key.
W: http://ftp.us.debian.org/debian/dists/stretch/Release.gpg: The key(s) in
the keyring /etc/apt/trusted.gpg are ignored as the file is not readable by
user '_apt' executing apt-key.

I've read elsewhere that this file is not used for the debian repositories
and is safely removed. Is that correct?

The file in question is dated the 6th of February.
-rw--- 1 root root   32 Feb  6 17:58 trusted.gpg


Any feedback or advice appreciated.

Thanks
Forest

Re: apt-get update

[David Martin]

Désolé, je viens de trouvé... j'avais oublié un paramétrage
d'authentification dans mon apt.conf, qui filait sur un proxy.

LOL !

Je vais me faire bacher par le réseau .


Le 2 février 2017 à 09:47, David Martin <damart.vi...@gmail.com> a écrit :

> Bonjour,
>
> J'ai un deuxième soucis sur deux autre serveurs, j'ai beau avoir changé
> d'ip, d'interface réseau (ce sont deux vm), sollicité l'équipe réseau qui
> en voit pas les requetes Apt sortir...
>
> impossible de faire un apt-get update && apt-get upgrade
>
> Ca ne veut pas sortir... Alors je me pose la question suivante :
>
> Existerait-il un moyen au niveau système de bloquer l'upgrade d'une
> distribution ?
>
> J'ai checké iptables -L j'ai rien
>
> Je sèche ... si vous avez une idée...
>
> Ma résolution est bonne, j'ai bien vérifié ma configuration réseau aussi.
>
> --
> david martin
>
>


-- 
david martin

apt-get update

[David Martin]

Bonjour,

J'ai un deuxième soucis sur deux autre serveurs, j'ai beau avoir changé
d'ip, d'interface réseau (ce sont deux vm), sollicité l'équipe réseau qui
en voit pas les requetes Apt sortir...

impossible de faire un apt-get update && apt-get upgrade

Ca ne veut pas sortir... Alors je me pose la question suivante :

Existerait-il un moyen au niveau système de bloquer l'upgrade d'une
distribution ?

J'ai checké iptables -L j'ai rien

Je sèche ... si vous avez une idée...

Ma résolution est bonne, j'ai bien vérifié ma configuration réseau aussi.

-- 
david martin

Re: apt-secure / apt-get update gpg signature invalid

[aRkadeFR]

After upgrading aptly to newest version (0.9.7), the error disappear.

The only changes I noticed are the inclusion of the SHA512 sums in the files 
and the creation of the content-arch.gz





 Original Message 
Subject: apt-secure / apt-get update gpg signature invalid
Local Time: January 13, 2017 9:57 AM
UTC Time: January 13, 2017 8:57 AM
From: cont...@arkade.info
To: debian-user@lists.debian.org <debian-user@lists.debian.org>

Hello,

After setting up a new apt repository with aptly, signing the repository and 
adding the public gpg key to the apt keyring, I encounter a failure during the 
`apt update` command:
Err:3 http://#REPO_URL#/#NAME# #DISTRIBUTION# InRelease The following 
signatures were invalid: #KEY_ID# Hit:4 http://apt.postgresql.org/pub/repos/apt 
sid-pgdg InRelease Reading package lists... Done W: GPG error: 
http://#REPO_URL#/#NAME# #DISTRIBUTION# InRelease: The following signatures 
were invalid: #KEY_ID# E: The repository 'http://#REPO_URL#/#NAME# 
#DISTRIBUTION# InRelease' is not signed. N: Updating from such a repository 
can't be done securely, and is therefore disabled by default. N: See 
apt-secure(8) manpage for repository creation and user configuration details.

And yet the signature and the gpg keys are good. I succeed to verify the gpg 
signature on the InRelease file:

curl http://#REPO_URL#/InRelease | gpg --keyring /etc/apt/trusted.gpg --verify 
gpg: Signature made Wed 11 Jan 2017 04:01:23 PM CET gpg: using RSA key #KEY_ID# 
gpg: Good signature from "#DESCRIPTION_GPG_KEY#" [unknown] gpg: WARNING: This 
key is not certified with a trusted signature! gpg: There is no indication that 
the signature belongs to the owner. Primary key fingerprint: 
#GOOD_KEY_FINGERPRINT#

I also verified the Release and Release.gpg file and they seem correct to me.


I tried to find what's done during the apt update with a strace -o /tmp/strace 
-ff apt update then grep:

grep 'apt.*key' ./strace* ./strace.29829:execve("/usr/bin/apt-key", 
["/usr/bin/apt-key", "--quiet", "--readonly", "verify", "--status-fd", "3", 
"/tmp/apt.sig.ORUwxh", "/tmp/apt.data.kKXyrN"], [/* 28 vars */]) = 0 
./strace.29829:open("/usr/bin/apt-key", O_RDONLY) = 4 
./strace.29888:execve("/usr/bin/apt-key", ["/usr/bin/apt-key", "--quiet", 
"--readonly", "verify", "--status-fd", "3", "/tmp/apt.sig.utRWBD", 
"/tmp/apt.data.Fo1Lka"], [/* 28 vars */]) = 0 
./strace.29888:open("/usr/bin/apt-key", O_RDONLY) = 4 
./strace.29947:execve("/usr/bin/apt-key", ["/usr/bin/apt-key", "--quiet", 
"--readonly", "verify", "--status-fd", "3", "/tmp/apt.sig.ug6xiV", 
"/tmp/apt.data.Yv4zFs"], [/* 28 vars */]) = 0 
./strace.29947:open("/usr/bin/apt-key", O_RDONLY) = 4 
./strace.30006:execve("/usr/bin/apt-key", ["/usr/bin/apt-key", "--quiet", 
"--readonly", "verify", "--status-fd", "3", "/tmp/apt.sig.QSyrCg", 
"/tmp/apt.data.LK9DGO"], [/* 28 vars */]) = 0 
./strace.30006:open("/usr/bin/apt-key", O_RDONLY) = 4

How can I debug and fix this error?

Thanks

apt-secure / apt-get update gpg signature invalid

[aRkadeFR]

Hello,

After setting up a new apt repository with aptly, signing the repository and 
adding the public gpg key to the apt keyring, I encounter a failure during the 
`apt update` command:
Err:3 http://#REPO_URL#/#NAME# #DISTRIBUTION# InRelease The following 
signatures were invalid: #KEY_ID# Hit:4 http://apt.postgresql.org/pub/repos/apt 
sid-pgdg InRelease Reading package lists... Done W: GPG error: 
http://#REPO_URL#/#NAME# #DISTRIBUTION# InRelease: The following signatures 
were invalid: #KEY_ID# E: The repository 'http://#REPO_URL#/#NAME# 
#DISTRIBUTION# InRelease' is not signed. N: Updating from such a repository 
can't be done securely, and is therefore disabled by default. N: See 
apt-secure(8) manpage for repository creation and user configuration details.

And yet the signature and the gpg keys are good. I succeed to verify the gpg 
signature on the InRelease file:

curl http://#REPO_URL#/InRelease | gpg --keyring /etc/apt/trusted.gpg --verify 
gpg: Signature made Wed 11 Jan 2017 04:01:23 PM CET gpg: using RSA key #KEY_ID# 
gpg: Good signature from "#DESCRIPTION_GPG_KEY#" [unknown] gpg: WARNING: This 
key is not certified with a trusted signature! gpg: There is no indication that 
the signature belongs to the owner. Primary key fingerprint: 
#GOOD_KEY_FINGERPRINT#

I also verified the Release and Release.gpg file and they seem correct to me.


I tried to find what's done during the apt update with a strace -o /tmp/strace 
-ff apt update then grep:

grep 'apt.*key' ./strace* ./strace.29829:execve("/usr/bin/apt-key", 
["/usr/bin/apt-key", "--quiet", "--readonly", "verify", "--status-fd", "3", 
"/tmp/apt.sig.ORUwxh", "/tmp/apt.data.kKXyrN"], [/* 28 vars */]) = 0 
./strace.29829:open("/usr/bin/apt-key", O_RDONLY) = 4 
./strace.29888:execve("/usr/bin/apt-key", ["/usr/bin/apt-key", "--quiet", 
"--readonly", "verify", "--status-fd", "3", "/tmp/apt.sig.utRWBD", 
"/tmp/apt.data.Fo1Lka"], [/* 28 vars */]) = 0 
./strace.29888:open("/usr/bin/apt-key", O_RDONLY) = 4 
./strace.29947:execve("/usr/bin/apt-key", ["/usr/bin/apt-key", "--quiet", 
"--readonly", "verify", "--status-fd", "3", "/tmp/apt.sig.ug6xiV", 
"/tmp/apt.data.Yv4zFs"], [/* 28 vars */]) = 0 
./strace.29947:open("/usr/bin/apt-key", O_RDONLY) = 4 
./strace.30006:execve("/usr/bin/apt-key", ["/usr/bin/apt-key", "--quiet", 
"--readonly", "verify", "--status-fd", "3", "/tmp/apt.sig.QSyrCg", 
"/tmp/apt.data.LK9DGO"], [/* 28 vars */]) = 0 
./strace.30006:open("/usr/bin/apt-key", O_RDONLY) = 4

How can I debug and fix this error?

Thanks

Error with apt-get update

[Steven Yeager]

root@eisen:/home/yeager# apt-get update
Hit http://download.virtualbox.org trusty InRelease
Ign http://debian.usu.edu jessie
InRelease 
Hit http://debian.usu.edu jessie-updates
InRelease 
Hit http://download.virtualbox.org trusty/contrib amd64
Packages   
Hit http://debian.usu.edu jessie
Release.gpg   
Hit http://debian.usu.edu jessie-updates/main
Sources  
Get:1 http://debian.usu.edu jessie-updates/main amd64 Packages/DiffIndex
[6,916 B]
Get:2 http://debian.usu.edu jessie-updates/main Translation-en/DiffIndex
[2,704 B]
Hit http://debian.usu.edu jessie
Release   
Hit http://debian.usu.edu jessie/main
Sources  
Hit http://debian.usu.edu jessie/main
Translation-en   
Ign http://download.virtualbox.org trusty/contrib
Translation-en_US
Ign http://download.virtualbox.org trusty/contrib
Translation-en   
Hit http://debian.usu.edu jessie/main amd64
Packages   
100% [Connecting to security.debian.org
(2607:ea00:101:3c0b::1deb:215)]  


When I apt-get update after I enter into su it freezes up and will not
finish updating

Re: Frequent Hash Sum mismatch on jessie-backports with apt-get update

[Curt]

On 2016-08-18, Greg Wooledge  wrote:
>
> There is a phenomenon in one of the online communities that I engage with.
> A sort of wink-nudge superstition, if you will: "If you want something
> to happen, complain in chat about it not happening."  Posting in IRC
> didn't work in this case, but apparently posting to debian-user worked.
>

https://en.wikipedia.org/wiki/Magical_thinking

-- 
 "Until the Lion learns to write, tales of the hunt shall always glorify the 
Hunter."
— African proverb

Re: Frequent Hash Sum mismatch on jessie-backports with apt-get update

[Greg Wooledge]

On Thu, Aug 18, 2016 at 12:33:27PM -0300, Henrique de Moraes Holschuh wrote:
> On Thu, 18 Aug 2016, Greg Wooledge wrote:
> > Now, starting last week, the problem is that when I try to apt-get update,
> > the files coming from security.debian.org HANG at 100% complete.  It
> > looks something like this:
> 
> While it really might be something else completely, the anti-virus
> function of an "UTM" box (firewall+av+ips+ids+content filter+kitchen
> sink) box is your first suspect.
> 
> You could try using https. It might help, or it might make matters much
> worse.

Around 10:30 this morning, it started working again all on its own.  I'm
guessing one of the networking people restarted something.

There is a phenomenon in one of the online communities that I engage with.
A sort of wink-nudge superstition, if you will: "If you want something
to happen, complain in chat about it not happening."  Posting in IRC
didn't work in this case, but apparently posting to debian-user worked.

Re: Frequent Hash Sum mismatch on jessie-backports with apt-get update

[Henrique de Moraes Holschuh]

On Thu, 18 Aug 2016, Greg Wooledge wrote:
> Now, starting last week, the problem is that when I try to apt-get update,
> the files coming from security.debian.org HANG at 100% complete.  It
> looks something like this:

While it really might be something else completely, the anti-virus
function of an "UTM" box (firewall+av+ips+ids+content filter+kitchen
sink) box is your first suspect.

You could try using https. It might help, or it might make matters much
worse.

-- 
  Henrique Holschuh

Re: Frequent Hash Sum mismatch on jessie-backports with apt-get update

[Greg Wooledge]

On Thu, Aug 18, 2016 at 04:47:55AM -0700, poiuytrez wrote:
> I have frequent errors when I do apt-get update: 
> W: Failed to fetch 
> http://http.debian.net/debian/dists/jessie-backports/main/source/Sources  
> Hash Sum mismatch

For you, I would suggest trying a different mirror.

$ host http.debian.net
http.debian.net is an alias for httpredir.debian.org.

This redirection service works very well for some people, and very poorly
for other people.  You appear to be in the latter group.

You can either select a single mirror directly from:
https://www.debian.org/mirror/list

(the single mirrors are listed at the bottom of the page)

or you can use one of the country-code round robin services, such as:
http://ftp.us.debian.org/debian/
http://ftp.ca.debian.org/debian/

(the round robins are listed at the top of the page).

Obviously you would want to choose a country that's close to you,
network-wise.

> Sometimes it works, sometimes it doesn't. The problem appeared on all my
> servers running Debian 8 (hosted on Google Cloud Platform) the last couple of
> days. 

I have also experienced a MASSIVE problem with apt-get in the last week
or so.  I don't know if it's the same problem you're having, or totally
unrelated, but I am going to piggyback on your thread.

I have my problem at WORK only.  At work, I am trapped inside a firewalled
network.  I have no control over the firewall.  The entities who control
it are mysterious dark wizards who do not reveal themselves or their
secrets to mere mortals like me.

One of the past features of this firewall was a "transparent" (worst term
ever) HTTP proxy with forced authentication (user name and password).
I was able to plead to get an exception in place.  HTTP connections coming
from my desktop workstation's IP address weren't required to perform a
Windows Active Directory login to the HTTP proxy.  So I put a Squid proxy
on my workstation and told all of the Debian servers to use that for apt.

This worked well enough for years.

Now, starting last week, the problem is that when I try to apt-get update,
the files coming from security.debian.org HANG at 100% complete.  It
looks something like this:

root@ebase-fla:~# apt-get update
Hit http://ftp.us.debian.org wheezy Release.gpg
Hit http://ftp.us.debian.org wheezy-updates Release.gpg
Hit http://ftp.us.debian.org wheezy Release
Hit http://ftp.us.debian.org wheezy-updates Release
Hit http://ftp.us.debian.org wheezy/main Sources 
Hit http://ftp.us.debian.org wheezy/contrib Sources
Hit http://ftp.us.debian.org wheezy/non-free Sources   
Hit http://ftp.us.debian.org wheezy/main amd64 Packages
Hit http://ftp.us.debian.org wheezy/contrib amd64 Packages 
Hit http://ftp.us.debian.org wheezy/non-free amd64 Packages
Hit http://ftp.us.debian.org wheezy/contrib Translation-en 
Hit http://ftp.us.debian.org wheezy/main Translation-en
Hit http://ftp.us.debian.org wheezy/non-free Translation-en
Hit http://ftp.us.debian.org wheezy-updates/main Sources   
Hit http://ftp.us.debian.org wheezy-updates/contrib Sources
Hit http://ftp.us.debian.org wheezy-updates/non-free Sources   
Hit http://ftp.us.debian.org wheezy-updates/main amd64 Packages/DiffIndex
Hit http://ftp.us.debian.org wheezy-updates/contrib amd64 Packages 
Hit http://ftp.us.debian.org wheezy-updates/non-free amd64 Packages/DiffIndex  
Hit http://ftp.us.debian.org wheezy-updates/contrib Translation-en 
Hit http://ftp.us.debian.org wheezy-updates/main Translation-en/DiffIndex  
Hit http://ftp.us.debian.org wheezy-updates/non-free Translation-en/DiffIndex  
Hit http://security.debian.org wheezy/updates Release.gpg  
Hit http://security.debian.org wheezy/updates Release
Hit http://security.debian.org wheezy/updates/contrib Sources
Hit http://security.debian.org wheezy/updates/non-free Sources
Get:1 http://security.debian.org wheezy/updates/main amd64 Packages [426 kB]
Hit http://security.debian.org wheezy/updates/contrib amd64 Packages   
Hit http://security.debian.org wheezy/updates/non-free amd64 Packages
Hit http://security.debian.org wheezy/updates/contrib Translation-en
Hit http://security.debian.org wheezy/updates/non-free Translation-en  
Get:2 http://security.debian.org wheezy/updates/main Sources [276 kB]
Get:3 http://security.debian.org wheezy/updates/main amd64 Packages [426 kB]   
Ign http://security.debian.org wheezy/updates/main Translation-en  
Get:4 http://security.debian.org wheezy/updates/main Sources [276 kB]
Err http://security.debian.org wheezy/updates/main amd64 Packages
  404  Not Found [IP: 128.101.240.215 80]
Fetched

Re: Frequent Hash Sum mismatch on jessie-backports with apt-get update

[Brad Rogers]

On Thu, 18 Aug 2016 04:47:55 -0700 (PDT)
poiuytrez  wrote:

Hello poiuytrez,

>What's wrong and what would you recommend?

If it persists for more than a day or two, I usually do;

# rm -r /var/lib/apt/lists/*

Not elegant but it works.

-- 
 Regards  _
 / )   "The blindingly obvious is
/ _)radnever immediately apparent"
Watching the people get lairy
I Predict A Riot - Kaiser Chiefs


pgphUiBKdyiDA.pgp
Description: OpenPGP digital signature

Frequent Hash Sum mismatch on jessie-backports with apt-get update

[poiuytrez]

Hello, 

I have frequent errors when I do apt-get update: 
W: Failed to fetch 
http://http.debian.net/debian/dists/jessie-backports/main/source/Sources  Hash 
Sum mismatch

W: Failed to fetch 
http://http.debian.net/debian/dists/jessie-backports/main/i18n/Translation-en  
Hash Sum mismatch

W: Failed to fetch 
http://http.debian.net/debian/dists/jessie-backports/main/binary-amd64/PackagesIndex
  Hash Sum mismatch

Sometimes it works, sometimes it doesn't. The problem appeared on all my 
servers running Debian 8 (hosted on Google Cloud Platform) the last couple of 
days. 

What's wrong and what would you recommend?

Thank you for your help.
poiuytrez

PS: cat /etc/apt.sources.list
deb http://httpredir.debian.org/debian/ jessie main
deb http://security.debian.org/ jessie/updates main
deb http://httpredir.debian.org/debian/ jessie-updates main
deb http://http.debian.net/debian jessie main
deb-src http://http.debian.net/debian jessie main

cat /etc/apt/sources.list.d/backports.list
deb http://httpredir.debian.org/debian/ jessie-backports main
deb-src http://httpredir.debian.org/debian/ jessie-backports main
deb http://http.debian.net/debian jessie-backports main
deb-src http://http.debian.net/debian jessie-backports main

Re: howto avoid "apt-get update" going guru?

[Jimmy Johnson]

On 07/05/2016 12:55 AM, Harald Dunkel wrote:

Hi folks,

this morning I found "apt-get update" getting stuck due to an
unresponsive host:

# cat /etc/apt/sources.list
deb http://ftp.debian.org/debian sid main contrib non-free
deb-src http://ftp.debian.org/debian sid main contrib non-free

# apt-get update
Err:1 http://ftp.debian.org/debian sid InRelease
   Could not connect to klecker-ftp.debian.org:80 (130.89.148.12), connection 
timed out [IP: 2001:6b0:e:2018::173 80]
Reading package lists... Done
W: Failed to fetch http://ftp.debian.org/debian/dists/sid/InRelease  Could not 
connect to klecker-ftp.debian.org:80 (130.89.148.12), connection timed out [IP: 
2001:6b0:e:2018::173 80]
W: Some index files failed to download. They have been ignored, or old ones 
used instead.


I didn't mention klecker-ftp anywhere in my config files.
Its not on the round-robin list for ftp.debian.org either:

# host ftp.debian.org
ftp.debian.org has address 130.239.18.173
ftp.debian.org has address 130.239.18.165
ftp.debian.org has IPv6 address 2001:6b0:e:2018::165
ftp.debian.org has IPv6 address 2001:6b0:e:2018::173
ftp.debian.org mail is handled by 0 .


What would you suggest to avoid this kind of problem?


Every helpful comment is highly appreciated.
Regards
Harri


In testing/sid, it's a new apt. Try and using '#apt update' and no 
longer use apt-get.

--
Jimmy Johnson

Ubuntu 16.04 LTS - AMD64 - EXT4 at sda22
Registered Linux User #380263

Re: howto avoid "apt-get update" going guru?

[Mark Fletcher]

On Tue, 5 Jul 2016 at 17:02, Harald Dunkel <harald.dun...@aixigo.de> wrote:

> Hi folks,
>
> this morning I found "apt-get update" getting stuck due to an
> unresponsive host:
>
> # cat /etc/apt/sources.list
> deb http://ftp.debian.org/debian sid main contrib non-free
> deb-src http://ftp.debian.org/debian sid main contrib non-free
>
> # apt-get update
> Err:1 http://ftp.debian.org/debian sid InRelease
>   Could not connect to klecker-ftp.debian.org:80 (130.89.148.12),
> connection timed out [IP: 2001:6b0:e:2018::173 80]
> Reading package lists... Done
> W: Failed to fetch http://ftp.debian.org/debian/dists/sid/InRelease
> Could not connect to klecker-ftp.debian.org:80 (130.89.148.12),
> connection timed out [IP: 2001:6b0:e:2018::173 80]
> W: Some index files failed to download. They have been ignored, or old
> ones used instead.
>
>
> I didn't mention klecker-ftp anywhere in my config files.
> Its not on the round-robin list for ftp.debian.org either:
>
> # host ftp.debian.org
> ftp.debian.org has address 130.239.18.173
> ftp.debian.org has address 130.239.18.165
> ftp.debian.org has IPv6 address 2001:6b0:e:2018::165
> ftp.debian.org has IPv6 address 2001:6b0:e:2018::173
> ftp.debian.org mail is handled by 0 .
>
>
> What would you suggest to avoid this kind of problem?
>
>
> Every helpful comment is highly appreciated.
> Regards
> Harri
>
> I wonder if ftp.debian.org is redirecting you to a machine that isn't
available. If so, that should be temporary. You could try a country
specific mirror in the meantime.

Mark

howto avoid "apt-get update" going guru?

[Harald Dunkel]

Hi folks,

this morning I found "apt-get update" getting stuck due to an
unresponsive host:

# cat /etc/apt/sources.list
deb http://ftp.debian.org/debian sid main contrib non-free
deb-src http://ftp.debian.org/debian sid main contrib non-free

# apt-get update
Err:1 http://ftp.debian.org/debian sid InRelease
  Could not connect to klecker-ftp.debian.org:80 (130.89.148.12), connection 
timed out [IP: 2001:6b0:e:2018::173 80]
Reading package lists... Done
W: Failed to fetch http://ftp.debian.org/debian/dists/sid/InRelease  Could not 
connect to klecker-ftp.debian.org:80 (130.89.148.12), connection timed out [IP: 
2001:6b0:e:2018::173 80]
W: Some index files failed to download. They have been ignored, or old ones 
used instead.


I didn't mention klecker-ftp anywhere in my config files.
Its not on the round-robin list for ftp.debian.org either:

# host ftp.debian.org
ftp.debian.org has address 130.239.18.173
ftp.debian.org has address 130.239.18.165
ftp.debian.org has IPv6 address 2001:6b0:e:2018::165
ftp.debian.org has IPv6 address 2001:6b0:e:2018::173
ftp.debian.org mail is handled by 0 .


What would you suggest to avoid this kind of problem?


Every helpful comment is highly appreciated.
Regards
Harri

[SOLVED (sort of)]Re: apt-get update fails with sourceforge repo

[Michael Lange]

On Tue, 14 Jun 2016 00:13:43 +0200
Michael Lange  wrote:

> Ok, looks like it's a bug in Jessie's apt version.

Just for the record, in case anyone reads this:
I filed a bug report for apt about this issue
( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827365 ),
however it showed that a new feature in apt stops apt from accepting the
kind of hhtp(s) redirects sourceforge now uses. This at least explains
the initially odd observation that the sf repo still works with outdated
versions of apt.
So it looks like (at least for now) it is simply not possible to use
debian repositories hosted on sourceforge.
I added a note about this to the ticket at 
https://sourceforge.net/p/forge/site-support/12143/ , so they hopefully
will know what to do if they care to fix this.
For now obviously the best choice seems to move one's repos to a
different hosting service.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Vulcans believe peace should not depend on force.
-- Amanda, "Journey to Babel", stardate 3842.3

Re: apt-get update fails with sourceforge repo

[Michael Lange]

On Mon, 13 Jun 2016 19:57:08 +0200
Michael Lange <klappn...@freenet.de> wrote:

> Hi,
> 
> I just encountered an odd problem with a repo hosted on sourceforge,
> when calling apt-get update with this repo enabled in the sources.list
> I ended with a 301 error. Apparently this happens because sourceforge
> dropped its http service and now uses https exclusively. It took me a
> while to find that I had to install apt-transport-https to enable https
> support for apt-get and change the respective entry in sources.list
> from http:// to https:// , still it does not work however. Now on
> apt-get update I get the following error message:
> 
> Protocol "http" not supported or disabled in libcurl
> 
> This is obviously the same problem as described here:
> 
> https://sourceforge.net/p/forge/site-support/12143/
> 
> Oddly enough, with an old laptop that still runs a completely dated
> version of LMDE (no more updates for the last two years or so) after
> installing apt-transport-https and fixing the sources.list line it
> worked, but so far no luck with my up-to-date Jessie :(

Ok, looks like it's a bug in Jessie's apt version. I just tried with
testing, no luck either, but a differennt error: this time apt-get gives
me a 404 and claims the ../binary-amd64/Packages file is not found,
although when I browse the repo with firefox I can see that it's clearly
there. Seems like since the time when Jessie was still in testing stage
(that's what my dated LMDE is) they broke apt-get's https support :(

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

There is an order of things in this universe.
-- Apollo, "Who Mourns for Adonais?" stardate 3468.1

apt-get update fails with sourceforge repo

[Michael Lange]

Hi,

I just encountered an odd problem with a repo hosted on sourceforge, when
calling apt-get update with this repo enabled in the sources.list I ended
with a 301 error. Apparently this happens because sourceforge dropped its
http service and now uses https exclusively. It took me a while to find
that I had to install apt-transport-https to enable https support for
apt-get and change the respective entry in sources.list from http:// to
https:// , still it does not work however. Now on apt-get update I get the
following error message:

Protocol "http" not supported or disabled in libcurl

This is obviously the same problem as described here:

https://sourceforge.net/p/forge/site-support/12143/

Oddly enough, with an old laptop that still runs a completely dated
version of LMDE (no more updates for the last two years or so) after
installing apt-transport-https and fixing the sources.list line it
worked, but so far no luck with my up-to-date Jessie :(

Does anyone have an idea if there's something I can do about this?

TIA and best regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

[Doctors and Bartenders], We both get the same two kinds of customers
-- the living and the dying.
-- Dr. Boyce, "The Menagerie" ("The Cage"), stardate
   unknown

Re: Error apt-get update

[Camaleón]

El Fri, 27 May 2016 21:24:17 -0300, Willian Tola escribió:

(ese formato...)

> Alguien esta con problema de actualizacion en debian jessie
> 
> Err http://security.debian.org jessie/updates InRelease Err
> http://security.debian.org jessie/updates Release.gpg0 No se pudo
> iniciar la conexión con  security.debian.org:80
> (2801:82:80ff:8009:e61f:13ff:fe63:8e88). - connect (101: A rede está
> fora de alcance) [IP: 2801:82:80ff:8009:e61f:13ff:fe63:8e88 80]

Está usando IPv6 y salvo que tu infraestructura (local y remota) lo 
admita no va a funcionar. Prueba forzando el uso de IPv4:

apt-get update && apt-get -V upgrade -o Acquire::ForceIPv4=true

Saludos,

-- 
Camaleón

Error apt-get update

[Willian Tola]

Alguien esta con problema de actualizacion en debian jessie

Err http://security.debian.org jessie/updates InRelease
Err http://security.debian.org jessie/updates Release.gpg0
No se pudo iniciar la conexión con  security.debian.org:80
(2801:82:80ff:8009:e61f:13ff:fe63:8e88). - connect (101: A rede está fora
de alcance) [IP: 2801:82:80ff:8009:e61f:13ff:fe63:8e88 80]

Re: apt-get update jessie 32 bits : résolu

[andre_debian]

On Monday 02 May 2016 12:42:23 Sébastien NOBILI wrote:
> Le lundi 02 mai 2016 à 11:29, andre_deb...@numericable.fr a écrit :
> > "W: Aucune clé publique n'est disponible pour la/les clé(s) suivante(s) :
> > 1397BC53640DB551
> > W: Impossible de récupérer 
> > http://dl.google.com/linux/chrome/deb/dists/stable/Release  
> > Impossible de trouver l'entrée « main/binary-i386/Packages » 
> > attendue dans le fichier « Release » : 
> > ligne non valable dans sources.list ou fichier corrompu."
> > Voici mon sources.list :

> Le « sources.list » est éclaté dans plusieurs fichiers « *.list » dans le
> dossier « /etc/apt/sources.list.d/ ».
> Vu ton message d’erreur, j’imagine que tu dois avoir un « google*.list » ou
> « chrome*.list ».
> Sébastien

Oui, effectivement... c'est corrigé et résolu, grand merci.

André

Re: apt-get update jessie 32 bits

[Sébastien NOBILI]

Le lundi 02 mai 2016 à 11:29, andre_deb...@numericable.fr a écrit :
> "W: Aucune clé publique n'est disponible pour la/les clé(s) suivante(s) :
> 1397BC53640DB551
> W: Impossible de récupérer 
> http://dl.google.com/linux/chrome/deb/dists/stable/Release  
> Impossible de trouver l'entrée « main/binary-i386/Packages » 
> attendue dans le fichier « Release » : 
> ligne non valable dans sources.list ou fichier corrompu."
> 
> Voici mon sources.list :

Le « sources.list » est éclaté dans plusieurs fichiers « *.list » dans le
dossier « /etc/apt/sources.list.d/ ».

Vu ton message d’erreur, j’imagine que tu dois avoir un « google*.list » ou
« chrome*.list ».

Sébastien