Bug#1869: wu-ftpd has the old ftp.debian.org bug :-/
Package: wu-ftpd Version: 2.4-13 As you can see, wu-ftpd on chiark violates the FTP protocol pretty badly when the pwd fails. This makes ncftp fall over. Ian. -chiark:~> telnet localhost ftp Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. 220 chiark FTP server (Version wu-2.4(4) Wed Sep 13 09:31:11 MET DST 1995) ready. user ftp 331 Guest login ok, send your complete e-mail address as password. pass [EMAIL PROTECTED] 230 Guest login ok, access restrictions apply. cwd /pub/debian/private/project 250-To get files uploaded to ftp.debian.org via chiark: 250- 250-1. Upload it to chiark:/pub/debian/private/project/Incoming. 250-2. Move the files using RENAME to chiark:.../project/queue. 250- 250-If you want to abort an upload you may delete files from Incoming or 250-queue. Do not simply upload to queue, as chiark may start to transfer 250-the file to ftp.debian.org before you're finished uploading it. 250- 250 CWD command successful. pwd 550 [EMAIL PROTECTED]: pwd
chiark.chu.cam.ac.uk's Incoming
I've copied my cron-driven upload scripts to chiark, where they're now
running.
The procedure for uploading via chiark is now as follows:
1. Upload your files to chiark:/pub/debian/private/project/Incoming.
2. Rename them into chiark:/pub/debian/private/project/queue.
My cron will pick them up out of the queue and transfer them to the
main Incoming directory on ftp.debian.org. It will remove them from
the queue when it has done this, and delete them completely from
chiark a few days later.
If you want to cancel an upload that hasn't completed yet you can
delete the files from the Incoming or queue directories (but not from
`inprogress'). Don't upload directly to the queue directory or my
cron may transfer a half-uploaded version.
The old Incoming directory is no longer writeable, and there's a
message telling you to look in chiark:private/project and a message
there telling you what to do.
A copy of my upload scripts is attached. Please be careful with them
- there's lots of hardwired stuff you'll need to change.
Matt: you can now stop mirroring Incoming.uk from chiark and delete
it on ftp.debian.org.
Ian M.: I've copied all the stuff that was in my Incoming into the new
queue. This means that some stuff you've already moved out of
Incoming.uk will reappear in the main Incoming. A list of the files
I've moved is appended. The most recent of these packages was
netstd-1.23-1 which was uploaded to chiark around 1430 GMT on November
the 15th.
Ian.
bind-4.9.3-BETA26-1.deb
bind-4.9.3-BETA26-1.diff.gz
bind-4.9.3-BETA26-1.md5
bind-4.9.3-BETA26-1.tar.gz
dpkgname-0.3-0.changes
dpkgname-0.3-0.deb
dpkgname-0.3-0.diff.gz
dpkgname-0.3-0.tar.gz
dpkgname-0.4-0.changes
dpkgname-0.4-0.deb
dpkgname-0.4-0.diff.gz
dpkgname-0.4-0.tar.gz
fvwm-1.24r-9.deb
fvwm-1.24r-9.diff.gz
fvwm-1.24r-9.release
fvwm-1.24r-9.tar.gz
latex2rtf-1.1-1.changes
latex2rtf-1.1-1.deb
latex2rtf-1.1-1.diff.gz
latex2rtf-1.1-1.tar.gz
netbase-1.21-1-diffs.tar
netbase-1.21-1-src.tar
netbase-1.21-1.deb
netbase-1.21-1.md5
netstd-1.22-1-diffs.tar
netstd-1.22-1-src.tar
netstd-1.22-1.deb
netstd-1.22-1.md5
netstd-1.23-1-diffs.tar
netstd-1.23-1-src.tar
netstd-1.23-1.deb
netstd-1.23-1.md5
nlsutils-0.5-1.deb
nlsutils-0.5-1.diff.gz
nlsutils-0.5-1.md5
nlsutils-0.5-1.tar.gz
smail-3.1.29.1-14.deb
smail-3.1.29.1-14.diff.gz
smail-3.1.29.1-14.tar.gz
svgalib-1.28-1.deb
svgalib-1.28-1.diff.gz
svgalib-1.28-1.tar.gz
tcpdump-3.0.3-4.deb
tcpdump-3.0.3-4.diff.gz
tcpdump-3.0.3-4.md5
tcpdump-3.0.3-4.tar.gz
vm-5.95beta-1.deb
vm-5.95beta-1.diff.gz
vm-5.95beta-1.tar.gz
wu-ftpd-2.4-15.deb
wu-ftpd-2.4-15.diff.gz
wu-ftpd-2.4-15.md5
wu-ftpd-2.4-15.tar.gz
xcal-4.1-1.deb
xcal-4.1-1.diff.gz
xcal-4.1-1.release
xcal-4.1-1.tar.gz
xtrlock-2.0-0.deb
xtrlock-2.0-0.diff.gz
xtrlock-2.0-0.tar.gz
xypic-3.2-3.changes
xypic-3.2-3.deb
xypic-3.2-3.diff.gz
xypic-3.2-3.tar.gz
begin 664 dupload.tar.gz
M'XL(",X9K#`"`V1U<&QO860N=&%R`.Q=>VP1HWDV$G=U$Y'Y[/Y
M\/'N=N]%\72R*#YLVI1(D90C1%+OEGM[O!7W=L_[(*54=H:E2')J7P^_Z[Z/Y5-90F1I:R<%XB
M[#\5VO^:A[MU4S6\BD9V.6Y%MQ*UW6*+I-FV24FZZ9*ZHIN="!1[1HT3M09J
MZ^Z&R%P7^0V1$+U*.C&)[")IH)!JPW.=SJCG*#-:'Z'CB[AZ72.J5:[EMAIL PROTECTED]
M."212!PQHW$H'[EMAIL PROTECTED]@4B:J5-Q+1TESQV6CG9U%8"N'=?4N0:C
MR4?C^'V?3%,:(,[EMAIL PROTECTED]>V_ZJMP61JNL:)-;'_ZZ[_4KHU_Z=3
M.21D40QD;0]DR[#`&&*,&RM8IE::&P?,OMO==VZVS_09-_^`:>I_:?DT/X_
MF/:/(\6UBE&][MD52YW=P_;F"(9TCBDGV,7I7E+*J*K!RW>U1:[IBSR;4
MFI=0E7I"41/>+&.KVE;]!HQ,^D.,H\,AJFV9KC+-RW'TF6(4&!+193,4[$L.
MPP%C1Y&4.PV'T+FJ0`#I)APC9FS-<6BTE4#W$%WD))E728]1)D=%MZ:[EMAIL PROTECTED]
M$B0E5G41BT!;*1!46C):\,LBGL;LALHHJBI-8M$AT$S?23F*RG*R5,6)[J63QI0.4E5
M?=*D-XT'I3[".L\AKD7\P].("3LQW9QAO#S#")G6#%V;[EMAIL PROTECTED]@[EMAIL PROTECTED]
M=4-S2$V!!,6&4YA6(6,/]T5%4%>/`:W>LT1*C/=(5.3MN5=F8!@F)KYBB9'Z'.!JE$03"3BQ&[EMAIL PROTECTED]
MIFFQ^RRL%S21I\6)`WM9C795(DIV[X9LAC7C)*,T$TKS*;Y4RZCT^`3Q%V`E
M\^=_TZIYC83EN3^'\U\F)2T[_Z7E5#:<_]17%.+";`GKQG52KY\W
MD*I7J\L+7LH1J%FX_Z/V[^_BU^C^Y[KGOW0Z%SC_9='^)2F\__F`[O^6;*_8
M#:S(=D&0``8E*N8)7#B+J546<[EMAIL PROTECTED];'Q4VGT)_-_IV:-;]6$\`-[3^_PO[E\/[W
MPW'_TSS-/`JGF9;!TZ$4.&&Q,Q7=B-,/_S_!O3:=&0P'SI1E=IR(5<[EMAIL PROTECTED])
MU+5MO_C0R_`J;D.9I=U.>/T8BCNUJQ
[EMAIL PROTECTED]<9'8]=Y[&M?_/0(=8K65NK6R"GXS$02^LR;&O:WLG!'CW=FTL"
[EMAIL PROTECTED]/5*2.M$:LN:0SPX&=FDIME:'[EMAIL PROTECTED])H):93.
MAA3120H!G0A%O&8QE;I6C(%P-F=VXN,U/KWQ6O?!E,<9`79'Z?T*7F>TBDDV
M.5AAK3B_EI+$4Z(XIQAZ!1KO%W*\89.ZXJHU=H_5<3C5LU/IJ1[M[B!'[B60
M?\;E2462ELENZ."[EMAIL PROTECTED]:%":WO(:B)YO:P2O>`H;D:,0M\+8A"Q?$Q
MGU*IL)1`/J`MS163"H0B4$R,`LPJ0I/]C:3?VE55(+=JVNR]5'-M6#4+LK%Z
MKIIL6BY1Z*U8%%9.6C,3^I'5UM!<5[,=TME0'%>K$,O$2ZDJWE=VXYC_6S4?+XE?)_,L
M7K?_KPNTZJNUS#9GK"$GB0/9>C32X22]9'*F`W=X/JLYS+B0JW)CU\1K^R.NC7'4GF3L#I\7N""S6ZHM8<[EMAIL PROTECTED]&YT=3`L
MUR%6E2PQ-+2K.'3D":+,*+`+!H7-*R=$WBB;'V5Q38I$8LPC(A98:T@,DE9O
MQA%L;[EMAIL PROTECTED]"63W;UP?([8:C%V?[-L$&QKKF?#MIN:C^=@:9#,
M'X^@>[EMAIL PROTECTED]@BC$<;0G1"W8%&`[3FHJJ.LBZQ%^RH^68C\FNU9I'
MQT)S+8HVN:/!_H*4&7S\<*0EK2/JMR_*I".3#BUK"EBA>Z>&3*QV?.-]
MT=H&@'*`LZEF>BCQM<\Z(Q)K2B!'=JWLAG)[EMAIL PROTECTED])^*`;:PA:QX3W+%2
Unidentified subject!
I don't know if this is a good news or bad news. but I think there is a big misunderstanding about debian-0.93 and debian-1.0 I really forsee the need to do this debian-0.93 release -> debian-0.93 development/debian-1.0 NOTICE: NO LINK development/trial-packages (or some such instead of inside private/project) I am getting 10 - 15 complaints a day about this debian-1.0 and how it won't install all the way or that it isn't all ELF as advertised previously. Well I know I bite my teeth and press delete on all of them I gave up responding two days ago. I am also noticing concerns from MANY mirror sites that they have stopped getting dbian-0.93 because 1.0 was out I have to mail back telling them that this is a development tree and that they should exclude 1.0 and get 0.93. I don't know if I am the only one that gets this type of mail but most of mine comes from [EMAIL PROTECTED] Anyway it is getting real late and I am going to bed CYA! Matthew S. Bailey TOTALS FOR SUMMARY PERIOD Thu Nov 16 1995 TO Thu Nov 16 1995 Files Transmitted During Summary Period 10910 Bytes Transmitted During Summary Period2407017672 Systems Using Archives 0 Average Files Transmitted Daily 10910 Average Bytes Transmitted Daily2407017672 Daily Transmission Statistics Number OfNumber ofAveragePercent Of Percent Of DateFiles Sent Bytes Sent Xmit Rate Files Sent Bytes Sent --- -- --- -- -- -- Thu Nov 16 1995 10910 24070176724.5 KB/s100.00 100.00 Total Transfers from each Archive Section (By bytes) Percent Of Archive Section Files Sent Bytes Sent Files Sent Bytes Sent - -- --- -- -- /debian/debian-1.0/binary 1788 54593887216.39 22.68 /debian/debian-1.0/source 4604 45530336942.20 18.92 /debian/debian-0.93/binar 1384 44530522412.69 18.50 /debian/private/project 435 252289604 3.99 10.48 /debian/debian-0.93/sourc 1200 21768847211.00 9.04 /debian/debian-0.93/disks100 102240519 0.92 4.25 /pub/ftp.freebsd.org/2.1.21456974607 1.96 2.37 /debian/debian-1.06755435031 0.61 2.30 /debian/debian-0.93 6151342624 0.56 2.13 /debian 23040629335 2.11 1.69 /debian/debian-1.0/disks 3840335117 0.35 1.68 /pub/ftp.freebsd.org/2.0. 9438166763 0.86 1.59 /pub/ftp.netscape.com/2.0 3628851931 0.33 1.20 /debian/contrib/source4622766755 0.42 0.95 /debian/contrib/binary9720278528 0.89 0.84 /pub/ftp.cs.helsinki.fi/v 2 4706870 0.02 0.20 /debian/debian-1.0/ms-dos 53 4378852 0.49 0.18 /pub/ftp.cs.helsinki.fi/v 10 4126035 0.09 0.17 /debian/debian-0.93/ms-do 49 4041241 0.45 0.17 /debian/non-free/binary 57 3284435 0.52 0.14 /pub1/win95/canon 2 2672426 0.02 0.11 /debian/tools 27 2092958 0.25 0.09 /debian/doc 36 1447720 0.33 0.06 /debian/project/experimen 14 1385830 0.13 0.06 /pub/ftp.cs.helsinki.fi3 1276231 0.03 0.05 /pub1/win3/winsock 6 722355 0.05 0.03 /pub1/win95/commprog 3 473896 0.03 0.02 /debian/non-free/ms-dos 44 357698 0.40 0.01 /debian/debian-bugs/html 15 339260 0.14 0.01 /pub1/win95/graphics 2 320989 0.02 0.01 /debian/kernel 5 314956 0.05 0.01 /pub/ftp.netscape.com/uns 2 291524 0.02 0.01 /debian/debian-bugs/text 15 278695 0.14 0.01 /debian/project/standards 31 177300 0.28 0.01 /pub/ftp.freebsd.org/docs 2 149960 0.02 0.01 /pub1/win95/sysutil4 141459 0.04 0.01 /debian/contrib/tools 3 94476 0.03 0.00 /pub1/win3 6 91314 0.05 0.00 /debian/contrib/ms-dos54 47362 0.49 0.00 /pub1/win3/clock 1 34425 0.01 0.00 /pub1/win955 32858 0.05 0.00 /pub1/win3/graphics2 32366 0.02 0.00 /pub/ftp.netscape.com/col 4 28192 0.04 0.00 /pub1/win3/desktop 1 18456 0.01 0.00 /pub/ftp.netscape.com/ser 3
Re: chiark.chu.cam.ac.uk's Incoming
> > Matt: you can now stop mirroring Incoming.uk from chiark and delete > it on ftp.debian.org. GONE!!! Enjoy! -- Matthew S. Bailey 107 Emmons Hall Central Michigan University Mt. Pleasant, MI 48858 [EMAIL PROTECTED] ... Any resemblance between the above views and those of my employer, my terminal, or the view out my window are purely coincidental. Any resemblance between the above and my own views is non-deterministic. The question of the existence of views in the absence of anyone to hold them is left as an exercise for the reader. The question of the existence of the reader is left as an exercise for the second god coefficient. (A discussion of non-orthogonal, non-integral polytheism is beyond the scope of this article.)
Announce: libreadline-2.0-5
Users of libreadline-2.0-4, please upgrade. Changes since libreadline-2.0-5: * Use /usr/include/readline instead of /usr/include . * Automagically use ncurses, following the explanation in H.J. Lu's 'ELF: From The Programmer's Perspective'. * Install tilde.h . -rw-r--r-- 1 root root 144202 Nov 16 21:43 libreadline-2.0-5.deb -rw-r--r-- 1 root root 2395 Nov 16 21:43 libreadline-2.0-5.diff.gz -rw-r--r-- 1 root root 425200 Nov 16 21:43 libreadline-2.0-5.tar.gz ce1b82b7c3b864d59176b53087d4500b libreadline-2.0-5.deb d1cb376c5595f4a9fc0340fcd1340858 libreadline-2.0-5.diff.gz ac10c6ce8bf7ebf078f0e7cd01e18b8f libreadline-2.0-5.tar.gz Ray -- UNFAIR Term applied to advantages enjoyed by other people which we tried to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY, UNDERHAND and JUST LUCKY I GUESS. - The Hipcrime Vocab by Chad C. Mulligan
aout-* packages
Hi.. Are these new aout-* packages going to stay the same name forever? And also, are there going to be elf-* packages under the debian-1.0 tree too? It's a little confusing having "aout-gcc-2.6.3-4.deb" and "gcc-2.7.0-2.deb" - is the 2.7 ELF? I think I read a little about this before somewhere, but I cant quite remember. ...Karl -- | PO Box 828 Office: (09)316-3036 Fax: (09)381-3909 |OWER INTERNET SERVICES Canning Bridge After Hours: 015-779-828 WA, 6153 Sales Support: [EMAIL PROTECTED] Internet Service Providers and Networking Solutions
Re: Unidentified subject!
Date: Fri, 17 Nov 1995 00:17:33 -0500 (EST) From: Matthew Bailey <[EMAIL PROTECTED]> I am getting 10 - 15 complaints a day about this debian-1.0 and how it won't install all the way or that it isn't all ELF as advertised previously. Well I know I bite my teeth and press delete on all of them I gave up responding two days ago. I'll write a big warning and put it in /debian and /debian/debian-1.0. I am also noticing concerns from MANY mirror sites that they have stopped getting dbian-0.93 because 1.0 was out I have to mail back telling them that this is a development tree and that they should exclude 1.0 and get 0.93. Why would the mirror program be removing debian-0.93?
Re: aout-* packages
> Are these new aout-* packages going to stay the same name forever?
Probably as long as we support a.out.
> And also,
> are there going to be elf-* packages under the debian-1.0 tree too?
The elf-* packages were experimental packages, for those maintainers that
wanted too look ahead towards ELF; they kind of treated ELF as a cross-compile
platform, using /usr/i486-linuxelf.
They are now rapidly being obseleted.
Since 1.0 is going to be ELF (meaning that all its binaries will be ELF, and
that it compiles for ELF by default), with backward compatibility to compile
and run a.out binaries, new packages are being made, that put their ELF stuff
in the standard locations, and treat a.out as a cross-compile platform.
E.g.
elf-gcc-2.7.0 used /usr/i486-linuxelf; it is superseded by the new
gcc-2.7.0, which uses /usr/{bin,lib,...}. This conflicts with the
old gcc, which also used these directories, and which is therefore replaced by
aout-gcc, which uses /usr/i486-linuxaout.
Currently, the following parts of this transition are done or nearly done:
gcc, binutils, libc, libgdbm, libreadline.
As far as I can see, the following packages will have to go through this
transition: electric-fence, libdb (part of libc4, but not of libc5; I'll take
a look at this), libg++, libident, libncurses.
David, can you comment on this list?
Hope this helps,
Ray
--
Obsig: developing a new sig
Re: aout-* packages
On Fri, 17 Nov 1995, J.H.M.Dassen wrote: > Since 1.0 is going to be ELF (meaning that all its binaries will be ELF, and > that it compiles for ELF by default), with backward compatibility to compile > and run a.out binaries, new packages are being made, that put their ELF stuff > in the standard locations, and treat a.out as a cross-compile platform. This brings up a potentially important question: 1.2.13 won't compile under ELF by default, and though there have been many threats of 1.2.14 it has yet to materialize. Are we going to push forward with 1.3.x, or stick with 1.2.13 and patch? Mike. -- "I'm a dinosaur. Somebody's digging my bones."
Re: aout-* packages
> This brings up a potentially important question: > > 1.2.13 won't compile under ELF by default, and though there have been > many threats of 1.2.14 it has yet to materialize. Are we going to push > forward with 1.3.x, or stick with 1.2.13 and patch? I run 1.3 kernels myself, but they are not sufficiently tested for production systems. AFAIK H.J. Lu's ELF patch for 1.2.11 works with 1.2.13, so perhaps we should include this patch in our 1.2.13 sources. Bruce? Ray -- LOGIC The principle governing human intellection. Its nature may be deduced from examining the two following propositions, both of which are held by human beings to be true and often by the same people: 'I can't so you mustn't', and 'I can but you mustn't.' - The Hipcrime Vocab by Chad C. Mulligan
Announce: aout-libreadline-2.0.3-4
Changes: * Library in /lib instead of /usr/i486-linuxaout/lib, since a base package (bash) depends on it. Thanks to David Engel for finding this one. * Hardwired /usr/i486-linuxaout where necessary 46972d5000aa7785bad36eed1d4505e7 aout-librl-2.0.3-4.deb 971d01c3a3f401d1f927e9bcaaf4a4d7 aout-librl-2.0.3-4.diff.gz cd686b6a6f9123ca3179bd3c1006cebe aout-librl-2.0.3-4.tar.gz -rw-r--r-- 1 root users 112098 Nov 17 16:27 aout-librl-2.0.3-4.deb -rw-r--r-- 1 root users 62291 Nov 17 16:26 aout-librl-2.0.3-4.diff.gz -rw-r--r-- 1 root users 423732 Nov 17 16:25 aout-librl-2.0.3-4.tar.gz Ray -- LOGIC The principle governing human intellection. Its nature may be deduced from examining the two following propositions, both of which are held by human beings to be true and often by the same people: 'I can't so you mustn't', and 'I can but you mustn't.' - The Hipcrime Vocab by Chad C. Mulligan
Re: Unidentified subject!
Matthew Bailey <[EMAIL PROTECTED]> said: > I don't know if this is a good news or bad news. > but I think there is a big misunderstanding about debian-0.93 and debian-1.0 > I really forsee the need to do this > > debian-0.93 > release -> debian-0.93 > development/debian-1.0 > NOTICE: NO LINK > development/trial-packages (or some such instead of inside private/project) Perhaps this is part of the problem: -rw-r--r-- 1 1 debian2982 Oct 27 02:55 README.DEBIAN drwxrwxr-x 6 1 debian 512 Nov 17 04:36 debian-0.93 lrwxrwxr-x 1 1 debian 11 Nov 17 04:55 debian-0.93R6 -> debian-0.93 drwxrwxr-x 6 1 debian 512 Nov 17 04:36 debian-1.0 lrwxrwxr-x 1 1 debian 10 Nov 17 04:55 development -> debian-1.0 DEBIAN.README predates the 0.93 vs. 1.0 split, and there's no info in there about what the difference between 0.93 and 1.0 is or which is appropriate to download for what purpose. The only hint that 1.0 is bleeding edge is the fact that there's a symlink named "development" pointing to it. What's probably happening is that downloaders focusing are in on the debian-0.93 and debian-1.0 directory names, not considering or not understanding the intended implications of the naming of the symlinks pointing to them, and going for what looks like the latest debian release. They may be reading README.DEBIAN first, but not getting any help there. I think the following rearrangement would help: 1. Junk the debian-0.93 and debian-1.0 directory names. 2. Rename debian-0.93 "stable_release" or somesuch. 3. Rename debian-1.0 "pre_alpha" or somesuch. 4. Place an INDEX file in /debian. In that file, provide a list of all files and directories in /debian and a short explanation of what each file is. Explain that debian-1.0 is pre-alpha and not yet well tested in that file. Send a copy of that file, identifying it as the ftp.debian.org:/debian/INDEX file to those complaining of problems with debian-1.0. 5. Have someone assigned by name to maintain (4). 6. Have someone assigned by name to maintain README.DEBIAN. 7. Have someone assigned by name to maintain whatever else needs maintaining. 8. Remove unmaintained items from the distribution site. However, items 1-3 would probably kick off another round of mirroring confusion. OK, instead of items 1 thru 3, just delete the "debian-0.93R6" and "development" symlinks, and do a really good job with item 4. Also, place (maintained) README and INDEX files at the top level of the debian-0.93 and debian-1.0 trees. Also perhaps place file named something like "THIS_IS_UNRELEASED_PRE-ALPHA_MATERIAL" at the top level of the debian-1.0 tree.
rxvt doesn't need to be suid (fwd)
Carlos Carvalho writes: > From @mongo.pixar.com:[EMAIL PROTECTED] Fri Nov 17 02:10:50 1995 > Old-Return-Path: <[EMAIL PROTECTED]> > Date: Thu, 16 Nov 1995 16:10:51 -0200 > From: Carlos Carvalho <[EMAIL PROTECTED]> > Message-Id: <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Subject: rxvt doesn't need to be suid > Resent-Message-ID: <"lDTOoB.A.Q8.S03qw"@mongo> > Resent-From: [EMAIL PROTECTED] > X-Mailing-List: <[EMAIL PROTECTED]> archive/latest/2746 > X-Loop: [EMAIL PROTECTED] > Precedence: list > Resent-Sender: [EMAIL PROTECTED] > > Package: rxvt > Version: 2.10 > > rxvt is now set suid root. This isn't necessary if it can write to > utmp. The package should put utmp and rxvt in the same group and open > write permission of utmp to the group. This doesn't sound like a good idea to me. What do other people think. Is it really that bad for us to have setuid binaries, xterm is suid as well. Andrew -- Dehydration - 34%, Recollection of previous evening - 2%, embarrassment factor - 91%. Advise repair schedule:- off line for 36 hours, re-boot startup disk, and replace head - wow, what a night! -- Kryten in Red Dwarf `The Last Day' Andrew Howell [EMAIL PROTECTED] Perth, Western Australia [EMAIL PROTECTED]
Re: aout-* packages
[EMAIL PROTECTED] (J.H.M.Dassen) said: > As far as I can see, the following packages will have to go through this > transition: electric-fence, libdb (part of libc4, but not of libc5; I'll take > a look at this), libg++, libident, libncurses. add flex (for libfl)
Unanswered problem reports
The following problem reports have not yet been marked as `taken up' by a message to [EMAIL PROTECTED] OVER 9 MONTHS OLD - ATTENTION IS REQUIRED: Ref PackageKeywords/Subject Package maintainer 379 mount Repeatable mount(1) problem wi Bruce Perens <[EMAIL PROTECTED]> 416 wenglish perl doesn't flush output auto [EMAIL PROTECTED] (Robinson, 421 term unreasonable restriction on te Jim Robinson <[EMAIL PROTECTED] OVER 8 MONTHS OLD - ATTENTION IS REQUIRED: Ref PackageKeywords/Subject Package maintainer 563 tartar -x fails to overwrite or c Ian Murdock <[EMAIL PROTECTED] 579 image (?) missing /usr/man/man8 manpages Bruce Perens <[EMAIL PROTECTED]> OVER 7 MONTHS OLD - ATTENTION IS REQUIRED: Ref PackageKeywords/Subject Package maintainer 660 gdbGDB gets address of structure Ian Murdock <[EMAIL PROTECTED] 662 procps top doesn't behave sensibly if Ian Murdock <[EMAIL PROTECTED] 691 textutils textutils package, fmt(1) prog Ian Murdock <[EMAIL PROTECTED] 702 findutils locate crash with large db Ian Murdock <[EMAIL PROTECTED] 710 xs3X server problem with hardware (unknown -- `xs') 713 mh mh should pause after printing Jim Robinson <[EMAIL PROTECTED] 723 xconfigX server default configuration (unknown -- `xconfig') 725 xbase twm places windows incorrectly Stephen Early <[EMAIL PROTECTED] 729 procps Bizarre corrupted output from Ian Murdock <[EMAIL PROTECTED] 731 ncursesncurses wgetnstr doesn't work (unknown -- `ncurses') 737 gawk gawk references to `$0' in END Ian Murdock <[EMAIL PROTECTED] 740 xbase xclock leaves `droppings' in i Stephen Early <[EMAIL PROTECTED] 746 cpio mt doesn't support setblk (and Ian Murdock <[EMAIL PROTECTED] 759 kbd, xbase /usr/bin/X11/showfont conflict Ian Murdock <[EMAIL PROTECTED] 773 xbase xmh falls over if mh is not in Stephen Early <[EMAIL PROTECTED] 775 xbase twm reports errors on incorrec Stephen Early <[EMAIL PROTECTED] 783 tartar --same-order doesn't work Ian Murdock <[EMAIL PROTECTED] 784 manpages Infelicities in fopen manpage Ian Murdock <[EMAIL PROTECTED] 785 cpio mt problemsIan Murdock <[EMAIL PROTECTED] 786 syslogdsyslogd gone awol Martin Schulze <[EMAIL PROTECTED] 797 (base) /etc/termcap console keydefs f (unknown) 798 svgalibsvgalib gets control key mucke Ted Hajek <[EMAIL PROTECTED] 808 emacs Info anchors not active in ema Ian Murdock <[EMAIL PROTECTED] OVER 6 MONTHS OLD - ATTENTION IS REQUIRED: Ref PackageKeywords/Subject Package maintainer 817 tartar -T /dev/null extracts whol Ian Murdock <[EMAIL PROTECTED] 818 bash bash builtin `echo' doesn't ch Ian Murdock <[EMAIL PROTECTED] 819 tartar should have null-separated Ian Murdock <[EMAIL PROTECTED] 820 tcsh tcsh builtin `echo' doesn't ch Andrew Howell <[EMAIL PROTECTED] 821 shellutils /bin/echo doesn't check write Ian Murdock <[EMAIL PROTECTED] 822 tartar -t doesn't check write err Ian Murdock <[EMAIL PROTECTED] 824 cpio cpio should have non-verbose, Ian Murdock <[EMAIL PROTECTED] 825 trntrn warning messages corrupt t Ian Jackson <[EMAIL PROTECTED] 827 libc or sh who reports wrong hostname (wa Ian Murdock <[EMAIL PROTECTED] 835 sysklogd syslogd dies, leaves system un (unknown -- `sysklogd') 836 (base) Possible bugs in termcap syste (unknown) 841 ncursesdselect from dpkg 0.93.34 says (unknown -- `ncurses') 844 manpages readdir(3) should document str Ian Murdock <[EMAIL PROTECTED] 845 manpages access(2) is ambiguous Ian Murdock <[EMAIL PROTECTED] 850 indent [indent] option mentioned in d [EMAIL PROTECTED] (Bill 853 shellutils `nice' does not do anythingIan Murdock <[EMAIL PROTECTED] 857 gs_bothgs (2.6.1pl4-4) doesn't use /e (unknown -- `gs_both') 860 mount `only root can mount' can mean Bruce Perens <[EMAIL PROTECTED]> 864 make make gets MAKEFLAGS wrong Ian Murdock <[EMAIL PROTECTED] 887 xarchieR6 xarchie barfs when ftp closes (unknown -- `xarchier') 889 info Info 3.1-6 Ian Jackson <[EMAIL PROTECTED] OVER 5 MONTHS OLD - ATTENTION IS REQUIRED: Ref PackageKeywords/Subject Package maintainer 902 lprlpr can't print a PostScript f Peter Tobias <[EMAIL PROTECTED] 903 (base) /dev miscellaney (unknown) 911 libc libc causes rsh to fail on com Ian Murdock <[EMAIL PROTECTED] 918 miscutils mkboot and image packages Bruce Perens <[EMAIL PROTECTED]> 923 xbase xdm failed with `unknown sessi Stephen Early <[EMAIL PROTECTED] 927 ncurses? dselect display bug(unknown -- `ncurses') 932 pine Pine over-encodes files and au Ted Hajek <[EMAIL PROTECTED] 933 pine Pine wants to po
Re: Unidentified subject!
On Fri, 17 Nov 1995, Ian Murdock wrote: > > Why would the mirror program be removing debian-0.93? > No, They have told mirror to exclude it due to space restrictions I have been telling them NOT to mirror 1.0 if they are under a space crunch. But rather just get debian-0.93 instead.. -- Matthew S. Bailey 107 Emmons Hall Central Michigan University Mt. Pleasant, MI 48858 [EMAIL PROTECTED] ... Any resemblance between the above views and those of my employer, my terminal, or the view out my window are purely coincidental. Any resemblance between the above and my own views is non-deterministic. The question of the existence of views in the absence of anyone to hold them is left as an exercise for the reader. The question of the existence of the reader is left as an exercise for the second god coefficient. (A discussion of non-orthogonal, non-integral polytheism is beyond the scope of this article.)
Packages available
I have taken over the installation system from Ian Murdock, and need some time to work on that. I'm going to convert it to ELF, go to a one-floppy install, and eventually rewrite the installation interface in C++, with multi-language support, using Ncurses forms. I need to do work on the "base" package, including splitting it into sub-packages. I also want to take some time to finish Debian's ham radio support. I don't think I can do this much work without blocking critical paths in other areas, given my current task load. Thus, I'm looking for package maintainers for the following packages. Note that all but two of these are critical components of the system. The Kernel: This includes both 1.2.13 and 1.3.42 (or whatever the numbers are this week) packaged in the image, source, and includes packages. Experience required. miscutils: needs a lot of detail work. mount: a few error message bugs and such still exist. procmail: routine upstream version tracking only. setserial: version tracking and bug fixes required. rspfd: routine upstream version tracking only. syslinux: routine upstream version tracking only. The candidate should be able to build and upload initial ELF versions of the packages within a week or so of taking them on. Please be sure you can technically handle the task, and can allocate the time required. Thanks Bruce Perens -- Visit the "Toy Story" Web Page! http://www.toystory.com
Re: aout-* packages
> > Are these new aout-* packages going to stay the same name forever?
> Probably as long as we support a.out.
>
> > And also,
> > are there going to be elf-* packages under the debian-1.0 tree too?
>
> The elf-* packages were experimental packages, for those maintainers that
> wanted too look ahead towards ELF; they kind of treated ELF as a cross-compile
> platform, using /usr/i486-linuxelf.
> They are now rapidly being obseleted.
>
> Since 1.0 is going to be ELF (meaning that all its binaries will be ELF, and
> that it compiles for ELF by default), with backward compatibility to compile
> and run a.out binaries, new packages are being made, that put their ELF stuff
> in the standard locations, and treat a.out as a cross-compile platform.
>
> E.g.
> elf-gcc-2.7.0 used /usr/i486-linuxelf; it is superseded by the new
> gcc-2.7.0, which uses /usr/{bin,lib,...}. This conflicts with the
> old gcc, which also used these directories, and which is therefore replaced by
> aout-gcc, which uses /usr/i486-linuxaout.
>
> Currently, the following parts of this transition are done or nearly done:
> gcc, binutils, libc, libgdbm, libreadline.
> As far as I can see, the following packages will have to go through this
> transition: electric-fence, libdb (part of libc4, but not of libc5; I'll take
> a look at this), libg++, libident, libncurses.
>
> David, can you comment on this list?
Why? I think you answered it rather well. :-)
David
--
David EngelOptical Data Systems, Inc.
[EMAIL PROTECTED] 1101 E. Arapaho Road
(214) 234-6400 Richardson, TX 75081
Re: aout-* packages
> This brings up a potentially important question: > > 1.2.13 won't compile under ELF by default, and though there have been > many threats of 1.2.14 it has yet to materialize. Are we going to push > forward with 1.3.x, or stick with 1.2.13 and patch? The kernel can still be compiled in a.out format. The a.out development tools aren't completely going away. They just won't be the default. If you really want to compile 1.2.13 in ELF format, I suggest you politely request Linus to update it one last time. David -- David EngelOptical Data Systems, Inc. [EMAIL PROTECTED] 1101 E. Arapaho Road (214) 234-6400 Richardson, TX 75081
Re: aout-* packages
> > As far as I can see, the following packages will have to go through this > > transition: electric-fence, libdb (part of libc4, but not of libc5; I'll > > take > > a look at this), libg++, libident, libncurses. > > add flex (for libfl) This brings up a good question. Do we really want to provide new, a.out versions of *all* development packages, even if they don't contain any shared libraries? Not doing so might be a good way to encourage all development to switch to ELF. David -- David EngelOptical Data Systems, Inc. [EMAIL PROTECTED] 1101 E. Arapaho Road (214) 234-6400 Richardson, TX 75081
Re: New a.out/ELF development packages
F'up to debian-devel! > "Dirk" == Dirk Eddelbuettel <[EMAIL PROTECTED]> writes: Dirk> Will ligb++-2.7.x be debianized or do we have to grab that ourselves? libg++ is high on my personal priority list, since I'm using it extensively for my work. But you'll have to wait til my network connection is up to pace sometime next week. I'm tired of downloading at well below 1K/s. Dirk> I need it for my work. And I'd like to, if I can, do without the aout Dirk> versions of gcc and friends and go to elf directly. At least for a transition period both binary formats should be supported using gcc's -b flag (default to ELF). Beyond that I need some cross development tools for SCO and OS/2, but those seem to be out of Debian's scope. Greetings Siggy -- email: [EMAIL PROTECTED] // programmer/*nix admin for hire \\ Opinions are strictly my own, voice: +49-251-864978 \\ everything else is GPLed Mime(RFC1521) encoded messages welcome \\ http://coming.soon/
Re: aout-* packages
On Fri, 17 Nov 1995, David Engel wrote: > The kernel can still be compiled in a.out format. The a.out > development tools aren't completely going away. They just won't be > the default. If you really want to compile 1.2.13 in ELF format, I > suggest you politely request Linus to update it one last time. As I remember, from trying to get a 1.3 kernel to compile with debian's gcc-elf, the Makefiles for the kernel don't seem to be set up in such a way as to make it easy to redefine and then propogate $(CC) -- which would seem necessary to use 'gcc -b i486-linuxaout'. I guess it is worth while to at least find out if 1.2.14 is totally out of the question --- I seem to remember a few other small bugfixes which were slated to appear. Mike. -- "I'm a dinosaur. Somebody's digging my bones."
Re: aout-* packages
> > The kernel can still be compiled in a.out format. The a.out > > development tools aren't completely going away. They just won't be > > the default. If you really want to compile 1.2.13 in ELF format, I > > suggest you politely request Linus to update it one last time. > > As I remember, from trying to get a 1.3 kernel to compile with debian's > gcc-elf, the Makefiles for the kernel don't seem to be set up in such a > way as to make it easy to redefine and then propogate $(CC) -- which would > seem necessary to use 'gcc -b i486-linuxaout'. Actually, it's pretty easy, at least for us. Since we have completely separate a.out tools, all we need to do is put /usr/i486-linuxaout/bin before /usr/bin in our PATH and compile away. David -- David EngelOptical Data Systems, Inc. [EMAIL PROTECTED] 1101 E. Arapaho Road (214) 234-6400 Richardson, TX 75081
