'sudo apt-get update' stall/error

$ 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 &

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

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

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

; 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 >

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

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

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

n '/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 > > &g

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

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

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

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 >

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

 - 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

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

oremove > 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 br

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

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

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

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

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

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.

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

> 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

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

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

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

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 *

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

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

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

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

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

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.

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

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

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

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

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

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

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

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

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

d 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 goe

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

e 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 le

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

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

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

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 pack

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

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

Re: apt-get update release expired

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

Re: apt-get update release expired

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

apt-get update release expired

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 ? Cordial

Re: error while doing apt-get update

r 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

Re: error while doing apt-get update

0 - 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

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.

Re: error while doing apt-get update

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

Re: error while doing apt-get update

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

error while doing apt-get update

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

Re: Output from apt-get update.

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

Re: Output from apt-get update.

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

Correct: Re: Output from apt-get update.

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 fr

Re: Output from apt-get update.

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 >

Re: Output from apt-get update.

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$

Re: Output from apt-get update.

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 h

Re: Output from apt-get update.

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

Re: Output from apt-get update.

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

Re: Output from apt-get update.

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.

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

Re: apt-get update error

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

Re: apt-get update error

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? >

Re: apt-get update error

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

Re: apt-get update error

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

Re: apt-get update error

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

apt-get update error

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

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

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

[SOLVED] Re: apt-get update hangs forever

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

Re: apt-get update hangs forever

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

apt-get update hangs forever

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

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: >> >> ==

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

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

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/debi

apt-get update on sid: Hash Sum mismatch

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

Re: Problem using "apt-get update"

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* T

Re: Problem using "apt-get update"

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

Re: Problem using "apt-get update"

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 w

Re: Problem using "apt-get update"

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 co

Re: Problem using "apt-get update"

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 m

Re: Problem using "apt-get update"

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"

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://manpage

Re: Problem using "apt-get update"

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 mess

Re: Problem using "apt-get update"

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

Re: Problem using "apt-get update"

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 >

Re: Problem using "apt-get update"

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 wo

Re: Problem using "apt-get update"

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

Problem using "apt-get update"

://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

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:

Re: apt-get update error

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: >>>

Re: apt-get update error

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

Re: apt-get update error

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

apt-get update error

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

Re: apt-get update

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 p

apt-get update

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

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

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

apt-secure / apt-get update gpg signature invalid

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

Error with apt-get update

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

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

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

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

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

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

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

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

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 mir

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

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 _ / )

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

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

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

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 contri

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

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

howto avoid "apt-get update" going guru?

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.

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

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

Re: apt-get update fails with sourceforge repo

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

apt-get update fails with sourceforge repo

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

Re: Error apt-get update

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

Error apt-get update

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

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

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

Re: apt-get update jessie 32 bits

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 « 

  1   2   3   4   5   6   7   8   9   10   >