Re: Problem installing rvplayer.deb
Shaleh wrote: The newest rvplayer in hamm will not install because it provides 'netscape' and some other package does too. What is happening here? I did not install the netscape deb package. Please sned me the exact error message you are getting. rvplayer does not Provides: netscape. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies package
On Thu, 9 Apr 1998, Nathan E Norman wrote: Hello, We have a ton of older PS/2 MCA machines around here, many with ESDI disks, others with the IBM SCSI HBA. Neither ESDI nor the IBM HBA are supported by the current rescue disks. So, in a not quite right state of mind, I decided I would make some boot floppies so that my coworkers, and anyone else with PS/2s out there could make use of my work rather than hack through the installs (the usual method) However, the boot-floppies system has got me confused. I'm not a Makefile wizard, so digging in there is a bit tough. The documentation is otherwise quite sparse (it says Edit the variables in the Makefile :) Here's the problem ... I need to use a special kernel image. How do I tell boot-floppies to use it? If I give it the path to my kernel-image package, it bombs out saying I don't know how to make your-kernel-image which is required by linux ... which isn't too meaningful to me. Doesn't it just want to unpack the kernel-image deb? I'm confused. I really don't need to remake the entire boot-disk set, just the rescue disk and the drivers disk. Someone want to slap me and set me straight here? If all you need to do is put a different kernel on the rescue floppy (which is what it sounds like) simply take the delivered image, mount it, and copy the kernel image from your custom package (the vmlinuz file) to the file linux on the mounted image. You can either dd the image to a floppy, mount the floppy (msdos) and copy the kernel, or you can mount the image file with one of the loop devices and do the replacement to the image file. Any future copies of that image file will have the new kernel. HTH, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: AUC-TeX in xemacs
On Thu, Apr 09, 1998 at 05:28:45PM -0500, Douglas Bates wrote: Fabien Ninoles [EMAIL PROTECTED] writes: Sorry but from upgrading to xemacs20 make AUC-TeX not seems to work well in xemacs, especially the key bindings and no menu.=20 Here's an extract from my .emacs file, I only put the relevant part. ;; ;; AUC-TeX settings ;; ;; (setq TeX-auto-save t) (setq TeX-parse-self t) (setq-default TeX-master nil) ;; XEmacs seems to forget everything about LaTeX and by example bind C-c C-e to tex-close-latex-block in place of LaTeX-environment who aren't even define (but exists in auctex/latex.elc). This old behavior miss me a lot... Can some one can give me an hint? Try using M-x load-library tex-site RET immediately after starting xemacs. If that works then put (require 'tex-site) in your .emacs file. I think the thing that has changed is that tex-site is no longer autoloaded in the 50debian-site.el file -- Douglas Bates[EMAIL PROTECTED] Statistics Department608/262-2598 University of Wisconsin - Madisonhttp://www.stat.wisc.edu/~bates/ That's the point... I try to load the file but after already open a TeX file. May be this should be mentionned somewhere. Or is it a bug (minor one)? -- Fabien Ninoles Running Debian/GNU Linux E-mail:[EMAIL PROTECTED] WebPage: http://www.callisto.si.usherb.ca/~94246757 WorkStation [available when connected!]: http://nightbird.tzone.org/ RSA PGP KEY [E3723845]: 1C C1 4F A6 EE E5 4D 99 4F 80 2D 2D 1F 85 C1 70 pgp7iwKWsNXEy.pgp Description: PGP signature
Re: FILESYSTEM CORRUPTION
[Following up on debian-devel] On Thu, 9 Apr 1998, John Goerzen wrote: I reported a similar bug 33 days ago against mount (#19039). It has been ignored by the maintainer of mount. I warned then, and I repeat today, that this bug CAN and DOES cause filesystem corruption! This bug relates to PCMCIA support. The PCMCIA refuses to unload if the network has not been switched off first, in some cases. However, the network refuses to switch off and the PCMCIA shutdown script hangs. I have found that if I remove the network card from the computer while it is in the PCMCIA shutdown script, it will go a bit further along. This happened to me last night, and I removed the card, and it got a but further and then hung. I finally shut off the computer, as this has happened before with little ill effects. However, when I turned it on today, my root filesystem was hozed so badly that the kernel gave a panic on boot. e2fsck would not fix it without removing files en masse. /usr was hozed seriously as well. I am looking at a full reinstall here. FORTUNATELY, /home was clean. (WHEW!) Had that one been messed up, I would be in a very serious situation. Anyway -- To the Mount maintainer -- LOOK AT THE BUG AND FIX IT. To the PCMCIA maintainer: This is a bug that you may not be aware of. Let me know if you need more details -- you probably do. But since I have to reinstall, it may be a few days. (speaking a 'mount' maintainer) I agree crash disks aren't fun at all, however from this email and from your previous bug report, I fail to see where 'mount' is involved in this infortunate process: 1/ the kernel still doesn't support forced umounts, so doesn't umount consequently ( unfortunatly); although umount has preliminary '--force' support (just try umount -f /something), it won't work until the kernel-side is ready. When you have run-away or zombies processes with open file descriptors, it's the kernel that prevents the unmounting. 2/ when rebooting with an unclean filesystem, the '/' is mounted r/o so e2fsck can be loaded to check all the filesystems BEFORE mount attempts to mount them r/w. The problem as you say involves PCMCIA (which fails to unload), you (for turning off the machine) and the kernel (for panicing), but why would mount be involved? Cordialement, -- - Vincent RENARDIAS [EMAIL PROTECTED],pipo.com,debian.org} - - Debian/GNU Linux: Pipo:WAW: - - http://www.fr.debian.orghttp://www.pipo.com http://www.waw.com - --- - La fonctionnalite Son Visuel vous delivre des avertissements visuels. - - [Message durant l'installation de Windows95]:wq -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: package pre-selections tool
Enrique -
I would like to update my package profiles. I have settled on just
two. Here are their statistics:
basic 33113 KB main=76 contrib=0 non-free=0
standard 122680 KB main=137 contrib=0 non-free=0
Here are my suggested description lines:
basic standalone system without development tools 34 MB
standard system: networking, C development, emacs, and TeX 123 MB
I should explain that for the original important profile, I selected
all the base and important packages, then accepted dselect's
suggestions about related packages. Apparently libc5, gcc, and
several X related packages were recommended by something. By removing
those, I have trimmed yesterday's important profile down to less
than 34 MB. I decided it was no longer worth while to attempt an even
smaller profile, and renamed it basic.
The two profiles are attached.
- Jim Van Zandt
begin 644 select-basic.gz
M'XL(.AZ+34``W-E;5C=UB87-I8P%F[EMAIL PROTECTED](UVRFY$B=SL[V
M[N]#($`R8Q!0+:2I[^-;,D2OW9-%JGDZQ:IO^!_FQ%,O+/EY3%H([EMAIL PROTECTED])
M7REK]W(U^3'_*+T15L?G![R2_;IA?NY_WCY;__^4,H-28=?\P_9J!!K?U#
MZ.K_SO@;[EMAIL PROTECTED]'G:.*]JU,MC'[EMAIL PROTECTED],U:QF?4$6F/[EMAIL
PROTECTED]
[EMAIL PROTECTED]:.QQ$2E=5\]-^$JVL_C==5T^I-.OGPQ4#.L9-F9CJ_F9
MY,'XK1\`\9ODW*'2,[EMAIL PROTECTED]@6T)-Q.L)N2D\T'OO=FV18?.I!
M`CP9EV6N)%\=:%T2H*MN.=98L?C,0Z!$%HT:7;C'PJKO54*=DSI]J3M\N.
MS$TP5LCOUB9\K))O;.L$#^.J^[EMAIL PROTECTED]/XC^F%$/+'5,3=:I
M'*4C22C;F.7=5EV#)5[`'04*+J*VNND;(E]%AW$\BSOAZ+7@(?T,.8
MD_5+D#/[EMAIL PROTECTED],P%(4@LLO#EEW,M52#X'J_*)%ENRRT(Y]I21A:%T:Q679@
[EMAIL PROTECTED]'[MD39OVT5UHB+[?.[%6^X7I3D#^
MUE;+'(ULNL41=T*30N,H0$2]0(VKT-8U3O\%V`D)$3/#9A[##EZ1GI\91_2
M0T,)SOG:969AT**V]\J;MM[ZATC5[J*G0':I)]ISHYU2K(M5#Q$05;K+,\
M47FHC5DJ([EMAIL PROTECTED],7W#D3HX^`?SC,''O*0V4GY.M[B10*5JO_\
M!2NX[EMAIL PROTECTED]FG?#'Z6G.#\5)8,Y69^J9]A0Q4MVSU1:/N7^'@6;*
M)[EMAIL PROTECTED]'4]NTI2^P=JH^^3M4]N%*?.C]D!F=YE3+
M+6`5OM:[EMAIL PROTECTED]I)GM20418:]FW03B]5[T^\N]UY`)2H`3IU%#
M]JOR0RHW%7MC4DB#('+^)1TM(5FZMQ6V?*LXZ!M])E6)]/+PWE^K9QB5
MX[^KO+,JI5:(OD[!=V'R8Y1Z?OSX^]\TGDQSJU%/H5BUMLCNQV90FL59NK
M4F5_JT4W%6OAUI_?!Q;+JFA]2_H:,XT0A7C;J/ADY;W^XGLU^'MN80)
MF)(V/[EMAIL PROTECTED];]9V`B;^4%^5K8IB'^?:M^8L55[A!4?7OZ0FT[J)XWW-A3[C_
MZZ_CYQ/,SW(6'L9W6BC6MBOAXP=3;[EMAIL PROTECTED]/W^B?X/[EMAIL
PROTECTED]@F+[A[G\Y/!
M\YG;`\+./'\0/\$W?\4/%U%?::17QGY%5%H9ON^IMK08N$SH=SOO_Y
[EMAIL PROTECTED]DG1\C;[EMAIL PROTECTED];C)O2EG`R/*TMF!MJZ-DW##VW)J6DX]4K:E
MDX`^/A?UX+T/R;*;NP=35I)\^/`+QZ0,U;T_PSLN*,\XOURF^CK3,K=S+
MD6FKZ.?Y(Y9BN6_9X=Y49WT;H%NT\3M]`TP[ESLUP`=J(/4Z41O)'EQ!IH
M3?TGPYW_BYL;6-XM`LO.!2JFB85,M+JU1UU)6]W2.;TYA\DB0;;2JS
M8)I\=X+5E/!,8PC43,BI2763VIN#77C.!37[-^H,F#MVP]-JUT)EBO\GYL
M(!XXG?G'JSGXJEM#MQZ!MWIL(SA(IJP/HR)MFR]/0#!W8UK3CY69^N[
MZ/U0)]%5\,$-19CQ,J1ZYSV6*J.NS^X2^I$03BTL)\WCF/)*4.C\8GNN
M@)JZ3/WBODXND)OAQPWS\LL+K#$VVDX3DA+:SDW7O!F7,%_./!Z,P,
MBNJ$.I(9UAJ6I';:DPBZ%A%YRS!C,Y`7Y9#GW35?P`(J^$L4#]XH_SM
MRB(SJ;9EP%M;0G1X0-+YDTM.[EMAIL PROTECTED]P^I,N%ZF;I53.N,5\7_9?#B
MB/=!4?=Z8EQRYM#*1CQ=QS!0G8,C;)SP[=,%=B@)U\(]I(:0BK5=VI)4Q'(
M!Y(%)!TJA7[%BHQ:[8D;L;[EMAIL PROTECTED][EMAIL PROTECTED]AY;SK1R1C3
M?3(1+)NLH%[M\/OWX?W77GDCP$YJ)PU5M+587]L4,S6I+I)@\-1\)U4ES@
MM5*A;![EMAIL PROTECTED]:[EMAIL PROTECTED]'E$2_MWZP%40AP1TT\:%23/=.D%A6_=
MN2^8.4C?1=#LKYR)O?25SM0F[C_)$7QS[EMAIL PROTECTED]',HFJV
MLK2?!_B([EMAIL PROTECTED]*.EK:*GY$0WPZ213\IRX8+X+8%MN
MG'GSC4,EO7$]Y5BG!)X?8\B4$XSD;![Y7V+?8.9W7`UP_CC`U2]!ABGF
MVUVZZ7NEGJ(U!PU3C36D)X.2,@[?^5K#II$-;%%/LTZ-3C2/N=\\7
M_M+ELN[N#JZ'[EMAIL PROTECTED](-2O!];W14'OG)ONBTG11#3^GT
M5.-H^K)A+PDY!7Z[13\KI-6D1)0P\7W`N/[EMAIL PROTECTED]/'R%1I/W851
M6JX]\\LI%-XMIHPCERR*WJ'\SQ`V:^(.`I/TUD?PRCO6];Y.9+L,V6;2
MY0._5:[EMAIL PROTECTED]I1F40U8X,K)!SPU/!28([3E11(,O.
M$`*;/7D^NA2DPT?A,T/CZ:@(2FX#X.\'VJ4)P8EV+CDUZAYG=)50Y
IWWZ+)1K)!B,\G8TZ`N0R8N+\X0)[EMAIL PROTECTED])[EMAIL
PROTECTED]//U_KM%-8D
`
end
begin 644 select-standard.gz
M'XL(.AZ+34``W-E;5C=US=%N9%R9`[EMAIL PROTECTED]@./97^':=(8J6_;:
M,Q?NQI==D(@!16!T`BK1__34HD2*[6[4.IL9?-TPT2^`_CT7X95(ZOG
M_)F+=O]ZO*ZC=C]_//WUI/1%VQ=]N7'DW9YA]/,.3I/_J_3^O/R_'U
MZ=]__B:4K).W^8?XV%N:W\3OWF7`E2J_,NT)C$*-$\;[EMAIL PROTECTED];I+T@
M([(TAL5C7(HBB-90@@^\8[,19(]R*K)O.+,O:X2AR'A7FI_TB6HE^-UV'
MB?_Y3I#ZP;6,VPHQJ*UF1P\FB]X;XC9VZR8?(BH$#??R7B4,I2HA6$)/
MQNE$]E$H.G8[YXDX^)-=Q(12/@591D=F?V2D=*H6Z($K+%B\92[0(DBC6X
M//^E:,=58KLE=+M2=MEX(X;X9L8K)?^TEFB0JRR;VS[#Z)!7E]VKY\%E
MBDWYI/!OT?N!XCE#Z)2;I#L-([EMAIL PROTECTED]@RF5APO*JN1#)=M0:!1MC0([EMAIL
PROTECTED]
M_E?([EMAIL PROTECTED]@?:9,2;[EMAIL PROTECTED];4Z[N`K!UPH:E^$E
M(6R(,,96P@(+.AX6+W'80MM)0F#1GWC)]5[)E8MR?LFB#(+;6QRY;T^9]
M+%:4^CWMM9J_U*Z$R1/:ZME248VW)\=W5KFPA(3`1M;T';1UC=/?T1-K
MU2.:%3;SY,:7%!CI\9F91_L$ID+GHJB%MC.*V]:O-UWD(.KZ(]L`K[E1G
M!UQR.G`GJGCW^W619Z@`SUHJ')@5@Z:#0L50NY3=E3B34DCD\25P^5
[EMAIL PROTECTED]06M1_?!`D1N(AO40IO5M`J0R\7H$8\T-#XJ:^;BX0Q
M90\1(M4M(VWQ4/I7,M%,UV#?/S0DWX+(,0E\9`^.O0J,9D/+9L#SD!*::`
MDW%/'*C/7?%P47'[EMAIL PROTECTED]([EMAIL PROTECTED];J_$/)ET)/*HI$HZ:UZX??8X
Re: Problem installing rvplayer.deb
Joey Hess wrote: Shaleh wrote: The newest rvplayer in hamm will not install because it provides 'netscape' and some other package does too. What is happening here? I did not install the netscape deb package. Please sned me the exact error message you are getting. rvplayer does not Provides: netscape. -- see shy jo Soory for doing it from memory (-; Reading database ... 37548 files and directories currently installed.) Preparing to replace rvplayer 5.0b3-4 (using rvplayer_5.0-1.deb) ... Unpacking replacement rvplayer ... dpkg: error processing rvplayer_5.0-1.deb (--install): trying to overwrite `/usr/lib/netscape', which is also in package acroread Update-menus: waiting for dpkg to finish (forking to background) Update-menus: (checking /var/lib/dpkg/lock) Errors were encountered while processing: rvplayer_5.0-1.deb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing rvplayer.deb
Shaleh wrote: Soory for doing it from memory (-; Reading database ... 37548 files and directories currently installed.) Preparing to replace rvplayer 5.0b3-4 (using rvplayer_5.0-1.deb) ... Unpacking replacement rvplayer ... dpkg: error processing rvplayer_5.0-1.deb (--install): trying to overwrite `/usr/lib/netscape', which is also in package acroread Update-menus: waiting for dpkg to finish (forking to background) Update-menus: (checking /var/lib/dpkg/lock) Errors were encountered while processing: rvplayer_5.0-1.deb Hmm, what version of acroread do you have installed? Both packages contain a /usr/lib/netscape/plugins/ directory, but that shouldn't create a problem. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing rvplayer.deb
Joey Hess wrote: Shaleh wrote: Soory for doing it from memory (-; Reading database ... 37548 files and directories currently installed.) Preparing to replace rvplayer 5.0b3-4 (using rvplayer_5.0-1.deb) ... Unpacking replacement rvplayer ... dpkg: error processing rvplayer_5.0-1.deb (--install): trying to overwrite `/usr/lib/netscape', which is also in package acroread Update-menus: waiting for dpkg to finish (forking to background) Update-menus: (checking /var/lib/dpkg/lock) Errors were encountered while processing: rvplayer_5.0-1.deb Hmm, what version of acroread do you have installed? Both packages contain a /usr/lib/netscape/plugins/ directory, but that shouldn't create a problem. -- see shy jo Acroread 3.0-1. BTW How did you respond before I sent my letter?? My time should be xntpd based now. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Problem installing rvplayer.deb
Shaleh wrote: Acroread 3.0-1. Well, we both have the same versions of acroread and rvplayer and I didn't experience this problem installing. I don't know what's causing this. BTW How did you respond before I sent my letter?? My time should be xntpd based now. Mine isn't. :-) -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies package
On Fri, 10 Apr 1998, Vincent Renardias wrote: : : On Thu, 9 Apr 1998, Nathan E Norman wrote: : : We have a ton of older PS/2 MCA machines around here, many with ESDI : disks, others with the IBM SCSI HBA. Neither ESDI nor the IBM HBA are : supported by the current rescue disks. : : The lastest boot disks from Debian 1.3 work just fine; I've used them for : installing on a MCA Laptop (ESDI drive) which I upgraded to : hamm-current immediatly after. : But I agree it's not a reason not to support MCA in hamm too. ;) : : Cordialement, But, they do not support the IBM MCA/SCSI Adaptor, which means you see the disconcerting No hard drives found message. -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies package
On Thu, 9 Apr 1998, Dale Scheetz wrote: : On Thu, 9 Apr 1998, Nathan E Norman wrote: : : Hello, : [ snip ] : If all you need to do is put a different kernel on the rescue floppy : (which is what it sounds like) simply take the delivered image, mount it, : and copy the kernel image from your custom package (the vmlinuz file) to : the file linux on the mounted image. : : You can either dd the image to a floppy, mount the floppy (msdos) and copy : the kernel, or you can mount the image file with one of the loop devices : and do the replacement to the image file. Any future copies of that image : file will have the new kernel. Yes, I know this. However, what people have been asking for is an image of the rescue disk, not a new kernel for the disk (it is difficult to run rdev.sh if you have no Linux system handy) Furthermore, it might become necessary to change the available modules (I honestly don't know whether this is the case), and I don't believe the rescue disk has device files for ESDI disks. They are /dev/ed[ab], correct? Vincent Renardias says the 1.3 boot disks support MCA (they do) and ESDI (I never found /dev/ed[ab] devices). No Debian boot disk supports IBM MCA/SCSI afaik. Finally, I'd really like to *know* how to build these things! Why is it so opaque? Thanks, -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: #19519: tmpreaper: Will not remove dirs
[ Please remove CC's of impertinent replies to the bugs address. ]
Summary: `tmpreaper' will not remove empty dirs because the atime
gets changed by `ls' or any touch of the directory. I've been asked
to implement an option to delete empty dirs with (= mtime+grace now).
There is some difficulty in programming this `mtime-mt-dir' option.
The problem is that it must first recurse down any subdirectories to
look for files to remove there, prior to attempting to remove the
directory itself. If there's any files there that get removed, the
mtime of that directory will be changed.
I'm afraid I'm just not knowledgeable enough to do this quickly. It
will require building a list of files and directories to remove prior
to recursing down the /tmp tree.
Perhaps it should be rewritten in `suid-perl' or `suidexec scsh'?
I would really appreciate it if a more experienced programmer would
spend an afternoon rewriting `tmpreaper', if you must have it right
away. Otherwise, expect it to take me a few weeks. I must study the
problem and learn not only the algorithm, but the data structure iff
I implement in `c'. Would someone assist me in designing the
program? I am unsure of how to approach the problem.
Q: Does anyone know if `ftw' is safe to use for this purpose, or does
it suffer from the same problems as `find ... -exec rm {} \;'?
(remind me to keep in mind that `scsh' ought to be checked for suid
safety as I learn how it operates.)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Upgrading from bo to hamm
LeRoy D. Cressy [EMAIL PROTECTED] writes: I question the purpose of leaving broken symbolic links when upgrading the libraries. For instance libreadline2 leaves the following broken links reported by ldconfig: Those symlinks are part of libreadline2-dev. If you upgrade to libreadline2-altdev, then the links will be fixed. Guy -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
error installing new mh.
Setting up mh (6.8.4-20) ... chmod: /usr/lib/mh/spopfi: No such file or directory dpkg: error processing mh (--install): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: debian/dists/frozen/contrib/binary-i386/net/rvplayer_5.0-1.deb mh DPKG ERROR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: How to install editor lisp files?
You should just include the .el file, without bytecompiling, in /usr/share/emacs/site-lisp/packagename/ If there's code you want every user to run on startup. you can create a file in /etc/emacs/site-start.d/packagename ideally it should only contain autoloads. The imporant section from /usr/doc/emacsen-common/debian-emacs-policy.gz: 5) Packages with only marginal emacs relevance Generally, if a normal package just contains some emacs helper files, and does not need to perform any byte-compilation or other emacs dependent activities upon installation (for performance or other reasons), then it is not necessary to specify a dependency on emacsen or any flavor of emacs, and the package may just include files located in the standard emacs add-on directories. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Number of Maintainers
Brian Bassett [EMAIL PROTECTED] writes: After both Manoj Srivastava and Bob Hilliard pointed out to me the faults in using the Maintainers file for determining the number of maintainers, I have decided to use the Debian PGP keyring. After deleting duplicate keys, the keyring says that there are 313 developers, making Q 8.85 and K 5. Brian You know what would be cool - if the www.debian.org homepage had a running count of the number of maintainers! That's Debian's biggest selling point, as far as I'm concerned. Cheers, - Jim pgpKezikvA920.pgp Description: PGP signature
Re: Debian Bug#20445 disagree
On Thursday, April 9, 1998, Brian White [EMAIL PROTECTED] I think that if somebody can get the 2.2 kernel source off of CD, build the kernel (hopefully as a debian package) and install it, they have the knowledge and the ability to download packages from the network using one of the many possibilities of dpkg, dselect, dftp, or another. What we lose is including packages that break either during installation or when run on a stock Hamm system. Since we are shipping a hamm CD, I believe that that CD should be as problem free as possible. If people start mixing things from different CDs, they have to realize things may not work out of the box. I must have missed the part of this conversation that had the facts in it... Exactly what 2.1.x-kernel-ready packages currently in hamm break parts of a 2.0.x system? For example, if modutils 2.1.71 works perfectly fine with 2.0.x kernels, and there are no outstanding bug reports against it related to that (a quick glance says there aren't), then there's no reason to go back to the 2.0.0 version. 2.0.x is our release priority - however I think having hamm ready for 2.2 kernels *without causing problems for 2.0.x users* is a good idea. Debian does have a bit of a reputation for packaging all the latest and greatest stuff. The original bug report mentioned these packages: ax25-utils smbfsx ncpfsx vold pciutils romfs ipportfw bridgex * Juan Cespedes mentioned that romfs works with 2.0.x with the included patches. In any case it does not hinder 2.0.x functionality. *crosses off list* * ax25-utils doesn't hinder 2.0.x functionality, and patches are available. *crosses off list* * pciutils doesn't hinder 2.0.x functionality. *crosses off list* * vold doesn't hinder 2.0.x functionality. *crosses off list* * ipportfw doesn't hinder 2.0.x functionality and has a supplied 2.0.x patch. *crosses off list* * bridgex doesn't hinder 2.0.x functionality and has a supplied 2.0.x patch. *crosses off list* That leaves us with smbfs/smbfsx and ncpfs/ncpfsx. Can someone verify that these packages coexist or that smbfsx/ncpfsx works with 2.0.x? I personally think non-interactively printing a message during installation like Warning - this package requires a 2.1.blah or later kernel to function. would be more than adequate. -- Robert Woodcock - [EMAIL PROTECTED] All I want is a warm bed and a kind word and unlimited power. -- Ashleigh Brilliant -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: jdk1.1-runtime
Corey Miller [EMAIL PROTECTED] writes: When I try to install jdk1.1-dev (I want to install JavaICQ, which makes use of the jdk), it says that it depends on jdk1.1-runtime. I was wondering where I could find this package? I looked in incoming, frozen, unstable, and even used the package search utility on www.debian.org. Thanks for you help, It got nuked when hamm was frozen (source is still in project/orphaned, I think, but the binary is gonzo) Stephen Zander [EMAIL PROTECTED] is working on uploading jdk1.1.5 - so I didn't bother with fixing 1.1.3. You can still get it from: ftp://ftp.jimpick.com/pub/debian/pkgs-old/jdk1.1/1.1.3.v2-1 Sorry for any inconvenience. Cheers, - Jim pgpAKlUEDo85e.pgp Description: PGP signature
Is this a bug in libc6?
Hi,
try running the following simple program:
#include stdio.h
void main(void)
{
FILE *fp;
fp = fopen(file.txt, r);
fclose(fp);
fclose(fp);
}
You'll see that it generates a segmentation fault and dumps core in
libc's code.
Try with an existing file.txt (touch file.txt) and later without a
file.txt (rm file.txt). In both cases it'll crash in fclose() (which
one depends on whether file.txt exists or not).
Can you reproduce this problem? If you can, then can you tell me if
fclose() is supposed to behave that way?
According to fclose's man page, it will return EOF and set errno to
EBADF if the argument is not an open stream.
Under libc5 is seems to crash only if file.txt does not exist.
Am I missing something here? Should I consider this a bug in libc?
This whole thing has made me waste a couple of days tracking down a
problem in the HylaFAX fax server sigh :-)
Thanks,
E.-
--
Eloy A. Paris
Information Technology Department
Rockwell Automation de Venezuela
Telephone: +58-2-9432311 Fax: +58-2-9431645
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is this a bug in libc6?
On 10 Apr 1998, Eloy A. Paris wrote:
Hi,
try running the following simple program:
#include stdio.h
void main(void)
{
FILE *fp;
fp = fopen(file.txt, r);
fclose(fp);
fclose(fp);
}
This is not valid. fclose's behavoir on a null fp is apparently not
defined, but exiting with error would be prefered to faulting. A double
fclose is just as bad as a double free() and is not a library error should
it fault or corrupt memory.
Jason
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: base-files 1.6 (source all) uploaded to master
Hi, Nicolás == Nicolás Lichtmaier [EMAIL PROTECTED] writes: I append my personal prompt setting scheme, in hopes this inspires someone else (any improvements greatly appreciated) Nicolás Uhh..! You must have lots of free time! Not really. The first modified date on these is March 23 1988. Over a decade, you can get to have fairly complex prompt setting schemes. I know what I like, and I have invested effort to get it. Ain't it grand, though? You should see what I have for Emacs customization ;-) manoj -- Cynic: n. a blackguard whose faulty vision sees things as they are, not as they ought to be. -- Ambrose Bierce Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Bug#20445 disagree
Hi, Add diald to the list of packages having a problem with 2.1.X kernels. I have downloaded the patch from the diald list archives, but even that failed for 2.1.94. manoj -- Please refrain from making me puke on my workstation. Alan Weiss ([EMAIL PROTECTED] Manoj Srivastava [EMAIL PROTECTED] http://www.datasync.com/%7Esrivasta/ Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: future development of doc-base
This discussion belongs to debian-doc, not debian-devel. Please send any follow ups _ONLY_ to debian-doc. Thanks, Chris -- Christian Schwarz [EMAIL PROTECTED], [EMAIL PROTECTED], Debian has a logo![EMAIL PROTECTED], [EMAIL PROTECTED] Check out the logo PGP-fp: 8F 61 EB 6D CF 23 CA D7 34 05 14 5C C8 DC 22 BA pages at http://fatman.mathematik.tu-muenchen.de/~schwarz/debian-logo/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: FILESYSTEM CORRUPTION
Vincent Renardias [EMAIL PROTECTED] writes: (speaking a 'mount' maintainer) I agree crash disks aren't fun at all, however from this email and from your previous bug report, I fail to see where 'mount' is involved in this infortunate process: Thanks for your reply, Vincent It would have been appreciated had you replied last month however :-) 1/ the kernel still doesn't support forced umounts, so doesn't umount consequently ( unfortunatly); although umount has preliminary '--force' support (just try umount -f /something), it won't work until the kernel-side is ready. When you have run-away or zombies processes with open file descriptors, it's the kernel that prevents the unmounting. In this case, it is a kernel bug (and a serious one). However, note that processes with open FDs are not the only problem. (Although they can be, I have experienced cases where things like ls hang waiting for an NFS that cannot be fulfilled. kill -9 will not kill them, and they will prevent it from being umounted later. Another kernel bug.) In my original bug report, I complained that if it tries to unmount a NFS-mounted partition, and cannot for whatever reason (server crashed, unreachable, etc.) it will hang and not umount local drives. Therefore, I believe it would be prudent, as a temporary workaround for the kernel bug, to umount all local drives before umounting network drives. It is generally not a big deal if a network drive doesn't get umounted anyway. 2/ when rebooting with an unclean filesystem, the '/' is mounted r/o so e2fsck can be loaded to check all the filesystems BEFORE mount attempts to mount them r/w. Yes. Not quite sure what this has to do with the bug report, but oh well :-) My root FS was hosed so bad that the kernel couldn't find init and paniced. The problem as you say involves PCMCIA (which fails to unload), you (for turning off the machine) and the kernel (for panicing), but why would mount be involved? There is also a separate PCMCIA issue. Unfortunately, I did not realize that the corruption occured until almost 24 hours later (I thought nothing of it at the time) and so I do not have details on the PCMCIA problem and I feel leery of reporting a bug against PCMCIA without information to back it up. I hope, however, that the PCMCIA maintainer will see these messages and at least be on the lookout for future occurances of these problems. I shall also make sure to get in-depth information when/if this occurs again (as far as PCMCIA is concerned). You are correct in saying that this latest problem is not mount's fault (I believe). The end result is the same as the mount/kernel issue -- filesystems do not get umounted and corruption can result. I think we have a problem with ordering... PCMCIA services are turned off before the network is turned off, apparently. This causes difficulty, for instance, if the laptop is acting as an NFS server, as mine does. (Great way to carry data around!) If I forget to umount it from the NFS client (my desktop machine), I can have two problems: * When I shutdown my desktop, it will hang trying to umount. * When I shutdown my laptop, it will hang trying to turn off PCMCIA. grr. Deadlock. :-( Regards, John Install it again Goerzen -- John Goerzen | Developing for Debian GNU/Linux (www.debian.org) Custom Programming | Debian GNU/Linux is a free replacement for [EMAIL PROTECTED]| DOS/Windows -- check it out at www.debian.org. -+-- uuencode - /vmlinux | mail -s Windows NT security fix [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Debian Bug#20445 disagree
On Thu, Apr 09, 1998 at 09:54:57PM +0200, Marcus Brinkmann wrote: On Thu, Apr 09, 1998 at 01:09:39PM -0400, Raul Miller wrote: Brian White [EMAIL PROTECTED] wrote: The subject in question is whether to include these packages in stable. unstable will include them for sure. I think they are appropriate for stable provided they are classifed as Extra. That is what the Extra priority is for, after all. I happen to agree. And we also need a 2.1.x Kernel package. Brian, here in Germany, every Megabyte you have to download is costing real money. A lot of money. Please put as much on the CD as possible. Declare it extra, put it in an unstable dir, put warnings all over the place, but please include it. Why not just include a tarball of the source rather than as a debian package. Then people can't complain that Debian messed something up since they did it all by themselves. To make the kernel-source package all they would have to do is download the diff.gz and do that dpkg-source, dpkg-buildpackage thing. If we have room for the 2.1 kernel I think we should put it on since it will save people downloading about 11MB (or 9.5? for the bz2 version). Adrian email: [EMAIL PROTECTED] | Debian Linux - www.debian.org http://www.poboxes.com/adrian.bridgett | 2.0 release soon - over 1800 PGP key available on public key servers | packages on a stable OS -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: foo
Processing commands for [EMAIL PROTECTED]: reassign 20909 dpkg-dev Bug#20909: We have two Debian keyrings in our packages. Bug assigned to package `dpkg-dev'. reassign 20914 seyon Bug#20914: seyon package copyright Bug assigned to package `seyon'. close 20937 Bug#20937: hi Bug closed, ack sent to submitter - they'd better know why ! reassign 20941 xbase Bug#20941: Sessreg and debian Bug assigned to package `xbase'. reassign 20875 egcc Bug#20875: Patch and notes for egcs on Alphas Bug reassigned from package `egcs' to `egcc'. reassign 20743 general Bug#20743: autoup.sh: wtmp, utmp and btmp Bug reassigned from package `autoup.sh' to `general'. reassign 20567 general Bug#20567: logo license outdated Bug reassigned from package `logo' to `general'. thanks Stopping processing here. Please contact me if you need assistance. Ian Jackson (administrator, Debian bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Number of Maintainers
On 9 Apr 1998, Jim Pick wrote: Brian Bassett [EMAIL PROTECTED] writes: After both Manoj Srivastava and Bob Hilliard pointed out to me the faults in using the Maintainers file for determining the number of maintainers, I have decided to use the Debian PGP keyring. After deleting duplicate keys, the keyring says that there are 313 developers, making Q 8.85 and K 5. Brian You know what would be cool - if the www.debian.org homepage had a running count of the number of maintainers! That's Debian's biggest selling point, as far as I'm concerned. What happens with a public key if a maintainer orphans all his/her packages and leaves the project? Is it kept in the keyring or is it removed? If it isn't removed the numbers would be too high, IMO. Remco -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies package
On Thu, 9 Apr 1998, Nathan E Norman wrote: On Thu, 9 Apr 1998, Dale Scheetz wrote: : On Thu, 9 Apr 1998, Nathan E Norman wrote: : : Hello, : [ snip ] : If all you need to do is put a different kernel on the rescue floppy : (which is what it sounds like) simply take the delivered image, mount it, : and copy the kernel image from your custom package (the vmlinuz file) to : the file linux on the mounted image. : : You can either dd the image to a floppy, mount the floppy (msdos) and copy : the kernel, or you can mount the image file with one of the loop devices : and do the replacement to the image file. Any future copies of that image : file will have the new kernel. Yes, I know this. However, what people have been asking for is an image of the rescue disk, not a new kernel for the disk (it is difficult to run rdev.sh if you have no Linux system handy) The paragraph you cut out would do that. If you need modules added you must unpack the root fs and add them. If you mount resc1440.bin on a loop device, you can treat it just like any other file system (BTW this is the way the boot-floppies package builds the image in the first place), replacing the kernel or the root file system Furthermore, it might become necessary to change the available modules (I honestly don't know whether this is the case), and I don't believe the rescue disk has device files for ESDI disks. They are /dev/ed[ab], correct? Vincent Renardias says the 1.3 boot disks support MCA (they do) and ESDI (I never found /dev/ed[ab] devices). No Debian boot disk supports IBM MCA/SCSI afaik. The SCSI drivers are usually built-in to the kernel, so this is just another kernel issue. Finally, I'd really like to *know* how to build these things! Why is it so opaque? Building the root file system is a non-trivial problem. The boot-floppies package builds everything that you find in a disks-i386 directory, so it is a bit complex. The cryptic instructions that you indicated previously are an indication of the place to tailor the package to your system. If memory serves, there are two paths defined in the top of the make file. One is the path to the kernel image (note: not a kernel package...I think), while the other is the path to your archive (used to built the root fs) Also, I don't believe that there are any modules installed on the root fs of the rescue disk. It is assumed that any other drivers will be installed from the drivers disk. This disk just contains a tarball of the modules directories. For my last custom CD I rebuilt the rescue and drivers disks to use the 2.0.33 kernel. This was simply a matter of replacing the drivers disk tarball with one built from the 2.0.33 kernel modules directories, and replacing the kernel image on the rescue floppy with the kernel image from the 2.0.33 kernel. I did both of these things to the image files (resc1440.bin, resc1200.bin, drv1440.bin, and drv1200.bin) which could then be used by the installer to build rescue and drivers disks. I don't see where you gain any needed functionality by doing this job with the boot-floppies package. In addition, you stand the chance of building an unusable root file system if the archive you build it from is different from the one used to build the original. As you don't need anything changed in the root fs (as far as I can tell) why take the chance of making it non-functional? Luck, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: boot-floppies package
On Fri, 10 Apr 1998, Dale Scheetz wrote: [ snip ] : Furthermore, it might become necessary to change the available modules : (I honestly don't know whether this is the case), and I don't believe : the rescue disk has device files for ESDI disks. They are /dev/ed[ab], : correct? Vincent Renardias says the 1.3 boot disks support MCA (they : do) and ESDI (I never found /dev/ed[ab] devices). No Debian boot disk : supports IBM MCA/SCSI afaik. : : The SCSI drivers are usually built-in to the kernel, so this is just : another kernel issue. Yes, you're correct. I've built a kernel that works fine, and as you mentioned if I unpack the root fs I could add the device files (some of this is becoming more clear as I go on) : Finally, I'd really like to *know* how to build these things! Why is it : so opaque? : : Building the root file system is a non-trivial problem. The boot-floppies : package builds everything that you find in a disks-i386 directory, so it : is a bit complex. : : The cryptic instructions that you indicated previously are an indication : of the place to tailor the package to your system. If memory serves, there : are two paths defined in the top of the make file. One is the path to the : kernel image (note: not a kernel package...I think), while the other is : the path to your archive (used to built the root fs) Well, looking at the Makefile, there is a directive for the archive base. I have a local mirror mounted via NFS, so I specified that. No problem. Further perusal of the Makefile reveals that it is indeed looking for a kernel-image deb ... aren't the kernel-image-version files built with kernel-package? I thought they were ... At any rate, if I run ``make'' without modifying the Makefile, I end up with a set of floppy images. However, if I change the ``kernel'' definition to point at my own kernel-image deb, make bombs out with No rule to make target `kernel-image-2.0.33_2.0.33-6.deb', needed by `linux'. Stop which indicates to me that I don't have a clue what's happening here. : Also, I don't believe that there are any modules installed on the root fs : of the rescue disk. It is assumed that any other drivers will be installed : from the drivers disk. This disk just contains a tarball of the modules : directories. Indeed. That was my motivation for using the boot floppies script in the first place: if I roll a new kernel, with a different set of modules, and then want that to be usable for others I need to distribute the rescue disk *and* the drivers disk, right? I figured I would use the tool provided for the job rather than doing it all by hand. Perhaps this was an error. : For my last custom CD I rebuilt the rescue and drivers disks to use the : 2.0.33 kernel. This was simply a matter of replacing the drivers disk : tarball with one built from the 2.0.33 kernel modules directories, and : replacing the kernel image on the rescue floppy with the kernel image from : the 2.0.33 kernel. I did both of these things to the image files : (resc1440.bin, resc1200.bin, drv1440.bin, and drv1200.bin) which could : then be used by the installer to build rescue and drivers disks. This is more or less the functionality I'm looking for. Are there compatibility issues with different kernel versions vs. the base disks themselves? : I don't see where you gain any needed functionality by doing this job with : the boot-floppies package. In addition, you stand the chance of building : an unusable root file system if the archive you build it from is different : from the one used to build the original. As you don't need anything : changed in the root fs (as far as I can tell) why take the chance of : making it non-functional? I don't understand this part. Could you explain this a bit more, if you have time? Private email is fine ... I feel terribly stupid but I just don't quite get why the filesystem would be unusable Having said that, you are probably correct as far as the usefulness of boot-floppies for this project. I'm probably trying to kill a gnat with a shotgun ... Thanks for your time :) -- Nathan Norman MidcoNet - 410 South Phillips Avenue - Sioux Falls, SD 57104 mailto://[EMAIL PROTECTED] http://www.midco.net finger [EMAIL PROTECTED] for PGP Key: (0xA33B86E9) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Number of Maintainers
On Fri, 10 Apr 1998, Remco Blaakmeer wrote: On 9 Apr 1998, Jim Pick wrote: Brian Bassett [EMAIL PROTECTED] writes: After both Manoj Srivastava and Bob Hilliard pointed out to me the faults in using the Maintainers file for determining the number of maintainers, I have decided to use the Debian PGP keyring. After deleting duplicate keys, the keyring says that there are 313 developers, making Q 8.85 and K 5. Brian You know what would be cool - if the www.debian.org homepage had a running count of the number of maintainers! That's Debian's biggest selling point, as far as I'm concerned. What happens with a public key if a maintainer orphans all his/her packages and leaves the project? Is it kept in the keyring or is it removed? If it isn't removed the numbers would be too high, IMO. But it also leaves out testers, who provide no pgp keys. So the number could be too low ;-) Luck, Dwarf -- _-_-_-_-_- Author of The Debian Linux User's Guide _-_-_-_-_-_- aka Dale Scheetz Phone: 1 (850) 656-9769 Flexible Software 11000 McCrackin Road e-mail: [EMAIL PROTECTED] Tallahassee, FL 32308 _-_-_-_-_-_- If you don't see what you want, just ask _-_-_-_-_-_-_- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
semi-vacation in Columbus, OH/Chicago, IL
I will be between Columbus, Ohio and Chicago, Illinois for the next week or so. I will have online access, but probably not much of an opportunity to do debian work. If anyone from the area wants to arrange a meeting and pgp signing, I'll be happy to cooperate :-). Igor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Number of Maintainers
On Fri, Apr 10, 1998 at 11:12:58AM -0400, Dale Scheetz wrote: What happens with a public key if a maintainer orphans all his/her packages and leaves the project? Is it kept in the keyring or is it removed? If it isn't removed the numbers would be too high, IMO. If we notice this we remove the key from the keyring. Regards, Joey -- / Martin Schulze * [EMAIL PROTECTED] * 26129 Oldenburg / / Beware of bugs in the above code; I have only / / proved it correct, not tried it. -- Donald E. Knuth / -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
What exactly belongs in frozen?
I had originally posted this to debian-private, but in the interest of getting more feedback (and timely feedback, since if this is going into frozen it needs to go *soon*) I'm re-posting it here. (It probably belongs here anyway, as it's not really a closed maintainers-only issue, but more of a how debian works issue). What exactly determines if a new version of a package should go into frozen or unstable? All I've heard is bug fixes in frozen; everything else in unstable. Actually, though I guess I'd appreciate answers to the general question, what I'd really like is an answer for my specific case: I'm a new Debian maintainer and have just taken over fvwm95. I have packaged up a new version but have not uploaded it because I can't decide if it's frozen or unstable: The main change in this package was that a long-standing feature of the upstream source has been fixed (I actually had done this about a week before bug 20866 came in, but it's essentially the same code change) so that Read statements can be used sanely in the configuration files. As a natural improvement, the configuration has now been made to resemble that of fvwm2 extremely closely. (with .hook files all over the place) Points for putting it into unstable: * this package does the configuration of fvwm95 completely differently from before; this may be considered a new feature. * this is by a new maintainer who re-wrote all the control scripts (from skeletons, but still) himself Points for putting it in frozen: * this package closes several (well, three) bugs related to workarounds for the Read problem. * the old style of configuring fvwm95 was so kludgy and allowed for so little user customization that it could have been considered a reasonably important bug. (The fvwm95 configuration was the single thing I thought RedHat 5 did hands-down better than Debian 1.3.1) * the name of the config. files changed between fvwm95 2.0.42a (the version in bo) and fvwm95 2.0.43b (the current version). The package currently in frozen (2.0.43b-2) makes no allowances for this change of names; my new (2.0.43b-3) does - however, if people upgrade first to (2.0.43b-2) and then to (2.0.43b-3) configuration files that weren't modified won't automatically get switched to the new names. That is, upgrading to my new version after upgrading from bo to 2.0.43b-2 leaves certain old config. files (named /etc/X11/fvwm95/*fvwm2rc95) on one's system, even if one hasn't changed a thing. On the other hand, if the system config. files were never touched, upgrading directly from bo to my version clears out the old files. This makes my version preferable over the version currently in frozen for people upgrading directly from bo. * This isn't new upstream source. (than the version currently in frozen) I'd like to see this in frozen, just because it irks me to have RedHat be vastly superior to official Debian on any point. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
sgmltools - .dhelp, .dwww-index, index.html :)
Hi!
You thing it is difficult to support systems like dhelp or dwww in your
packages? It#s not :).
If your HTML documentation was produced by the sgml-tools (linuxdoc) you
can use this new script in your rules file. It creates the needed .dhelp,
.dwww-index, and index.html files.
Please feel free to use it :).
begin 644 sgml2dhelp.pl
M(R$O=7-R+V)I;B]P97)L(UW@HC($-O'ER:6=H=`H8RD@,3DY.!B2!-
M87)C;R!=61D92`H0G5D95`='4M:%R8G5R9RYD92D*(R!'[EMAIL PROTECTED])A
M;!0=6)L:6,@3EC96YS90H*(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,*(R`@('-G;6QT
M;V]LR`M/B!D:5L[EMAIL PROTECTED]'=W=RP@:[EMAIL
PROTECTED]:'1M;`@(`@(`@(`@(`@
M(`@(`@(,*(R`@(`@(`@(`@(`@(`@(`@(`@(`@(`@(`@(`@
M(`@(`@(`@(`@(`@(`@(`@(`@(,@B,@(`@([EMAIL PROTECTED](!S
M9VUL,F1H96QP(#QD:5L!S96-T:6]N/B`\9'=W=R!S96-T:6]N/B`@(`C
MB,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C@HC('EO=0HD;6%I;G1A:6YEB`](=-87)C
M;R!=61D92`H0G5D95`='4M:%R8G5R9RYD92DG.PH*(R!R96=E'[EMAIL PROTECTED]\@
M9FEN9!T:4@F]O=!H=UL(9I;4@;[EMAIL PROTECTED];V-U;65N=`HD9FEL95]E
M'!R(#T@)UXH+BLI6UXP+3E=7YH=UL)[@HC(')E9V5X!T;R!PF]D
M=6-E($@;EN:R!N86UE(9R;[EMAIL PROTECTED]AE(9I;4@;F%M90HD=ET;5?97AP
MB`](=*XK*5PN:'1M;0G.PH*B,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C
M(R,C(R,C(PHC([EMAIL PROTECTED])S=')A8W0@;[EMAIL
PROTECTED]]C=6UE;G0@(,*(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,C(R,C@IS=6(@9V5T7V%BW1R86-TGL*
M(!M2`DG[@H@([EMAIL PROTECTED]`B/`D9FEL96YA;64B*2!OB!D:64@
M(F-A;B=T(]P96X@)9I;5N86UE(5QN(CL*(`D86)S=')A8W0@/2`G)SL*
M(!W:EL92`H)'IW(#T@/$E./BD*(![B`@(!I9B`H)'IW(#U^(\\4#X\
M2%(^/$5-/[EMAIL PROTECTED]@(`@PH@(`@(`D86)S=')A8W0@/2`D,3L*(`@
M([EMAIL PROTECTED];[EMAIL
PROTECTED]1Z=R`A?B`O/%PO14T^/$A2/CQ+U`^+RD*(`@(`@PH@
M(`@(`@(1Z=R`](#Q)3CX[B`@(`@(`@)%BW1R86-T(X](@)R`N
M(1Z=SL*(`@([EMAIL PROTECTED](`@('T*(!]B`@)%BW1R86-T(#U^(',O/%PO
M14T^/$A2/CQ+U`^+R\[[EMAIL PROTECTED][EMAIL PROTECTED]B,C(R,C(R,C(R,C
M(R,C(R,C(PHC(!WFET92`N9AE;'`@(,*(R,C(R,C(R,C(R,C(R,C(R,C
M@IS=6(@=W)I=5?9AE;'`*PH@('!R:6YT($1(14Q0((\:71E;3Y;B([
MB`@')I;[EMAIL PROTECTED]@(CQD:7)E8W1OGD^)$%21U9;,%U;B([B`@')I
M;[EMAIL PROTECTED]@(CQL:6YK;F%M93XD;EN:VYA;65;B([B`@')I;[EMAIL PROTECTED]
M3%`@(CQF:6QE;F%M93XD9FEL96YA;65;B([B`@')I;[EMAIL PROTECTED]@(CQD
M97-CFEP=EO;CY;B1A8G-TF%C=%QN/]D97-CFEP=EO;CY;B([B`@
M')I;[EMAIL PROTECTED]@(CPO:71E;3Y;EQN(CL@(`I]@H*(R,C(R,C(R,C(R,C
M(R,C(R,C(R,C(R,C(PHC(`N9'=W=RUI;F1E!S=7!P;W)T(`CB,C(R,C
M(R,C(R,C(R,C(R,C(R,C(R,C(R,*G-U8B!D=W=W7W!W9`I[B`@)'!W9`]
M([EMAIL PROTECTED]@(1P=V0@/[EMAIL PROTECTED]/UPO=7-R7]D;V-+RHH+BHI+SL*(`D
M'=D(#T@)#$[GT*G-U8B!WFET95]D=W=WGL*(!PFEN=!$5U=7((C
MV5C=EO;CH@)$%21U9;,5U;B([B`@')I;[EMAIL PROTECTED]/1T/CQA(AR
M968]7(D'=D+R1F:6QE;F%M95PB/B1L:6YK;F%M93PO83Y;B([B`@')I
M;[EMAIL PROTECTED]/1D/B1A8G-TF%C=%QN7XB.PI]@HC(R,C(R,C(R,C(R,C
M(R,C(R,C(R,C(R,*(R`@:[EMAIL PROTECTED]:'1M;!S=7!P;W)T(`CB,C(R,C(R,C
M(R,C(R,C(R,C(R,C(R,C(PH*W5B('=R:71E7VEN95XGL*(!PFEN=!)
M3D1%6`B/$14/CQ!($A2148]7(D9FEL96YA;65(CXD;EN:VYA;64\+T$^
M7XB.PH@('!R:6YT($E.1$58((\1$0^)%BW1R86-T7Y;B([GT*@HC
M(R,C(R,C(R,C(R,C(R,CB,@(`@(UA:6X@(`@(,*(R,C(R,C(R,C(R,C
M(R,C(PH*;W!E;F1IB`H1$E22$%.1$Q%+`G+BI.PI`9ER8V]N=5N=`]
M(')E861D:7(@*$1)4DA!3D1,12D[F-L;W-E9ER(A$25)(04Y$3$4I.PH*
M;W!E;B`H1$A%3%`L((^(YD:5L(I.PIO5N(A)3D1%6P@(CX@:6YD
[EMAIL PROTECTED]:'1M;(I.PIPFEN=!)3D1%6`B/$A434P^7X\0D]$62!1T-/3$]2
M/491D91CY;CQ$3#Y;B([[EMAIL PROTECTED]L((^(YD=W=W+6EN95X
M(BD[B9D=W=W7W!W9#L*F9OF5A8V@@)9I;5N86UE(AS;W)T($!D:7)C
M;VYT96YT*0I[B`@:[EMAIL PROTECTED]1F:6QE;F%M92`]?B`O)9I;5?97APB\IB`@
MPH@(`@)9I;5N86UE(#U^(\D=ET;5?97APB\[B`@(`D;EN:VYA
M;64@/2`D,3L*(`@('!R:6YT((D9FEL96YA;65;B([B`@(`F9V5T7V%B
MW1R86-T.PH@(`@)G=R:71E7V1H96QP.PH@(`@)G=R:71E7VEN95X.PH@
M(`@)G=R:71E7V1W=W[[EMAIL PROTECTED]@IC;]S92`H1$A%3%`I.PIPFEN=!)
M3D1%6`B/]$3#Y;CQ(4CY;CQ!1$1215-3/CQ334%,3#Y;B([G!R:6YT
M($E.1$58()0;5AV4@V5N9!C;VUM96YTR!T;R`D;6%I;G1A:6YEBY
M;B([B1T:6UE([EMAIL PROTECTED]:6UE(AT:6UE*3L*')I;[EMAIL PROTECTED]@@(CQ4CY4
M:ES('[EMAIL PROTECTED](-R96%T960@)'1I;[EMAIL PROTECTED]/]!1$12
M15-3/EQN(CL*')I;[EMAIL PROTECTED]@@(CPO0D]$63Y;CPO2%1-3#Y;B([F-L
;W-E(A)3D1%6D[F-L;W-E(A$5U=7*3L*@``
`
end
cu, Marco
--
Uni: [EMAIL PROTECTED] Fido: 2:240/5202.15
Mailbox: [EMAIL PROTECTED]http://www.tu-harburg.de/~semb2204/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: #19519: tmpreaper: Will not remove dirs
Rob Browning [EMAIL PROTECTED] writes: Assuming that you don't have to worry about new files inserted into the tree while tmpreaper is running (do you?), then it's probably easiest to just do this operation in two passes. (This is off the top of my head, so I'm nearly certain there's a better approach): Actually, I realized that the algorithm I posted may not be safe enough. It probably has the same race conditions as the traditional find | xargs solution, but if for each file you kept: path timestamp creation-date inode and refused to delete anything whose inode number (or creation date if the inode is the same) had changed since you last looked, would that be safe? Is there any way to atomically get the inode number/creation date and delete the file after checking it? Not being a security expert, I should probably shut up now. -- Rob Browning [EMAIL PROTECTED] PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Is this a bug in libc6?
In article [EMAIL PROTECTED], Jason Gunthorpe [EMAIL PROTECTED] wrote: fclose(fp); fclose(fp); This is not valid. fclose's behavoir on a null fp is apparently not defined, but exiting with error would be prefered to faulting. It isn't a NULL fp. It's a fp that just points to a random FILE * in freed up memory. A double fclose is just as bad as a double free() and is not a library error should it fault or corrupt memory. Indeed. If you open another file, it might happen that the struct FILE is allocated at the same place as the previous one. And if you then fclose(old_fp) you're really in trouble. Mike. -- Miquel van Smoorenburg | Our vision is to speed up time, [EMAIL PROTECTED] | eventually eliminating it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
