Re: Status of Sarge Release Issues (Updated for June)
Hi, Marcelo E. Magallon wrote: On Sat, Jun 14, 2003 at 09:19:19PM +0200, Christoph Hellwig wrote: Stock OpenOffice seem to be able to embedd java applets into documents. RedHat nuked this. And we can't do the same because ... ??? We have done that (as Jan wrote.) Building needs Java anyhow... Regards, René -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 pgpd1WqgWzCoW.pgp Description: PGP signature
Re: Status of Sarge Release Issues (Updated for June)
On Sun, Jun 15, 2003 at 11:31:27PM +0200, Stefano Zacchiroli wrote: On Mon, Jun 02, 2003 at 02:38:47PM -0500, Drew Scott Daniels wrote: 2 ocaml status? http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg00986.html and bug 187155. Done? Done! OCaml 3.06 has successfully entered testing with the whole set of correlated packages, including the Postgres bindings. That said, depending on the upstream release plans for 3.07 and the advancement of sarge, i have planes to ship sarge with ocaml 3.07. I don't know if this will be possible dependency-wise in time, but upstream is planning to release ocaml 3.07 in late july if everything goes well, and it should not take us more than a month to have everything testing-ready, but again, this would depend on the avancement of sarge, and if it doesn't work out like that, ocaml 3.06 is now in testing, and will not be replaced by 3.07 until 3.07 is ready to enter testing. Friendly, Sven Luther
Status of Sarge Release Issues (Updated for June)
I didn't have much of a chance to update this report to be accurate to more than from a few days ago, but here it is as I'll likely be busy for the next few days. I'll try to post another message updating this stuff again next month. Note I haven't included the latest apt translation announcement or the much discussed menu system update announcement. I may not be pointing to the canonical locations. My guesses about priorities (1-3) of things to be done before Sarge is released is below with status information. I'm unsure as to where to get status information about some things in the second paragraph below (which is mainly about packages). 2 Installer TODO: http://cvs.debian.org/debian-installer/doc/TODO?rev=HEADcontent-type=text/vnd.viewcvs-markup 1 Debian installer Ports(and architectures?) status: http://people.debian.org/~mckinstry/ports-status.html http://lists.debian.org/debian-boot/2003/debian-boot-200305/msg00445.html says all ports not likely for sarge. http://lists.debian.org/debian-hurd/2003/debian-hurd-200305/msg00165.html talks about the hurd status. http://www.m17n.org/linux-sh/debian/packages.html seems to show that the super H (sh) is almost ready (all base compiled). 2 i386 libc support? (The large thread starting with http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg01895.html and going into the May archive talks about this). Do we have to wait for upstream to fix this? We want to stay compatible with other distributions which broke support for i386 in libc. http://lists.debian.org/debian-devel/2003/debian-devel-200305/msg00360.html describes the current situation. 1 gcc 3.3 (and g++ abi change?) transition status (versions with c102 suffix): http://people.debian.org/~rmurray/c++transition.html a search reveils: http://www.google.ca/search?as_q=c102num=100hl=enie=UTF-8oe=UTF-8btnG=Google+Searchas_epq=as_oq=as_eq=lr=as_ft=ias_filetype=as_qdr=allas_occt=anyas_dt=ias_sitesearch=packages.debian.orgsafe=images but this search is inaccurate. It only tells about the last crawled i386 package pages and includes packages that depend/recomend/suggest these i386 c102 packages. g++-3.2 and 3.3 have the same ABI. Transition should now be done to 3.3, but I beleive this means packages already compiled with 3.2 should still work. 2 Release Critical Bugs status: http://bugs.debian.org/release-critical/ 1 Problems in testing: http://ftp-master.debian.org/testing/testing_probs.html 2 IPV6 status status guesses: http://debdev.fabbione.net/cgi-bin/getstats 3 Debian Description Translation Projects (DDTP?) status: http://ddtp.debian.org/stats/ with an anoncment ( http://lists.debian.org/debian-devel-announce/2003/debian-devel-announce-200304/msg00015.html ) of an APT with translation support. Also: http://www.de.debian.org/international/l10n/ has status and ranked information about l10n and i18n in package Descriptions and templates. http://www.de.debian.org/doc/devel-manuals#i18n (in development) talks about howto do l10n, i18n, and m17n. http://lists.debian.org/debian-devel/2003/debian-devel-200305/msg00348.html discusses 4 basic goals. 2 UTF-8 or UTF8? http://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01520.html suggests a status site. http://lists.debian.org/debian-devel/2003/debian-devel-200305/msg02012.html talks about the current list of programs with i18n support disabled. 3 Package attributes: (Is done by tags and/or keywords. I'd like to include upstream trove information): http://deb-usability.alioth.debian.org/debtags/index.html has details of the tag Package browser, debtags package information and links to other package tag discussions/information. 3 Menu system update to conform to http://www.freedesktop.org/standards/menu/draft/menu-spec/menu-spec.html (as suggested in http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg00800.html ) The old update was abandonded but contributes to the new standard. 3 AMD x86-64 port? Several threads have been on debian-devel about this. i386 packages will aparently work for this arch. (Note: According to http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg01975.html AMD prefers the port to be called AMD64 and not x86-64 or alike) gcc-3.3 is a prerequisite says http://lists.debian.org/debian-devel/2003/debian-devel-200305/msg00360.html There is also a mailing list at http://lists.debian.org/debian-x86-64 to replace the old alioth mailing list. 2 flex transition: Silently a major revision of flex came into unstable and broke parts of openoffice.org, postgresql and many others. flex-old is now available so a slower transition can be allowed while not delaying sarge. 1 XFree86 status (sarge'll have 4.3.0, 4.2.1 was been abandonded due to gcc compilation issues, but is back): http://people.debian.org/~branden/xsf/ http://lists.debian.org/debian-x/2003/debian-x-200305/msg00134.html gives some status and information about how to help.
Re: Status of Sarge Release Issues (Updated for June)
Hi, Drew Scott Daniels wrote: 2 i386 libc support? (The large thread starting with http://lists.debian.org/debian-devel/2003/debian-devel-200304/msg01895.html and going into the May archive talks about this). Do we have to wait for upstream to fix this? We want to stay compatible with other distributions which broke support for i386 in libc. http://lists.debian.org/debian-devel/2003/debian-devel-200305/msg00360.html describes the current situation. eh? libc? libstdc++5... 2 flex transition: Silently a major revision of flex came into unstable and broke parts of openoffice.org, postgresql and many others. flex-old is now available so a slower transition can be allowed while not delaying sarge. .. when the people update their Build-Depends OOo is going to be fixed in 1.0.3-3 btw to work with the new flex... 3 Ooo (OpenOffice.org 1.0.3?): More info at least on the debian ooo mailing list, is there a status site? http://packages.qa.debian.org/o/openoffice.org.html shows some info That do you want to have wrt status? OOo is in testing now (1.0.3-2), 1.0.3-3 is in preparation.. René -- .''`. René Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73 pgpV7gousvFRb.pgp Description: PGP signature
