$ 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 &
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
...
; 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 s
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
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
The Wanderer wrote:
...
> I had enough trouble with this at the last Debian release, and came
> close enough to having trouble with it again this time, that I want to
> make sure the solution is available and findable for anyone else who may
> need it.
...
considering i use only testing in my ap
On Sun, Aug 15, 2021 at 04:40:31PM +0300, ellanios82 wrote:
>
> - bewildered , am getting stuff like this :
>
>
> GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY F942E0D4E1C726CD
>
- bewildered , am getting stuff like this :
GPG error: http://mxrepo.com/mx/repo bullseye InRelease: The
following signatures couldn't be verified because the public key is not
available: NO_PUBKEY F942E0D4E1C726CD
.
what to try please ??
thanks
.
On 8/15/21 4:08 AM, Greg Wooledge wrote:
Why not simply "apt update"?
: i have myself muddled : am getting "NO_PUBKEY"
- what to try, please ?
thank you
regards
.
kg ('$ 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-keyr
On Sat, 14 Aug 2021 20:02:51 -0400
The Wanderer wrote:
Hello The,
>As do I. It may be possible that this is what makes the difference.
I'm almost certain that is the root of it.
I recall having to do this at the previous Debian release. I forgot
that I'm now using a new machine built after t
On 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 l
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.
> 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 simpl
On Sat, Aug 14, 2021 at 08:52:19PM -0400, Polyna-Maude Racicot-Summerside wrote:
> I got a series of line saying N and one saying E:
>
> N: Repository 'http://security.debian.org buster/updates InRelease'
> changed its 'Suite' value from 'stable' to 'oldstable'
> N: Repository 'http://security.de
> 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', how
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 su
On 15-08-2021 10:02, The Wanderer wrote:
> On 2021-08-14 at 19:49, Brad Rogers wrote:
>
>> On Sat, 14 Aug 2021 19:28:32 -0400 Greg Wooledge
>> wrote:
>>
>> Hello Greg,
>>
>>> It will be interesting to see if anyone else reports the same
>>> problem you're seeing.
>>
>> I experienced it here.
>>
>
On 2021-08-14 at 19:49, Brad Rogers wrote:
> On Sat, 14 Aug 2021 19:28:32 -0400 Greg Wooledge
> wrote:
>
> Hello Greg,
>
>> It will be interesting to see if anyone else reports the same
>> problem you're seeing.
>
> I experienced it here.
>
> I usually use Synaptic to perform updates. Synapt
On Sat, 14 Aug 2021 19:28:32 -0400
Greg Wooledge wrote:
Hello Greg,
>It will be interesting to see if anyone else reports the same problem
>you're seeing.
I experienced it here.
I usually use Synaptic to perform updates. Synaptic put up the warning
message about the codename change, but I cou
On 2021-08-14 at 19:41, Greg Wooledge wrote:
> On Sat, Aug 14, 2021 at 07:26:44PM -0400, The Wanderer wrote:
>> The warnings I'd be OK with; I might even be OK with the errors,
>> except for the fact that they point not to anything with useful
>> information but to a place which doesn't actually
On Sat, Aug 14, 2021 at 07:26:44PM -0400, The Wanderer wrote:
> See bug #879786, and the various bugs that have been merged into it
> (listed near the very bottom, IIRC).
Man, some people have the most *bizarre* setups. And then when someone
points it out, they act all confused. :-/
Most of the
On Sat, Aug 14, 2021 at 07:12:30PM -0400, The Wanderer wrote:
> Maybe somehow I'm running an older apt-get version than what has the
> fix(es)? But as far as I know that's shipped in the 'apt' package, and I
> have that at version 2.2.4, which is what's currently in both stable and
> testing (unsur
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 sm
er 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 ha
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
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 o
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
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"
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
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.
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
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
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
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 suf
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 configur
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.
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
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$
ckaging/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
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
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 hav
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
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
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 hand
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
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 a
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://sec
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
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
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 (Si
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 pa
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
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
Sven Joachim 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:
>>
>> =
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
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
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
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
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
age 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 mess
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
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
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
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
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
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.
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
>
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
Verbatim command, verbatim message and verbatim sources.list, please.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
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?
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
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 a
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 Dea
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
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'
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
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
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
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 apparen
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
> >
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
fu
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
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 obviou
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
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
On Tue, 5 Jul 2016 at 17:02, 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 htt
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.
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 fe
On Mon, 13 Jun 2016 19:57:08 +0200
Michael Lange 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 sourceforg
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
On Tuesday 19 April 2016 07:23:23 Abdelkader Belahcene wrote:
> HI,
> I got the entire site from debian and ubuntu ( with apt-mirror) (not
> necessary stable),
> sometimes there is a problem of the cheksum, I want to disable the
> check sum,
> in apt-get update command.
>
HI,
I got the entire site from debian and ubuntu ( with apt-mirror) (not
necessary stable),
sometimes there is a problem of the cheksum, I want to disable the check
sum,
in apt-get update command.
How to tell apt-get to ignore the checksum.
thanks a lot
On Sat, November 28, 2015 11:18 pm, Charles Kroeger wrote:
> Ah, thanks so much..the offending q directory was in there (///lists) so
> I just deleted that instead, but all is now well.
If you delete the entire directory, it is rebuilt automatically as soon as
you execute "apt-get upd
On Sun, 29 Nov 2015 05:20:01 +0100
rlhar...@oplink.net wrote:
> On Sat, November 28, 2015 8:50 pm, Charles Kroeger wrote:
> > I was hoping someone might know what this message means after running
> > apt-get update:
> ...
> > Reading package lists... Done
> > W
On Sat, November 28, 2015 8:50 pm, Charles Kroeger wrote:
> I was hoping someone might know what this message means after running
> apt-get update:
...
> Reading package lists... Done
> W: Problem unlinking the file q - Clean (21: Is a directory)
Now and then something gets corrupted
I was hoping someone might know what this message means after running apt-get
update:
Reading package lists... Done
W: Problem unlinking the file q - Clean (21: Is a directory)
I cannot find any directory named 21 or Clean. A search with dpkg -l | grep q
Clean or 21 turns
On Mon, 12 Oct 2015 16:20:11 -0400, Ed Jabbour wrote:
> On Monday, October 12, 2015 02:34:25 AM Reco wrote:
> > Hi.
> >
> > On Sun, 11 Oct 2015 21:19:32 -0400
> >
> > Ed Jabbour wrote:
> > > Running Wheezy. Recently, update has been hanging on
> > > http://security.debian.org/ wheezy/upda
On 10/12/2015 01:20 PM, Ed Jabbour wrote:
Looks OK to me. I changed the backports repo from debian.net to
uchicago.edu and everything just flows. Now, if I can only find the
problem with security.debian.net, which as I understand it, has no
trustworthy mirrors
I'm not using backports, but for
On Monday, October 12, 2015 02:34:25 AM Reco wrote:
> Hi.
>
> On Sun, 11 Oct 2015 21:19:32 -0400
>
> Ed Jabbour wrote:
> > Running Wheezy. Recently, update has been hanging on
> > http://security.debian.org/ wheezy/updates main and
> > http://http.debian.net/debian wheezy-backports main.
1 - 100 of 771 matches
Mail list logo
