-----BEGIN PGP SIGNED MESSAGE-----

Hi there,

I somewhere read that you need more beta testing of frozen, so I
updated my system yesterday. Here's my report:

System: P100, 64 MB RAM, IBM 4,3 GB (DCAA), Quantum 1,2 GB (Fireball),
        Fritz! ISDN, Spea Mercury P64
OS:     WinNT and Debian 1.3.1r6
        The debian System was updated regulary, from 1.1 (?) on.

Steps:
   1) Made 2 CDs from ftp.de.debian.org, 04/21/98, one containing
      the main stuff, the other containing non-free, contrib and
      non-US
   2) Used autoup.sh to upgrade safely to libc6
   3) Used dselect with the "main" CD to upgrade
      Used dselect with "non-free, contrib, non-US" CD to upgrade
   4) Rebooted.

aka 1): How do you plan to create CDs? It was a bit messy when dselect
 first only updates the list of the "main" packages and complained
 because many of the old non-free etc. packages were missing some
 library after updating the list of available packages:
    xtar-dmotif, xtetris, tgif, gs-aladdin, xwpick, xpdf, xsnow
 were looking for "elf-x11r6lib" which was no more longer available.
 This let me end up in the dependency conflict situation we all
 like so much ;-)
 
aka 2): I used: autoup.sh,v 0.23 1998/03/26 15:31:10 for upgarding
 safely . I guess a newer version exists, but I was not able to find
 it (very slow connection yesterday, some servers unavailable).
 The process went fine (there were some warnings/errors but at the end
 everything seemed to be ok). 
 What I missed here were the last lines of the autoup.sh-file
 displayed (about rebooting and recreation of wtmp/utmp).
 Does dpkg really depend on libstdc++ ?

aka 3): I do not know if my autoup.sh-script was outdated, but the
 first thing (after more or less resolving all dependency problems) I
 ran into was trouble with slang. It was the first package dselect
 wanted to install (lines wrapped):

  :  Looking for part 1 of slang0.99.38 ... /cdrom/debian/stable/\
         binary-i386/libs/slang0.99.38_0.99.38-2.18.deb
  :  Running dpkg -iB for slang0.99.38 ...
  :  dpkg: regarding .../slang0.99.38_0.99.38-2.18.deb containing\
         slang0.99.38:
  :   slang0.99.38 conflicts with slang0.99.34 (<< 0.99.38-2.3)
  :      slang0.99.34 (version 0.99.38-2) is installed.
  :  dpkg: error processing /cdrom/debian/stable/binary-i386/libs/\
         slang0.99.38_0.99.38-2.18.deb (--install):
  :   conflicting packages - not installing slang0.99.38
  
 After that, dselect did not work any more, I had to deinstall
 slang0.99.34 and the install slang0.99.38 by hand. Then dselect was
 fine again...

 Then there were many small problems like:
   Unpacking doc-base (from .../doc/doc-base_0.5.deb) ...
      /var/lib/dpkg/tmp.ci/preinst: `cleanup-old-bug': not a valid identifier
   libcompfaceg1 conflicts with compface (<= 89.11.11-10)
      compface (version 89.11.11-9) is installed.
   libgpmg1 conflicts with libgpm1 (<< 1.12-3)
     libgpm1 (version 1.10-6) is installed.
   The wu-ftpd error (manpage ftpd).
 but most of them disappeared after the second or third run of
 "Install".

 The biggest problems I had were:
    e2fsprogs, e2fslibsg, quota: Completely broken dependency scheme.
      quota wants e2fslibsg, e2fsprogs providesit, quota doesn't want
      e2fsprogs provided version and so on. There were other packages
      involved in this, too, but most of them suddenly installed
      fine. quota didn't. I now have e2fsprogs installed and quota
      with --force-depends. Did not yet check if it works.
    emacs20, emacs19, emacs, emacsec-common, elib: What the heck are
      you doing here? It is absolutely unclear which to install!? I
      first tried emacs20/emacsen-common/elib but ran into trouble
      when byte-compiling elib. Then I tried emacs (there is no
      emacs19 package although some other(s?) depends on it), but
      emacsen-common and elib do not like him. This is, at least, a
      "tricky thing"...
      I now have emacs-19.34 installed, but pcl-cvs is not working
      because of the missing elib. The package emacsen-common suggests
      that it is common for all emacs. Why doesn't it like mine?
      There has to be some more explanation. The small infos to emacs
      and emacs20 were: "GNU Emacs is the extensible self-documenting
      text editor." Thanks for that, but I knew it before. What I
      would like to have is some suggestion which to install (and
      why).

Suggestion:
  What dselect really needs is some more control over the priority of
  packages and the installation order.
  The problem is as follows: I have a debian 1.3.1r6 System with
  package A, version x, installed. Now I upgrade to frozen (2.0) and
  would like to have a package B which depends on A, version y > x!
  The new package A, which is to be installed _after_ B, has the
  required version number, but when B gets to be installed, dselect 
  barfs about the wrong version number of A (it only knows x!) and
  does not install B. Later, when it gets to A, A is installed and B
  will be installed on the second run!

  What debian needs is some more suggestions when it comes to packages
  that provide the same functionality (like the emacs thing above, but
  there are some more). And some good idea how the CDs are organized
  (see 1)).

Ok, it took about 4 hours (emacs20 was byte-compiling calc three
times ;-), but it seems to be stable now. Afterall, I'm very happy
with my frozen system (I upgraded another two weeks ago and it was a
mess because of the broken grep package!). And there are _many_ things
which I really like (and which I could find out before falling asleep
at my desk ;-). 

Thanks for this great system!

  Jonas

- -- 
 "OS/2?  Hah.  I've got Linux.  What a cool name"  (Linus Torvalds)



-----BEGIN PGP SIGNATURE-----
Version: 2.6.3i
Charset: noconv

iQCVAwUBNT3uvPx2qiHWGhZtAQEPFgQArhLNFUOE/+We32LVhFHSrGyHYqlVApWi
+aHW1rGD3e42wmK06VISGW492K2RKRP3wJ/5lMC/tX4gU2X6bzH4CWJhTiqlXc9h
htP68FK3KR+kLMUwir5nle6tuy6QQ8QCbbUmqEsbf8zop1eCuMBSHpAJH9oDUpiC
6PbIkLCJoDk=
=zMQo
-----END PGP SIGNATURE-----


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to