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-up
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'
On Fri, Apr 6, 2012 at 10:55 AM, Bob Proulx wrote:
> That is incorrect and the source of your problems. Remove those
> lines. Add these lines:
>
> deb http://ftp.us.debian.org/debian squeeze-updates main
> deb-src http://ftp.us.debian.org/debian squeeze-updates main
That fixed it! Thanks for th
On Friday 06 April 2012 18:42:51 MPR wrote:
> Last year I started getting errors when running apt-get update. The
> errors look like this:
>
> W: Failed to fetch
> http://volatile.debian.org/debian-volatile/dists/squeeze/volatile/main/sour
>ce/Sources.gz 404 Not Found [IP: 130.89.148.13 80]
>
> W:
On Fri, Apr 6, 2012 at 1:42 PM, MPR wrote:
>
> Last year I started getting errors when running apt-get update. The
> errors look like this:
>
> W: Failed to fetch
> http://volatile.debian.org/debian-volatile/dists/squeeze/volatile/main/source/Sources.gz
> 404 Not Found [IP: 130.89.148.13 80]
>
>
MPR wrote:
> Last year I started getting errors when running apt-get update. The
> errors look like this:
>
> W: Failed to fetch
> http://volatile.debian.org/debian-volatile/dists/squeeze/volatile/main/source/Sources.gz
> 404 Not Found [IP: 130.89.148.13 80]
Right. The Lenny volatile repositor
On Vi, 06 apr 12, 10:42:51, MPR wrote:
>
> Does anyone know how to fix this? I had not made any changes to the
> server to cause this and have just been living with it.
Volatile has been replaced with squeeze-updates
http://www.debian.org/volatile/
http://lists.debian.org/debian-volatile-announc
Last year I started getting errors when running apt-get update. The
errors look like this:
W: Failed to fetch
http://volatile.debian.org/debian-volatile/dists/squeeze/volatile/main/source/Sources.gz
404 Not Found [IP: 130.89.148.13 80]
W: Failed to fetch
http://volatile.debian.org/debian-volati
On Sunday 26 October 2008, L.V.Gandhi <[EMAIL PROTECTED]> wrote
about 'apt-get update error':
>*deb http://live.debian.net/debian/ etch main
>*to */etc/apt/sources.list.
Based on what I saw that http://live.debian.net/debian , they are not using
the pooled la
For debian-live, as said in
http://www.pendrivelinux.com/2007/05/31/create-your-own-live-linux-cd-or-usb-distribution/
I have added the following line
*deb http://live.debian.net/debian/ etch main
*to */etc/apt/sources.list.
But when I do apt-get update, I get following error
Err http://live.debia
Hi,
> One reply suggested the following:
> gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 6070D3A1
> gpg --export --armor 6070D3A1 | apt-key add -
>
> Another reply suggested:
> gpg --recv-key A70DAF536070D3A1
> gpg --export A70DAF536070D3A1|apt-key add -
>
> When I run the first line of either pa
The original message in this thread referred to this URL:
http://ftp.debian.org.
I'm having the same problem but the URL is security.debian.org.
One reply suggested the following:
gpg --keyserver wwwkeys.eu.pgp.net --recv-keys 6070D3A1
gpg --export --armor 6070D3A1 | apt-key add -
Another rep
Ishwar Rattan:
>
> Just saw this:
> W: GPG error: http://ftp.us.debian.org testing Release: The following
> signatures couldn't be verified because the public key is not available:
> NO_PUBKEY A70DAF536070D3A1
> W: You may want to run apt-get update to correct these problems
> #
>
> How do I fi
On Thu, 19 Feb 2004 22:51:02 +0530, Deboo wrote:
> I'm using debian woody. After reading an article in LG on apt (Issue 86 -
> Debian APT, part2), I wanted to try using some package from testing and I
> did as per the artile, putting 2 new lines for testing and unstable in
> sources.list. But afte
Wes Reneau wrote:
I've done this and mine worked, as I had the same problem once.
also you might just edit the lines in sources.list from stable to
testing or unstable and comment out the security line with a # mark.
One thing to keep in mind youre gonna be mixing up your version with
stabl
On Thursday 19 February 2004 10:21 am, Deboo wrote:
> I'm using debian woody. After reading an article in LG on apt (Issue 86 -
> Debian APT, part2), I wanted to try using some package from testing and I
> did as per the artile, putting 2 new lines for testing and unstable in
> sources.list. But af
I'm using debian woody. After reading an article in LG on apt (Issue 86 -
Debian APT, part2), I wanted to try using some package from testing and I
did as per the artile, putting 2 new lines for testing and unstable in
sources.list. But after I apt-get update, at the end, I get this output:
Readin
Err http://security.debian.org stable/updates/main Packages
Sub-process gzip returned an error code (1)
Get:4 http://security.debian.org stable/updates/main Release [110B]
Get:5 http://security.debian.org stable/updates/contrib Packages [2181B]
Get:6 http://security.debian.org stable/updates/cont
On Wed, Dec 18, 2002 at 03:04:11PM -0500, Steve wrote:
> On 12/18/2002 11:50 AM, Colin Watson pounded the keyboard with stubby
> fingers to type:
> >On Wed, Dec 18, 2002 at 09:33:18AM -0500, Steve wrote:
> >
> >>And these archives are found where?
> >
> >
> > http://lists.debian.org/debian-user/
>
On 12/18/2002 11:50 AM, Colin Watson pounded the keyboard with stubby
fingers to type:
On Wed, Dec 18, 2002 at 09:33:18AM -0500, Steve wrote:
And these archives are found where?
http://lists.debian.org/debian-user/
Thanks I'll look there, I searched my local archives for the past two week
On Wed, Dec 18, 2002 at 09:33:18AM -0500, Steve wrote:
> And these archives are found where?
http://lists.debian.org/debian-user/
--
Colin Watson [[EMAIL PROTECTED]]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Con
On 12/18/2002 5:04 AM, Rob Weir pounded the keyboard with stubby fingers
to type:
On Tue, Dec 17, 2002 at 08:22:50PM -0500, Steve wrote:
Hello, on adding testing to my source lists (I'm presently on stable), I
get the following error(s):
Reading Package Lists... Error!
E: Dynamic MMap ran out
On Tue, Dec 17, 2002 at 08:22:50PM -0500, Steve wrote:
> Hello, on adding testing to my source lists (I'm presently on stable), I
> get the following error(s):
>
> Reading Package Lists... Error!
> E: Dynamic MMap ran out of room
> E: Error occured while processing heimdal-dev (NewVersion1)
> E:
Hello, on adding testing to my source lists (I'm presently on stable), I get the
following error(s):
Reading Package Lists... Error!
E: Dynamic MMap ran out of room
E: Error occured while processing heimdal-dev (NewVersion1)
E: Problem with MergeList
/var/state/apt/lists/security.debian.org_debi
On Mon, 4 Dec 2000, Jim Frey wrote:
> On running apt-get update, I get the following error listing:
Upgrade to a nemer version..
Jason
Hello,
On running apt-get update, I get the following error listing:
Reading Package Lists . . . Error!
E: Dynamic MMap ran out of room
E: Error occured while processing squid (NewVersion1)
E: Problem with MergeList
/var/state/apt/lists/http.us.org_debian_dists_u
nstable_main_binary_i386_Packages
35 matches
Mail list logo
