Uploaded python-4suite 0.11.1-7 (m68k all) to ftp-master
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 12 Aug 2002 13:24:27 +0200 Source: python-4suite Binary: python2.1-4suite python-4suite Architecture: m68k all Version: 0.11.1-7 Distribution: unstable Urgency: low Maintainer: buildd m68k user account [EMAIL PROTECTED] Changed-By: Alexandre Fayolle [EMAIL PROTECTED] Description: python-4suite - FourThought XML Processing Tools for Python [dummy package] python2.1-4suite - FourThought XML Processing Tools for Python (2.1.x) Changes: python-4suite (0.11.1-7) unstable; urgency=low . * New maintainer. Files: 161e20b519016565914ff963297a2b6b 720758 interpreters optional python2.1-4suite_0.11.1-7_m68k.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Made with pgp4pine 1.75-6 iD8DBQE9WYI/WgZ1HEtaPf0RAtR/AJ42N13sWvcl11jTB0fUajVD0IoSjQCaAul4 K9mgkhpvndjr2lpMdyREe9k= =H7uW -END PGP SIGNATURE-
Unidentified subject!
Bonjour, Impossible lancer une compile du 2.4 AVEC make menuconfig. Je pars d'une base install fraiche de la deb 3.0 (netinst via http) ... Si je dl le kernel-source et les headers du 2.4, que je reprend la config du 2.2 (cp /boot/conf-2.2 /usr/src/kernel-source) impossible de dmarrer l'option menuconfig ... Ceci mme quand ncurses est dans la box ... Au final, je n'ai que make config, ce qui n'est pas l'idal non ? :) Je ne sais si c'est un bug, ou si c'est moi : mais out of the box, ben... make menuconfig ca marche pas ...:/ merci d'avance Patrick
RE: Unidentified subject!
Il faut le package ncurses-dev pour faire un menuconfig -Message d'origine- De : Patrick [mailto:[EMAIL PROTECTED] Envoy : mercredi 14 aot 2002 11:48 : debian-user-french@lists.debian.org Cc : [EMAIL PROTECTED]; debian-devel-french@lists.debian.org Objet : Unidentified subject! Bonjour, Impossible lancer une compile du 2.4 AVEC make menuconfig. Je pars d'une base install fraiche de la deb 3.0 (netinst via http) ... Si je dl le kernel-source et les headers du 2.4, que je reprend la config du 2.2 (cp /boot/conf-2.2 /usr/src/kernel-source) impossible de dmarrer l'option menuconfig ... Ceci mme quand ncurses est dans la box ... Au final, je n'ai que make config, ce qui n'est pas l'idal non ? :) Je ne sais si c'est un bug, ou si c'est moi : mais out of the box, ben... make menuconfig ca marche pas ...:/ merci d'avance Patrick -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Unidentified subject!
Patrick [EMAIL PROTECTED] writes: Bonjour, Bonjour, Impossible lancer une compile du 2.4 AVEC make menuconfig. Quel est le message d'erreur ? Christian
Re: Unidentified subject!
Selon Christian Marillat [EMAIL PROTECTED]: Je suppose que les libs ncurses ne sont pas installees... apt-get install libncurses5-dev il me semble... Patrick [EMAIL PROTECTED] writes: Bonjour, Bonjour, Impossible lancer une compile du 2.4 AVEC make menuconfig. Quel est le message d'erreur ? Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] Best regards / Mit freundlichen Grüßen Mathieu Fluhr Mathieu Fluhr IT Administration Ahead Software AG phone: +49 (0)7248 911 811 (direct line) Im Stoeckmaedle 18fax: +49 (0)7248 911 888 76307 Karlsbademail: [EMAIL PROTECTED] Germany webwww.nero.com
Woody Install Error -- Not bootable
I am just installing a Woody system (bf 2.4) on a 486 DX 33 tonight and after finally getting to the stage to make the system bootable, the system is left in an unbootable state. It does this to the hard drive as well as the floppy disk I made with the installer. The error is the following Loading Linux: ... Uncompressing Linux ... invalid compressed format (err=2) System halted This uses the installer's rescue disk kernel which boots fine, so I don't know where the problem lies. I tried to get around it by using the rescue disk to boot and install a different kernel image however, I couldn't do that since the actual hard drive / is mounted as /target by the installer. So. I'm not sure where to go now, any ideas? Thanks -- Stephen Depooter [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: g++ 3.2 on woody ?
Hi Nikita, Nikita V. Youshchenko wrote: Hello. I wanted to install g++ 3.2 (instead of 3.1 that is buggy) on our server running woody with several packages from unstable. I noticed that g++ 3.2 depends on recent libc6. Is it safe to install libc6 from unstable now? Are libdb problems resolved? I would guess its more safe to build and install gcc 3.2 in your /usr/local directory tree than upgrading glibc. 3.2 is not yet released, but thats just a matter of some days (hopefully). You can find the latest snapshot in ftp://gcc.gnu.org/pub/gcc/ . Please note that the C++ ABI has been changed with gcc 3.2. The old libraries compiled with g++ 3.0.x or 3.1.x can't be used with 3.2 anymore. And you might want to check this page: http://gcc.gnu.org/gcc-3.2/c++-abi.html Good luck Harri
Re: g++ 3.2 on woody ?
On Wed, Aug 14, 2002 at 06:57:24AM +0200, Harald Dunkel wrote: Please note that the C++ ABI has been changed with gcc 3.2. The old libraries compiled with g++ 3.0.x or 3.1.x can't be used with 3.2 anymore. Again? *sigh* Apparently their C++ ABI stability goes about as far as my vision. (For those not in the know, that's not very..) -- Joseph Carter [EMAIL PROTECTED] Available in cherry and grape miguel `You have been unsubscribed from the high energy personal protection devices mailing list' miguel I dont remember getting into the mailing list pgpWYodFOPTtp.pgp Description: PGP signature
Re: g++ 3.2 on woody ?
On Tue, Aug 13, 2002 at 22:06:12 -0700, Joseph Carter wrote: On Wed, Aug 14, 2002 at 06:57:24AM +0200, Harald Dunkel wrote: Please note that the C++ ABI has been changed with gcc 3.2. Again? *sigh* The main point of the GCC 3.2 release is to have a relatively stable and common C++ ABI for GNU/Linux and BSD usage. Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0 and GCC 3.1 releases. (http://gcc.gnu.org/gcc-3.2/c++-abi.html) Ray -- Pinky, Are You Pondering What I'm Pondering? I think so Brain, but who wants to see Snow White and the Seven Samuri? Pinky and the Brain in Big in Japan
Bug#156617: general: Kde K menu is confusing
Package: general Version: 20020814 Severity: normal There is a 'K/Preferences/System' menu and there is also a 'K/system' menu. This is redundant and thus confusing. -- System Information Debian Release: testing/unstable Kernel Version: Linux pumpkin 2.4.16-586 #1 Wed Nov 28 08:21:15 EST 2001 i686 unknown unknown GNU/Linux
Re: free-java-sdk and friends - status report
On Tue, Aug 13, 2002 at 05:16:42PM +0200, Grzegorz Prokopski wrote: Hello! First I wanted to thank all who discussed about the idea of free-java-sdk. I have included small FAQ and (as adviced) I'll be including some documentation about 'why ABC is better than XYZ'. Please, could you send this information to the Java FAQ? (as a wishlist bug to java-common) It could be very useful there too. IMHO it would be better if the documentation was placed in the FAQ and not in the package (the package Depends: on java-common?) in order to not spread the information too much around. Regards Javi
Re: Woody Install Error -- Not bootable
On 14 Aug 2002 00:27:05 -0400 Stephen Depooter [EMAIL PROTECTED] wrote: This uses the installer's rescue disk kernel which boots fine, so I don't know where the problem lies. I tried to get around it by using the rescue disk to boot and install a different kernel image however, I couldn't do that since the actual hard drive / is mounted as /target by the installer. So. I'm not sure where to go now, any ideas? You could try using grub floppy to boot the system up and do a trial-and-error booting. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
Re: chroot administration
On Wed, 14 Aug 2002 05:35, Shaya Potter wrote: On Tue, 2002-08-13 at 22:09, Colin Walters wrote: On Tue, 2002-08-13 at 17:48, Russell Coker wrote: I have written SE Linux policy for administration of a chroot environment. That allows me to give full root administration access (ability to create/delete users, kill processes running under different UIDs, ptrace, etc) to a chroot environment without giving any access to the rest of the system. Since no one else has apparently said it explictly yet, I have to say that's extremely cool :) Thanks Colin. argh. its so cool that you essentially stole my summer research. :(. Does this allow you to create any amount of chroot jails? We are also It allows the administrator to create any number of chroot jail setups for a given user, and they can set them up for as many users as they like. working on making virtual IPs that each jail would get. We are also working on being able to move the processes while running (w/ network connections) from machine to machine w/o needing any state on initial machine. I am not planning to work on moving processes etc. If you'd like to build on top of my work then you are welcome, it'll all be in Debian in a few days. -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.
M$ true type fonts in non-free?
Even if M$ has made unavailable for download true type fonts required by msttcorefonts, the fonts license (as someone pointed out on the familiar mailing list http://www.handhelds.org/mailman/listinfo.cgi/familiar, Message-ID: [EMAIL PROTECTED]) seems to permit redistribution. This is the key point (reported by the poster on the ML, I haven't checked it): Reproduction and Distribution. You may reproduce and distribute an unlimited number of copies of the SOFTWARE PRODUCT; provided that each copy shall be a true and complete copy, including all copyright and trademark notices, and shall be accompanied by a copy of this EULA. Copies of the SOFTWARE PRODUCT may not be distributed for profit either on a standalone basis or included as part of your own product. We can move msttcorefonts to non-free and embed the fonts in it. Fonts tarball is available at: http://keithp.com/~keithp/fonts/truetype.tar.gz Cheers. -- Stefano Zacchiroli - undergraduate student of CS @ Univ. Bologna, Italy [EMAIL PROTECTED] | ICQ# 33538863 | http://www.cs.unibo.it/~zacchiro I know you believe you understood what you think I said, but I am not sure you realize that what you heard is not what I meant! -- G.Romney
MyInsuranceJob.com weekly Insurance Industry Newsletter
The MyInsuranceJob.com weekly Insurance Industry Newsletter The Premier On-Line Insurance Industry Career Site Newsletter *** Read by more than 19,000 Insurance professionals each week ! *** (( All postings free until August 31, 2002 to celebrate our Grand Opening)) Tuesday, August 13, 2002 --- Volume 1, Issue 2 To view this e-Zine as a web page, click http://www.myinsurancejob.com/ezine/ezine.html Job of the Week... Chief Financial Manager Prestigious insurance entity is seeking a Chief Financial Manager for their New York operation. Candidates will be responsible for managing a group of controllers from various profit centers and SBU's. Qualified candidates must have a minimum of 15 years experience in the Property/Casualty Insurance financial and accounting arena.Strong management skills are imperative. Additional requirements are CPA, public accounting experience, STAT, and GAAP experience. Exposure to the treasury side and financial systems are important... MORE - http://www.myinsurancejob.com/ezine/ezine.html#1 Resume of the Week... JULIE J. EVERETT EXPERIENCE 1987-present The St. Paul Companies, formerly USFG, Jackson, MS 1996-present Commercial Property/Casualty Underwriter Responsible for profitably managing an underwriting territory consisting of all lines of commercial insurance totaling $6 million in premium volume for 35 independent agents throughout Mississippi. 1987-1996 Agency Services Specialist Rated, coded and issued policies for all lines of commercial insurance; provided customer support to agents. 1985-1987American States Insurance, Jackson, MS Commercial Lines Technician Rated and coded commercial property and casualty policies. 1983-1985 Commercial Union Insurance Co., Jackson, MS Commercial Lines Technician Rated and coded commercial property and casualty policies. 1980-1983 MS State Rating Bureau, Jackson, MS Auditor Checked rating of commercial property policies. EDUCATION 2002Belhaven College, Jackson, MS Bachelor of Business Administration, Summa Cum Laude MORE - http://www.myinsurancejob.com/ezine/ezine.html#2 In Focus This Week... Job Search Tip: Online Job Hunting According to a recent survey from the Pew Internet Project, 52 million Americans have looked online for information about jobs, and more than 4 million do so on a typical day. Among those who are the most likely to do online searches for jobs: * Young Internet users between the ages of 18 and 29. Some 61% of them have looked for jobs online, compared to 42% of those ages 30-49 and 27% of those ages 50-64. * Men. Some 50% of online men had sought job information, compared to 44% of online women. On a typical day, twice as many online men are job hunting as women. * The unemployed. About 51% of those who do not currently have jobs have Internet access. On a typical day, a tenth of the unemployed with Internet access are online scouring job sites, compared to 4% of the wired Americans who have full-time jobs. * African-Americans and Hispanics. While 44% of whites have done online job seeking, close to 60% of African-Americans and Hispanics with Internet access have sought job information on the Internet. * Those in sales-related jobs. Some 55% of those with Internet access who currently hold media sales jobs have looked for new job information online, compared to 44% of the online executives and professionals, and 49% of the wired clerical and office workers. However, on a typical day online the most active job searchers are online office workers. Skilled laborers and service workers are the least likely to have done job hunting online. * Those in higher income brackets and with high education levels. High socioeconomic status is correlated with online job searching. Those who live in households with incomes over $75,000 are more likely than others with lesser incomes to have done job searches online, and those with college or graduate degrees are more likely than those with high school diplomas to have explored the job classifieds online. Overall, these figures represent a more than 60% jump in the number of online job hunters from March 2000 when the project first asked about the subject. Cartoon of the Week...
Re: Library namespace conflicts
On Fri, Aug 09, 2002 at 04:40:43AM -0400, Simon Law wrote: I grant you that, this piece of software is a young 'un; although I'm surprised that this didn't come up any sooner. (Lucky us.) I don't think either library has more than one piece of software that currently requires it; but this could change for libdnet.sf.net in the future, seeing as there is activity on the nmap mailing lists. Since you've had the name for such a long time, I'd like to defer judgement to you. What do you think is a reasonable way to handle this? Rename one of the libraries and tweak code that depends on it? Rename one of the libraries and make them both conflict with each other? Provide libdnet.sf.net in fragroute and link statically? As the man page at http://libdnet.sourceforge.net/dnet.3.txt refers to the library as dnet - dumb networking library how about renaming it libdumbnet? :-) patrick
MailMan Security patch for Woody Broken?
Hi all,
I believe that the just released MailMan security fix for woody may be broken.
I am running a Debian woody server which runs several MailMan lists which
have been running sweetly until just recently. The only thing I can think of
that has changed is that, like you do, I installed the recent MailMan
security fix for woody that came out a cuppla days ago.
Now, no messages are getting through. If I do a test subscribe from the web
interface, I get the acknowledgement email asking for a reply but nothing
comes back.
A check in the logs reveals this suspicious tid-bit:
Aug 14 18:48:03 2002 qrunner(1300): File /usr/lib/mailman/Mailman/MailComma
ndHandler.py, line 123, in ParseMailCommands
Aug 14 18:48:03 2002 qrunner(1300): precedence = msg.get('precedence',
'').lower()
Aug 14 18:48:03 2002 qrunner(1300): AttributeError : 'string' object has no
attribute 'lower'
Is anyone else having trouble since the new version was released?
--
David
Re: debian-security-announce-$lang@lists?
On Tue, Aug 13, 2002 at 09:23:57PM +0200, Martin Schulze wrote: Given the above, what do you think about establishing localized security-announce lists? Please discuss this issue on debian-security and not on debian-devel or debian-project to reach a larger audience. Not being a CVS guru myself... What about a CVS trigger to automatically maintain the -$lang lists? I know that sending the DSA directly to the list would be much quicker, but the other way we could automatically assemble the text with URLs. Mmmh... Comes to mind... What are the chances for a non-developer to be on writers at CVS now that we're authenticating via developer-related ssh keys? That would be very convenient just as many people (at least on the Spanish team) remain not being Debian Developers themselves, and relay on the developers to upload their changes. We've been thinking on a quite complicated way involving a second CVS on our servers :-D, but it's a lot of burden, if you ask me. Regards, Ricardo.
Bug#156617: general: Kde K menu is confusing
reassign 156617 kdebase thanks There is a 'K/Preferences/System' menu and there is also a 'K/system' menu. This is redundant and thus confusing. One is for system programs, the other for system settings. What's redundant about that? Thomas --
Processed: Re: Bug#156617: general: Kde K menu is confusing
Processing commands for [EMAIL PROTECTED]: reassign 156617 kdebase Bug#156617: general: Kde K menu is confusing Bug reassigned from package `general' to `kdebase'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Re: chroot administration
Shaya Potter [EMAIL PROTECTED] wrote: I have written SE Linux policy for administration of a chroot environment. That allows me to give full root administration access (ability to create/delete users, kill processes running under different UIDs, ptrace, etc) to a chroot environment without giving any access to the rest of the system. Since no one else has apparently said it explictly yet, I have to say that's extremely cool :) argh. its so cool that you essentially stole my summer research. :(. Does this allow you to create any amount of chroot jails? We are also working on making virtual IPs that each jail would get. We are also working on being able to move the processes while running (w/ network connections) from machine to machine w/o needing any state on initial machine. You might want to investiage `security contexts', a new kernel feature that can be used for virtual IP roots as well as making processes in one context (even root) not able to see other contexts' processes. The userland utilities also offer a way to remove Linux's capabilities (eg, to disallow raw sockets or bypassing filesystem permissions). http://www.solucorp.qc.ca/miscprj/s_context.hc -- Sam Vilain, [EMAIL PROTECTED] Easyspace: an accredited ICANN GPG: http://sam.vilain.net/sam.ascregistrar web hosting company 7D74 2A09 B2D3 C30F F78E Have your domain run by techies 278A A425 30A9 05B5 2F13 with a clue. www.easyspace.com Ambition is the curse of the political class. - anon.
Re: Bug#156617: general: Kde K menu is confusing
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wednesday 14 August 2002 10:35 am, Thomas Schoepf wrote: reassign 156617 kdebase thanks There is a 'K/Preferences/System' menu and there is also a 'K/system' menu. This is redundant and thus confusing. One is for system programs, the other for system settings. What's redundant about that? I'll prod calc later about seeing if it is possible to change K/System to K/System Tools. This has been changed in kde3.1. as you now have a settings menu, but it does not replicate the kcontrol hierarchy. - -- David Pashley [EMAIL PROTECTED] Nihil curo de ista tua stulta superstitione. -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE9WkL1YsCKa6wDNXYRAm7zAJ0d0gFQVcR9hqbmuKyOFIfK2QV/8QCfQBtb 5cWC69G3Pir32IWswSQEhaE= =33aS -END PGP SIGNATURE-
Re: Library namespace conflicts
On Wed, Aug 14, 2002 at 10:11:33AM +0100, Patrick Caulfield wrote: On Fri, Aug 09, 2002 at 04:40:43AM -0400, Simon Law wrote: As the man page at http://libdnet.sourceforge.net/dnet.3.txt refers to the library as dnet - dumb networking library how about renaming it libdumbnet? :-) One step ahead of you. That's exactly what the package I'm in the process of creating is named[1]. Could you be a dear and mention libdumbnet in your package description, for people who would be looking for the canonical name? Simon [1] Ack! I need to turn libdumbnet into a shared library. Oh, and his Autoconf scripts are broken. Aye!
Re: Library namespace conflicts
On Wed, Aug 14, 2002 at 08:06:54AM -0400, Simon Law wrote: On Wed, Aug 14, 2002 at 10:11:33AM +0100, Patrick Caulfield wrote: On Fri, Aug 09, 2002 at 04:40:43AM -0400, Simon Law wrote: As the man page at http://libdnet.sourceforge.net/dnet.3.txt refers to the library as dnet - dumb networking library how about renaming it libdumbnet? :-) One step ahead of you. That's exactly what the package I'm in the process of creating is named[1]. I though you might, but it was worth mentioning. Could you be a dear and mention libdumbnet in your package description, for people who would be looking for the canonical name? Certainly. patrick
Re: Bug#156503: M$ true type fonts in non-free?
Even if M$ has made unavailable for download true type fonts required by msttcorefonts, the fonts license (as someone pointed out on the familiar mailing list http://www.handhelds.org/mailman/listinfo.cgi/familiar, Message-ID: [EMAIL PROTECTED]) seems to permit redistribution. Yes, I know. I haven't given up, but I don't want to jump to any conclusions just yet. This is the key point (reported by the poster on the ML, I haven't checked it): Reproduction and Distribution. You may reproduce and distribute an unlimited number of copies of the SOFTWARE PRODUCT; provided that each copy shall be a true and complete copy, including all copyright and trademark notices, and shall be accompanied by a copy of this EULA. Copies of the SOFTWARE PRODUCT may not be distributed for profit either on a standalone basis or included as part of your own product. We can move msttcorefonts to non-free and embed the fonts in it. Fonts tarball is available at: http://keithp.com/~keithp/fonts/truetype.tar.gz Unfortunately, this isn't quite true. There used to be more information about Microsoft's interprettation of their own EULA on the font web page. Since that page is gone, it's no longer there, but the gist of it was that they were taking a very very strict view of a true and complete copy, to the extent that changing the packaging of the fonts in any way (even just changing the filename without changing the file contents) would make it no longer a true and complete copy. They were pretty clear on this point. In other words, no tarballs allowed. Distribution has to be in the form of a collection of separate Windows 95 self-installing executables. That's why I wrote the package as a contrib installer in the first place. Embedding the fonts in the package would have been much simpler and easier. The question at this point is, how do we make distrubting such files ourselves work logistically? I can't dupload an exe to the debian mirror system. I could put the .exe's on people.debian.org under my own account, but this isn't mirrored. I may need to contact Microsoft for clarification of the terms of their license. I don't know why MS ended their font program, but if it's because they felt that the interest of cross platform compatibility was no longer in MS's best interest, then I don't expect them to be particularly generous in their terms. That's why I want to make sure we follow this EULA to the strictest of possible standards. Eric
Re: chroot administration
btw, when I said stole i didnt mean it to be harsh. sorry if it came off that way. shaya On Wed, 2002-08-14 at 04:26, Russell Coker wrote: On Wed, 14 Aug 2002 05:35, Shaya Potter wrote: On Tue, 2002-08-13 at 22:09, Colin Walters wrote: On Tue, 2002-08-13 at 17:48, Russell Coker wrote: I have written SE Linux policy for administration of a chroot environment. That allows me to give full root administration access (ability to create/delete users, kill processes running under different UIDs, ptrace, etc) to a chroot environment without giving any access to the rest of the system. Since no one else has apparently said it explictly yet, I have to say that's extremely cool :) Thanks Colin. argh. its so cool that you essentially stole my summer research. :(. Does this allow you to create any amount of chroot jails? We are also It allows the administrator to create any number of chroot jail setups for a given user, and they can set them up for as many users as they like. working on making virtual IPs that each jail would get. We are also working on being able to move the processes while running (w/ network connections) from machine to machine w/o needing any state on initial machine. I am not planning to work on moving processes etc. If you'd like to build on top of my work then you are welcome, it'll all be in Debian in a few days. -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.
Re: chroot administration
On Wed, 2002-08-14 at 06:50, Sam Vilain wrote: Shaya Potter [EMAIL PROTECTED] wrote: I have written SE Linux policy for administration of a chroot environment. That allows me to give full root administration access (ability to create/delete users, kill processes running under different UIDs, ptrace, etc) to a chroot environment without giving any access to the rest of the system. Since no one else has apparently said it explictly yet, I have to say that's extremely cool :) argh. its so cool that you essentially stole my summer research. :(. Does this allow you to create any amount of chroot jails? We are also working on making virtual IPs that each jail would get. We are also working on being able to move the processes while running (w/ network connections) from machine to machine w/o needing any state on initial machine. You might want to investiage `security contexts', a new kernel feature that can be used for virtual IP roots as well as making processes in one context (even root) not able to see other contexts' processes. The userland utilities also offer a way to remove Linux's capabilities (eg, to disallow raw sockets or bypassing filesystem permissions). yea, I know all about it, but thats a bit more involved than what we want/need. I looked at that already. Might take another look at it again later, but it seemed too much for our needs, and therefore a little heavy. debian
Re: chroot administration
On Wed, 14 Aug 2002 12:50, Sam Vilain wrote: argh. its so cool that you essentially stole my summer research. :(. Does this allow you to create any amount of chroot jails? We are also working on making virtual IPs that each jail would get. We are also working on being able to move the processes while running (w/ network connections) from machine to machine w/o needing any state on initial machine. You might want to investiage `security contexts', a new kernel feature that can be used for virtual IP roots as well as making processes in one context (even root) not able to see other contexts' processes. The userland utilities also offer a way to remove Linux's capabilities (eg, to disallow raw sockets or bypassing filesystem permissions). http://www.solucorp.qc.ca/miscprj/s_context.hc Is someone going to package this for Debian? There are some limitations with it. The biggest limitation when compared to my SE Linux work is it's lack of flexibility. I can setup a SE Linux chroot, then do a bind mount of /home/www, and grant read-only access to the files and directories of user_home_t and search access to directories of type user_home_dir_t. In my default policy I have given the user who starts the chroot environment full access to files and directories in the chroot (of course if their UID!=0 then they won't be able to do much). Also in my policy I have two different security domains, one for all programs which has limited write access, and another for administration tools (such as dpkg/dselect) which can write all files and directories. I could make an addition to this and have another file type which is append-only for the ordinary chroot domain and can only be read by the user who starts the chroot and the super domain. This would greatly limit the ability of someone who breaks the security of a chroot environment. The advantage of my work is that it's all in policy files that can easily be changed - you could even change the policy at run-time and grant different permissions to running processes! The advantage of the security contexts system described on that web page is a comprehensive solution to the IP address issue (I've got a design but no working code so far). I don't expect to ever get a solution that works as well as their solution unless/until new features are added to SE Linux. -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.
Re: chroot administration
On Wed, 14 Aug 2002 14:47, you wrote: btw, when I said stole i didnt mean it to be harsh. sorry if it came off that way. No probs, I didn't take any offense. I'd be happy to work with you on developing such things if your interests are similar to mine. -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.
Re: Bug#156503: M$ true type fonts in non-free?
On Wed, Aug 14, 2002 at 08:47:31AM -0400, Eric Sharkey wrote: I may need to contact Microsoft for clarification of the terms of their license. I don't know why MS ended their font program, but if it's because they felt that the interest of cross platform compatibility was no longer in MS's best interest, then I don't expect them to be particularly generous in their terms. That's why I want to make sure we follow this EULA to the strictest of possible standards. Anyway they had written true and complete copy, don't trust their current interpretation of the sentence, because surely M$ don't want to distribute that fonts anymore. I suggest to ask for a debian-legal interpretation of the sentence. IANAL, but true and complete copy seems to me fullfilled if I embed this true and complete copy in somewhat else (e.g. a tarball). Cheers. -- Stefano Zacchiroli - undergraduate student of CS @ Univ. Bologna, Italy [EMAIL PROTECTED] | ICQ# 33538863 | http://www.cs.unibo.it/~zacchiro I know you believe you understood what you think I said, but I am not sure you realize that what you heard is not what I meant! -- G.Romney
Re: Bug#156503: M$ true type fonts in non-free?
On Wed, Aug 14, 2002 at 08:47:31AM -0400, Eric Sharkey wrote: There used to be more information about Microsoft's interprettation of their own EULA on the font web page. Since that page is gone, it's no longer there, but the gist of it was that they were taking a very very strict view of a true and complete copy, to the extent that changing the packaging of the fonts in any way (even just changing the filename without changing the file contents) would make it no longer a true and complete copy. They were pretty clear on this point. In other words, no tarballs allowed. Distribution has to be in the form of a collection of separate Windows 95 self-installing executables. Then there should still be nothing wrong with packing all of those .exe's in a tar file, for transport. The package would then be based on the current installer package. -- Bart.
Re: Move to python 2.2 as default release?
On Aug 06, Torsten Landschoff wrote: As the new upstream of python-gnome (for GNOME 2) needs python 2.2 for building I am wondering when python 2.2 will get the default version for Debian. Any insights? I believe a consensus was reached on debian-python that we would move to Python 2.3 as the next default Python, skipping 2.2 entirely. My recommendation would be to separately maintain a python 2.2-compatible python-gnome and a 2.1 compatible version, at least until the 2.3 release. Chris -- Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/ Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi 208 Deupree Hall - 662-915-5765 The new Python Business Forum (www.python-in-business.com) is collaborating with the Python developers to produce Python-in-a-Tie, a business-targetted release of Python. This is a 'Sumo-Release', which will include other useful Python libraries and programs which are not part of the standard Python releases. What we want is a release we tell our cyustomers to run which will give them 18 months or so during which there is no need for them, as users, not developers, to upgrade a to a newer version of Python. Then we will target a next release, and to be the next Python-in-a-Tie. I am the Chairman of the Python-in-a-Tie SIG, and the Python-in-a-Tie release is going to be based on 2.2, not 2.1 or 2.3. Thus 2.2 is the release which we are telling Python developers is the release which they should write for. Therefore I think that skipping the 2.2 release in favour of the 2.3 would be a mistake. Please cc any discussion and replies to me since I do not read debian-devel. Thanks very much, Laura Creighton
Re: Bug#156503: M$ true type fonts in non-free?
On Wed, Aug 14, 2002 at 08:47:31AM -0400, Eric Sharkey wrote: There used to be more information about Microsoft's interprettation of their own EULA on the font web page. Since that page is gone, it's no longer there, but the gist of it was that they were taking a very very strict view of a true and complete copy, to the extent that changing the packaging of the fonts in any way (even just changing the filename without changing the file contents) would make it no longer a true and complete copy. They were pretty clear on this point. In other words, no tarballs allowed. Distribution has to be in the form of a collection of separate Windows 95 self-installing executables. Then there should still be nothing wrong with packing all of those .exe's in a tar file, for transport. The package would then be based on the current installer package. The problem with copyright lawsuits is that the opinion of the defendant has absolutely no bearing. What matters is the opinion of the plaintiff, who decides if a suit should be filed, and the opinion of the judge, who decides who wins. I don't want to end up in a position where I even need to think about the opinion of a judge. Here's the Web Fonts FAQ, care of archive.org: http://web.archive.org/web/20020124073322/www.microsoft.com/typography/faq/faq8.htm Note the following: * You may only redistribute the fonts in their original form (.exe or .sit.hqx) and with their original file name from your Web site or intranet site. * You must not supply the fonts, or any derivative fonts based on them, in any form that adds value to commercial products, such as CD-ROM or disk based multimedia programs, application software or utilities. See Microsoft's permissions site for more details. This sounds pretty clear to me as to what their intent is with these fonts. Encapsulation in a .tar runs against the first point, and in a .deb may run against the second. It's not a chance I'm willing to take. Eric
Re: Upcoming bug mass-filing re. non-free TrueType fonts in main
On Fri, Aug 02, 2002 at 01:16:14PM -0300, Ben Armstrong wrote: So now, the list of packages in violation of non-free font licenses: ... feh - contains 'helmetr' (Sun)[1] gozer - contains 'helmetr' (Sun)[1] ... xplanet - contains 'helmetr' (Sun)[1] ... Footnotes: ... [1] I have been told that the OpenOffice fonts are not free and were pulled from CVS a short while ago. This puts ttf-openoffice into question and any other package that contains a font included in ttf-openoffice. I need confirmation of this before I can file bugs. I now have official word from Sun in a private email that these fonts were never free to begin with, that they were only in OpenOffice CVS for 6 months before they were yanked, and that in any event, even StarOffice has stopped using them becuase of 'insufficient quality'. So, not only the above packages are buggy, but also ttf-openoffice and any package with a dependency on it. I'm planning on filing all of the bugs tonight. Now would be a really good time for people to email authors of decent TrueType freeware fonts to see if they can be convinced to put their fonts under a DFSG-free license if anyone is interested in doing that. Ben -- nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED] Debian http://www.debian.org [EMAIL PROTECTED] [ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ] [ gpg key fingerprint = 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ]
Re: chroot administration
On Wed, Aug 14, 2002 at 11:50:14AM +0100, Sam Vilain wrote: You might want to investiage `security contexts', a new kernel feature that can be used for virtual IP roots as well as making processes in one context (even root) not able to see other contexts' processes. The userland utilities also offer a way to remove Linux's capabilities (eg, to disallow raw sockets or bypassing filesystem permissions). http://www.solucorp.qc.ca/miscprj/s_context.hc Does this avoid selinux's patent encumbrance issues? -- Mike Stone
Re: g++ 3.2 on woody ?
On Wed, Aug 14, 2002 at 08:16:46AM +0200, J.H.M. Dassen (Ray) [EMAIL PROTECTED] was heard to say: On Tue, Aug 13, 2002 at 22:06:12 -0700, Joseph Carter wrote: On Wed, Aug 14, 2002 at 06:57:24AM +0200, Harald Dunkel wrote: Please note that the C++ ABI has been changed with gcc 3.2. Again? *sigh* The main point of the GCC 3.2 release is to have a relatively stable and common C++ ABI for GNU/Linux and BSD usage. Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0 and GCC 3.1 releases. (http://gcc.gnu.org/gcc-3.2/c++-abi.html) Wasn't that the point of the GCC 3.1 release? Daniel -- / Daniel Burrows [EMAIL PROTECTED] ---\ |Whoever created the human body left in a fairly basic| |design flaw. It has a tendency to bend at the knees.| | -- Terry Pratchett, _Men at Arms_ | \-Evil Overlord, Inc: planning your future today. http://www.eviloverlord.com-/
Re: g++ 3.2 on woody ?
On Thu, 2002-08-15 at 02:00, Daniel Burrows wrote: On Wed, Aug 14, 2002 at 08:16:46AM +0200, J.H.M. Dassen (Ray) [EMAIL PROTECTED] was heard to say: On Tue, Aug 13, 2002 at 22:06:12 -0700, Joseph Carter wrote: On Wed, Aug 14, 2002 at 06:57:24AM +0200, Harald Dunkel wrote: Please note that the C++ ABI has been changed with gcc 3.2. Again? *sigh* The main point of the GCC 3.2 release is to have a relatively stable and common C++ ABI for GNU/Linux and BSD usage. Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0 and GCC 3.1 releases. (http://gcc.gnu.org/gcc-3.2/c++-abi.html) Wasn't that the point of the GCC 3.1 release? wasnt 3.1 just bug fixes for the 3.0.x? -- ph33r! Linux mdew 2.4.19-xfs-rmap13c-preemptive #2 Sat Aug 10 02:18:14 NZST 2002 i686 unknown unknown GNU/Linux GPG Key: http://mdew.orcon.net.nz/gpg signature.asc Description: This is a digitally signed message part
Re: g++ 3.2 on woody ?
On Wed, Aug 14, 2002 at 10:00:35AM -0400, Daniel Burrows wrote: On Wed, Aug 14, 2002 at 08:16:46AM +0200, J.H.M. Dassen (Ray) [EMAIL PROTECTED] was heard to say: On Tue, Aug 13, 2002 at 22:06:12 -0700, Joseph Carter wrote: On Wed, Aug 14, 2002 at 06:57:24AM +0200, Harald Dunkel wrote: Please note that the C++ ABI has been changed with gcc 3.2. Again? *sigh* The main point of the GCC 3.2 release is to have a relatively stable and common C++ ABI for GNU/Linux and BSD usage. Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0 and GCC 3.1 releases. (http://gcc.gnu.org/gcc-3.2/c++-abi.html) Wasn't that the point of the GCC 3.1 release? Well, shame on them for having bugs in their software. GCC just isn't up to Debian standards, I guess. We should count ourselves lucky that we don't have stable releases using each of the GCC 2.9x, 3.0, and 3.1 ABIs. Steve Langasek postmodern programmer pgpDhI4l3LXkI.pgp Description: PGP signature
Re: g++ 3.2 on woody ?
On Wed, Aug 14, 2002 at 10:00:35AM -0400, Daniel Burrows wrote: On Wed, Aug 14, 2002 at 08:16:46AM +0200, J.H.M. Dassen (Ray) [EMAIL PROTECTED] was heard to say: The main point of the GCC 3.2 release is to have a relatively stable and common C++ ABI for GNU/Linux and BSD usage. Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0 and GCC 3.1 releases. (http://gcc.gnu.org/gcc-3.2/c++-abi.html) Wasn't that the point of the GCC 3.1 release? I thought it was one of the promises of 3.0 :) -- Mike Stone
Re: MailMan Security patch for Woody Broken?
On Wed, Aug 14, 2002 at 07:23:05PM +1000, David Fisher wrote:
I believe that the just released MailMan security fix for woody may be broken.
I am running a Debian woody server which runs several MailMan lists which
have been running sweetly until just recently. The only thing I can think of
that has changed is that, like you do, I installed the recent MailMan
security fix for woody that came out a cuppla days ago.
Now, no messages are getting through. If I do a test subscribe from the web
interface, I get the acknowledgement email asking for a reply but nothing
comes back.
A check in the logs reveals this suspicious tid-bit:
Aug 14 18:48:03 2002 qrunner(1300): File /usr/lib/mailman/Mailman/MailComma
ndHandler.py, line 123, in ParseMailCommands
Aug 14 18:48:03 2002 qrunner(1300): precedence = msg.get('precedence',
'').lower()
Aug 14 18:48:03 2002 qrunner(1300): AttributeError : 'string' object has no
attribute 'lower'
This is certainly suspicious, since all Python 'string' objects are supposed
to have a 'lower()' method, as far as I know.
But that line is one which was added in the security update. What version
of Python are you running? If you change that line to:
precedence = ''
does it fix the problem?
--
- mdz
Re: MailMan Security patch for Woody Broken?
Hi, Matt Zimmerman [EMAIL PROTECTED] wrote: Aug 14 18:48:03 2002 qrunner(1300): AttributeError : 'string' object has no attribute 'lower' This is certainly suspicious, since all Python 'string' objects are supposed to have a 'lower()' method, as far as I know. I can't look at mailman right now, but some observations that might help: - with python 2.1: 'barstring'.foo() Traceback (most recent call last): File stdin, line 1, in ? AttributeError: foo - with python 2.2 barstring.foo() Traceback (most recent call last): File stdin, line 1, in ? AttributeError: 'str' object has no attribute 'foo' which is closer to the David's error message, *but* has 'str' instead of 'string'. BTW: type(dfsfsd) type 'str' I don't know where this 'string' comes from. -- Florent
Re: Move to python 2.2 as default release?
Thanks for the post, Laura. I agree -- Python 2.3 won't be ready for a long time, and I recommend to the Debian folks that they standardize on Python 2.2. For now, that will be Python 2.2.1; a maintenance release, 2.2.2 will be issued some time later this year. I don't expect 2.3 to reach maturity until mid 2003. --Guido van Rossum (home page: http://www.python.org/~guido/) [Context:] Subject: Re: Move to python 2.2 as default release? From: Laura Creighton [EMAIL PROTECTED] To: debian-devel@lists.debian.org, [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Date: Wed, 14 Aug 2002 15:25:01 +0200 X-Spam-Level: On Aug 06, Torsten Landschoff wrote: As the new upstream of python-gnome (for GNOME 2) needs python 2.2 for building I am wondering when python 2.2 will get the default version for Debian. Any insights? I believe a consensus was reached on debian-python that we would move to Python 2.3 as the next default Python, skipping 2.2 entirely. My recommendation would be to separately maintain a python 2.2-compatible python-gnome and a 2.1 compatible version, at least until the 2.3 release. Chris -- Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/ Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi 208 Deupree Hall - 662-915-5765 The new Python Business Forum (www.python-in-business.com) is collaborating with the Python developers to produce Python-in-a-Tie, a business-targetted release of Python. This is a 'Sumo-Release', which will include other useful Python libraries and programs which are not part of the standard Python releases. What we want is a release we tell our cyustomers to run which will give them 18 months or so during which there is no need for them, as users, not developers, to upgrade a to a newer version of Python. Then we will target a next release, and to be the next Python-in-a-Tie. I am the Chairman of the Python-in-a-Tie SIG, and the Python-in-a-Tie release is going to be based on 2.2, not 2.1 or 2.3. Thus 2.2 is the release which we are telling Python developers is the release which they should write for. Therefore I think that skipping the 2.2 release in favour of the 2.3 would be a mistake. Please cc any discussion and replies to me since I do not read debian-devel. Thanks very much, Laura Creighton
Bug#156673: ITP: aspell-nl -- Dutch wordlists for aspell
Package: wnpp Version: N/A; reported 2002-08-14 Severity: wishlist * Package name: aspell-nl Version : 0.0-0.10 Upstream Author : Dirk Vermeir [EMAIL PROTECTED] * URL : http://tinf2.vub.ac.be/~dvermeir/software/dv/nl-aspell/index.html http://savannah.gnu.org/download/aspell/dicts/ * License : unclear Description : Dutch dictionary and language support for aspell This package provides a dutch dictionary and a language file for use with the aspell spelling checker. The word list has been compiled from a number of sources: 1. The list used in the aspell-nl-0.1.rpm package. The main reason I decided to build the present package is that I could not find a tarball distribution of this rpm and that some ``exceptions'' from the official lists seemed to be missing. 2. The lists in the official announcement (1996) about spelling changes. 3. The list by Piet Tutelaers available on http://www.ntg.nl/spell-nl-v5b/. The full word list (approx. 222K words) is available as a text file dutch.words in the distribution. The language definition is in the file dutch.dat. The license is a bit unclear. I will contact upstream about this. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux kalypso 2.4.19-pre9-ac2 #2 za jun 8 23:55:04 CEST 2002 i686 Locale: LANG=en_US, [EMAIL PROTECTED] -- no debconf information
Re: Move to python 2.2 as default release?
On Wed, Aug 14, 2002 at 03:25:01PM +0200, Laura Creighton wrote: On Aug 06, Torsten Landschoff wrote: As the new upstream of python-gnome (for GNOME 2) needs python 2.2 for building I am wondering when python 2.2 will get the default version for Debian. Any insights? I believe a consensus was reached on debian-python that we would move to Python 2.3 as the next default Python, skipping 2.2 entirely. My recommendation would be to separately maintain a python 2.2-compatible python-gnome and a 2.1 compatible version, at least until the 2.3 release. Chris -- Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/ Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi 208 Deupree Hall - 662-915-5765 The new Python Business Forum (www.python-in-business.com) is collaborating with the Python developers to produce Python-in-a-Tie, a business-targetted release of Python. This is a 'Sumo-Release', which will include other useful Python libraries and programs which are not part of the standard Python releases. What we want is a release we tell our cyustomers to run which will give them 18 months or so during which there is no need for them, as users, not developers, to upgrade a to a newer version of Python. Then we will target a next release, and to be the next Python-in-a-Tie. I am the Chairman of the Python-in-a-Tie SIG, and the Python-in-a-Tie release is going to be based on 2.2, not 2.1 or 2.3. Thus 2.2 is the release which we are telling Python developers is the release which they should write for. Therefore I think that skipping the 2.2 release in favour of the 2.3 would be a mistake. Please cc any discussion and replies to me since I do not read debian-devel. Thanks very much, But, this does not say that python2.2 will not be available. It is, and, as far as I know, will continue to be. I think that the general consensus was that debian would maintain whatever versions we had to, if Python-in-a-Tie were packaged in debian, it would mark python2.2 as a requirement, and until said package was either rewritten to use python2.3+, or removed from the archive, it would be impossible to remove python2.2. Nor is it much of a pain for a developer: scripts being /usr/bin/python2.2, rather than just /usr/bin/python. Your group does not even need to be aware of this; this is something the debian developer should be taking care of. There has been dicussion of removing python1.5. But this is because there are very few packages left that depend on it. Debian does not historically remove packages easily or without thought. Jim Penny Laura Creighton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Move to python 2.2 as default release?
On Wed, Aug 14, 2002 at 11:02:18AM -0400, Guido van Rossum wrote: Thanks for the post, Laura. I agree -- Python 2.3 won't be ready for a long time, and I recommend to the Debian folks that they standardize on Python 2.2. For now, that will be Python 2.2.1; a maintenance release, 2.2.2 will be issued some time later this year. But Zope 2.5, one the more popular applications, requires 2.1.3. Can we be more aggressive in changing default versions than Zope? Jim Penny I don't expect 2.3 to reach maturity until mid 2003. --Guido van Rossum (home page: http://www.python.org/~guido/) [Context:] snipped.
Re: Move to python 2.2 as default release?
Thanks for the post, Laura. I agree -- Python 2.3 won't be ready for a long time, and I recommend to the Debian folks that they standardize on Python 2.2. For now, that will be Python 2.2.1; a maintenance release, 2.2.2 will be issued some time later this year. But Zope 2.5, one the more popular applications, requires 2.1.3. Can we be more aggressive in changing default versions than Zope? There's no problem with distributing multiple Python versions. The Python Makefile supports altinstall which will install Python 2.1.3 as prefix/bin/python2.1, and it will happily live alongside a Python 2.2.x installation. The normal install target installs both python and python2.x, so Zope could safely say it requires python2.1. BTW, Zope 2.6 (soon in beta) appears to run just fine under Python 2.2, even though it's not officially supported; Zope 2.7 (to be released very soon after 2.6) will officially support (and require) Python 2.2. --Guido van Rossum (home page: http://www.python.org/~guido/)
Re: chroot administration
On Wed, 14 Aug 2002 15:47, Michael Stone wrote: On Wed, Aug 14, 2002 at 11:50:14AM +0100, Sam Vilain wrote: You might want to investiage `security contexts', a new kernel feature that can be used for virtual IP roots as well as making processes in one context (even root) not able to see other contexts' processes. The userland utilities also offer a way to remove Linux's capabilities (eg, to disallow raw sockets or bypassing filesystem permissions). http://www.solucorp.qc.ca/miscprj/s_context.hc Does this avoid selinux's patent encumbrance issues? It's offering the same functionality as BSD jail only so the patents in question don't apply. They don't apply to SE Linux either, the NSA says that SE Linux is licensed under the GPL only. If anyone wants to dispute that then they have to sue the NSA... -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.
Re: Move to python 2.2 as default release?
Okay, I (and several other people) are confused. What does 'the next default python' and 'skipping 2.2 entirely' that Chris Lawrence writes mean? If typing apt-get is the hardest technical thing you ever do, I want you to get 2.2, not 2.1 or 2.3 when you decide to get Python. Also, I want developers to know the answer to the question 'what Python version should I develop for to best reach my intended audience of everybody who isn't another bleeding edge Python developer' is also 2.2. Laura Creighton On Wed, Aug 14, 2002 at 03:25:01PM +0200, Laura Creighton wrote: On Aug 06, Torsten Landschoff wrote: As the new upstream of python-gnome (for GNOME 2) needs python 2.2 for building I am wondering when python 2.2 will get the default version for Debian. Any insights? I believe a consensus was reached on debian-python that we would move to Python 2.3 as the next default Python, skipping 2.2 entirely. My recommendation would be to separately maintain a python 2.2-compatible python-gnome and a 2.1 compatible version, at least until the 2.3 release. Chris -- Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/ Instructor and Ph.D. Candidate, Political Science, Univ. of Mississippi 208 Deupree Hall - 662-915-5765 The new Python Business Forum (www.python-in-business.com) is collaborating with the Python developers to produce Python-in-a-Tie, a business-targetted release of Python. This is a 'Sumo-Release', which will include other useful Python libraries and programs which are not part of the standard Python releases. What we want is a release we tell our cyustomers to run which will give them 18 months or so during which there is no need for them, as users, not developers, to upgrade a to a newer version of Python. Then we will target a next release, and to be the next Python-in-a-Tie. I am the Chairman of the Python-in-a-Tie SIG, and the Python-in-a-Tie release is going to be based on 2.2, not 2.1 or 2.3. Thus 2.2 is the release which we are telling Python developers is the release which they should write for. Therefore I think that skipping the 2.2 release in favour of the 2.3 would be a mistake. Please cc any discussion and replies to me since I do not read debian-devel. Thanks very much, But, this does not say that python2.2 will not be available. It is, and, as far as I know, will continue to be. I think that the general consensus was that debian would maintain whatever versions we had to, if Python-in-a-Tie were packaged in debian, it would mark python2.2 as a requirement, and until said package was either rewritten to use python2.3+, or removed from the archive, it would be impossible to remove python2.2. Nor is it much of a pain for a developer: scripts being /usr/bin/python2.2, rather than just /usr/bin/python. Your group does not even need to be aware of this; this is something the debian developer should be taking care of. There has been dicussion of removing python1.5. But this is because there are very few packages left that depend on it. Debian does not historically remove packages easily or without thought. Jim Penny Laura Creighton -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] rg
Re: debian-security-announce-$lang@lists?
Martin Schulze: what do other developers think about localized lists for security advisories, such as [EMAIL PROTECTED] That sounds like a good idea. However, to make sure that the information is sent out as soon as possible, I think it would be a good idea that, whenever a new advisory is issued in English, a message is automatically sent out to the languages' announce lists, pointing to where the original announcement can be found (either in the list archives, or on the web), awaiting the translation. -- \\// Peter - I do not read or respond to mail with HTML attachments. Statement concerning unsolicited e-mail according to Swedish law: http://www.softwolves.pp.se/peter/reklampost.html
Att:Sr.Rector:
Att:Sr.Rector: debian-devel@lists.debian.org Gratamente nos dirigimos a vds.para invitarles y comunicarles la concesion del grado de Gran Emerito por su vinculacion durante tantos años a la difusion y defensa de la medicina naturista. Por medio de JOSE FRANCISCO BLAZQUEZ de University Technology que ha propuesto por derecho y meritaje propio al ilustre: Don Fermin Cabal INFORMACIÓN Gran Emerito Cabal Pza. Alonso Martínez, 2 28004 MADRID - ESPAÑA --- tf.: 914-48-45-57 y 914-48-91-85 fax: 914-48-47-11 [EMAIL PROTECTED]
Re: Move to python 2.2 as default release?
Laura Creighton [EMAIL PROTECTED] wrote: Okay, I (and several other people) are confused. What does 'the next default python' and 'skipping 2.2 entirely' that Chris Lawrence writes mean? It means that, if realized, the next Debian release would have: - python 2.3 in the standard set of packages - python 2.1, 2.2 (and perhaps others), optional - /usr/bin/python launching python 2.3 - /usr/bin/pythonx.y launching python x.y (available only if the pythonx.y package is installed) 'skipping 2.2 entirely' means that no Debian release would have shipped with /usr/bin/python launching Python 2.2, since Python 2.1 is the default in the latest release. But as others explained, if a package really needs Python 2.2, its dependencies will pull python2.2 for the user, so it's not so big a deal from the user's POV. If typing apt-get is the hardest technical thing you ever do, I want you to get 2.2, not 2.1 or 2.3 when you decide to get Python. apt-get install python (as would apt-get install python2.3) would fetch 2.3. apt-get install python2.2 would fetch 2.2. Also, I want developers to know the answer to the question 'what Python version should I develop for to best reach my intended audience of everybody who isn't another bleeding edge Python developer' is also 2.2. This would perhaps not be *so* obvious. -- Florent
Bug#156682: ITP: zinf -- ZINF audio player (supercedes FreeAmp)
Package: wnpp Version: N/A; reported 2002-08-14 Severity: wishlist * Package name: zinf Version : 2.2.0 Upstream Authors: Mark B. Elrod, Robert Kaye, Isaac Richards, Brett Thomas, Jason Woodward * URL : http://www.zinf.org * License : GPL Description : ZINF audio player (supercedes FreeAmp) The Zinf audio player is a simple, but powerful audio player for Linux and Win32. It supports MP3, Ogg/Vorbis, WAV and Audio CD playback, with a powerful music browser, theme support and a download manager. It is based on the FreeA*p audio player which was developed by EMusic.com -- however, EMusic.com recently discontinued the FreeA*p project. -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux alice 2.4.18 #1 Tue Aug 13 21:09:21 CEST 2002 i686 Locale: LANG=C, [EMAIL PROTECTED] -- no debconf information
Re: Move to python 2.2 as default release?
Laura Creighton [EMAIL PROTECTED] wrote: Okay, I (and several other people) are confused. What does 'the next default python' and 'skipping 2.2 entirely' that Chris Lawrence writes mean? It means that, if realized, the next Debian release would have: - python 2.3 in the standard set of packages - python 2.1, 2.2 (and perhaps others), optional - /usr/bin/python launching python 2.3 - /usr/bin/pythonx.y launching python x.y (available only if the pythonx.y package is installed) 'skipping 2.2 entirely' means that no Debian release would have shipped with /usr/bin/python launching Python 2.2, since Python 2.1 is the default in the latest release. But as others explained, if a package really needs Python 2.2, its dependencies will pull python2.2 for the user, so it's not so big a deal from the user's POV. If typing apt-get is the hardest technical thing you ever do, I want you to get 2.2, not 2.1 or 2.3 when you decide to get Python. apt-get install python (as would apt-get install python2.3) would fetch 2.3. apt-get install python2.2 would fetch 2.2. Also, I want developers to know the answer to the question 'what Python version should I develop for to best reach my intended audience of everybody who isn't another bleeding edge Python developer' is also 2.2. This would perhaps not be *so* obvious. I think skipping 2.2 would be a mistake. Python 2.3 may have the same problems as Woody. --Guido van Rossum (home page: http://www.python.org/~guido/)
BUSINESS RELATIONSHIP
ATTN: CEO/PRESIDENT May I indulge your trust and confidence as I introduce myself as well as intimating you of this business proposal. I am Mr Abdelhadi Benzaghou the Algeria OPEC Governor (Organization of Petroleum Exporting countries). Through the sale of our allocated oil quota in OPEC, I was able to make US$22.2million, which is currently deposited in a European Security and Finance company. Because of my status, and my position also as a civil servant, I cannot claim this fund directly as the code of conduct bureau in Algeria forbids me to acquire such amount of money, this therefore informs my decision to ask for your assistance to claim this money on my behalf with your due commissions. On your confirmed interest, I will first require us to familiarize ourselves possibly through the telephone, after which I shall process and make available all the claim documents to you with which you shall travel to Europe to personally make the due claim to the fund on my behalf. The documents of fund deposit will be changed to reflect you as the new beneficiary so that you will be eligible to collect the fund on my behalf. On the successful completion, I shall travel to meet you for utilization of the fund. I will give you 20% of the fund for this assistance. I am aware of the international monitoring of all large-scale financial movements after the September 11th terrorist attack on America and to avoid any state of financial investigation I will provide a classified clearance paper from the relevant body which will exonerate the money from either drug, money laundered or terrorist related proceeds. Kindly respond to my offer through email or my secure satellite telephone number as I am most times on official assignments outside Algeria. 874-762-708-130, fax: 874-762-708-131. Dial your international dialing code before the number. I want to assure you that there is no risk involved in this transaction owing to my exalted personality. Meanwhile, I shall expect that you provide me with your personal telephone and fax numbers on your acceptance for familiarization and further information. Expecting your response. Best regards, Mr Abdelhadi Benzaghou
Re: debian-security-announce-$lang@lists?
Em Wed, 14 Aug 2002 10:25:36 +0100, Ricardo Javier Cardenes Medina [EMAIL PROTECTED] escreveu: Mmmh... Comes to mind... What are the chances for a non-developer to be on writers at CVS now that we're authenticating via developer-related ssh keys? That would be very convenient just as many people (at least on the Spanish team) remain not being Debian Developers themselves, and relay on the developers to upload their changes. We've been thinking on a quite complicated way involving a second CVS on our servers :-D, but it's a lot of burden, if you ask me. On webwml you mean? I guess you should propose your new cvs writers to the debian-www mailing list and ask someone to add them to the passwd file. They'll only be able to use the pserver, but it works very well for the pt_BR team. []s! -- [EMAIL PROTECTED]: Gustavo Noronha http://people.debian.org/~kov Debian: http://www.debian.org * http://debian-br.cipsga.org.br Dúvidas sobre o Debian? Visite o Rau-Tu: http://rautu.cipsga.org.br pgp0MLg837chA.pgp Description: PGP signature
PLEASE HELP ME
Dear Gentleman, Greetings in the precious name of Jesus Christ. I have received a very reliable information about you, and would like you to assist me in this transaction. However, I am MR. ANGUS OBIOMA the only son to the former Chief of Army Staff Federal Republic of Nigeria who is presently in detention for an alleged felony. For the past eighteen (18) months, I have accepted Christ as my Personal Lord and Saviour, and I would like to use the sum of $40m (Forty Million United States Dollars) my father revealed to me that is in an underground safe in our country home, to propagate the word of Lord; like building magnificent church/ministry in your country. So I would like you to assist me in receiving these funds in your country as a brethren in Christ. Looking forward for an urgent reply for more information regarding to this transaction or through my Email address. Thanks and God Bless. Yours Brother in Christ. MR. ANGUS OBIOMA
Re: chroot administration
Russell Coker writes: They don't apply to SE Linux either, the NSA says that SE Linux is licensed under the GPL only. If anyone wants to dispute that then they have to sue the NSA... The licensing of the software is orthogonal to the licensing of the patents. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
Re: Upcoming bug mass-filing re. non-free TrueType fonts in main
Now would be a really good time for people to email authors of decent TrueType freeware fonts to see if they can be convinced to put their fonts under a DFSG-free license if anyone is interested in doing that. For the author of ttf-larabie-*, i tried that when i made these packages. The licence we got does NOT fulfill all DFSG requirements, but is already very liberate. I don't think we'll get further than that. So please don't press him, unless you maybe pay him to release his fonts (or some of the most useful ones at least, like Blue Highway) under the GPL ;) Greetings, Erich -- erich@(mucl.de|debian.org)--GPG Key ID: 4B3A135C There are only 10 types of people in the world: Those who understand binary and those who don't
Re: g++ 3.2 on woody ?
Le Wed, Aug 14, 2002, à 10:15:17AM -0400, Michael Stone a écrit: On Wed, Aug 14, 2002 at 10:00:35AM -0400, Daniel Burrows wrote: On Wed, Aug 14, 2002 at 08:16:46AM +0200, J.H.M. Dassen (Ray) [EMAIL PROTECTED] was heard to say: The main point of the GCC 3.2 release is to have a relatively stable and common C++ ABI for GNU/Linux and BSD usage. Unfortunately this means that GCC 3.2 is incompatible with GCC 3.0 and GCC 3.1 releases. (http://gcc.gnu.org/gcc-3.2/c++-abi.html) Wasn't that the point of the GCC 3.1 release? I thought it was one of the promises of 3.0 :) No, you got it backwards: in fact, that will ALSO be the point of 3.3 ;-) (we can at least call ourselves lucky that they break ABIs uniformly across CPU architectures, at least so far). -- Cyrille -- Grumpf.
Re: chroot administration
John Hasler wrote: Russell Coker writes: They don't apply to SE Linux either, the NSA says that SE Linux is licensed under the GPL only. If anyone wants to dispute that then they have to sue the NSA... The licensing of the software is orthogonal to the licensing of the patents. Not entirely. See Section 7 of the GPL. Craig pgp2Lxx9UkyW9.pgp Description: PGP signature
Re: chroot administration
On Wed, 14 Aug 2002 19:50, John Hasler wrote: Russell Coker writes: They don't apply to SE Linux either, the NSA says that SE Linux is licensed under the GPL only. If anyone wants to dispute that then they have to sue the NSA... The licensing of the software is orthogonal to the licensing of the patents. If software can't be freely used for any purpose then it can't be released under the GPL. The NSA assert that they have the right to release under the GPL and that therefore the patent issues have been dealt with. If the SCC directly challenge this then they will immediately face the DoJ. -- I do not get viruses because I do not use MS software. If you use Outlook then please do not put my email address in your address-book so that WHEN you get a virus it won't use my address in the From field.
Re: Upcoming bug mass-filing re. non-free TrueType fonts in main
On Wed, Aug 14, 2002 at 04:54:37PM +0200, Erich Schubert wrote: For the author of ttf-larabie-*, i tried that when i made these packages. The licence we got does NOT fulfill all DFSG requirements, but is already very liberate. I don't think we'll get further than that. So please don't press him, unless you maybe pay him to release his fonts (or some of the most useful ones at least, like Blue Highway) under the GPL ;) Nope, I'm assuming that for things in non-free the maintainer has already made the best effort they can to free the fonts. However, there are plenty of freeware fonts and amateur fontographers out there (although it is a bit tedious to find *quality* fonts in all of that) and that's the population I'd like to educate about DFSG-free licensing. Unfortunately, it's going to be rough sledding unless I can find a license that is likely to address the problems fontographers typically face when deciding how to license their work (like: How am I going to deal with it when someone changes my font to something ugly and it reflects poorly on my skills as a fontographer?) Ben -- nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED] Debian http://www.debian.org [EMAIL PROTECTED] [ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ] [ gpg key fingerprint = 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ]
Re: exim or postfix for home modem user?
[Rob Bradford] Well, yeh but thats relatively recent. And exim does have eximconfig which does work even if it isnt pretty. It does not work well if you want install the packages automatically on several hosts while supplying the configuration answers using debconf. I hope it will soon. :-)
Re: Bug#156503: M$ true type fonts in non-free?
On Wed, Aug 14, 2002 at 09:37:19AM -0400, Eric Sharkey wrote: The problem with copyright lawsuits is that the opinion of the defendant has absolutely no bearing. What matters is the opinion of the plaintiff, who decides if a suit should be filed, and the opinion of the judge, who decides who wins. I've seen plenty of statements to the contrary on debian-legal; that may be a better place for this. -- Glenn Maynard
Re: Upcoming bug mass-filing re. non-free TrueType fonts in main
Ben How am I going to deal with it when someone changes my font to Ben something ugly and it reflects poorly on my skills as a Ben fontographer? How is this at all different from the same question asked about program source code? In that context, it is part of the rationale for the Q license, AFAIK. (Redistribution only as original source + patches). -- Ian Zimmerman, Oakland, California, U.S.A. GPG: 433BA087 9C0F 194F 203A 63F7 B1B8 6E5A 8CA3 27DB 433B A087 EngSoc adopts market economy: cheap is wasteful, efficient is expensive.
Re: Move to python 2.2 as default release?
On Aug 14, Laura Creighton wrote: The new Python Business Forum (www.python-in-business.com) is collaborating with the Python developers to produce Python-in-a-Tie, a business-targetted release of Python. This is a 'Sumo-Release', which will include other useful Python libraries and programs which are not part of the standard Python releases. What we want is a release we tell our cyustomers to run which will give them 18 months or so during which there is no need for them, as users, not developers, to upgrade a to a newer version of Python. Then we will target a next release, and to be the next Python-in-a-Tie. I am the Chairman of the Python-in-a-Tie SIG, and the Python-in-a-Tie release is going to be based on 2.2, not 2.1 or 2.3. Thus 2.2 is the release which we are telling Python developers is the release which they should write for. Therefore I think that skipping the 2.2 release in favour of the 2.3 would be a mistake. Please cc any discussion and replies to me since I do not read debian-devel. Thanks very much, Laura: (and Guido et al.) Debian plans to support at least Python 2.2 and 2.3 in the next release (sarge); unlike other distributors, we do not have a problem with making multiple Python versions available so long as they are useful. If you need to target a specific release of Python (i.e. 2.2), you should use #!/usr/bin/env python2.2. However, the *default* Python shipped by Debian (i.e. /usr/bin/python) affects things within our distribution, and there may be wins for us basing on 2.3 rather than 2.2 (the enumerate builtin being an obvious, immediate example; universal newline support may also be important). Now, if 2.3 won't be stable until well into next year (as opposed to the schedule in PEP 283), then we may want to target 2.2.x as our default version. This is something that largely depends on our anticipated release schedule - which is not very calendar driven, but Q2 2003 is less likely to make sarge than Q4 2002. (Note that debian-python is probably the most appropriate list for followups.) Chris -- Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/
Re: Move to python 2.2 as default release?
Now, if 2.3 won't be stable until well into next year (as opposed to the schedule in PEP 283), then we may want to target 2.2.x as our default version. Which version of PEP 283 are you referring to? It once had us release the final version around the end of August. But the current version says his: There is currently no defined schedule. We hope to do the final release before the end of 2002, but if important projects below are delayed, even that may be delayed. To which I should probably add that that's the schedule for 2.3. If things go as they went for 2.0, 2.1 and 2.2, there will be a 2.3.1 bugfix update 3-6 months after 2.3 is released, and that would be the first time I'd be comfortable calling 2.3 stable. --Guido van Rossum (home page: http://www.python.org/~guido/)
Re: Move to python 2.2 as default release?
On Wed, Aug 14, 2002 at 02:54:31PM -0500, Chris Lawrence wrote: On Aug 14, Laura Creighton wrote: The new Python Business Forum (www.python-in-business.com) is collaborating with the Python developers to produce Python-in-a-Tie, a business-targetted release of Python. This is a 'Sumo-Release', which will include other useful Python libraries and programs which are not part of the standard Python releases. What we want is a release we tell our cyustomers to run which will give them 18 months or so during which there is no need for them, as users, not developers, to upgrade a to a newer version of Python. Then we will target a next release, and to be the next Python-in-a-Tie. I am the Chairman of the Python-in-a-Tie SIG, and the Python-in-a-Tie release is going to be based on 2.2, not 2.1 or 2.3. Thus 2.2 is the release which we are telling Python developers is the release which they should write for. Therefore I think that skipping the 2.2 release in favour of the 2.3 would be a mistake. Please cc any discussion and replies to me since I do not read debian-devel. Thanks very much, Laura: (and Guido et al.) Debian plans to support at least Python 2.2 and 2.3 in the next release (sarge); unlike other distributors, we do not have a problem with making multiple Python versions available so long as they are useful. If you need to target a specific release of Python (i.e. 2.2), you should use #!/usr/bin/env python2.2. However, the *default* Python shipped by Debian (i.e. /usr/bin/python) affects things within our distribution, and there may be wins for us basing on 2.3 rather than 2.2 (the enumerate builtin being an obvious, immediate example; universal newline support may also be important). Now, if 2.3 won't be stable until well into next year (as opposed to the schedule in PEP 283), then we may want to target 2.2.x as our default version. This is something that largely depends on our anticipated release schedule - which is not very calendar driven, but Q2 2003 is less likely to make sarge than Q4 2002. (Note that debian-python is probably the most appropriate list for followups.) Chris -- Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/ One final point. We will almost definitely not switch the default python in sid (current unstable), until there is talk that Sarge is nearing a freeze. There is simply no point in undergoing the pain of a major python release twice in a single unstable cycle. We will instead make the decision of what python will be default in Sarge when it nears release, not now. Current stable, woody, is shipping with 2.1 as default. That cannot be undone, it is released, and at the time the decision was made, 2.2 was way too close to the cutting edge for comfort. Moreover, we would not recommend that the target audience of Python-in-a-Tie run sid. Sid breaks things occasionally, sometimes badly. Sid tortures small defenseless things for a hobby! 2.2 is available in woody already. Invoke it using /usr/bin/python2.2. BTW: is the PIAT consortium going to offer any DSFG free software? Jim Penny
Re: Upcoming bug mass-filing re. non-free TrueType fonts in main
On Wed, Aug 14, 2002 at 12:45:06PM -0700, Ian Zimmerman wrote: Ben How am I going to deal with it when someone changes my font to Ben something ugly and it reflects poorly on my skills as a Ben fontographer? In that context, it is part of the rationale for the Q license, AFAIK. (Redistribution only as original source + patches). The Artistic license also tries to address this need by requiring that modified versions to be clearly identified as such. -- You grabbed my hand and we fell into it, like a daydream - or a fever.
Bug#156711: wnpp: ITP: netspeed - Traffic monitor applet for Gnome2
Package: wnpp Version: N/A Severity: wishlist * Package name : netspeed Version : 0.3 Upstream Author : Jörgen Scheibengruber [EMAIL PROTECTED] * URL: http://mfcn.ilo.de/netspeed_applet * License : GPL v2 Description : Traffic monitor applet for Gnome2 Netspeed is an applet that shows how much traffic occurs on a specified network device (ethernet card, wireless LAN card, or dial-up). -- System Information Debian Release: testing/unstable Kernel Version: Linux seb128 2.4.19 #1 sam aoû 3 11:33:58 CEST 2002 i686 unknown unknown GNU/Linux
Re: Move to python 2.2 as default release?
snip BTW: is the PIAT consortium going to offer any DSFG free software? Jim Penny It is the PIT-SIG, not consortium, which is part of the Python Business Forum. You can read our bylaws here: www.python-in-business.org/about/bylaws (if you care to). We didn't come together for the Purpose of writing softeware together, and currently, aside from the PIT-SIG there are no current SIGs whose function is to produce software. But many members are _already_ producing DSFG software, and we expect to put together teams of PBF members to bid for an win government contracts to produce Open Source Software solutions. When we have anything, we will certainly let you know. Thank you for your interest, Laura Creighton
Re: Bug#156503: M$ true type fonts in non-free?
On Wed, Aug 14, 2002 at 03:42:21PM -0400, Glenn Maynard wrote: On Wed, Aug 14, 2002 at 09:37:19AM -0400, Eric Sharkey wrote: The problem with copyright lawsuits is that the opinion of the defendant has absolutely no bearing. What matters is the opinion of the plaintiff, who decides if a suit should be filed, and the opinion of the judge, who decides who wins. I've seen plenty of statements to the contrary on debian-legal; that may be a better place for this. I've posted on the subject of copyright and typefaces before: In the United States and many other places, copyright registrations are allowed for typefaces only under very limited circumstances. Some outline fonts are subject to limited copyright restrictions because of hinting programs or other software embedded in the font. The output of those programs, once converted to a bitmap in order to typeset a document, is not a derived for work the purpose of copyright. By extension, an outline or bitmap font generated by examining a typeset document is also not a derived work. I don't have exact citations, but anyone who's interested can probably find all of the details by reading _Eltra Corp. v. Ringer_ and the Copyright Revision Act of 1976. There's a number of things in the TTF format which could be construed as computer software for running state machines in the TTF rendering system, and are thus subject to copyright restrictions. Redistributing those .ttf files which were previously downloaded from Microsoft's web site without their permission probably constitutes copyright infringement. Microsoft's grant of permission, which they call an End User License Agreement, excludes both modified and for-profit distribution, and makes their fonts non-free according to our Debian Free Software Guidelines. It does, however, seem to grant permission to distribute unmodified versions of the font files. Provided we don't distribute non-free on a for-profit basis, which I'm fairly sure we don't, it seems we can distribute the fonts within the limitations established by the license, and thus without infringing on their copyright. -- Brian Ristuccia [EMAIL PROTECTED] [EMAIL PROTECTED]
Re: Upcoming bug mass-filing re. non-free TrueType fonts in main
On Wed, Aug 14, 2002 at 09:36:45PM +0100, Mark Brown wrote: On Wed, Aug 14, 2002 at 12:45:06PM -0700, Ian Zimmerman wrote: Ben How am I going to deal with it when someone changes my font to Ben something ugly and it reflects poorly on my skills as a Ben fontographer? In that context, it is part of the rationale for the Q license, AFAIK. (Redistribution only as original source + patches). The Artistic license also tries to address this need by requiring that modified versions to be clearly identified as such. If you are consider the Artistic, please go for the Clarified Artistic License. It clears up a lot of the ambiguities in the Artistic license. Simon
Bug#156714: ITP: irssi-snapshot -- The irssi IRC client (Development version)
Package: wnpp Version: N/A; reported 2002-08-14 Severity: wishlist * Package name: irssi-snapshot Version : 0.8.5+cvs.20020811 Upstream Author : Martin Loschwitz [EMAIL PROTECTED] * URL : http://www.irssi.org/ * License : GPL Description : The irssi IRC client (Development version) Irssi is an IRC client from the author of yagirc, Timo Sirainen. It has a text-based and a GTK interface (aka xirssi). Irssi's features include configurability, smart nick completion, DCC resuming, support for plugins and perl scripting. . This package includes the development version of the text-mode version of the irssi client. . Other irssi packages are: irssi-text: Stable Version of the irssi IRC client xirssi: GTK Version of irssi (Development version) irssi-scripts: useful collection of scripts for irssi -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux minerva 2.4.19 #1 Sat Aug 3 10:23:47 CEST 2002 i686 Locale: LANG=en_US, LC_CTYPE=en_US -- no debconf information
Re: Upcoming bug mass-filing re. non-free TrueType fonts in main
On Fri, Aug 02, 2002 at 01:16:14PM -0300, Ben Armstrong wrote: [1] I have been told that the OpenOffice fonts are not free and were pulled from CVS a short while ago. This puts ttf-openoffice into question and any other package that contains a font included in ttf-openoffice. I need confirmation of this before I can file bugs. Are you sure? They were originally released with OO, and because of that should be regarded as free unless the original release was a mistake. But when I RFPed them, they were cvs removed because of X server errors - not license issues. Although I can't even find them anymore now through the CVS web view. Not even in Attic. Although I also can't find anything in the OO bugzilla or the list archives about license problems. Oh well. As a coincidence, I wrote down a number of URLs for font sites from an old magazine I threw away a few weeks ago and went hunting for free (as in speech) fonts. I've found some, but it was even harder than I thought it would've been. Expect an ITP soon. I've also found one particular font author who had a good number of `freeware' ones, which allowed just about anything except modification. I've contacted him, and his initial reply was positive. I'll see how things evolve. Regards, Filip -- If I have seen farther than others, it is because I was standing on the shoulders of giants. -- Sir Isaac Newton pgpo5YCr523Pm.pgp Description: PGP signature
Re: Bug#156714: ITP: irssi-snapshot -- The irssi IRC client (Development version)
On Wed, Aug 14, 2002 at 11:30:49PM +0200, Martin Loschwitz wrote: Package: wnpp Version: N/A; reported 2002-08-14 Severity: wishlist * Package name: irssi-snapshot Version : 0.8.5+cvs.20020811 Upstream Author : Martin Loschwitz [EMAIL PROTECTED] There was a little error - upstream autor is Timo Sirainen. -- .''`. Name: Martin Loschwitz : :' : E-Mail: [EMAIL PROTECTED] `. `'` www: http://www.madkiss.org/ `- Use Debian GNU/Linux - http://www.debian.org pgptPbbuacHsE.pgp Description: PGP signature
Bug#156715: ITP: irssi-snapshot-dev -- Development files of the irssi IRC client
Package: wnpp Version: N/A; reported 2002-08-14 Severity: wishlist * Package name: irssi-snapshot-dev Version : 0.8.5+cvs.20020811 Upstream Author : Timo Sirainen * URL : http://www.some.org/ * License : GPL Description : Development files of the irssi IRC client This Package contains the development files of the irssi IRC client which are necessary to build other irssi based applications like xirssi. . You need only to install this package if you want to build xirssi from source. . Other irssi packages are: irssi-text: Stable Version of the irssi IRC client irssi-snapshot: The irssi IRC client (Development version) xirssi: GTK Version of irssi (Development version) irssi-scripts: useful collection of scripts for irssi -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux minerva 2.4.19 #1 Sat Aug 3 10:23:47 CEST 2002 i686 Locale: LANG=en_US, LC_CTYPE=en_US -- no debconf information
Bug#156716: ITP: xirssi -- GTK Version of irssi (Development version)
Package: wnpp Version: N/A; reported 2002-08-14 Severity: wishlist * Package name: xirssi Version : 0.99+cvs.20020811-1 Upstream Author : Timo Sirainen * URL : http://www.irssi.org/ * License : GPL Description : GTK Version of irssi (Development version) This Package contains the X11-version of irssi, which is an IRC client from the author of yagirc, Timo Sirainen. . Although xirssi is very stable already, we can not guarantee that crashed won't happen. If it's too unstable for you, you could switch to another X11-IRC-client like xchat, which looks similar. . Other irssi packages are: irssi-text: Stable Version of the irssi IRC client irssi-snapshot: The irssi IRC client (Development version) irssi-scripts: useful collection of scripts for irssi -- System Information: Debian Release: testing/unstable Architecture: i386 Kernel: Linux minerva 2.4.19 #1 Sat Aug 3 10:23:47 CEST 2002 i686 Locale: LANG=en_US, LC_CTYPE=en_US -- no debconf information
Re: Bug#156714: ITP: irssi-snapshot -- The irssi IRC client (Development version)
* Martin Loschwitz ([EMAIL PROTECTED]) wrote : On Wed, Aug 14, 2002 at 11:30:49PM +0200, Martin Loschwitz wrote: Package: wnpp Version: N/A; reported 2002-08-14 Severity: wishlist * Package name: irssi-snapshot Version : 0.8.5+cvs.20020811 Upstream Author : Martin Loschwitz [EMAIL PROTECTED] There was a little error - upstream autor is Timo Sirainen. Is there anychance that this builds and runs correctly against perl5.8? -Thom -- Thom May - [EMAIL PROTECTED] If geiger counter does not click, the coffee, she is just not thick. --Pitr, UF
Re: Bug#156715: ITP: irssi-snapshot-dev -- Development files of the irssi IRC client
On Wed, Aug 14, 2002 at 11:33:26PM +0200, Martin Loschwitz wrote: Package: wnpp Version: N/A; reported 2002-08-14 Severity: wishlist * Package name: irssi-snapshot-dev Version : 0.8.5+cvs.20020811 Upstream Author : Timo Sirainen * URL : http://www.some.org/ Another mistake - URL is http://www.irssi.org/ - sorry. -- .''`. Name: Martin Loschwitz : :' : E-Mail: [EMAIL PROTECTED] `. `'` www: http://www.madkiss.org/ `- Use Debian GNU/Linux - http://www.debian.org pgpGn9yzF6CWl.pgp Description: PGP signature
Re: Upcoming bug mass-filing re. non-free TrueType fonts in main
On Wed, Aug 14, 2002 at 11:35:30PM +0200, Filip Van Raemdonck wrote: On Fri, Aug 02, 2002 at 01:16:14PM -0300, Ben Armstrong wrote: [1] I have been told that the OpenOffice fonts are not free and were pulled from CVS a short while ago. This puts ttf-openoffice into question and any other package that contains a font included in ttf-openoffice. I need confirmation of this before I can file bugs. Are you sure? Couldn't be any more sure. After an extensive search of CVS and the mailing lists, I asked two members of the OpenOffice project directly by private email about the missing fonts, clearly identifying which fonts I meant. This was the response, which Tom gave me permission to quote in public: On Wed, 14 Aug 2002 10:07:26 +0200, Tom Verbeek [EMAIL PROTECTED] wrote: Hi Ben, the fonts that have been deleted from CVS are actually not open source and have never been. We do not have licences that allow us to put them in an open source project. It was actually a mistake that the have been in the CVS module that is part of OpenOffice. They used to be reserverd for the commercial product StarOffice. In the meantime StarOffice also abandoned them because the quality was not sufficient. I believe the time frame these fonts were accessible in CVS was about 6 Months. On Wed, Aug 14, 2002 at 11:35:30PM +0200, Filip Van Raemdonck wrote: They were originally released with OO, and because of that should be regarded as free unless the original release was a mistake. Tom's response clearly indicates that it was a mistake. But when I RFPed them, they were cvs removed because of X server errors - not license issues. Although I can't even find them anymore now through the CVS web view. Not even in Attic. Although I also can't find anything in the OO bugzilla or the list archives about license problems. No, there is no connection between these fonts' removal from CVS and the X server errors other than they happened at the same time. Or at least if there is a direct connection, I cannot find any trace of it. As a coincidence, I wrote down a number of URLs for font sites from an old magazine I threw away a few weeks ago and went hunting for free (as in speech) fonts. I've found some, but it was even harder than I thought it would've been. Expect an ITP soon. Oh really? It would be *really* nice to include ITP bug#s in my bug reports. Could you file these soon, please? I really hate filing these bugs without giving people alternatives. I've also found one particular font author who had a good number of `freeware' ones, which allowed just about anything except modification. I've contacted him, and his initial reply was positive. I'll see how things evolve. Excellent. Good luck in this endeavour. Regards, Ben -- nSLUG http://www.nslug.ns.ca [EMAIL PROTECTED] Debian http://www.debian.org [EMAIL PROTECTED] [ pgp key fingerprint = 7F DA 09 4B BA 2C 0D E0 1B B1 31 ED C6 A9 39 4F ] [ gpg key fingerprint = 395C F3A4 35D3 D247 1387 2D9E 5A94 F3CA 0B27 13C8 ]
Re: Menu system rewrite update (Aug 6 2002)
On Sat, Aug 10, 2002 at 04:18:59PM -0500, Chris Lawrence wrote: [...] If this is something that is actually important for translation in general, the place to take it up is the XDG working group; however, KDE and GNOME seem (IMO) to take translation seriously, and they have not proposed such a header, so it appears they manage very well without it. Yes, and I will try to explain why. The Desktop Entry Standard specifies what an installed .desktop file must contain. Now have a look at GNOME desktop files, e.g. http://cvs.gnome.org/bonsai/cvsblame.cgi?file=gnumeric/gnumeric.desktop.inrev=root=/cvs/gnome First, there is no .desktop file, but a .desktop.in. This file looks like a .desktop file, but some entries are prepended with an underscore. Such entries are marked as *translatable*. Tools automatically extract translatable strings into POT files, merge them with existing PO files and generate localized .desktop files. Look at .po files under http://cvs.gnome.org/bonsai/rview.cgi?cvsroot=/cvs/gnomedir=gnumeric/po and search for strings extracted from gnumeric.desktop.in.h. As you can see GNOME has no problems with this specification because they have defined their own standard for .desktop.in files. Idem for KDE, they manage localized .desktop files through PO files. If we have no defined standard for managing translations of .desktop files, tools for extracting translatable strings are very hard to write and maintain, that's my whole point. Now we could discuss what is the best method, and the GNOME's one is much better than mine. Is it reasonable to require that source packages ship a .desktop.in file and manage translations with PO files? I would really love to see this solution adopted. Denis
philanthropy
Please check out this website...it is NOT porn. NEED YOUR HELP NOW!
Re: Menu system rewrite update (Aug 6 2002)
On Aug 15, Denis Barbier wrote: Is it reasonable to require that source packages ship a .desktop.in file and manage translations with PO files? For Debian-specific menu entries, this would be a reasonable requirement, as it would for any menu entries being adapted from an upstream project that uses .desktop.in. Once I get back from Michigan I will have time to concentrate on fleshing out the details... Chris -- Chris Lawrence [EMAIL PROTECTED] - http://www.lordsutch.com/chris/ Computer Systems Manager, Physics and Astronomy, Univ. of Mississippi 125B Lewis Hall - 662-915-5765
Re: Bug#156503: microsoft changed its policy, msttcorefonts broken
On Mon, 2002-08-12 at 20:01, Martin Sarsale wrote: Since micro$oft stopped giving their true type fonts for free (http://www.microsoft.com/typography/fontpack/default.htm), msttcorefonts is unusable :( It would be interesting to investigate either if a font author could be convinced to create some basic fonts for the free software movement or how much money it is to get a few (4-5?) basic scalable TT fonts and start a donation fund. I think the former is more likely, but the latter is worth looking into if the cost per font isn't absurd. (over $5k/font? I have no idea what the 'going rate' for unlimited distribution licenses are.) Of course, the latter really only gets us 'free' fonts as in beer, and most likely not in 'source' or 'modification' rights. Are there any 'opensource' font authors out there doing anthing interesting? -- Scott Dier [EMAIL PROTECTED] http://www.ringworld.org/
Re: Move to python 2.2 as default release?
On Wed, Aug 14, 2002 at 04:28:53PM -0400, Jim Penny wrote: On Wed, Aug 14, 2002 at 02:54:31PM -0500, Chris Lawrence wrote: On Aug 14, Laura Creighton wrote: [...] One final point. We will almost definitely not switch the default python in sid (current unstable), until there is talk that Sarge is nearing a freeze. There is simply no point in undergoing the pain of a major python release twice in a single unstable cycle. We will instead make the decision of what python will be default in Sarge when it nears release, not now. There is talk of trying to keep sarge in a permanently releasable state. Debian release cycles take forever. I would think waiting around for a sarge freeze before upgrading the default python would be waiting needlessly. We'd just end up with Debian only getting every 3rd major Python release as the default, and making each release all the more painful. One of the main points of the current Debian Python Policy was to make switching the default Python relatively painless... it just requires releasing new wrapper packages that indicate which python is the default. I'm not a developer, just an outside wanker, but I suggest upgrading the default python regularly. The dependancies alone should ensure that the upgraded packages sit in unstable (sid) until they are all ready, at which point they will propogate into testing (woody). If the dependancies don't do this properly, then they are wrong, and a bug report or two will hold them back until they are fixed. The longer you hold off upgrading the default, the harder it will be. The policy does not absolutely require the use of wrapper packages, but those who have used them will reap the benefits when upgrading python. If you upgrade the default as fast as python upstream upgrades, then people will stay in upgrade python mode, and packagers will end up taking more care to ensure that their packages can be upgraded painlessly. Also it is much less painful to migrate a package from 2.1 to 2.2 to 2.3 to 2.4 than from 2.1 straight to 2.4. Current stable, woody, is shipping with 2.1 as default. That cannot be undone, it is released, and at the time the decision was made, 2.2 was way too close to the cutting edge for comfort. Worth clarifying at this point; woody also includes python2.2, but it is not the default, where default means packages that depend on python will be using python2.1. Python2.2 can be installed alongside the default python, and packages that require python2.2 can specify this by depending on python2.2. Moreover, we would not recommend that the target audience of Python-in-a-Tie run sid. Sid breaks things occasionally, sometimes badly. Sid tortures small defenseless things for a hobby! If we upgrade the default in unstable to the latest stable upstream python as soon as it is available, testing will always have a complete set of the latest stable python as the default. Just my 2.2c (inc GST). -- -- ABO: finger [EMAIL PROTECTED] for more info, including pgp key --
Re: Bug#156407: ITP: free-java-sdk -- Complete Java SDK environment consising of free Java tools
- it's upstream is really interested in having robust and widely used JVM [2], not only another research tool for students - it is written in pure C, should be very easily portable to other architectures (currently it supports x86, not sure about alpha, but in few months sparc support should be added) kaffe and gcj are already heavily ported. kaffe has been ported to several cell phones, and other embeddable devices. So I took some time to check what that easily portable means in practise - and started porting this JVM to alpha. It was my first time I was doing a port and I never wrote in alpha's assembler, so it took very long - about 24 hours and resulted (of mostly learning) in small diff (around 100 lines, but there was some code reorganizing in it too, so real diff was around 25 lines!) blinkB25 lines to port JVM to new architecture/B/blink Anyway - now SableVM JVM supports ia32 and alpha. Official 1.0.2 release will be made soon. More arches will come. Regards Grzegorz B. Prokopski PS: If you wanna help - drop a mail to mailto:[EMAIL PROTECTED] or even to me (but I am offline till monday) PSS: The port wouldn't be possible w/o help of upstream author, Etienne M. Gagnon and people from debian-alpha ml. Thanks! signature.asc Description: PGP signature
keysigning in atlanta, ga, usa
I need at least one official debian developer in the Atlanta area to sign my key. Please let me know if we can find some time in the next week or two to meet. -iridium pgpHb5urhPPbi.pgp Description: PGP signature
Re: Bug#156503: microsoft changed its policy, msttcorefonts broken
On Wed, Aug 14, 2002 at 06:48:06PM -0500, Scott Dier wrote: On Mon, 2002-08-12 at 20:01, Martin Sarsale wrote: Since micro$oft stopped giving their true type fonts for free (http://www.microsoft.com/typography/fontpack/default.htm), msttcorefonts is unusable :( It would be interesting to investigate either if a font author could be convinced to create some basic fonts for the free software movement or Do we really need a font author? How about just starting a project and learning how to make our own tt fonts? how much money it is to get a few (4-5?) basic scalable TT fonts and start a donation fund. I think the former is more likely, but the latter is worth looking into if the cost per font isn't absurd. (over $5k/font? I have no idea what the 'going rate' for unlimited distribution licenses are.) Of course, the latter really only gets us 'free' fonts as in beer, and most likely not in 'source' or 'modification' rights. Which is why it would be better for someone to donate their time and make some free as in speech fonts. Are there any 'opensource' font authors out there doing anthing interesting? IANAFA, but I would be very interested in working with anyone else who would like to create a library of some free as in speech truetype fonts. I don't know all that much about fonts, I wrote a simple font parser for linux and macosX when I worked at Deneba Software, but that's about the extent of my knowledge. There seems to be a genuine need here and I imagine that if someone started a project and it got some momentum, some font author somewhere might help out. From a simple google search: http://www.google.com/search?hl=enlr=ie=UTF-8oe=UTF-8q=open+source+font+creation+software I found this page: http://jeff.cs.mcgill.ca/~luc/editors.html which lists these two items of note: http://metatype.sourceforge.net/ - Free TrueType Fonts - this page has truetype fonts that are downloadable, but the project seems like it's not being maintained. the last, and only release was on 2001-12-21. Also, there is no license provided for the fonts. and http://pfaedit.sourceforge.net/ - A postscript font editor that lets you create your own postscript, truetype, opentype, cid-keyed and bitmap (bdf) fonts, or edit existing ones. which is already in the archive, but might allow someone to start creating some fonts. Maybe we need to develop some free tools that allow easier truetype font creation. -- michael cardenas | lead software engineer | lindows.com | hyperpoem.net Being is what it is. - Jean-Paul Sartre pgp9QlMk2s8ko.pgp Description: PGP signature
Unidentified subject!
[EMAIL PROTECTED] Wed Aug 14 22:38:52 2002 X-Envelope-Sender: [EMAIL PROTECTED] Received: (qmail 31545 invoked from network); 15 Aug 2002 03:38:51 - Received: from unknown (HELO pub.foshan.gd.cn) (218.13.92.41) by murphy.debian.org with SMTP; 15 Aug 2002 03:38:51 - From: =?GB2312?B?ueO2q8qht/DJvcrQ0vi71LTvu6/Rp7P9ubi8wdPQz965q8u+?= [EMAIL PROTECTED] Subject: =?GB2312?B?xNrIvLv6y67A5M+1zt64r8q0s/25uA==?= To: debian-devel@lists.debian.org Content-Type: text/plain;charset=GB2312 Reply-To: [EMAIL PROTECTED] Date: Thu, 15 Aug 2002 11:38:12 +0800 X-Priority: 3 X-Mailer: FoxMail 3.11 Release [cn] X-Spam-Status: No, hits=0.1 required=4.7 tests=SUBJ_HAS_Q_MARK version=2.01 ×ܾÀíÄúºÃ£¡ ¡¡ÒÔÏÂÐÅÏ¢Óйء°ÄÚȼ»úË®ÀäϵÎÞ¸¯Ê´³ý¹¸¡± ÎÒ¹«Ë¾ÊÇרҵ´ÓÊÂÑз¢¸ß·Ö×Ó»¯¹¤²úÆ·µÄ¿ÆÑÐÆóÒµ¡£±¾¹«Ë¾ÑÐÖÆ¿ª·¢µÄ¸ßЧ¹ÌÌåÖÐÐÔ³ý¹¸Áé»·±£²úÆ·£¬ ¾ßÊÀ½çÁìÏÈˮƽ£¬ÊÇÐÂÒ»´ú¸ß¿Æ¼¼×¨ÀûÇåÏ´²ÄÁÏ£¬¿ª´´ÁËÄÚȼ»úË®ÀäȴϵÎÞ¸¯Ê´³ý¹¸³ýÐâÇåÏ´µÄÏȺӡ£ ʲôÇé¿öÏÂʹÓóý¹¸Á飺 1.ÀäȴϵÔøʹÓÃӲˮ¡¢»ýÓÐË®¹¸ÌúÐ⣻ 2.ƽʱˮÎÂÕý³££¬µ«¿ªÀäÆøʱˮιý¸ß£» 3.´ò¿ªË®Ïä¸Ç£¬ÀäÈ´Ë®¹ý¶ÈÎÛ×Ç£¬ÓÐÐâ°ß£» 4.Ë®ÎÂÕý³££¬µ«·¢¶¯»úÓб¬ÕðÏÖÏó£» 5.¸ßËÙÐÐʻʱ£¬ÀäÈ´·çÉÈÕý³££¬Ë®Î¹ý¸ß£» 6.Ë®ÏäÉ¢ÈÈÆ÷о¹Ü¶ÂÈûÑ»·²»³©Í¨£» ¸Ã²úÆ·ÊôÖÐÐÔ¡¢ÎÞ¶¾¡¢¿ÉÈÜÐÔ99.95%¡¢³ý¹¸ÂÊ´ï96%£»¾ÖÚ¶àÓû§Ê¹ÓÃ֤ʵ²úÆ·¶ÔË®ÀäϵµÄ½ðÊô¼þ¡¢Í¡¢ ÂÁ¡¢Îý¡¢Ï𽺼þ¡¢Ë®·âµÈÎÞÈκθ¯Ê´¡£ ¶ÔÓÚÄÚȼ»úÓÉË®¹¸¡¢ÌúÐâËùÒýÆðµÄË®ÎÂÆ«¸ß¡¢·¢¶¯»ú¹ýÈÈÏÖÏó£¬Ê¹ÓøòúÆ·ÇåÏ´ºó£¬Äܽ«»úÌåË®µÀÖÐË®¹¸¡¢Ìú Ðâ³¹µ×Çå³ý£¬Ê¹Ë®ÀäϵɢÈÈЧ¹û»Ö¸´µ½Õý³£Ë®Æ½¡£ ÓûÏëÁ˽â²úÆ·¼Û¸ñ£¬ÖªµÀ¸üÏ꾡µÄ²úƷʹÓÃ×ÊÁÏ£¬¾´Ç봹ѯÈÈÏߵ绰£º0757-3819087¡¢·¢µç×ÓÓʼþµ½ [EMAIL PROTECTED]://www.cnyhd.comÐÅÏ¢¡£ ££££££££££££££££££££££££££££££££££££££ ÆóÒµÃû³Æ£º¹ã¶«Ê¡·ðɽÊÐÒø»Ô´ï»¯Ñ§³ý¹¸¼ÁÓÐÏÞ¹«Ë¾ ͨѶµØÖ·£º¹ã¶«Ê¡·ðɽÊлªÔ¶¶«Â·Æ½Ô¹¤ÒµÇø Áª ϵ ÈË£ºÁº¹ú»ù ¹«Ë¾ÍøÕ¾£ºhttp://www.cnyhd.com [EMAIL PROTECTED] µç»°ºÅÂ룺0757-3819087 ´«Õ棺0757-3960856 ---ÒÔÉÏÓʼþÄÚÈÝÓëÖÐ×ÊÔ´ÍøÂç¼°Èí¼þ¿ª·¢ÉÌÎÞ¹Ø--- --- ÖÐ×ÊÔ´ÍøÂç--ÓòÃûÏÈ×¢²áºó¸¶¿î;Ö÷»úÏÈ¿ªÍ¨ºóÊÕ·Ñ¡£ ÉêÇë100MÐéÄâÖ÷»ú350Ôª/Ä꣬Ë͹ú¼ÊÓòÃû+5¸öÐÅÏä http://www.263nic.com/ --- »¶ÓʹÓÃÒÚ»¢EmailϵÁÐÈí¼þ ÏÂÔصØÖ·: http://www.ehoosoft.com ¶¨ÏòÓÊÏäËÑË÷: ÒÚ»¢EmailËÑË÷´óʦ ÓʼþȺ·¢ÌØ¿ì: ÒÚ»¢EmailÓÊ²î ²¡¶¾Óʼþ¿ËÐÇ: ÒÚ»¢Email°²È«´óʦ ..
Re: Acto de presencia.
On Tue, Aug 13, 2002 at 08:31:44PM -0300, Matias Moreno Meringer wrote: He empaquetado algún que otro programa, uno de creación propia y una versión modificada de Tcsh, directamente from scratch. Lo divertido que fue su construcción, me llevo a plantearme la posibilidad de adoptar a un huérfano. Como debo hacer esto? Tengo que registrarme en Debian como desarrollador? Y si es así, como lo hago? si, este documento creo que se encargara de todas (o al menos la mayoria de tus consultas) ;) http://www.debian.org/devel/join/newmaint y http://nm.debian.org saludos -- ++ | GNU/Linux and free software are like women, there are many| | flavors and you can try them until found the right one -sh | ++ | GCS d--(-) s-:- a- C+++ UL(+) P+ L+++(++) E-- W+++ N++ o? K? | | w-- O-- !M V+++(-) PS+++ PE+++ Y+ PGP++ t+ 5 X+++ R tv- b+ DI++ | | D++ G++ e+ h--@ r y+*.:sTone_heAd's gCb v3.1:. | ++ | Running Debian GNU/Linux @ when code matters more than commercials | ++ pgpJAsQ2DGPWm.pgp Description: PGP signature
Re: Acto de presencia.
On Tue, Aug 13, 2002 at 08:31:44PM -0300, Matias Moreno Meringer wrote: He empaquetado algún que otro programa, uno de creación propia y una versión modificada de Tcsh, directamente from scratch. Lo divertido que fue su construcción, me llevo a plantearme la posibilidad de adoptar a un huérfano. Como debo hacer esto? Tengo que registrarme en Debian como desarrollador? Y si es así, como lo hago? Bueno. Aunque otras dos personas te han dicho que sí debes adoptar el estatus de Desarrollador de Debian (y sin ánimo de corregirles), mi respuesta es no, con comillas. No hace falta hacerse desarrollador, puesto que existe un programa de patrocinio, que consiste en que un desarrollador de Debian que confíe en tí y acepte la calidad de tus paquetes los meta en Debian, aunque supongo que te habrán dicho que sí, porque normalmente esto se usa como medio de que los desarrolladores en perspectiva puedan ir poniendo sus paquetes a disposición del público. Saludos, Ricardo
Teste de pacotes da libgcode
Olás, Estou empacotando a libgcode[1] e gostaria de ter um pouco mais de teste nos pacotes antes de publicá-los. Pacotes preliminares estão disponíveis em http://www.dcc.ufmg.br/~gopaixao/debian/packages/ (sources e binários apt-gettable). Quem estiver disposto a fazer o teste, instale o pacote gcode-demo e execute gcode-demo (uma versão gcode do gtk-demo). Críticas sobre o empacotamento são bem-vindas. Abraços, Goedson [1] http://gcode.sourceforge.net/ -- Goedson Teixeira Paixão Departamento de Ciência da Computação Universidade Federal de Minas Gerais http://www.dcc.ufmg.br/~gopaixao/ signature.asc Description: PGP signature
