Sorry about the belated reply. For those who do not know, the URL for the X Strike Force (XSF) page is <http://master.debian.org/%7Ebranden/xsf.html>. I do my work on master.debian.org in /debian2/tmp/branden/; anyone with an account on master is welcome to peruse the files there. On Thu, Jun 04, 1998 at 08:57:18PM +0200, Richard Braakman wrote: > Package: xbase > Maintainer: Branden Robinson <branden@debian.org> > 22329 Patch for #20685 prevents talk working > 22422 xbase: xterm and rxvt sessions no longer logged [HELP] The above two bugs are merged. Please see the XSF page for more information. > 22668 TERM=xterm meaning has changed incompatibly [STRATEGY] Coordinate with ncurses-base maintainer to use XFree86's xterm entry for xterm, put our modified version into a new terminal type called xterm-debian, and change XTerm's app-defaults file to use xterm-debian by default. See the XSF page for more information. > 22877 xbase: xdm port, and X applications > 22878 xbase: xdm port, and X applications [HELP] The above two bugs are merged. These have been forwarded upstream but I haven't heard anything from XFree86 about them to date. Fixing them is beyond my knowledge. > 22928 New upstream security fix release [FIX] The patches have been applied (and they applied cleanly, except for ones that we had already done ourselves and had forwarded to them), but a build has not been done. > 23002 Problem With Fresh Install [HELP] I need some advice on this one. This person is complaining that the xbase-configure script (which is called by xbase's postinst) calls xf86config instead of XF86Setup when XF86Setup cannot be used because the font packages are in an unconfigured state. Our xfnt packages no longer ship the fonts.dir files, since they are created in the xfnt postinst's anyway, and this provided me an easy check to see if it was worth calling XF86Setup or not. Essentially, this person is complaining that the postinst for some xfnt packages isn't run before xbase's postinst. However, it is not reasonable to make xbase depend on any xfnt package. To make things worse, XF86Setup isn't even *in* xbase, it's in xserver-vga16, because it requires the VGA16 X server to run. This is a poor design. xbase-configure would be more properly called xserver-configure, and in slink when I jigsaw the upstream sources differen tly there's going to be an xserver-common package where xserver-configure, XF86Setup, et al. will go. It would not prudent to engineer such a radical change at this point. What should I do in the meantime? > Package: xlib6g > Maintainer: Branden Robinson <branden@debian.org> > 23122 typo in debian/rules [FIX] Already applied to the source tree, but no package has been built yet. Finally, #23274 has been reported against xlib6g since Richard sent his mail. It is release-critical, however I think I have already [FIXED] it. I'll find out when I do another build. -- G. Branden Robinson | I've made up my mind. Don't try to Purdue University | confuse me with the facts. branden@purdue.edu | -- Indiana Senator Earl Landgrebe http://www.ecn.purdue.edu/~branden/ |
Attachment:
pgpN6Ig8Zs7O2.pgp
Description: PGP signature