Woody coraz bliżej

Zbliża się grudzień. Za oknami coraz chłodniej, coraz trudniej jest też wyjść z ciepłego domu do pracy… Pogorszenie pogody jest chyba dobrą wymówką na zostanie w łóżku, wzięcie klawiatury do rąk i poprawianie błędów w niektórych pakietach Debiana. Jest to tym bardziej wskazane, że dobiega końca pierwsza faza zamrażania (słowo zdecydowanie na czasie) tej dystrybucji.
Jeśli w ciągu najbliższych dni nie zostanie poprawiona część poważnych błędów w niektórych pakietach, mają one duże szanse na wyrzucenie z nowego Debiana. Więcej informacji na ten temat, jak również częściową listę problematycznych programów, znajdziecie poniżej…

  Date: Mon, 19 Nov 2001 21:10:09 +1000  From: Anthony Towns   To: debian-devel-announce@lists.debian.org  Subject: Freeze Update [2001/11/19]    Hello world,    We're almost into the last week for uploads of base packages. If there're  outstanding bugs you'd like to see have some chance of getting fixed,  upload now.    Likewise, we're getting into the last seven days for making sure standard  and task packages get included in the woody release. At the moment,  many many packages look like they'll need to be removed, notably gpm (on  which packages such as jed, links, mc, pdmenu, vim, and w3m depend), lyx,  mutt, cvs, procmail, apache, gnuplot, lincity, mime-support, mozilla,  openssh, postgresql, strace, tetex-base and tetex-bin [0]. People who  can fix these bugs and care about those packages are encouraged to send  in patches or upload fixed packages [1].    The following (source) packages have been removed from woody / testing  or will be over the next couple of days:            * scm (buggy, old version depends on rx to be removed)          * gnucash (doesn't build, old version depends on old scm)          * swi-prolog (orphaned, doesn't build, buggy)          * ucbmpeg (orphaned, doesn't build)          * tkgofer (doesn't build)          * lilypond (doesn't build)          * alsaconf-0.4 (broken: alsa-base dependency conflicts with ac-0.4)          * skam (doesn't build)          * bock (doesn't build)          * pysol (doesn't include source - #118126, python policy)          * pysol-cardsets (depends on pysol)          * junior-games-card (depends on pysol)          * python-imaging (python policy, new deps on buggy sane-backends)          * sketch (buggy, depends on python-imaging)          * liboo2cx11 (liboo2cx11-dev deps oo2c, oo2c conflicts liboo2cx11-dev)          * voberon (voberon-dev deps liboo2cx11-dev and oo2c)    If the appropriate bugs and dependencies are resolved while new packages  are allowed for the appropriate priority, those packages will be accepted  back into woody.    Maintainers and folks interested in QA are encouraged to look over:            Uninstallable packages in testing:                  http://ftp-master.debian.org/testing/testing_probs.html            Out of date packages in testing:                  http://ftp-master.debian.org/testing/testing_outdate.txt            Uninstallable packages in unstable:                  http://ftp-master.debian.org/testing/unstable_probs.html            Out of date packages in unstable:                  http://ftp-master.debian.org/testing/unstable_outdate.txt            Build logs, statistics, etc:                  http://buildd.debian.org/            Problems getting packages into testing:                  http://ftp-master.debian.org/testing/update_excuses.html    The first two lists *should* be empty by release time (they're *all*  RC bugs of one sort or another), but are a long way off that right now.  Out of date packages in testing can be fixed by uploading a current  package to unstable (if the version in unstable is releasable), or to  woody-proposed-updates (otherwise). Packages on those lists are candiates  for removal, especially ones that affect i386 (and thus the majority  of users).    The latter list should help you get some handle on why your package  isn't getting into testing. In particular the "Depends: foo bar" lines  should be of interest, if your package is being held out because of bugs  in other packages.    Cheers,  aj    [0] Listed by source package. What a wonderful excuse for you to use the      nifty new `http://bugs.debian.org/src:gpm' urls to look them up.    [1] Some unofficial NMU guidelines that are a little simpler than the ones      in the developers-reference are at:                 http://people.debian.org/~ajt/nmus.txt        They're not official, so use some discretion and judgement rather      than blindly following them. It's probably a good idea to check the      vacation field in db.debian.org of the maintainer of the package      you're considering NMUing. Consequently, it's probably a good idea      to list any special NMU requirements you might want paid attention      to in said vacation field.    --   Anthony Towns    I don't speak for anyone save myself. GPG signed mail preferred.     "Security here. Yes, maam. Yes. Groucho glasses. Yes, we're on it.     C'mon, guys. Somebody gave an aardvark a nose-cut: somebody who      can't deal with deconstructionist humor. Code Blue."                  -- Mike Hoye,                        see http://azure.humbug.org.au/~aj/armadillos.txt    

Archiwalny news dodany przez użytkownika: honey.
Kliknij tutaj by zobaczyć archiwalne komentarze.