Alexis PiKo a �crit : > Fraide Hache a �crit : > >> Charles Plessy wrote: >> >>> On Sun, Aug 22, 2004 at 03:24:10AM +0200, Alexis PiKo wrote : >>> >>> >>>> Cel� fait combien de temps qu'ils ont commenc� � le mettre dans la >>>> sid ? >>> >>> >>> >>> >>> Je ne suis pas 100% s�r d'avoir tout compris au syst�me de >>> g�n�ration de .debs � partir des sources, mais il me semble que, vu le >>> gel tr�s prochain de sarge, vu les bugs � fixer et certaines >>> transitions � effectuer, les machines d�di�es � la construction des >>> paquet ont en ce moment une queue digne de l'�re Brejnev. >>> >>> De plus, il y a un syst�me de priorit�s, et je suppose que >>> pour KDE, les responsables ont eu la sagesse de mettre urgency=low, � >>> moins que justement l'objectif soit de rentrer dans sarge. >> >> >> >> Nouvelles hebdomadaires Debian >> http://www.debian.org/News/weekly/2004/32/ >> Nouvelles hebdomadaires Debian - 17 ao�t 2004 >> >> .../... >> >> Quelle version de KDE pour Sarge ? Le co-responsable de version Steve >> Langasek s'est [36]plaint d'un envoi de derni�re minute d'un certain >> nombre de paquets de KDE 3.3 dans unstable. Comme il consid�re qu'il >> n'est pas d�sirable d'avoir un m�lange de diff�rentes versions et >> qu'il est impossible d'avoir tout KDE 3.3 dans Sarge � temps pour la >> publication, il a conclu que le KDE de Sarge ne sera pas mis � jour >> depuis unstable et que les corrections sur les paquets li�s � KDE >> devraient �tre envoy�es dans testing-proposed-updates. Chris Cheney a >> [37]object� au jugement de Steve tandis que [38]Ben Burton et [39]Ren� >> Engelhard l'ont approuv�. Ren� a �galement [40]remarqu� que >> [41]kdelibs-data a � nouveau cr�� des conflits de fichiers avec >> [42]openoffice.org-mimelnk. >> >> 36. http://lists.debian.org/debian-release/2004/08/msg00222.html >> 37. http://lists.debian.org/debian-release/2004/08/msg00223.html >> 38. http://lists.debian.org/debian-release/2004/08/msg00224.html >> 39. http://lists.debian.org/debian-release/2004/08/msg00230.html >> 40. http://lists.debian.org/debian-release/2004/08/msg00228.html >> 41. http://packages.debian.org/kdelibs-data >> 42. http://packages.debian.org/openoffice.org-mimelnk >> >> ;-) >> > En clair je ne peux pas installer KDE 3.3 sur ma debian avant un bon > bout de temps... c'est ca ? > Mais je r�it�re ma question : N'est-il pas possible d'installer une > autre version de KDE avec des packages debian ?
cf une discusion sur debian.devel.release, voil� le 1er message et pour ceux que �a interesse de lire la suite : http://groups.google.fr/groups?dq=&hl=fr&lr=lang_en|lang_fr&ie=UTF-8&threadm=2vSCC-2v9-3%40gated-at.bofh.it&prev=/groups%3Fhl%3Dfr%26lr%3Dlang_en%257Clang_fr%26ie%3DUTF-8%26group%3Dlinux.debian.devel.release Yoann -------- Message original -------- Sujet: KDE 3.3 and sarge Date de renvoi: Sat, 14 Aug 2004 23:50:07 -0500 (CDT) De (renvoi): [email protected] Date: Sat, 14 Aug 2004 21:50:52 -0700 De: Steve Langasek <[EMAIL PROTECTED]> Copie: [email protected] Forums de discussion: gmane.linux.debian.devel.qt-kde,gmane.linux.debian.devel.release [Please cc: debian-release on replies.] As some of you probably already know, a number of packages from KDE 3.3 have been uploaded today to unstable. This upload of a major new upstream release was not discussed with the release team prior to upload; actually, it's caused quite a bit of consternation and generally made for a crappy day on account of the impact on the libtiff freeze. The problems for libtiff have, however, been sorted at this point. Consequently, this note is to let maintainers of KDE packages know that the release team does not plan to delay the freeze for KDE3.3. After discussing with Ben Burton, it is clear that allowing only part of KDE 3.3 into sarge so close to the freeze is likely to lead to new bugs, and that any attempt to get all of KDE3.3 into sarge at this point would unacceptably delay the release schedule. If you maintain KDE-related packages that still need to be updated for sarge, this means that you will need to upload your changes to testing-proposed-updates after discussing them with the release team first, because any packages built against unstable will have an unsatisfiable versioned dependency on kdelibs. You can thank Chris Cheney for this turn of events. I am aware that testing-proposed-updates will be needed for kdegraphics, kdelibs, and kdebase because of a combination of security fixes and the still outstanding requirement to get rid of libtiff3g for sarge. Ben Burton has already expressed his willingness to NMU these packages if necessary; Chris, if you are available to work on this yourself, I am of course happy to work with you to get these packages ready for sarge. These uploads will in any case have to wait for libtiff4 to reach sarge, which should happen in two to three days once the new libtiff3g package is built on all architectures. -- Steve Langasek postmodern programmer
