Hola Gonzalo,
He cambiado los repositorios con alguna dificultad con las xwindow. al final he
desinstalado el xserver-xorg, que era el que me daba los problemas y luego lo
he vuelto a instalar y asi me ha funcionado.
Saludos y gracias por todo.
version numbering scheme has changed), which causes problems
with older dpkgs.
and now dpkg won't run because of the problem. How do I work around this?
Delete available for now? Thanks for any help!
I recently did an 1.1-1.2 upgrade. When I encountered this problem, I
removed the offending entries
After a trouble-free complete 1.2 install on a new laptop, I began the
process of upgrading my 1.1 box. dpkg and dselect have broken after
the list of available packages is updated:
log
Uncompressing
/u/dna/usr1/people/nathan/src/debian/stable/binary-i386/Packages.gz
... done.
Replacing
Well, I upgraded, from 1.1 to 1.2 (Cheap Bytes CDROM). I did the base
first, and that worked fine. The rest, however, did not go quite so well.
Tcsh refused to upgrade: I'll figure out what's wrong there one of these
days. I'm fairly sure I did not mark maelstrom for removal, but it's just
a
From: [EMAIL PROTECTED]
...
While I'm at it, XF86Config -- I've notice this odd behavior while configuring
X windows, if I specify the memory of the video card as it should be, the
screen is all screwed up for all resolutions. However, if I specify the memory
at twice what it is, then all
are writing about when upgrading
1.1 - 1.2.
Keeping in step with the development team has it's advantages 8-)
One reason may be that I just don't have as many packages installed,
but I was wondering if anybody had any other explainations as to why many
small incremental upgrades over the months
From: Rick Macdonald [EMAIL PROTECTED]
I've been living off the unstable tree for almost a year. Back when the
version was 0.95r6 or something like that.
I really haven't had any problems to speak about, and certainly
not all the problems that people are writing about when upgrading
1.1
One reason may be that I just don't have as many packages installed,
but I was wondering if anybody had any other explainations as to why many
small incremental upgrades over the months seems to be more stable (in the
sense of installations not breaking) than making larger leaps from
point
that people are writing about when upgrading
1.1 - 1.2.
One reason may be that I just don't have as many packages installed,
but I was wondering if anybody had any other explainations as to why many
small incremental upgrades over the months seems to be more stable (in the
sense
I've been living off the unstable tree for almost a year. Back when the
version was 0.95r6 or something like that.
I really haven't had any problems to speak about, and certainly
not all the problems that people are writing about when upgrading
1.1 - 1.2.
One reason may be that I just don't
Daniel S. Barclay writes:
From: [EMAIL PROTECTED]
I'm using the InfoMagic CDrom set (Dec 96) to upgrade. Here are some notes:
3) several packages have 2 versions and dselect happily installs both
versions without trying to distinguish between them. And because of the
From: [EMAIL PROTECTED]
...
I'm using the InfoMagic CDrom set (Dec 96) to upgrade. Here are some notes:
...
3) several packages have 2 versions and dselect happily installs both
versions without trying to distinguish between them. And because of the
directory order (checked with 'ls -U'),
On Mon, 30 Dec 1996, Daniel S. Barclay wrote:
If you return to dselect to install other things, will it leave these
packages alone, or will it try to upgrade/downgrade these?
You can insure that dselect leaves them alone, by marking them with an
H. This will hold off any action on those
I didn't see any follow-ups on this one so here I go...
[Klippa, klapp, kluppit]
4) In the configuration mode of dselect, I needed to use the 'Z'
parameter to move to the background and examine configuration
files. The first package I tried this on was 'xntp'. After I was
finished
To answer myself and inform the folks on this list
I'd like to suggest that an option be added to the conflict list of dselect.
This option would allow one to pull-up the Packages description on a
After digging around, I found the I/i key did the trick for above! A big
_thanks_ to the
I'm using the InfoMagic CDrom set (Dec 96) to upgrade. Here are some notes:
1) I installed dpkg*.deb and ldso*.deb by hand (per messages from this list)
2) Xlib6 and xlib have conflicts which cause problems in dselect. I remember a
fix for this, but I can't find the message(s). Would someone
I broke down and got Debian on CD (InfoMagic Dec 96 issue). In trying to
install/upgrade, I ran into trouble 8-). Some of it was covered by the
messages from this list (hurray!) However, I'm not familar enough with the
programming tools to make an intellegent decision as to what to select in the
-BEGIN PGP SIGNED MESSAGE-
On Fri, 27 Dec 1996 [EMAIL PROTECTED] wrote:
5) mail/smartlist*.deb depends on base = 1.2.0-3 My system is being upgraded
and base = 1.1.0-14 ! So, where is the upgrade package for base? I haven't
been able to find it on the CDROM 8-(
Accoring to
I have 3 Intel machines running Debian 1.1. I have just upgraded
one of them to Debian 1.2. These are the minor problems I had
1) netstd and gcc required cpp, but did not tell me up front in dselect, but
at the time it tried to install. I fixed it with a manual dpkg -i
of cpp, then a
Ok, I'm back on-line.
I completely obliterated my debian installation through not reading the
documentation, but that's my problem. I am now working on 1.2 and would like to
thank everyone involved. It looks brilliant. I might even try and get X to
work...
A couple of little things
1)
On Tue, 17 Dec 1996, Matthew Swift wrote:
I have searched the Debian web page and the ftp hierarchy and been
unable to find any instructions on upgrading to 1.2 from 1.1, except
for a cryptic sentence in the README in the upgrades directory -- the
rest of the documentation there is
I have searched the Debian web page and the ftp hierarchy and been
unable to find any instructions on upgrading to 1.2 from 1.1, except
for a cryptic sentence in the README in the upgrades directory -- the
rest of the documentation there is outdated. What to do with the
files mentioned in the
I was greatly impressed with the relatively painless upgrade from 1.1 to
1.2. Good job, guys! However I did notice a couple of things which I
feel should be mentioned here:
1) The modules package overwrites /sbin/request-route without checking
to see if it has been modified by the user.
2) I
23 matches
Mail list logo
