Lennart Sorensen wrote:
On Sun, Oct 31, 2004 at 10:38:52AM -0800, David Liontooth wrote:
Thanks, Len -- I didn't realize the upgrade was free, so that's very
useful.
It turns out the problem can't have been vmware after all, however, as the
same thing happened when I wasn't using it. I reverted
[EMAIL PROTECTED] wrote:
Hi,
I am able to login the amd64 box anymore, I have practically
lost it as a bootable one.
I do however have a lot of stuff (about 2GB) in
/var/cache/apt/archives/
My question is: After setting up a fresh system from CD,
how can I make the newly installed OS update itself
On Mon, Nov 01, 2004 at 10:43:20PM +0200, [EMAIL PROTECTED] wrote:
> Hi,
>
> I am able to login the amd64 box anymore, I have practically
> lost it as a bootable one.
>
> I do however have a lot of stuff (about 2GB) in
>
> /var/cache/apt/archives/
>
> My question is: After setting up a fresh sy
Hi,
I am able to login the amd64 box anymore, I have practically
lost it as a bootable one.
I do however have a lot of stuff (about 2GB) in
/var/cache/apt/archives/
My question is: After setting up a fresh system from CD,
how can I make the newly installed OS update itself from
these already downlo
Hi -
Using debian x86_64 2.6.8-9-amd64-k8, I think I see the same problem
that greg reported in
http://lists.debian.org/debian-amd64/2004/10/msg00315.html
It gets stranger, though:
1. The same memory stick reads and writes fine on my x86 sarge
laptop.
2. When I check to see if VFAT wor
On Sun, Oct 31, 2004 at 10:38:52AM -0800, David Liontooth wrote:
> Thanks, Len -- I didn't realize the upgrade was free, so that's very
> useful.
> It turns out the problem can't have been vmware after all, however, as the
> same thing happened when I wasn't using it. I reverted the most recent
>
On Mon, Nov 01, 2004 at 08:13:48PM +0100, Harald Dunkel wrote:
>
> Did you note that there are some Packages.gz files from
> 4 days ago, while the up-to-date Packages.gz.new are
> waiting to be renamed?
This seems to have been caused by the new archive key. The
secret keyring had a size of 0. T
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andreas Jochens wrote:
|
| pbuilder is trying to debootstrap a 'sarge' chroot environment.
| The gcc-3.4 archive does not have 'sarge' at the moment, only
| 'unstable'. This is why the debootstrap cannot download packages
| from 'sarge' and fails.
|
Pbu
On 04-Nov-01 16:55, Harald Dunkel wrote:
> Pbuilder is in the archive. I could manually download and
> install it. But at runtime (using the same server
> http://debian-amd64.alioth.debian.org/gcc-3.4) pbuilder
> complained about the Packages file and about Bash:
>
> Distribution is sarge.
> Build
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bob Proulx wrote:
| Harald Dunkel wrote:
|
|>pbuilder seems to be missing. There were no updates in the
|>amd64(gcc-3.4) pool for some days, anyway.
|
|
| Of course if the gcc-3.4 archive has a problem it needs to be fixed.
| But your note suggests that
Harald Dunkel wrote:
> pbuilder seems to be missing. There were no updates in the
> amd64(gcc-3.4) pool for some days, anyway.
Of course if the gcc-3.4 archive has a problem it needs to be fixed.
But your note suggests that you are just looking for a good pbuilder
package. So I will comment on th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi folks,
pbuilder seems to be missing. There were no updates in the
amd64(gcc-3.4) pool for some days, anyway.
Would you mind to take a look?
Many thanx
Harri
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Deb
On Tue, Oct 26, 2004 at 10:16:54PM +0200, Kurt Roeckx wrote:
> On Tue, Oct 26, 2004 at 03:51:48PM -0400, [EMAIL PROTECTED] wrote:
> >
> > So it appears there's a problem with TLS. I should note that this
> > problem started happening when libc6 was updated a couple of weeks ago.
> > I noticed tha
13 matches
Mail list logo
