Re: Packages to give away (was: xfig and transfig)
From: Edward Betts <[EMAIL PROTECTED]> Subject: Packages to give away (was: xfig and transfig) Date: Sun, 9 May 1999 01:56:47 +0100 > xfig and transfig maintainer here. > > I am not really sure what the question is, Very sorry, but I want to know what you replied. Thanks for your rapid reply. From: Roland Rosenfeld <[EMAIL PROTECTED]> Subject: Re: Packages to give away Date: Sun, 9 May 1999 14:26:30 +0200 > very much), but I regularly use xfig, so I could take this over, if > nobody else volunteers. > > But I cannot promise to close all bug reports in the next days. Of course. But if you maintain, I hope you set high priority to fix the bug I pointed out ;-) Thanks,1999.5.10 -- ** Atsuhito Kohda Dep. Math., Tokushima Univ. [EMAIL PROTECTED]
Re: Dents v0.0.3 - DNS server
In article <[EMAIL PROTECTED]> you wrote: > I wonder if s/o is already working on this or if it doesn't make sense > to package it. Given the BIND package will move to non-free in version 8.2 due to the license on the RSA code used for DNSSEC, it's good to see an alternative that will be in main... even if it's less functional. Bdale
Re: Dents v0.0.3 - DNS server
Bdale Garbee <[EMAIL PROTECTED]> writes: > In article <[EMAIL PROTECTED]> you wrote: > > I wonder if s/o is already working on this or if it doesn't make sense > > to package it. > Given the BIND package will move to non-free in version 8.2 due to > the license on the RSA code used for DNSSEC, it's good to see an > alternative that will be in main... even if it's less functional. Is it possible to keep an older version of Bind in main? Many of us will not be using DNSSEC anyways for awhile. -- Craig Brozefsky<[EMAIL PROTECTED]> Less matter, more form! - Bruno Schulz ignazz, I am truly korrupted by yore sinful tzourceware. -jb The Osmonds! You are all Osmonds!! Throwing up on a freeway at dawn!!!
Re: Perl 5.005 in potato AND why freeze?
> Just to troll "out of the box" a bit: > > What are the reasons for freezing in the first place? Distribution > versioning is not something I know much about! Help me out. > 1) A known (re)starting point. > 2) Bandwidth conservation - offload from mirrors to CD-ROM. > 3) Life is simpler for the non sysadmins. > What else? > > -- > > Certainly things should "work". What if the freeze would > only apply to contents of baseN_N.tgz (base_-MM-DD.tgz) > or some very strictly limited subset? Maybe a new source > tree, stable/unstable becomes base/stable/unstable > where base is used to build the base*.tgz. The idea of a distribution is that all of it should work in sync. That is, it's no use having a nicely working base system if half of the other software falls over due to broken dependencies or bad compilation or serious bugs or whatever. The freeze period is a time during which regular uploads into the distribution are stopped and we try to ensure that as much of the distribution as possible is working together, without being hampered by uploads (except for bug-fixes). Note that this is far broader than just detecting and reporting bugs in individual packages: we are looking also for bugs in the distribution as a whole. Then, about a month later (here's hoping!), we can announce to the Big Wide World that Debian Version x.y has been released, you can download it from , etc. Without the stability offered by a freeze, this would not be possible. > Nor do I understand the ins and outs of why not perl5.005: > if something is inevitable, general the quicker done the better. > My business needs it and has been running it since it appeared > in unstable for a few days some time ago. Does that mean > base/stable/unstable/bleed? :-) The main problem with Perl 5.005, AFAIK, is that it is not binary-compatible with Perl 5.004. This means that any packages which include compiled Perl extensions will fall over when Perl 5.005 is installed. A secondary, but also very significant point, was the desire to have versioned Perls, so that a Debian system may simultaneously house Perl 5.004, 5.005, 5.006, 6.000, 6.001 etc. This required a lot of thinking, and will almost certainly lead to significant instability in unstable while the problems are ironed out. All credit to our Perl team for such stirling work! HTH, Julian =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED] Debian GNU/Linux Developer. [EMAIL PROTECTED] -*- Finger [EMAIL PROTECTED] for my PGP public key. -*-
Re: Dents v0.0.3 - DNS server
In article <[EMAIL PROTECTED]> you wrote: >> Given the BIND package will move to non-free in version 8.2 due to >> the license on the RSA code used for DNSSEC, it's good to see an >> alternative that will be in main... even if it's less functional. > Is it possible to keep an older version of Bind in main? Many of us > will not be using DNSSEC anyways for awhile. I suppose it would be possible, but I'm not particularly interested in maintaining more than one version. A better solution would be to figure out how to fraction the 8.2 sources. It's not obvious to me how to do it, and I don't have much time to work on it right now, but the notion of a base bind package and a bind-dnssec in non-free is conceptually appealing. I'll think about this some as I finish putting the 8.2 package together. The bits work fine, but I've had it with the existing configuration mess, and am trying to both give us something simple and rational for new installs, and deal with the mess previous version of bind have left behind... and it's not much fun. Bdale
Re: Perl 5.005 in potato
Mike Stone said: > I'm still convinced that the reason slink's freeze took so long is that > some major packages were uploaded just prior to it, because they > "needed" to be in. Just like people want to do with perl... There is a difference in this case: freeze is not in effect, and not immenent. If it were, Mike'd have a valid argument: perl-5.005 is -not- being snuck in under deadline, because deadline does not presently exist. I'd love to see perl-5.005 in, personally. -Jim
Re: Perl 5.005 in potato
Mike Stone said: > Perl is just another app. For most distributions, this is true. Proof: you can run those dists without perl. For debian, however, Mike's statement is not valid. Proof: try to release debian without perl in any form. You're gonna find that perl happens to have been made essential to debian, not due to any intrinsic quality, but because some developers have chosen to use perl and perl scripts in maintainer scripts. This means that upgrading perl (whenever it is done) will need the same degree of care applied as for dpkg, dselect, boot-floppies, debian-cd and all other essential parts of debian infrastructure, and -not- that of "just another app". -Jim
Re: Debian coding style?
Joseph Carter <[EMAIL PROTECTED]> writes: > > for (int nI=0; nI<10; nI++) ... > > Anybody who does that willingly must be shot. => No, no; no need for violence. Anyone who does that is already suffering enough at their own hands and doesn't need external help.
Re: Netscape Bus Errors
Yea...I started a thread about this a few weeks ago...it seems to be an issue and someone posted a theory (or an explanation..don't remember anymore) of what was actually happeneing and a hack/fix for it I think.. Ivan On Thu, May 06, 1999 at 10:14:25AM -0500, Mark Mealman wrote: > Anyone else getting hit with these? > > Was using netscape 4.08 when I started having these problems(after a > massive apt-get upgrade, naturally), so I upgraded to 4.51 and I still > seem to be getting a lot of bus errors. > > The errors only happen now and again when I close a netscape window. > > Nothing critical, just a pain. > > Is this an issue in the new C libs? > > > Mark - wanting mozilla > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] ---end quoted text--- -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ivan E. Moore II Rev. Krusty http://www.tdyc.com [EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- GPG KeyID=0E1A75E3 GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Debian coding style?
[EMAIL PROTECTED] (Zygo Blaxell) writes: > "Why 78 characters per line of code?" > "Because the laser printer wants that." > "Why does the laser printer want that?" > "Uhhh...because IBM made a business decision in the 1950's?" I will actually point out that although the exact number 80 is arbitrary, the general number "about 80" is not. The issue is that that's the number of characters/line that looks good to the human eye - typesetters know this; open a book and count. Too much longer than that (say, 200 columns) and it becomes difficult when tracking your eye all the way back to the left to find the right row. This is remembered vaguely from an introduction I saw once to writing (I think) LaTeX style files, talking about classic beginner mistakes. Short lines are good. Of course, I suppose one could then say "but code lines that stick out past the 80th column are mostly indentation - your eye is only tracking back 40 characters". Well, that's true, but the eye tracking issue does help to explain why a printer (designed, most likely, for printing text that's not mostly indentation) would pick some number near 80 as its line length
Freeze stuff, summary.. (perl 5.005, etc)
I'm seeing a few rather vocal people who really just want to release ASAP for whatever reason, most are willing to wait to get stable, but they still 'just want to get it out'... I'm also seeing a lot of FUD being spread about perl5.005, guys, we /HAVE/ a plan, the maintainer is busy working on it instead of getting in long debates, which is a good thing, for specifics please see the -devel and -perl archives.. As far as I can see, we simply are not ready to freeze, we have many many 'little' and 'big' things working quietly to get things done for potato, we have a good number of people working on IPv6, BenC and a few others on PAM, others on perl5.005, Overfiend and friends working on things for X, and many other things which I have not been keeping a eye on... Give it time, glibc2.1 is still not entirely stable (I think, someone hit me over the head hard if its fully stable, espy please), and we have many things cooking which will be very very nice when they are ready.. Zephaniah E. Hull.. (AKA Mercury) -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. pgpGLjIMSvaz9.pgp Description: PGP signature
RE: Installing things into run-parts or .d directories.
Or the script could simply test and run like the init.d scripts do. On 09-May-99 Karl M. Hegbloom wrote: > > What if a package is installed, and puts a script in a run-parts > directory or into a .d directory, but isn't configured due to a > missing dependancy? The newbie "sysadmin" doesn't know to look for > it, and leaves it there, then gets email from cron. Per sends off a > tech support question. > > This could be prevented by having a place (/etc/cron.scripts, or > /etc/cron.d/crontabs) to install things to, then require that the > postinst create a symlink during configuration. > > Hmmm... > /etc/crontabs > /etc/crontabs/crontab > /etc/crontabs/cron.d/ > /etc/crontabs/pkg_blah_script > ... > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Perl 5.005 in potato
On Sun, May 09, 1999 at 08:14:24PM -0700, Jim Lynch wrote: > Mike Stone said: > > Perl is just another app. > > For most distributions, this is true. Proof: you can run those dists without > perl. > > For debian, however, Mike's statement is not valid. Proof: try to release > debian without perl in any form. You're gonna find that perl happens to have > been made essential to debian, not due to any intrinsic quality, but because > some developers have chosen to use perl and perl scripts in maintainer > scripts. > > This means that upgrading perl (whenever it is done) will need the same degree > of care applied as for dpkg, dselect, boot-floppies, debian-cd and all other > essential parts of debian infrastructure, and -not- that of "just another > app". You forget to mention some important points -- those new features in perl 5.005 are both underdeveloped and buggy. In the same way, debian does not depend on them at all However I agree they are useful. But, getting them into potato should carry the same importance as some popular python module... -- ..Aaron Van Couwenberghe... [EMAIL PROTECTED] [EMAIL PROTECTED] Berlin: http://www.berlin-consortium.org Debian GNU/Linux: http://www.debian.org "...Nothing astonishes men so much as common sense and plain dealing..." -- Ralph Waldo Emerson
Re: Perl 5.005 in potato
On Sun, May 09, 1999 at 08:00:21PM -0700, Jim Lynch wrote: > Mike Stone said: > > I'm still convinced that the reason slink's freeze took so long is that > > some major packages were uploaded just prior to it, because they > > "needed" to be in. Just like people want to do with perl... > > There is a difference in this case: freeze is not in effect, and not > immenent. If it were, Mike'd have a valid argument: perl-5.005 is -not- > being snuck in under deadline, because deadline does not presently exist. > > I'd love to see perl-5.005 in, personally. AOL. Nothing wrong with having it done before deadline. The problem comes when it gets done simply to meet deadline; history dictates that this has been one of the major causes of release delays for debian. Mike is just trying to make the case that a new version of perl should not influence debian's final freeze date, in the same way that no other package can... except for necessity, such as libc and kernel versions for boot-floppies, et al. -- ..Aaron Van Couwenberghe... [EMAIL PROTECTED] [EMAIL PROTECTED] Berlin: http://www.berlin-consortium.org Debian GNU/Linux: http://www.debian.org "...Nothing astonishes men so much as common sense and plain dealing..." -- Ralph Waldo Emerson
Re: Freeze stuff, summary.. (perl 5.005, etc)
I've been distracted by revenue production for a couple of months. Are we expected to upload our packages rebuilt for glibc2.1?
Re: Dents v0.0.3 - DNS server
At 18:16 -0600 1999-05-09, Bdale Garbee wrote: In article <[EMAIL PROTECTED]> you wrote: I wonder if s/o is already working on this or if it doesn't make sense to package it. Given the BIND package will move to non-free in version 8.2 due to the license on the RSA code used for DNSSEC, it's good to see an alternative that will be in main... even if it's less functional. The glibc upstream had a discussion awhile back regarding intregrating bind 8.2's libresolv. There were two issues, firstly, the DNSSAFE license, secondly, RSA itself. RFC 2535 makes DSA mandatory, and only "recommends" RSA/MD5. 3.2 The KEY Algorithm Number Specification ... Algorithm specific formats and procedures are given in separate documents. The mandatory to implement for interoperability algorithm is number 3, DSA. It is recommended that the RSA/MD5 algorithm, number 1, also be implemented. Algorithm 2 is used to indicate Diffie-Hellman keys and algorithm 4 is reserved for elliptic curve. It was planned to use a free implementation of DSA and not bother to implement RSA until the patent expires. -- Joel Klecker (aka Espy)Debian GNU/Linux Developer mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED]> http://web.espy.org/> http://www.debian.org/>
Re: Freeze stuff, summary.. (perl 5.005, etc)
Oscar Levi <[EMAIL PROTECTED]> writes: > I've been distracted by revenue production for a couple of months. > Are we expected to upload our packages rebuilt for glibc2.1? It wouldn't hurt but I don't think it's necessary. glibc2.1 can drop-in replace 2.0 (unless you have a program that depends on certain internal stuff which it shouldn't be using anyway). Really, what is more important and has changed is CC from gcc272 to egcs. But again, it would probably be nice to recompile sometime over then next two months, but not really necessary AFAIK. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
Re: Pandora is born
On 9 May 1999, Guy Maor wrote: > Debian DNS administrators, please change nonus.debian.org to be a > CNAME for pandora.debian.org. Okay, I will send an email to the mirrors list and switch it over sometime Tuesday evening. This switch will cause them all to fetch the whole archive again, but it is very small. We also need to get Hieko to make his site a mirror, people mirror off him through names we do not control :| > Debian Maintainers, the nonus incoming directory is > /org/nonus.debian.org/incoming on pandora. Any anonymous upload > queues for nonus should be converted to upload to there. All > maintainers should have an account on pandora. Please email [EMAIL PROTECTED] if you do not, also send a pgpg signed email if you forgot your password (and your ssh key doesn't work..) Jason
[ashp@bastard.co.uk: Bug#37349: qt1g needs urgent recompile for potato]
Hello, is some of you maintainers willing to recompile the qt1-1.42 package on a potato system and then do a NMU? (I don't have a potato system currently.) Thanks, Best Regards from Dresden/Germany Viele Gruesse aus Dresden Heiko Schlittermann -- [internet & unix support - Heiko Schlittermann] [http://debian.schlittermann.de/";> Debian 2.1 CD ] [Heiko Schlittermann HS12-RIPE finger:[EMAIL PROTECTED] -] [pgp: A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92 ---] - Forwarded message from Ashley Penney <[EMAIL PROTECTED]> - Package: qt1g Version: 1.42-2 QT needs to be recompiled against glibc 2.1, as it's impossible to run KDE applications that have been compiled from source. They will reliably seg fault and cause general trouble. I recompiled QT using the source package and everything worked perfectly - so I believe a simple recompile will do. I am using Debian Potato, kernel version 2.2.7-ac1, with glibc 2.1.1-3, egcs 1.1.2-1 and the KDE 1.1.1 packages. -- Ashp |Debian GNU/Linux User [EMAIL PROTECTED] | "Linux - A GNU generation." - End forwarded message -
Re: install report for Debian 2.1 and some comments on installation profiles
On Sun, May 09, 1999 at 04:08:34PM -0400, Adam Di Carlo wrote: > > [Talking about tasks and profile from boot-floppies] > > > "brandon" == Brandon Mitchell <[EMAIL PROTECTED]> writes: > brandon> I'd personally like to see a way to easily add a profile via > brandon> dpkg -get-selections and make for a cookie cutter install > brandon> (think large labs). > > Eh... I don't see this as a good idea. I personally would rather see > all the "tasks" made into "metapackages" (packages which are basically > just a bunch of dependancies, and some info in /usr/doc/). > > Then you can maintain your tasks and profiles all the time. > > Also, tasks would be task- metapackages, depending on actual > Debian packages. Profiles would be profile- > metapacakges, depend on just the tasks. > > Voila. Elegant, uses the existing packaging system (i.e., no need to > skip the select step in dselect), This is the main point against your approach. We introduced the tasks and profiles to avoid going through the list of 3000 packages in dselect. It could be a nightmare to find those new metapackages in that huge list. Don't get me wrong, I like the idea of using metapackages, but those metapackages must be shown in a different level/screen on our package selection tools (gnome-apt, dselect, whatever...). Until our tools are modified to do that, I guess metapackages won't be that useful. Another point against metapackages is that it's trivial for a new user to make a new "task" (it's just a list of packages, one name on each line) but it's not so easy to make a metapackage (it's a deb package, with its changelog, control file, rules file and so on...). That may probably be fixed by implementing a debhelper tool just for building metapackages. > Another nice benefit to my scheme is that each task/profile can be > maintained independantly by different Debian developers. In fact, I > volunteer to take over the SGML environment task if we do move to this > scheme. Why wait? You can build that metapackage now, and we may use it as a "test case" to see if any strange problem arises. A "gnome" metapackage would be a nice one too. Volunteers? -- Enrique Zanardi[EMAIL PROTECTED]
Re: Pandora is born
On Mon, May 10, 1999 at 01:23:28AM -0600, Jason Gunthorpe wrote: : On 9 May 1999, Guy Maor wrote: : > Debian DNS administrators, please change nonus.debian.org to be a : > CNAME for pandora.debian.org. That's what I call `democracy'. :-( -- Sorry. Heiko -- [internet & unix support - Heiko Schlittermann] [http://debian.schlittermann.de/";> Debian 2.1 CD ] [Heiko Schlittermann HS12-RIPE finger:[EMAIL PROTECTED] -] [pgp: A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92 ---]
Compilation problems
In order to package nis+ utilities I upgraded a slink system to potato (apt-get, first libc6, then rest, then kernel 2.2.5 image). Now a face strange compilation problems, like for the cvs package $dpkg-source -x cvs_1.10.4-1.dsc $cd cvs-1.10.4/ $debuild [..] gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c hardlink.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c hash.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c history.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c ignore.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c import.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c lock.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c log.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c login.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c logmsg.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c main.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c mkmodules.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c modules.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c myndbm.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c no_diff.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c parseinfo.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c patch.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c rcs.c gcc -I. -I.. -I. -I../lib -I../diff -DHAVE_CONFIG_H -g -O2 -c ./rcscmds.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c recurse.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c release.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c remove.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c repos.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c root.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c rtag.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c scramble.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c server.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c status.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c tag.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c update.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c watch.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c wrapper.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c vers_ts.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c subr.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c filesubr.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c run.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c version.c gcc -I. -I.. -I. -I../lib -DHAVE_CONFIG_H -g -O2 -c error.c gcc -I. -I.. -I. -I../lib -I../zlib -DHAVE_CONFIG_H -g -O2 -c ./zlib.c gcc add.o admin.o buffer.o checkin.o checkout.o classify.o client.o commit.o create_adm.o cvsrc.o diff.o edit.o entries.o expand_path.o fileattr.o find_names.o hardlink.o hash.o history.o ignore.o import.o lock.o log.o login.o logmsg.o main.o mkmodules.o modules.o myndbm.o no_diff.o parseinfo.o patch.o rcs.o rcscmds.o recurse.o release.o remove.o repos.o root.o rtag.o scramble.o server.o status.o tag.o update.o watch.o wrapper.o vers_ts.o subr.o filesubr.o run.o version.o error.o zlib.o ../lib/libcvs.a ../diff/libdiff.a -lz -lcrypt -o cvs checkin.o: file not recognized: File truncated collect2: ld returned 1 exit status make[2]: *** [cvs] Error 1 make[2]: Leaving directory `/scratch/rainer/cvs/cvs-1.10.4/src' make[1]: *** [all] Error 1 make[1]: Leaving directory `/scratch/rainer/cvs/cvs-1.10.4' make: *** [build-stamp] Error 2 Couldn't run dpkg-buildpackage: Illegal seek rai16 09:43:24$ I do not think, that it is a cvs problem, because compiling other code seems to have problems too, like /usr/bin/ld: cuddZddGroup.o: invalid string offset 285212672 >= 89 for section `.shstrtab' is quite popular. I would expect the problems more in egcs, libc6 or the kernel itself (the system rebooted this morning automatically). Any ideas what co8uld be wrong? The system was running slink rock-solid for months. rai16 09:55:37$ uname -a Linux rai16 2.2.5 #2 Fri Apr 16 18:58:40 EST 1999 i686 unknown rai16 09:55:40$ gcc -v Reading specs from /usr/lib/gcc-lib/i486-linux/egcs-2.91.66/specs gcc version egcs-2.91.66 Debian GNU/Linux (egcs-1.1.2 release) rai16 09:55:43$ ls -l /lib/libc.so.6 lrwxrwxrwx 1 root root 13 May 10 09:09 /lib/libc.so.6 -> libc-2.1.1.so -- Rainer Dorsch Abt. Rechnerarchitektur e-mail:[EMAIL PROTECTED] Uni StuttgartTel.: 0711-7816-215
Re: Freeze stuff, summary.. (perl 5.005, etc)
On Mon, May 10, 1999 at 02:11:42AM -0400, Adam Di Carlo wrote: > > I've been distracted by revenue production for a couple of months. > > Are we expected to upload our packages rebuilt for glibc2.1? > > It wouldn't hurt but I don't think it's necessary. glibc2.1 can > drop-in replace 2.0 (unless you have a program that depends on certain > internal stuff which it shouldn't be using anyway). > > Really, what is more important and has changed is CC from gcc272 to > egcs. But again, it would probably be nice to recompile sometime over > then next two months, but not really necessary AFAIK. Seems that for libs it's a VERY GOOD IDEA to rebuild. I've seen a number of examples of bad things happening with mixed glibc2.0 and glibc2.1 libs. I think the problems stem from gcc2.7/egcs, but they exist all the same. -- Joseph Carter <[EMAIL PROTECTED]>Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBEThe Source Comes First! - does Johnie Ingram hang out here on IRC? pgpfeH2ZpWzxE.pgp Description: PGP signature
Re: Pandora is born
On Mon, May 10, 1999 at 09:30:59AM +0200, Heiko Schlittermann wrote: > : > Debian DNS administrators, please change nonus.debian.org to be a > : > CNAME for pandora.debian.org. > > That's what I call `democracy'. :-( -- Sorry. Um, non-us has been terribly broken since BEFORE I was a developer. In fact, it was broken when I first installed Bo a year and a half ago. You have yourself pointed out a number of problems including lack of diskspace for the mirror and the inability to give the archive maintainers an account which could administer the system (or even at least just the portion of the ssytem that contained the mirror..) I don't mean to sound harsh here, but given all the problems with non-us and its current (still) broken state, a vote would have returned something like 399 to 1 that pandora be where it is. -- Joseph Carter <[EMAIL PROTECTED]>Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBEThe Source Comes First! - * boren tosses matlab across the room and hopes it breaks into a number aproaching infinite peices pgpJLpEcFlsB1.pgp Description: PGP signature
dependency of magicfilter
Hi, I am a member of Debian JP and use potato now. There is some problems on dependency of magicfilter and gs with Japanese support (which is in Debian JP at present ;-). magicfilter 1.2-29 set dependency as follows: Recommends: lpr|lprng, gs (>= 3.33) but gs can not handle Japanese characters correctly so we have gs-aladdin-vflib with Japanese support in Debian JP and it provides gs and gs-aladdin. (vflib is some mechanism to handle Japanese characters and is packaged in Debian JP) Unfortunately dselect (or dpkg or apt ?) can not handle version numbers in this case, that is gs-aladdin-vflib can not Provides: gs (>= 3.33) resonably. This prevents us, Japanese users, from installing magicfilter and gs with Japanese support. This means Japanese users can not have printing environment with satisfaction in Debian. So I wish to suggest some fixes. - Get changed Suggests: gs (>= 3.33) from Recommends: gs (>= 3.33) Is it possible to reduce Recommends to Suggests as above ? I think that the above is the most resonable and practical solution but there are other means of cource. - Improve dselect (or dpkg or apt) to be able to handle version numbers in dependency fields. - Contribute gs-aladdin-vflib to Debian from Debian JP and get changed the dependency of magicfilter as Recommends: lpr|lprng, gs (>= 3.33)|gs-aladdin-vflib # These are essential fixes but may take a long time. - Get changed as Recommends: lpr|lprng, gs (without version) # But this may be impossible by some reasons I do not recognize. Personally, I hold magicfilter of 1.2-28 which Recommends gs-aladdin without version so compatible with gs-aladdin-vflib. How do you think ? I want any comments about this issue. Or shall I report this to BTS as wishlist ? Thanks in advance, 1999.5.10 -- ** Atsuhito Kohda Dep. Math., Tokushima Univ. [EMAIL PROTECTED]
Re: Corel Setup Design Proposal
> "Andreas" == Andreas Jellinghaus <[EMAIL PROTECTED]> writes: >> I think this is a very difficult point, how do you plan to >> solve this, choose the right Xserver and XF86Config file for >> the users system ? Or do you plan to use the fbdev server ? i >> think not yet all graphic cards have video servers ... Andreas> pretty easy: every recent graphic card is pci or agp, so Andreas> it's detected as pci device and listed in the /proc Andreas> file... Andreas> a list device -> xfree options/server/driver should be Andreas> easy to build (with the combined help of usenet). Hmmm... someone could set up an SQL database, and use that to enter the information. Then a table for the distributed setup software to read could be generated by a formatted select query on that database.
Re: Setup API, The next step (Re: Corel Setup Design Proposal)
> "Dave" == Dave Neil <[EMAIL PROTECTED]> writes: Dave> Hi Everyone, There does not seem to be any objections to the Dave> initial proposal of doing a setup API and perhaps rethinking Dave> how we do an install. Would it be possible to come to a Dave> consensus on this and decide if it's worth pursuing as a Dave> joint project together? It's obviously worth pursuing. The Linux distribution developer community needs this. Dave> Here's an idea for a time table. 1.For Potato i386 we work Dave> together support an X install and the new setup API Dave> system. Perhaps a joint GTK based install GUI if it would Dave> help move this forward. The setup API ought to be specified with something that can be used to generate stubs for both GTK and KDE. There ought to be an underlevel that's in a library of its own, with calls designed for a user interface to utilize as a backend. Maybe that backend code could run in separate threads, so the UI can stay fresh and display status information? (I'll try and keep that sort of thing in the back of my mind while I read. I've begun to read about C++ and OOP.) (KDE/QT and Gnome/GTK+ ought to get their heads together and specify a standard way of propagating style or theme information and whatnot. Do I stand alone on this one? Am I way off base?) I've only a vague notion of this sort of system at this point... as I've been saying lately, ask me again in two years. I'll shut up now. :-| Dave> 3.We help with the dselect replacement, perhaps starting Dave> with work based around gnome-apt. I liked the idea of a common `thing' that could be driven by a UI running with either X (pick your GUI toolkit of choice), curses, CGI/WWW or perhaps even an automated thing, like Red Hat's `kickstart'. What ever happened to `deity'? I thought it was pretty neat. Like the emacsen and xwpe, it ran on both X and a console or xterm. Not too shabby, IMO. I guess if it used GGI, it would do framebuffers, tty, and X all from one program, isn't that right? What's the KDE `kpackage' like? How does it compare to `gnome-apt' and `dselect'? I've never gotten it to build. (It bombs in the rpm support stuff.) Something I've noticed about `gnome-apt' and `apt' is that they don't seem to support removing and purging a package as separate things. I think it's important for the package tools to have both of those options available. If `dselect' had the filtering things that `gnome-apt' had, it would be very much improved! I still like it better than `gnome-apt' for many reasons, in particular, for keyboard control of the interface. Dave> We here at Corel can and will put a lot of our resources Dave> into developing this. My hope is that we can work together Dave> to help Debian also benefit from this. By keeping it Dave> flexible in its design we should be able to make it fit into Dave> each our own visions of how it behaves and looks. This is Dave> now up to you the Debian developers to decide if it's ago. I'll help by continuing my studies. It's great that Corel is getting involved with the Debian project! I'd like to see others here as well, including Red Hat software. Corporate industry support is something we need, both for mentorship and potential future paying jobs. What ever happened to `Yggdrasil Plug-n-Play Linux'? They have the best name for a Linux distribution out of all of them, IMO. It's occured to me that perhaps "Yggdrasil" would be a better name for Debian than "Debian" is. Karl M. Hegbloom, Student, Portland State University, OR, USA Time to read.
Re: Corel Setup Design Proposal
> "Joseph" == Joseph Carter <[EMAIL PROTECTED]> writes: Joseph> Save yourself some pain and use slang for the console Joseph> based installation. What makes `slang' a better choice than `ncurses'?
Re: Compilation problems
On Mon, May 10, 1999 at 09:50:11 +0300, Rainer Dorsch wrote: > checkin.o: file not recognized: File truncated > /usr/bin/ld: cuddZddGroup.o: invalid string offset 285212672 >= 89 for > section `.shstrtab' > I would expect the problems more in egcs, libc6 or the kernel itself (the > system rebooted this morning automatically). I see no similarities with other EGCS or libc6 problem reports. > Any ideas what co8uld be wrong? The system was running slink rock-solid > for months. It sounds much more like a hardware problem (try the suggestions of http://www.bitwizard.nl/sig11) or having corrupted .debs installed (try forcefully reinstalling the current packages e.g. dpkg -OGR /archive). 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
Re: Pandora is born
On Mon, May 10, 1999 at 01:43:09AM -0700, Joseph Carter wrote: : On Mon, May 10, 1999 at 09:30:59AM +0200, Heiko Schlittermann wrote: : > : > Debian DNS administrators, please change nonus.debian.org to be a : > : > CNAME for pandora.debian.org. : > : > That's what I call `democracy'. :-( -- Sorry. I meant the way decisions are made. The discussion about a new nonus server has been here and in personal mails about 1 .. 3 months before, but with no real conclusion. [ The only result was, that some people (including Guy) wanted to help -- but didn't (this is no critism, it's only a fact). ] : You have yourself pointed out a number of problems including lack of : diskspace for the mirror and the inability to give the archive Diskspace problems have been solved a long time ago. Archive access was given to the people who wanted to help. : maintainers an account which could administer the system (or even at : least just the portion of the ssytem that contained the mirror..) The mirror and the nonus server are different things. : I don't mean to sound harsh here, but given all the problems with non-us : and its current (still) broken state, a vote would have returned The very current state is that incoming is closed since it was misused. But this state would have been changed in the next days. Best Regards from Dresden/Germany Heiko -- [internet & unix support - Heiko Schlittermann] [http://debian.schlittermann.de/";> Debian 2.1 CD ] [Heiko Schlittermann HS12-RIPE finger:[EMAIL PROTECTED] -] [pgp: A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92 ---]
Re: Corel Setup Design Proposal
On Mon, May 10, 1999 at 01:59:24AM -0700, Karl M. Hegbloom wrote: > > "Joseph" == Joseph Carter <[EMAIL PROTECTED]> writes: > > Joseph> Save yourself some pain and use slang for the console > Joseph> based installation. > > What makes `slang' a better choice than `ncurses'? Besides that ncurses makes stupid assumptions, is slower, and does more? => -- Joseph Carter <[EMAIL PROTECTED]>Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBEThe Source Comes First! - * dark greets liw with a small yellow frog. * liw kisses the frog and watches it transform to a beautiful nerd girl, takes her out to ice cream, and lives happily forever after with her liw: Umm it's too late to have the frog back? pgpxnqCY42A5v.pgp Description: PGP signature
Re: [ashp@bastard.co.uk: Bug#37349: qt1g needs urgent recompile for potato]
On Mon, May 10, 1999 at 01:37:24AM -0700, Joseph Carter wrote: : On Mon, May 10, 1999 at 09:27:16AM +0200, Heiko Schlittermann wrote: : > Hello, : > : > is some of you maintainers willing to recompile the qt1-1.42 package : > on a potato system and then do a NMU? (I don't have a potato system : > currently.) : : I can do this, and I can even bring it up to current standards version : and PROBABLY even do the newest release version (1.44 iirc) if you like. OOps, I thought we meant the latest 1.44 release. (I've done uploads of 1.44 about 2 days ago. They're installed already.) You may take 'em from master or from http://master.debian.org/~heiko/qt2/ Best Regards from Dresden/Germany Viele Gruesse aus Dresden Heiko Schlittermann -- [internet & unix support - Heiko Schlittermann] [http://debian.schlittermann.de/";> Debian 2.1 CD ] [Heiko Schlittermann HS12-RIPE finger:[EMAIL PROTECTED] -] [pgp: A1 7D F6 7B 69 73 48 35 E1 DE 21 A7 A8 9A 77 92 ---]
Debian.Org and nameservers
I just noticed that debian.org has a boatload of nameservers: # host -t ns debian.org debian.org NS saens.debian.org debian.org NS va.debian.org debian.org NS pandora.debian.org debian.org NS murphy.debian.org debian.org NS buoy.com debian.org NS www2.buoy.com debian.org NS ns2.cistron.nl debian.org NS miriam.fuller.edu debian.org NS open.hands.com debian.org NS ns1.waw.com debian.org NS ns1.ldsol.com debian.org NS samosa.debian.org However, for a nameserver to be useful, it must be registered at internic. It's no use to say "ns.domain.com is the nameserver for domain.com" if ns.domain.com isn't registered at a root nameserver itself (chicken-egg). Well, for most of the nameservers with debian.org: # for i in saens.debian.org va.debian.org pandora.debian.org murphy.debian.org samosa.debian.org; do host -a $i a.root-servers.net; done saens.debian.org ANY record currently not present at a.root-servers.net va.debian.org A 209.81.8.242 pandora.debian.org ANY record currently not present at a.root-servers.net murphy.debian.org ANY record currently not present at a.root-servers.net samosa.debian.org ANY record currently not present at a.root-servers.net So, listing saens, pandora, murphy and samosa as nameservers for debian.org is useless. Another thing, according to Internic only 3 servers have been registered as nameservers for debian.org: # host -t ns debian.org a.root-servers.net debian.org NS BUOY.COM debian.org NS WWW2.BUOY.COM debian.org NS VA.debian.org So the nameservers at cistron, fuller, hands, waw and ldsol are of questionable use as well. Perhaps someone should fix this .. Mike. -- Indifference will certainly be the downfall of mankind, but who cares?
Current problems with libc6_2.1.1-2
Folks, There has been talk on this for over a week, but I haven't seen a solution posted. I have managed to take control of my machine, by booting "init=/bin/sh", and starting the network manually. Even downloaded libc6_2.1.1-3, which I assume will fix the problem. I have seen others also talking about the problem, but there doesn't seem to be a solution posted. However, the installation fails, as tar fails (chown problem). Any solutions? Please keep the subject line the same, I will summarize twice daily. Regards, Sanjeev "Ghane" Gupta Tel: +91(11) 6941831, 6946619 Eurolink Systems LtdFax: +91(11) 6943732 New Delhi, India email: [EMAIL PROTECTED] Eurolink doesn't pay me to speak for it, so I don't Old age is not an accomplishment, nor youth a sin
Re: Pandora is born
In article <[EMAIL PROTECTED]>, Joseph Carter <[EMAIL PROTECTED]> wrote: >Um, non-us has been terribly broken since BEFORE I was a developer. In >fact, it was broken when I first installed Bo a year and a half ago. Not to mention that the European connectivity of pandora is _way_ better than that of the current nonus. It's in Germany and I can't even reach it most of the time from the Netherlands (and that's nextdoor). That's because the Dutch scientific network (Surfnet) has a very open peering policy while the German one (DFN) has a very closed peering policy, alas. Mike. -- Indifference will certainly be the downfall of mankind, but who cares?
Re: Compilation problems
Finally, it turned out, that it is a bug in the NFS-code/-setup. When I copy the file to a local hard disk (even with cp from a NFS mounted disk), I can compile cvs without any problems (and even to times). Before it was impossible to get Code which does not segault. The NFS server is a SUN-UltraSPARC running Solaris 2.6. My mount options are ramona:/export/disk1/scratchnfs defaults 0 2 Does not look suspicious, does it? Can I do more experiments, before I report a bug? --Rainer. > On Mon, May 10, 1999 at 09:50:11 +0300, Rainer Dorsch wrote: > > checkin.o: file not recognized: File truncated > > > /usr/bin/ld: cuddZddGroup.o: invalid string offset 285212672 >= 89 for > > section `.shstrtab' > > > I would expect the problems more in egcs, libc6 or the kernel itself (the > > system rebooted this morning automatically). > > I see no similarities with other EGCS or libc6 problem reports. > > > Any ideas what co8uld be wrong? The system was running slink rock-solid > > for months. > > It sounds much more like a hardware problem (try the suggestions of > http://www.bitwizard.nl/sig11) or having corrupted .debs installed (try > forcefully reinstalling the current packages e.g. dpkg -OGR /archive). > > 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
Packaging needed for IDL (libidl)
Hi all, Don't ask me what it does, I just know that mozilla code demands it :) So I'll package it. Download location is ftp.mozilla.org, but I'll try to find the origin. The licence is LGPL. If someone could grab it from me (either now, or after I do the initial packaging), I would REALLY appreciate it. -- enJoy -*/\*- http://jagor.srce.hr/~jrodin/
Re: Current problems with libc6_2.1.1-2
On Mon, May 10, 1999 at 02:43:39PM +0530, Sanjeev Gupta wrote: > Folks, > > There has been talk on this for over a week, but I haven't seen a solution > posted. I have managed to take control of my machine, by booting > "init=/bin/sh", and starting the network manually. Even downloaded > libc6_2.1.1-3, which I assume will fix the problem. > > I have seen others also talking about the problem, but there doesn't seem > to be a solution posted. > > However, the installation fails, as tar fails (chown problem). Are you running a 2.2 kernel? > Any solutions? Please keep the subject line the same, I will summarize > twice daily. The solution currently is to run a 2.2 kernel (except on sun4m which requires >= 2.2.7). The preinst checks for the correct kernel version and fails otherwise. We are still trying to find a way to get this to work with kernel 2.2 without regard to the sun4m problem.
Never mind... [Packaging needed for IDL (libidl)]
On Mon, May 10, 1999 at 02:32:44PM +0200, Josip Rodin wrote: > Don't ask me what it does, I just know that mozilla code demands it :) Hm. Apparently, this already exists as part of liborbit0, so I'll probably try to use that one. -- enJoy -*/\*- http://jagor.srce.hr/~jrodin/
Re: Pandora is born
On Mon, May 10, 1999 at 12:36:33PM +0200, Miquel van Smoorenburg wrote: > In article <[EMAIL PROTECTED]>, > Joseph Carter <[EMAIL PROTECTED]> wrote: > >Um, non-us has been terribly broken since BEFORE I was a developer. In > >fact, it was broken when I first installed Bo a year and a half ago. > > Not to mention that the European connectivity of pandora is _way_ > better than that of the current nonus. It's in Germany and I can't even > reach it most of the time from the Netherlands (and that's nextdoor). Not just European connectivity; to pandora I get 100% return, ~600ms; [11:07pm] [EMAIL PROTECTED]:~> ping nonus.debian.org PING dresden.de.debian.org (141.76.20.99): 56 data bytes 64 bytes from 141.76.20.99: icmp_seq=0 ttl=42 time=1325.5 ms 64 bytes from 141.76.20.99: icmp_seq=3 ttl=42 time=840.7 ms 64 bytes from 141.76.20.99: icmp_seq=5 ttl=42 time=1158.9 ms 64 bytes from 141.76.20.99: icmp_seq=6 ttl=42 time=814.5 ms 64 bytes from 141.76.20.99: icmp_seq=7 ttl=42 time=823.1 ms 64 bytes from 141.76.20.99: icmp_seq=8 ttl=42 time=881.2 ms 64 bytes from 141.76.20.99: icmp_seq=9 ttl=42 time=980.8 ms 64 bytes from 141.76.20.99: icmp_seq=10 ttl=42 time=933.7 ms 64 bytes from 141.76.20.99: icmp_seq=11 ttl=42 time=863.9 ms --- dresden.de.debian.org ping statistics --- 13 packets transmitted, 9 packets received, 30% packet loss round-trip min/avg/max = 814.5/958.0/1325.5 ms :-( -- Hamish Moffatt VK3SB (ex-VK3TYD). CCs of replies from mailing lists are welcome.
Re: Pandora is born
On Mon, May 10, 1999 at 01:43:09AM -0700, Joseph Carter wrote: > On Mon, May 10, 1999 at 09:30:59AM +0200, Heiko Schlittermann wrote: > > : > Debian DNS administrators, please change nonus.debian.org to be a > > : > CNAME for pandora.debian.org. > > > > That's what I call `democracy'. :-( -- Sorry. > > Um, non-us has been terribly broken since BEFORE I was a developer. In > fact, it was broken when I first installed Bo a year and a half ago. I think you're exagerating here, and that doesn't help the situation one bit. Hamish -- Hamish Moffatt VK3SB (ex-VK3TYD). CCs of replies from mailing lists are welcome. pgpYTgAk6hCmw.pgp Description: PGP signature
Re: Current problems with libc6_2.1.1-2
On Mon, 10 May 1999, Collins M. Ben wrote: > On Mon, May 10, 1999 at 02:43:39PM +0530, Sanjeev Gupta wrote: > > Folks, > > > > I have seen others also talking about the problem, but there doesn't seem > > to be a solution posted. > > > > However, the installation fails, as tar fails (chown problem). > > Are you running a 2.2 kernel? No, 2.0.35. 2.2.7 (self-compiled failed to boot, ditto 2.2.7 from .deb) > > Any solutions? Please keep the subject line the same, I will summarize > > twice daily. > > The solution currently is to run a 2.2 kernel (except on sun4m which > requires >= 2.2.7). I can't put in the 2.2.7 kernel now, as tar complains of chown problems. Summary: libc2.1.1-2 kernel 2.0.35 Boots, can't logon (Unable to change tty /dev/ttyp0: Success) chown broken libc2.1.1-2 kernel 2.2.7 Doesn't boot I was thinking of running the preinst/postinst scripts myself, if libc6 2.2.1-3 is OK. In what order do I run libc 2.2.1-2 postrm / 2.2.1-3 preinst? Thanks, Sanjeev "Ghane" Gupta Tel: +91(11) 6941831, 6946619 Eurolink Systems LtdFax: +91(11) 6943732 New Delhi, India email: [EMAIL PROTECTED] Eurolink doesn't pay me to speak for it, so I don't Old age is not an accomplishment, nor youth a sin
Re: Current problems with libc6_2.1.1-2
On Mon, May 10, 1999 at 06:43:44PM +0530, Sanjeev Gupta wrote: > I can't put in the 2.2.7 kernel now, as tar complains of chown problems. Boot using the one of the 2.2.1 resc1440 disks from slink and copy over the 2.2.1 kernel. You should be able to boot using that and be ok. If you experience the failure of init, then boot by passing the init=/bin/bash argument to SILO and follow the instructions I posted just a few minutes ago to another person with similar problems. > I was thinking of running the preinst/postinst scripts myself, if libc6 > 2.2.1-3 is OK. In what order do I run libc 2.2.1-2 postrm / 2.2.1-3 > preinst? glibc 2.1+ in potato is going to require a 2.2 kernel so this wont help. To be honest I am not sure how you passed the preinst phase since it should fail to even unpack the glibc 2.1.1. I'll look into why that happened.
Re: dependency of magicfilter
Note that the same problem occurs when using magicfilter with gs-aladdin. Jay Treacy
Re: Release Plans (1999-05-10)
On 10/05, Richard Braakman wrote: | * glibc 2.1 upgrade | As far as I know, this project is largely complete. There are one or two | bugs left in the backward compatibility code, and there's the question | of what to do with /dev/pts. Not largely complete on Sparc (we still have problems with Sun4m), but Ben Collins is actively working on fixing this :)
Re: Release Plans (1999-05-10)
On Mon, May 10, 1999 at 07:06:58PM +0200, Richard Braakman wrote: [...] > A number of release goals have been proposed. I don't intend to start > the freeze until all release goals are in place. [...] > * Working disk sets for all released architectures. > I don't know much about the plans for the boot-floppies yet. Could > someone volunteer as a contact person, or tell me the best list to read? The best list is [EMAIL PROTECTED] The main problem we are facing is our official 2.2.x kernels are huge, and there's no way to put the kernel and the root.bin image on a single floppy. The proposed solution is building a modularized kernel, and loading the needed modules using an initrd image, but AFAICT, there's nobody working on that. -- Enrique Zanardi[EMAIL PROTECTED]
Re: Current problems with libc6_2.1.1-2
On Mon, May 10, 1999 at 09:58:16AM -0400, Collins M. Ben wrote: > glibc 2.1+ in potato is going to require a 2.2 kernel so this wont help. > To be honest I am not sure how you passed the preinst phase since it > should fail to even unpack the glibc 2.1.1. I'll look into why that > happened. What? Linux apocalypse 2.0.36 #1 Mon Nov 16 21:24:03 EST 1998 i586 unknown ii libc6 2.1.1-3GNU C Library: Shared libraries and timezone Is my machine a ticking time bomb or something? Will it not boot up next time I have to reboot? Other than putting the acct package on hold, I've been tracking potato pretty closely. -- G. Branden Robinson |Yesterday upon the stair, Debian GNU/Linux |I met a man who wasn't there. [EMAIL PROTECTED] |He wasn't there again today, cartoon.ecn.purdue.edu/~branden/ |I think he's from the CIA. pgpYXWL5QbfWV.pgp Description: PGP signature
Re: Homapages in list of maintainers
Hi, I'm one of the members in Debian JP, and a self candidate to a maintainer in Debian. # I have sent application mail to [EMAIL PROTECTED] at May 05 1999. # I have much curiosity at the processing time to join the Debian project. # (I waited to join XFree86 as a non-voting member just 11days, 2 years ago) In article <[EMAIL PROTECTED]> Atsuhito Kohda <[EMAIL PROTECTED]> writes: > From: Andreas Tille <[EMAIL PROTECTED]> > Subject: Re: Homapages in list of maintainers > Date: Fri, 7 May 1999 11:27:03 +0200 (METDST) > > By the way: is there really a need to split Debian JP from > > Debian?? Sounds curious for me. > No, completely no :-) My poor English may confuse you but > the aim of Debian JP is > - to help Debian to be more internationalized, > - and so Debian JP will contribute packages created by maintainers > of Debian JP to Debian. ... > But some barriers prevent us from becoming official maintainers > so the merging Debian JP into Debian does not work well now. I have heard that some self-candidates from Debian JP felt that the Debian Project rejects them as a maintainer, because: one of them had not receive no answers for long time, more than a month is too long enough for ordinary people. one of them did not have no English-written certificate, He was a high school student at that time, and did not have the passport. He can not get Driver's License since the laws in Japan prohibit those under 18-years-old to get the license, as well as many high school in Japan also prohibit their student to get the license as the school rules. (In fact, the Driver's License itself is no-use because that is all written in Japanese, so the required is not only the license itself, but also International License with extra fee.) He got the chance to meet fellow Debian maintainers face to face after all, but it takes some extra period and effort unnecessary. and one of them had not enough time to wait the oversea call at home. He worked at laboratory, and during the experimentation, he can't respond any call. The experimentation sometimes continues all over the night. He can make time to debianize some software and he already uploads some interesting packages to Debian JP, but he can't upload to Debian now although he himself wishes to do it. He wishes that let him know at least the time of calling in advance, so he can prepare to respond the call. Currently, nothing is to be known when the telephone rings, even at day, night, or midnight. "developers-reference" told us A phone number where we can call you. Remember that the new maintainer team usually calls during evening hours to save on long distance tolls. Please do not give a work number, unless you are generally there in the evening. but When is the "evening hours" ? or Where this "the evening hours" have meaning at ? We don't know where the person at new-maintainer lives in. If he lives in, say, NewYork city, "the evening hours" may be 17:00-21:00 there, and 07:00-11:00 morning here. Without the announce in advance, those who lives in Japan have some difficulty to continue to wait a telephone call hopelessly for a few months at such working time. Some days ago, the dispute arose on Debian JP project, about the release of next JP Packages. We think that the JP Packages should (at least) be slim as much as we can, and our goal is the abolishment of JP Packages (all JP Pacakges either go into Debian or get being unnecessary, that means we do not require the separate localized packages to handle with our language). Some members including current Debian maintainers (whom we call as "official maintainers") insist that the action should have taken now to speed up the contribution of JP packages into Debian. The proposed action is to make an explicitly declaration that "official" maintainers can freely take and move the JP packages debianized by non "official" maintainers. Why is this needed ? There is a barrier or filter to be a maintainer on Debian currently, and it is easy to take and move than to wait patiently the willing JP member to be registered as a maintainer. BTW, related to that dispute, an "official" maitainer said the "filter" works effectively. Is this the common idea to Debian people ? Does Debian needs the filter to trap and drop the willing self-candidate who have made and maitained a qualified package already ? "developers-reference" told us: The process of registering as a developer is a process of verifying your identity and intentions. As the number of people working on Debian GNU/Linux has grown to over 400 people and our systems are used in several very important places we have to be careful about being compromised. Therefore, we need to verify new maintainers before we can give them accounts on our servers and letting them upload packages. I understand (or at lea
Re: Release Plans (1999-05-10)
I think that Power PC will be included in potato. Am I wrong? Have a nice day,Paulo Henrique Quoting Ossama Othman ([EMAIL PROTECTED]): > Hi, > > On 10 May, Richard Braakman wrote: > > * GNOME > > I wasn't there to see it, but I hear that the GNOME staging area has > > now been folded into potato and is ready for the freeze. > > It has. However, there are still some packages that may not have made > it in to the archive that need to be in there (e.g. libgtop1, > libghttp1). I posted to the debian-gtk-gnome list about this issue but > haven't received a response yet. > > > Return of the Revenge of Slink: > > A Debian 2.1r3 release should be made soon, to fix a number of > > outstanding bugs. I'll write a separate mail about this. > > It would be nice to get a GNOME update for slink, too. However, I'm > not sure where GNOME for slink stands. The last I heard, we are not in > synch with potato's GNOME yet. > > -Ossama > -- > Ossama Othman <[EMAIL PROTECTED]> > Center for Distributed Object Computing, Washington University, St. Louis > 58 60 1A E8 7A 66 F4 44 74 9F 3C D4 EF BF 35 88 1024/8A04D15D 1998/08/26 > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] >
Re: Release Plans (1999-05-10)
Samuel Tardieu <[EMAIL PROTECTED]> writes: > On 10/05, Richard Braakman wrote: > > | * glibc 2.1 upgrade > | As far as I know, this project is largely complete. There are one or two > | bugs left in the backward compatibility code, and there's the question > | of what to do with /dev/pts. > Not largely complete on Sparc (we still have problems with Sun4m), but > Ben Collins is actively working on fixing this :) I believe the problem is known and we have a fix. I'm just waiting for a stock Linus kernel to show up with the appropriate patches in it, so we can add it to potato. Same thing with X 3.3.3.1. We need a late kernel for Creator and Mach64 systems (and, perhaps, LEO systems). Steve [EMAIL PROTECTED]
intent to package some locale and i18n Perl modules
Hi, I intent to package the following Perl modules: - Locale::Maketext Locale::Maketext is a base class providing a framework for software localization and inheritance-based lexicons, as described in an article in The Perl Journal #13. Note that this is an underdocumented alpha release (the full version is on its way). It requires I18N::LangTags. - I18N::LangTags - functions for dealing with RFC1766-style language tags Language tags are a formalism, described in RFC 1766, for declaring what language form (language and possibly dialect) a given chunk of information is in. This library provides functions for common tasks involving language tags (notably the extraction of them, comparing them, and testing the formal validity of them) as is needed in a variety of protocols and applications. - Locale-Codes Distribution This distribution contains two modules which can be used to process ISO two letter codes for identifying language and country. Locale::Language Two letter codes for language identification (ISO 639). For example, 'en' is the code for 'English'. Locale::Country Two letter codes for country identification (ISO 3166). For example, 'bo' is the code for 'Bolivia'. The primary use (for me at least) is in the DebianDoc-SGML package. Thanks, Ardo -- Ardo van Rangelrooij home email: [EMAIL PROTECTED], [EMAIL PROTECTED] home page: http://www.tip.nl/users/ardo.van.rangelrooij PGP fp: 3B 1F 21 72 00 5C 3A 73 7F 72 DF D9 90 78 47 F9
Re: Release Plans (1999-05-10)
On May 10, Paulo Henrique Baptista de Oliveira wrote: > I think that Power PC will be included in potato. It will be definitly.
Re: Release Plans (1999-05-10)
At 19:06 +0200 1999-05-10, Richard Braakman wrote: * glibc 2.1 upgrade As far as I know, this project is largely complete. There are one or two bugs left in the backward compatibility code, and there's the question of what to do with /dev/pts. No there isn't, /dev/pts is taken care of. * glibc 2.1 source compatibility A larger task is to ensure that all packages still compile on a glibc 2.1 development system. The sparc people may have a list of problem packages. Most problems in this area have been fixed by the combined effort of the sparc, arm, and powerpc porters. However, many of the patches are sitting in the BTS and have yet to be applied. Potato Architectures: As far as I know it will be the same set as in slink, i.e. i386, m68k, sparc, and alpha. If any other architectures want to make a release they will have to decide soon. powerpc wishes to try for potato. -- Joel Klecker (aka Espy)Debian GNU/Linux Developer mailto:[EMAIL PROTECTED]> mailto:[EMAIL PROTECTED]> http://web.espy.org/> http://www.debian.org/>
Re: Release Plans (1999-05-10)
Le Mon, May 10, 1999 at 07:06:58PM +0200, Richard Braakman écrivait: > * perl 5.005 > I've been assured that a working upgrade plan now exists and is being > worked on, one that will not involve recompiling a lot of packages. > I'll still be happier if perl 5.005 is introduced at the start of > the next release cycle, though. There's a lot of perl code in Debian > that hasn't been tested with the new version. I've been working with the previous perl5.005 package (the one that had been uploaded to slink and retracted after) and I did not have many problems. Many of them were only paths problems (that may not appear with the official perl5.005 package). And I've already filled some bugs against netbase and netstd so that the packages do not break when perl5.005 is uploaded. Some other packages may need little changes but that would not be a problem. I'll propose myself as coordinator for the perl5.005 upgrade (you did explain that you wanted a coordinator for each release goal). > debian-release mailing list: > I think this is a good idea, and I will certainly join such a list. I'll join too. > A Debian 2.1r3 release should be made soon, to fix a number of > outstanding bugs. I'll write a separate mail about this. I hope that you'll include my NMU of dpkg. It didn't get installed into stable-updates so far ... Cheers, -- Raphaël Hertzog >> 0C4CABF1 >> http://prope.insa-lyon.fr/~rhertzog/
Re: Release Plans (1999-05-10)
Enrique Zanardi <[EMAIL PROTECTED]> writes: > On Mon, May 10, 1999 at 07:06:58PM +0200, Richard Braakman wrote: > > * Working disk sets for all released architectures. > > I don't know much about the plans for the boot-floppies yet. Could > > someone volunteer as a contact person, or tell me the best list to read? > > The best list is [EMAIL PROTECTED] The main problem we are > facing is our official 2.2.x kernels are huge, and there's no way to put > the kernel and the root.bin image on a single floppy. The proposed > solution is building a modularized kernel, and loading the needed modules > using an initrd image, but AFAICT, there's nobody working on that. Yes... I am troubled by this. I'd like to go into freeze with a mildly functional boot-floppies. Unfortunately, I'm too busy to hack code for this. Anyhow, so this is a big concern for potato. However, I think we should just start by basically zoinking the RedHat initrd stuff, as much as we can. I know Corel is interested in this too. Richard, you forgot a number of other items: What architectures will be in potato? Clearly, all the slink ones -- will PowerPC be ready too? Hurd-i386? (good god, I don't want to even *think* about what we'll need for Hurd boot-floppies -- *shudder*) Debian-CD has a number of problems that need fixing; see the Bugs against the package. Join to help. Are we going to go ahead and try out my new "Release Team" concept? If so, let's make the mailing list and troll the right people to join. BTW, I think it's good to set an *optimistic* freeze date, so people aren't shocked. I would set it at July 1, or maybe Bastille day (Debian pomme de terre?). -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
Re: Homapages in list of maintainers
Taketoshi Sano <[EMAIL PROTECTED]> writes: > I have heard that some self-candidates from Debian JP felt > that the Debian Project rejects them as a maintainer, > because: > > one of them had not receive no answers for long time, > >more than a month is too long enough for ordinary people. Yes, well, it takes from 4 weeks to 6 months or longer for *all* people. I agree this should be shorter... Anyhow Debian-JP is *not* getting singled out. Everyone has this issue. > one of them did not have no English-written certificate, There is no requirement that I know of that any identification must be written in English. > and one of them had not enough time to wait the oversea call at home. > >He worked at laboratory, and during the experimentation, >he can't respond any call. IF there's not way the guy can get a phone call, I'm afraid there's no way they can be confirmed and become a developer. >"developers-reference" told us > >A phone number where we can call you. Remember that >the new maintainer team usually calls during >evening hours to save on long distance tolls. >Please do not give a work number, unless you are generally >there in the evening. > >but When is the "evening hours" ? or Where this "the evening hours" >have meaning at ? We don't know where the person at new-maintainer >lives in. If he lives in, say, NewYork city, "the evening hours" >may be 17:00-21:00 there, and 07:00-11:00 morning here. >Without the announce in advance, those who lives in Japan have >some difficulty to continue to wait a telephone call hopelessly >for a few months at such working time. According to James, all he says is "it's unlikely to be between 8AM and 4PM British time on Monday-Friday". No one is asking you to sit by the phone for 3 months. But if you can only be reached at number XX-YYY at the hours of 3-7 GMT on Saturday, then tell the new maintainers that. Give them time windows that work for you. Give them a few different numbers and suggested times. I mean, common sense, people. > Some members including current Debian maintainers (whom we call > as "official maintainers") insist that the action should have > taken now to speed up the contribution of JP packages into Debian. > The proposed action is to make an explicitly declaration that > "official" maintainers can freely take and move the JP packages > debianized by non "official" maintainers. > > Why is this needed ? There is a barrier or filter to be a maintainer > on Debian currently, and it is easy to take and move than to wait > patiently the willing JP member to be registered as a maintainer. Sure, but put people in the queue. It may take up to 3 months or longer if you're hard to reach on the phone -- so just plan on that. > BTW, related to that dispute, an "official" maitainer said > the "filter" works effectively. Is this the common idea to > Debian people ? Does Debian needs the filter to trap and drop > the willing self-candidate who have made and maitained > a qualified package already ? Well, sure, this is a decent stop-gap measure, so long as the "filter" person is able to do their job and keep up, and forward bugs on to the actual person who knows the code. > I understand (or at least hope to understand) this and I think also > some verification mechanism is required. But I doubt the enoughness > and effectiveness of the current processing mechanism. Well, I think it's pretty clear that we need more active people in the New Maintainer Group. I hereby volunteer (I'm in the US, NYC area, and only speak English and smidgeons of Spanish, German, and French). > P.S. > I think, and hope that the Debian is "open" project. It is -- don't get paranoid. The New Maintainer Group is just swamped a bit. I think it needs more people -- highly trustable people, of course. -- .Adam Di [EMAIL PROTECTED]http://www.onShore.com/>
Re: Release Plans (1999-05-10)
Moin all, > * Working disk sets for all released architectures. > I don't know much about the plans for the boot-floppies yet. Could > someone volunteer as a contact person, or tell me the best list to read? A minimum is two months for this -- if we start now to work on this. > * glibc 2.1 source compatibility > A larger task is to ensure that all packages still compile on a glibc > 2.1 development system. The sparc people may have a list of problem > packages. The packages must work for glibc-2.1 _and_ linux-2.2, this is important. I think we have more then 100 release-critical bugs, not all such bugs are marked as critical. I've put my autobuilder logfiles (for bad packages) on http://master.debian.org/~koptein -- please have a look at it. This are not all glibc-2.1, linux or dpkg bugs, but mainly. > Timescale: > The freeze is at least one month away, and possibly a lot more than > that. I'm not going to set a date until the number of > release-critical bugs has been reduced considerably. Correct. > Potato Architectures: > As far as I know it will be the same set as in slink, i.e. i386, m68k, > sparc, and alpha. If any other architectures want to make a release > they will have to decide soon. + PowerPC The biggest showstopper are the boot-floppies -- for all architectures! Other topics: language support for boot-floppies (and then also cd-images) and dpkg & dselect (and newer apt-get versions). mozilla should work for potato Thnx, Hartmut
Re: Release Plans (1999-05-10)
Le Mon, May 10, 1999 at 07:06:58PM +0200, Richard Braakman écrivait: > * Working disk sets for all released architectures. > I don't know much about the plans for the boot-floppies yet. Could > someone volunteer as a contact person, or tell me the best list to read? There's also another thing that need to be worked on, the CDs. The script creating the images is not smart enough to select just the good number of packages for each CDs. Currently, the two binary CDs can still be generated for potato but not the source images (they are too big). And many dependencies on the first CD are not met. Cheers, -- Raphaël Hertzog >> 0C4CABF1 >> http://prope.insa-lyon.fr/~rhertzog/
Re: Current problems with libc6_2.1.1-2
Quoting Branden Robinson <[EMAIL PROTECTED]>: > Is my machine a ticking time bomb or something? Will it not boot up next > time I have to reboot? > > Other than putting the acct package on hold, I've been tracking potato > pretty closely. I'm not sure about glibc requiring 2.2.x but I have noticed (at least with one particular machine) that gnome/enlightenment (together) doesn't like 2.0.x kernels... fresh install (3 times in a row) using the stock kernel for some reason if you (well, me) use gnome-session to start up enlightenment, enlightenment hangs during startup. Immediatly upgrade to 2.2.5 and blamo...it works. this is just strange... Ivan =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ivan E. Moore II Rev. Krusty http://snowcrash.tdyc.com[EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- GPG KeyID=0E1A75E3 GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Release Plans (1999-05-10)
Hi, > BTW, I think it's good to set an *optimistic* freeze date, so people > aren't shocked. I would set it at July 1, or maybe Bastille day > (Debian pomme de terre?). For slink update or for potato? For potato we new min. two months and only if we start now working very hard (all maintainers, not only 10 people or so) on bad packages & boot-floppies & cd-images. The QA-team must then also have the power to do massive NMU's. How many open bugs have we, more then 7000? This must be down to ~1000. Thanks, Hartmut
Re: Release Plans (1999-05-10)
> The best list is [EMAIL PROTECTED] The main problem we are > facing is our official 2.2.x kernels are huge, and there's no way to put > the kernel and the root.bin image on a single floppy. The proposed > solution is building a modularized kernel, and loading the needed modules > using an initrd image, but AFAICT, there's nobody working on that. What about the ramdisk/root.bin (and then also for the netboot-ramdisk)? They are also very huge now. Floppies with 1.7MB isn't good ... Regards, Hartmut
Re: Pandora is born
Joseph Carter <[EMAIL PROTECTED]> writes: > Um, non-us has been terribly broken since BEFORE I was a developer. In > fact, it was broken when I first installed Bo a year and a half ago. Newbie ;-) > You have yourself pointed out a number of problems including lack of > diskspace Hasn't been the concern for non-US. Unless you count a defect disk drive as lack of diskspace. > and the inability to give the archive > maintainers an account which could administer the system (or even at > least just the portion of the ssytem that contained the mirror..) Well, we don't have multiple systems on one iron. A separate system would have solved this, and some months ago Wichert offered a sponsored box (probably the one that is pandora now ?). Wichert seems to prefer to run non-us in his neighbourhood. Hope we won't get a Debian Leader in China. Or Island, Tuvalu, wherever ;-) Sven -- Sven Rudolph <[EMAIL PROTECTED]>http://www.sax.de/~sr1/
Re: Release Plans (1999-05-10)
> There's also another thing that need to be worked on, the CDs. The > script creating the images is not smart enough to select just the > good number of packages for each CDs. Currently, the two binary CDs > can still be generated for potato but not the source images (they are too > big). And many dependencies on the first CD are not met. For m68k-mac and powermac we need 'hybrid' cd-images (msdos + hfs).
Re: Release Plans (1999-05-10)
On Mon, May 10, 1999 at 08:55:44PM +0200, Hartmut Koptein wrote: [...] > Other topics: language support for boot-floppies (and then also cd-images) >and dpkg & dselect (and newer apt-get versions). Almost ready for boot-floppies, we just need a dialog box for language selection at run-time, and space for ~10 message catalogs on the rescue disk. -- Enrique Zanardi[EMAIL PROTECTED]
Re: Release Plans (1999-05-10)
Sorry folks. I inadvertently posted to debian-devel-announce instead of debian-devel. (thanks to Brandon and Edward for pointing this out) With regard Richard's question regarding GNOME in potato: GNOME has been copied from the staging area into potato. I believe that just about all of the GNOME packages that I copied into Incoming have been installed into the archive. However, at least two packages should get into the archive before the freeze libgtop1 and libghttp1. I've posted to debian-gtk-gnome about this issue but haven't received any reply yet. It'd also be nice to get GNOME for slink out too. All that really needs to be done is to build all of the packages we built for potato for slink. The current GNOME slink packages are not all up-to-date with the potato packages. Many of us don't have slink installed or don't have a chrooted slink setup so any help with getting GNOME slink up-to-date would be greatly appreciated. Thanks, -Ossama -- Ossama Othman <[EMAIL PROTECTED]> Center for Distributed Object Computing, Washington University, St. Louis 58 60 1A E8 7A 66 F4 44 74 9F 3C D4 EF BF 35 88 1024/8A04D15D 1998/08/26
Re: Dents v0.0.3 - DNS server
On May 10, Bdale Garbee <[EMAIL PROTECTED]> wrote: >I suppose it would be possible, but I'm not particularly interested in >maintaining more than one version. A better solution would be to figure out We can't not have a package like BIND in our distribution. If you need some hints about setting up a double source package look at mutt-i (now obsoleted). -- ciao, Marco
KDE debian stuff
Just to let people know who are interested...I've been given CVS access to the kde source so that I can update and keep up to date the kde packages. Stephen has plans for the future (ie, kde 2.0.x and beyond) and just doesn't have time to keep the stuff updated at this time and I volunteered to do it. So if you have beefs with how kde is currently being done from a debian package standpoint and would like to see them done differently please let me know. Here is a current list of things that people have already stated needed to be changed or was a "god it would be nice" kdm not requiring xdm. (I migrated kdm out of kdebase so it is a seperate package..this should take care of this for the time being) migrate kde out of /usr/X11R6/bin and into /usr/bin (requested by someone) fixing up the scripts (still working on this...have current issues with the i18n stuff, but everything else works) Ivan =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ivan E. Moore II Rev. Krusty http://snowcrash.tdyc.com[EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- GPG KeyID=0E1A75E3 GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: KDE debian stuff
> kdm not requiring xdm. (I migrated kdm out of kdebase so it is a seperate > package..this should take care of this for the time being) > migrate kde out of /usr/X11R6/bin and into /usr/bin (requested by someone) > fixing up the scripts (still working on this...have current issues with the > i18n > stuff, but everything else works) /etc/init.d/kdm shouldn't use /etc/X11/config, its obsolete. #!/bin/bash # /etc/init.d/xdm: start or stop XDM. test -f /etc/X11/config || exit 0 grep -q ^xbase-not-configured /etc/X11/config && exit 0 case "$1" in start) grep -q ^start-kdm /etc/X11/config || exit 0 if grep -q ^start-xdm /etc/X11/config then echo "WARNING : can only start kdm or xdm, but not both !" fi Thanks, Hartmut
Re: Release Plans (1999-05-10)
Le Mon, May 10, 1999 at 09:03:37PM +0200, Hartmut Koptein écrivait: > The QA-team must then also have the power to do massive NMU's. Did you read the last text describing QA-members powers ? Isn't it enough ? I don't know. The only problem I may see, is the time we must wait before we are allowed to do an NMU. But from another point of view, speaking as a maintainer I do know that I would not like an NMU of my package if I hadn't the time to respond (but I wouldn't need 3 weeks to respond). But we should stop discussing about this and start working. > How many > open bugs have we, more then 7000? This must be down to ~1000. Ouch. That is about 12 bugs for each developer. :) Cheers, -- Raphaël Hertzog >> 0C4CABF1 >> http://prope.insa-lyon.fr/~rhertzog/
Re: Release Plans (1999-05-10)
On Mon, 10 May 1999, Hartmut Koptein wrote: > > There's also another thing that need to be worked on, the CDs. The > > script creating the images is not smart enough to select just the > > good number of packages for each CDs. Currently, the two binary CDs > > can still be generated for potato but not the source images (they are too > > big). And many dependencies on the first CD are not met. > > For m68k-mac and powermac we need 'hybrid' cd-images (msdos + hfs). A bootable CD for PReP will need a special layout as well. prep image + isofs...looks like we need multiple powerpc binary cd images. -- Matt Porter [EMAIL PROTECTED] This is Linux Country. On a quiet night, you can hear Windows reboot.
Re: KDE debian stuff
Quoting Hartmut Koptein <[EMAIL PROTECTED]>: > /etc/init.d/kdm shouldn't use /etc/X11/config, its obsolete. > yea..I forgot to mention that one as well...currently how I have it is that kdm (as a seperate package) requires xdm and uses a /etc/X11/kdm dir with a config in there instead so that it's happy. The ultimate goal (not just of my but of Stephen's as well) is to make kdm a seperate item and no longer require xdm. But in the meantime I have it jimmied so that it doesn't use /etc/X11/config :) Ivan =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ivan E. Moore II Rev. Krusty http://snowcrash.tdyc.com[EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- GPG KeyID=0E1A75E3 GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Release Plans (1999-05-10)
On Mon, May 10, 1999 at 02:46:44PM -0400, Adam Di Carlo wrote: > Richard, you forgot a number of other items: > > What architectures will be in potato? Clearly, all the slink ones -- > will PowerPC be ready too? Hurd-i386? (good god, I don't want to > even *think* about what we'll need for Hurd boot-floppies -- > *shudder*) Argh! Gimme another month :) Seriously, not yet. We are far from being complete. I have to set up autobuild before I can even think of participating in the release cycle. But nice that you are thinking of us! Boot floppies for Hurd will be pretty easy first, as we have not much to configure yet :P Marcus -- "The purpose of Free Software is Free Software. The End and the Means are the same." -- Craig Sanders Marcus Brinkmann <[EMAIL PROTECTED]>
Re: Homapages in list of maintainers
*Taketoshi Sano wrote: > Hi, I'm one of the members in Debian JP, > and a self candidate to a maintainer in Debian. > > # I have sent application mail to [EMAIL PROTECTED] at May 05 1999. > # I have much curiosity at the processing time to join the Debian project. > # (I waited to join XFree86 as a non-voting member just 11days, 2 years ago) > > I have heard that some self-candidates from Debian JP felt > that the Debian Project rejects them as a maintainer, > because: > > one of them had not receive no answers for long time, > >more than a month is too long enough for ordinary people. > > one of them did not have no English-written certificate, > These complaints are very common on debian-devel, and debian-mentors. Many people from many countries, including the U.S. and in Europe feel that their application is taking too long to process. Some feel, I think, that they are given special bad treatment. I think the answer is always that the people processing the applications are overworked volunteers, usually doing several jobs for Debian. I have seen more that once, people sending email, and thinking perhaps they would never be accepted and now they are accepted and active developers. I think it would be great for Debian JP and Debian to find someone in Japan who can do interviews in Japan and report to the new-maintainer people in Debian proper (in Europe or U.S.) That is to say, it would be good to have a new-maintainer person located in Japan. This could speed up the process and improve communications. By the way, I want to see ruby packaged ! I hear that it is already packaged for Debian JP. I ran the fibonacci test in the source and it really beat perl badly. I even improved the perl version and ruby still won. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: KDE debian stuff
*Ivan E. Moore II wrote: > So if you have beefs with how kde is currently being done from a debian > package > standpoint and would like to see them done differently please let me know. > Here > is a current list of things that people have already stated needed to be > changed > or was a "god it would be nice" Is the debugging info necessary ? I wonder if it slows things down. -- John Lapeyre <[EMAIL PROTECTED]>, [EMAIL PROTECTED] Tucson,AZ http://www.physics.arizona.edu/~lapeyre
Re: Release Plans (1999-05-10)
> > For m68k-mac and powermac we need 'hybrid' cd-images (msdos + hfs). > > A bootable CD for PReP will need a special layout as well. prep image + > isofs...looks like we need multiple powerpc binary cd images. PReP can't read msdos partition on cd?
Re: KDE debian stuff
Look into kde/kdm's bug list. It does some things very badly here (have heard the X maint gripe more than once on this).
Re: Release Plans (1999-05-10)
On Mon, May 10, 1999 at 08:55:44PM +0200, Hartmut Koptein wrote: > mozilla should work for potato Maybe it will ;) We'll try. -- enJoy -*/\*- http://jagor.srce.hr/~jrodin/
Re: Release Plans (1999-05-10)
Hi, sorry for the confuse layout on http://master.debian.org/~koptein `log for successful build of x' means also a bad/failed package; this comes from an bad return value of one of the autobuilder scripts (don't know which one). Thanks, Hartmut
Re: Release Plans (1999-05-10)
> >mozilla should work for potato > > Maybe it will ;) We'll try. I try it now serveral weeks (not constantly), but all what i get is the 'composer' mode on powerpc (the one without the menus) or a window without anything in it. It makes no different if i use the M4 version from master or the cvs version (with idl). Any tips/hints for this? Thnx, Hartmut
Re: Release Plans (1999-05-10)
On Mon, 10 May 1999, Hartmut Koptein wrote: > > > For m68k-mac and powermac we need 'hybrid' cd-images (msdos + hfs). > > > > A bootable CD for PReP will need a special layout as well. prep image + > > isofs...looks like we need multiple powerpc binary cd images. > > PReP can't read msdos partition on cd? Sure, it just needs a special layout to be bootable...which I'd like to see. I'm sure pmac and chrp have a special format to boot a CD too, right? Realistically, this is the least of my worries...I'm still hammering away on boot-floppies to get PReP working... :-/ -- Matt Porter [EMAIL PROTECTED] This is Linux Country. On a quiet night, you can hear Windows reboot.
Re: User-selected window-manager in an easy way
* Wichert Akkerman (Sat, May 08, 1999 at 10:17:26PM +0200) > Previously Stig Sandbeck Mathisen wrote: > > The first part was easy (if I got it right, that is), that's just a small > > patch to /etc/X11/Xsession. > > Isn't is easier have some small script check the list of available > window managers and offer to create/update the users .xsession? I don't think it's easier, but it might be a better solution, when it's ready. :-) > This sounds much more flexible (you can also offer to start things > like xscreensaver, ssh-add, etc. etc.). ssh-add is already started from /etc/X11/Xsession, if you have ssh installed. Other than that, you're right, of course. > Also, GNOME already offer this functionality via the gnome-panel and > gnome-session. That requires the user to run Gnome, I suspect. :-) I was thinking of some simple, global solution, available from the menu. I suspect that "simple" and "global" does not belong together on this issue. It might need some more thinking. -- SSM - Stig Sandbeck Mathisen Trust the Computer, the Computer is your Friend pgpFfumGhCxm8.pgp Description: PGP signature
Re: Debian coding style?
In article <[EMAIL PROTECTED]>, James R. Van Zandt <[EMAIL PROTECTED]> wrote: >Stephen Zander <[EMAIL PROTECTED]> writes: >>>> Remember that the person who is most qualified to test any >>>> piece of code is the person who wrote it. >>Wichert> I can argue about that. But I won't :) >>The person who wrote the code is almost always the *least* qualified >>person to test it. > >Thorough testing needs several viewpoints. The original programmer >may be the best one to single-step through the code, checking for >things that differ from his expectations, or things which could >cause trouble given other data. I think that that testing isn't really about style. Style implies ways to present your code to other _human_ developers who have to read it. The C compiler doesn't care how you indent 'if' statements or where you put spaces around expressions. Consistent indentation helps the programmer-to-programmer process but does nothing for the programmer-to-compiler process. Any coding convention that can be expressed as a syntactically-equivalent algorithmic transformation of any other coding convention is probably an element of style. Testing (and quality assurance in general) is a matter of good overall technique and using effective day-to-day procedures. A typical corporation develops common internal procedures to increase its efficiency, but at the same time the initial skill and experience sets of employees sometimes differ wildly (my experience has shown much greater variation between employees in a corporation than active developers on an open-source project, IMHO because the latter group selects itself). In order for a corporation to work, its new employees have to be trained in existing procedures, and the shortest path to achieving that goal is to make everyone start life by reading a common text that contains the basic knowledge necessary to function in the group. In a software shop, that common text tends to be the best known document available among the developers -- which often starts life as a coding style document. The role of this text gets expanded to include some of everything else a new employee needs to know, and it relies on knowledge that anyone who was not part of the corporation wouldn't necessarily have. We've seen this here: some Debian developers have never _seen_ Hungarian notation until three days ago, but most of Corel's developers have fingers that type "lpsz" without requiring conscious thought from nearly a decade of practice. On the other hand, some Corel developers are likely to have a really hard time setting their tab stops back to 8 characters for the first time in as many as 10 years, and anyone who has to work on both Corel and non-Corel code is going to be screaming epithets near release deadlines. I guarantee it. Open-source projects have less in common, and as such they have documents targeted toward different audiences. Part of the problem with the original set of alleged "Corel Linux" guidelines, aside from some of its contents, was that it was a witches' brew of elements of style, technique, and procedure, with not enough of any of those and too much of all of them. By contrast, the "GNU Coding Standards" is a full standards document that has style mostly separated from the technical and procedural stuff. While opinions vary about the technical content, the GNU document itself is a well organized collection of English text. All the words seem to be spelled correctly and except for the 'info' link syntax well-punctuated too. The much shorter "Linux Kernel coding style" document discusses _only_ style: indentation, placing braces, naming, function length, commenting, and using tools to adjust existing code to the correct style. It doesn't suggest any particular coding or testing techniques at all. Other Linux documents describe procedures (e.g. how to prepare and submit a patch) and technique (although defining coding technique in a kernel is always approximate at best, and sometimes actually varies by architecture). -- Zygo Blaxell, Linux Engineer, Corel Corporation. [EMAIL PROTECTED] (work) or [EMAIL PROTECTED] (play). Corel may disagree with my opinion (above). Size of 'diff -Nurw [...] winehq corel' as of Mon May 10 17:14:00 EDT 1999 Lines/files: In 54144 / 292, Out 16700 / 154, Both 48717 / 329
Re: KDE debian stuff
Quoting John Lapeyre <[EMAIL PROTECTED]>: > Is the debugging info necessary ? I wonder if it slows things down. probably not. From what I gather, alot of how the debian packages are created are for the benefit of the developers. This would at least explain debugging info...I will dig through the code a bit and see how I can clean it up even more. Ivan =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ivan E. Moore II Rev. Krusty http://snowcrash.tdyc.com[EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- GPG KeyID=0E1A75E3 GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: KDE debian stuff
Quoting [EMAIL PROTECTED]: > Look into kde/kdm's bug list. It does some things very badly here (have > heard > the X maint gripe more than once on this). > yea..I need to do that.. I know one of the big beefs was that kdebase required xdm since kdm was apart of kdebase...I took part of this issue out by taking kdm out of kdebase and making it it's own package. There is still alot to be done to the kdm package to fix the problems that exist with it. Ivan =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Ivan E. Moore II Rev. Krusty http://snowcrash.tdyc.com[EMAIL PROTECTED] -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- GPG KeyID=0E1A75E3 GPG Fingerprint=3291 F65F 01C9 A4EC DD46 C6AB FBBC D7FF 0E1A 75E3 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Re: Pandora is born
On Mon, May 10, 1999 at 11:09:18PM +1000, Hamish Moffatt wrote: > > > : > Debian DNS administrators, please change nonus.debian.org to be a > > > : > CNAME for pandora.debian.org. > > > > > > That's what I call `democracy'. :-( -- Sorry. > > > > Um, non-us has been terribly broken since BEFORE I was a developer. In > > fact, it was broken when I first installed Bo a year and a half ago. > > I think you're exagerating here, and that doesn't help the situation one bit. No, I don't think so. Prior to apt learning to cope with a down server when it comes time to do an update, I was CONSTANTLY having to add and remove non-us because it was down. Don't even get me started on the uncoming backlog, that non-us was supposed to have around the time of the hmm release moved to a main/contrib/non-free "real soon now", and the host of other problems we've had with it. And the biggest rub of all has been that the archive maintainers couldn't do anything about the problems. They would have liked to. -- Joseph Carter <[EMAIL PROTECTED]>Debian GNU/Linux developer PGP: E8D68481E3A8BB77 8EE22996C9445FBEThe Source Comes First! - * SynrG notes that the number of configuration questions to answer in sendmail is NON-TRIVIAL pgpK8iJbKDJoZ.pgp Description: PGP signature
Re: Release Plans (1999-05-10)
I'm sorry about the tone, but I'm getting very sick of repeating myself over and over. On Mon, May 10, 1999 at 08:26:19PM +0200, Raphael Hertzog wrote: > I've been working with the previous perl5.005 package (the one that had > been uploaded to slink and retracted after) and I did not have many > problems. Many of them were only paths problems (that may not appear with the > official perl5.005 package). And I've already filled > some bugs against netbase and netstd so that the packages do not break > when perl5.005 is uploaded. Some other packages may need little changes > but that would not be a problem. > > I'll propose myself as coordinator for the perl5.005 upgrade (you did explain > that you wanted a coordinator for each release goal). I highly question your ability to fill this role as it is quite clear that you have not been following the perl5.005 stuff, specificly the debian-perl list and the massages on -devel before -perl existed about how to attack it.. The current plan cleanly addresses the case of things ending up broken, and the perl maintainer is a bit busy but spending his time working on it instead of jumping up every thread where incorrect info is mentioned. You may still be someone who could handle it, but PLEASE read the archives first? Zephaniah E. Hull.. > > Cheers, > -- > Raphaël Hertzog >> 0C4CABF1 >> http://prope.insa-lyon.fr/~rhertzog/ > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. pgpGXv9sQcRRf.pgp Description: PGP signature
