Bug#3539: (no subject)

1996-07-10 Thread Martin Schulze 
Subject: mkisofs stops if an error occurs

Package: mkisofs
Version: 1.05-1

mkisofs unfortunately stops if a permission problem occors on the 
source filesystem, like a directory isn't world executable or readable.

I would appreciate if it would report a warning and go on.  Some users
(like myself) can't provide two times 650 MB for creating an image, instead
they have to nfs-mount all the stuff somewhere.  If there is "confidential"
stuff in a dirctory

Bug#3540: mkisofs stops if a problem occurs

1996-07-10 Thread Martin Schulze 
Package: mkisofs
Version: 1.05-1

Mkisofs unfortunately stops if a permission problem occors on the
source filesystem, like a directory isn't world executable or readable.

I would appreciate if it would report a warning and go on.  Some users
(like myself) can't provide two times 650 MB space just for creating an
cd image, instead they have to nfs-mount all the stuff somewhere.  If
there is "confidential" stuff in a dirctory that should not occur on the
cdrom then mkisofs suddenly stops.

Regards,

Martin

PS: If there is another bugreport beginning like this than it should be
reportet as a bug against mailx, because I pressed Ctrl-C to abort. Mailx
must not send that mail out...

Bug#3702: cflow is empty

1996-07-10 Thread heiko 
Package: cflow
Version: 2.0-1-
Libc: libc.so.5.2.18
Kernel etc: Linux muli 2.0.0 #3 Wed Jun 26 22:16:32 MET DST 1996 i486
Reporter: repair 0.1

... the binary package doesn't contain a binary.  (As far as _I_
can see ...)

I've included the diff to the original source.  If this diff
is applied to the original, a `./debian.rules binary' produces
the real binary.

Heiko

begin 644 cflow-2.0-1hs00.diff.gz
M'XL(`+="X3$"`\U7>W/:2!+_V_D4O0FW&)\E(1*_=(LK+!`?NWY00%*;JJLM
M#](`*NM5&@F;;/:[;_?,[EMAIL PROTECTED]:N]<�]_9KN7_>T/'\V`\.]3L&=!?&]
MT3*;9ISZ<^N*W?&9'_!'>DEZ<7!PL(M][RJ.X*<[EMAIL PROTECTED]
MAO&$KKU)SN&*K:[EMAIL PROTECTED])XV>GAW:31OD&F#/([EMAIL PROTECTED]
[EMAIL PROTECTED](S:;V#RU_G\TO.5^#/X)[#/,[EMAIL PROTECTED]@"9BP]A)2'\9*7&EY\!WMI
MN"Y:,8>?VOYP=#.YF7P<]L<-9^\?N!5G<;9*N#`7M);&7$D%0T#M5SBOO56R
M;L!9Y#ADQ$`K4M7%N`$'9OQH9L-O]>[EMAIL PROTECTED]";`8BK+H",+GIW4!Y
M$LV7/63ZR4;^\:B+G(/K\:1S>0DPZG=Z5WTH4T]9U%G`1^-_FH7:_NBJ\3E
M<',/K(!#$>2D7Z<]EOZ>:O)%XI\H<@7DCRY&E+NVU86)CI6
MM9H,H0R!KIJ_)P3;[EMAIL PROTECTED]/DOW7HG0CU^-1GD:D1_0BM"OTIK%88
M]B:+''["T([EMAIL PROTECTED](90]<*Q'=O>[EMAIL PROTECTED]'IJ>S]$R:4._Q@
M2J`GM1;UPQ/_ID]OKGAZANEL8AB#A/7012/,UP
M#PT3U<%=$'DD_(R;>>2:W,L=*\FGRE&,RY('5L"BN=6U'@.=L=2?]P=#8:3PPNW<7V*CP;MOGK("0$`L+,/,)[EMAIL PROTECTED]&@;
[EMAIL PROTECTED](PB0Y4L]2#.,\0Y);,1V!TE7
MG<'U!/_[(^&[EMAIL PROTECTED]:9DG
[EMAIL PROTECTED])4F1P,QI,/CJE;T@D?+IG(($\\EG'/
[EMAIL PROTECTED]'+L$9=L$_`;CI'+:?5A/YX0A;?4+ORPSSU8O?.+.4G,4B5!`#4SU*\S7R1
MI?XTEU#1#>-0,MS>J@;@?^)>O5X`4;-([EMAIL PROTECTED]/'
[EMAIL PROTECTED]&P_V!53<@]/=KO.5Z>&PQ^XFV=LBAUJRF=QJLXQDU;6CR&U
M(7_(//YX]D&TC-$`9^X"L)-B5X=[/UML>?2#VCROFP`=K!RU%"`6<1YX:%FI
ME]H\I4(6GNZU:8S3,5.5[.9IBL,`.I=R-XO3U5HF*,`J!?7"G3#'[.*TD>81
M:[EMAIL PROTECTED],L#O1*]F]I7:H3"7>QB;L0WT=XLRW\1)BJR]Q24DH3
M3(@\Y$)%>!7GL&!+7LF74E?)-;`E\P.*^R'D$1&Y=TCMWS2MVG[2,&K[RX:L
MH$-44]4MU:G&A&-3G..Q\+>X>K\(,PFQ=7CIX.N0;T>W#&[$0EXV1:UL'T%3
M3/:'<,[EMAIL PROTECTED]:)<]7@RI=Z-TX*;Y1KVA1YY$>/E3@,`JB0E#)74]L6"(TZ\Y&Z.G45>
M%\:ZDH8*UC3W`\^1UGZD1['>&[0-TKDG^T;WW67G8MRN&S>M.ESVBA66)_;[
M=X-?VM2Y@/#Y_?>(UAQ+#>$:)H8TH^<'^?XF+;Z/O)@KBWPV0[\H2+>ZZ4&E
M*J6"^J,[EMAIL PROTECTED]O_..A[EMAIL 
PROTECTED];!JA5=XRB^7LJQT@
M"8$E97"H6[\60X@VJ+JX
M?D_\!0>UE+=]O1$*4:[EMAIL PROTECTED]&[BQA>WA3ST,8%
MA_T[HHFAN&+-E_`OF+$`W[\:7_!F5Q.BS8U(/T[*&SJ>C+SV?BL!Q>D:3P17
C:M.":%#WOVVG]=ZZ6)%/D3E%_]5!TC?^BS\`G$V+CPT7
`
end

Bug#3703: mkisofs stops if a permission problem occurs

1996-07-10 Thread Martin Schulze 
Package: mkisofs
Version: 1.05-1

I would like to add this as a hint to the existing bugreport
but as usual I can't find it.  I even haven't received a
confirmation.  Anyway...

I would appreciate if mkisofs would test each file for read access
while it builds its directory structure and _before_ it tries to
create the image (and would stop after it has built 600 of 650 MB).
This could save the user a lot of time, especially if the machine
that builds the image isn't the fastest one.

Regards,

Martin