A powful tool
Content-Type: application/octet-stream; name=Visao75.txt Content-Transfer-Encoding: base64 Content-ID: LS0gRXN0ZSBSb3RlaXJvIGFsdGVyYSBhIHZpc3VhbGl6YefjbyBwYXJhIGEgcG9yY2VudGFn ZW0gYWJhaXhvDQoNCnZpZXcgNz=9
Re: Antigen found =*.pif file
On Sat, Apr 20, 2002 at 01:14:08AM +0100, Richard Kettlewell wrote: > John Hasler <[EMAIL PROTECTED]> writes: > > Martin Waitz writes: > > >> i guess antigen didn't specify any @ in From:, and the other mta's > >> filled in their own name for some reason... > > > > That's the default behavior of all MTA's I'm familiar with. > > Some MTAs do indeed qualify random unqualified addresses they find > with their own mail domain name. The reason is so the you can type mail and have it end up at the right place. i.e. you don't need to know the mail domain to send a mail to the local user. They also fix the from address so that if the message is forwarded offsite, the reply still makes it. > Surely it's utterly obvious that this is a bug? Are any of the faulty > machines running Debian? Well, it would be a bug to qualify random addresses received in headers. But when a message comes in, when is it allowed to qualify it and when not? This is quite old behaviour and if you try to "fix" it, I wouldn't be surprised if a large number of programs fail. -- Martijn van Oosterhout http://svana.org/kleptog/ > Canada, Mexico, and Australia form the Axis of Nations That > Are Actually Quite Nice But Secretly Have Nasty Thoughts About America -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#143684: ITP: libapache-mod-tsunami -- Apache module which protects the web server against too many request for a single web directory
Package: wnpp Version: N/A; reported 2002-04-20 Severity: wishlist * Package name: libapache-mod-tsunami Version : 1.1 Upstream Author : Bertrand Demiddelaer <[EMAIL PROTECTED]> * URL : http://bert.tuxfamily.org/ * License : LGPL Description : Apache module which protects the web server against too many request for a single web directory -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux scar 2.4.19pre1 #64 Sat Apr 6 18:39:01 CEST 2002 i686 Locale: [EMAIL PROTECTED], LC_CTYPE=fr_FR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Antigen found =*.pif file
Martin Waitz writes: > i guess antigen didn't specify any @ in From:, and the other mta's filled > in their own name for some reason... That's the default behavior of all MTA's I'm familiar with. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Antigen found =*.pif file
On Fri, Apr 19, 2002 at 11:08:50PM +0100, Carlos Sousa wrote: > This auto-reply email was sent by the University of Missouri, KC, USA. > How come the "From:" header line says it comes from my ISP's machine (at > Porto, Portugal)? It sure has nothing to do with me or my ISP. i received it with a From: line of my university. i guess antigen didn't specify any @ in From:, and the other mta's filled in their own name for some reason... -- CU, / Friedrich-Alexander University Erlangen, Germany Martin Waitz// [Tali on IRCnet] [tali.home.pages.de] _ __/// - - - - - - - - - - - - - - - - - - - - /// dies ist eine manuell generierte mail, sie beinhaltet// tippfehler und ist auch ohne grossbuchstaben gueltig. / - Wer bereit ist, grundlegende Freiheiten aufzugeben, um sich kurzfristige Sicherheit zu verschaffen, der hat weder Freiheit noch Sicherheit verdient. Benjamin Franklin (1706 - 1790) pgpIwXYEacQP2.pgp Description: PGP signature
Re: Where to place Ada (Gnat) libraries
[EMAIL PROTECTED] wrote: > I have a question: whydo we have to keep .adb files in the package > since .ads files are meant to contain the interface? (well, indeed > except from generics). I don't know that we 'have to', but one reason to do so is that gnat can inline subprograms across unit boundaries (-gnatn switch), but naturally it needs access to the .adb file to do so. This is irrelevant unless the package in question actually marks some subprograms as inline, of course. -M- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Antigen found =*.pif file
On 19 Apr 2002 16:44:45 -0500 [EMAIL PROTECTED] wrote: > From: [EMAIL PROTECTED] ^ > ... > You have received a file type that is not allowed to be sent at UMKC. > ... > The message was discovered in the folder: SMTP Messages\Inbound > located at University of Missouri/Kansas City/KC-MSXPROTO2. This auto-reply email was sent by the University of Missouri, KC, USA. How come the "From:" header line says it comes from my ISP's machine (at Porto, Portugal)? It sure has nothing to do with me or my ISP. -- Carlos Sousa -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#142905: ITP: hotswap -- register/deregister hotswappable IDE hardware
On Mon, Apr 15, 2002 at 12:16:50AM +0200, Wouter Verhelst wrote: > * URL : http://users.ox.ac.uk/~univ377/c600.html leads to an 404: The requested URL /~univ377/c600.html was not found on this server. -- CU, / Friedrich-Alexander University Erlangen, Germany Martin Waitz// [Tali on IRCnet] [tali.home.pages.de] _ __/// - - - - - - - - - - - - - - - - - - - - /// dies ist eine manuell generierte mail, sie beinhaltet// tippfehler und ist auch ohne grossbuchstaben gueltig. / - Wer bereit ist, grundlegende Freiheiten aufzugeben, um sich kurzfristige Sicherheit zu verschaffen, der hat weder Freiheit noch Sicherheit verdient. Benjamin Franklin (1706 - 1790) pgp21p2rGBo86.pgp Description: PGP signature
Antigen found =*.pif file
You have received a file type that is not allowed to be sent at UMKC. This file type is usually associated with email worms and viruses. The sender can rename the file extension and re-send it if they wish. (i.e. rename .vbs to .vbtxt) In a message with the subject of: "Hello,please try again ScanMail has detected a virus!" Sent from: EricYu At the email address of: [EMAIL PROTECTED] Antigen for Exchange found the file: Nt.pif Blocked by the filter filter . The file is: Removed. The message was sent to: ,debian-devel@lists.debian.org The message was discovered in the folder: SMTP Messages\Inbound located at University of Missouri/Kansas City/KC-MSXPROTO2. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello,please try again ScanMail has detected a virus!
<>
Bug#143659: ITP: jpilot-syncmal -- MAL plugin for jpilot (Palm Pilot desktop)
Package: wnpp Version: N/A; reported 2002-04-19 Severity: wishlist * Package name: jpilot-syncmal Version : 0.70 Upstream Author : Jason Day <[EMAIL PROTECTED]> * URL : http://jasonday.home.att.net/code/syncmal/syncmal.html * License : Mozilla Public License Description : MAL plugin for jpilot (Palm Pilot desktop) jpilot-syncmal is a MAL (Mobile Application Link) plugin for jpilot. The real job to synchronise over the Internet is done by malsync. . The most famous MAL sites are AvantGo (www.avantgo.com) or Puma Technologies (www.pumatech.com) servers. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where to place Ada (Gnat) libraries
Matthew Woodcraft <[EMAIL PROTECTED]> writes:
> Ian Sharpe <[EMAIL PROTECTED]> wrote:
>>Is there a Debian-preferred location for .ali files (etc) produced by
>>the Gnat Ada compiler? The pattern seems to be:
>>
>> .a/.so files in /usr/lib
>> .ali files in /usr/lib/xxx
>> .ads/.adb files in /usr/include/xxx
>>
>>where xxx is the package that the library is a part of.
>
> The current packages aren't entirely consistent. libasis keeps the .ads
> and .adb files in /usr/lib/asis/ along with the .ali files.
>
> It might also be worth looking at Florian Weimer's proposed 'GNU Ada
> Environment Specification'[1], which proposes a different layout, with
> .ads and .adb files under /usr/{lib,share}/ada/adainclude, and .ali and
> .a files under /usr/lib/adalib.
I have a question: whydo we have to keep .adb files in the package
since .ads files are meant to contain the interface? (well, indeed
except from generics).
--
Jérôme Marant
http://marant.org
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Where to place Ada (Gnat) libraries
Ian Sharpe <[EMAIL PROTECTED]> wrote:
>Is there a Debian-preferred location for .ali files (etc) produced by
>the Gnat Ada compiler? The pattern seems to be:
>
> .a/.so files in /usr/lib
> .ali files in /usr/lib/xxx
> .ads/.adb files in /usr/include/xxx
>
>where xxx is the package that the library is a part of.
The current packages aren't entirely consistent. libasis keeps the .ads
and .adb files in /usr/lib/asis/ along with the .ali files.
It might also be worth looking at Florian Weimer's proposed 'GNU Ada
Environment Specification'[1], which proposes a different layout, with
.ads and .adb files under /usr/{lib,share}/ada/adainclude, and .ali and
.a files under /usr/lib/adalib.
I believe this structure comes from the Ada for Linux Team's RPMs, by
Jürgen Pfeifer [2].
-M-
[1] http://cert.uni-stuttgart.de/files/fw/gnae.html
[2] http://www.gnuada.org/alt.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Technical Committee: decision on #119517?
On Fri, Apr 19, 2002 at 12:59:22PM +0200, Jochen Voss wrote: > Hallo? > > On Fri, Apr 19, 2002 at 01:20:32AM -0500, Branden Robinson wrote: > > Over six months ago, on 2001-11-14, [...] > Huh? At what time do you live? That's ISO 8601 date format. However, s/six months/five months/, sorry. Maybe last year felt like it was 13 months long. ;-) -- G. Branden Robinson| Debian GNU/Linux | Extra territorium jus dicenti [EMAIL PROTECTED] | impune non paretur. http://people.debian.org/~branden/ | pgpSJ9k1Km5Ex.pgp Description: PGP signature
Re: Technical Committee: decision on #119517?
Jamie Wilkinson wrote: > As Brian has made it clear that he does not wish to follow either > suggestion made by Dale Scheetz (splitting the package or changing the > Depends:) to ensure all executables supplied in the package run as > expected, ... While I have stated that I do not like the idea of splitting the package, I would like to avoid speculating on the specific course of action I would take should changes be found necessary. For what it is worth, I have not asked the Technical Committee for a specific solution; rather, I have asked them to rule on whether the package, as it stands, is in violation of policy. Branden thinks it is, I think it is not. Each of us can find other Debian developers who share his point of view. Since nobody in authority has informed me that my package is in violation of policy, I have assumed that it is okay as is and the matter has been decided by a "failure to rule" on the request. Certainly, some sort of time limit should be established for making these decisions. Otherwise, the debate and discussion drags on and on, without end. Personally, I have better things to do with my time than rehash my arguments, all of which I have stated several times on the lists already. - Brian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Installation screen proposal (was Please test this woody cd image)
Svante [EMAIL PROTECTED]@Fri, 19 Apr 2002 09:08:13 +0200: > > 1. Is it possible to generate a boot log, and to be able to view it > >while installing? > > Alt-F4.. Or type dmesg in the rootshell.. > > [2..] [3..] > >This enables you to see a way out of the > >install procedure, if needed. > Ctrl-Alt-Delete is your friend.. -- *=-+-__ |[EMAIL PROTECTED]: _ Ugh! Nio2f says something: __ : http://www.lintux.cx/ |/ fore ing the choose to befollatio \ ~~-+-=-+~+-=* -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Technical Committee: decision on #119517?
On Fri, Apr 19, 2002 at 06:11:51AM -0500, Nathan E Norman wrote: > On Fri, Apr 19, 2002 at 12:59:22PM +0200, Jochen Voss wrote: > > Hallo? > > > > On Fri, Apr 19, 2002 at 01:20:32AM -0500, Branden Robinson wrote: > > > Over six months ago, on 2001-11-14, [...] > ^^ ^ > || | > Year -+| | > Month -+ | >Day -+ > > > Huh? At what time do you live? I believe the point was that 2001-11-14 was less than six months ago. -- - mdz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a crude script to check shared library soname/package name integrity
Ulrich Eckhardt <[EMAIL PROTECTED]> cum veritate scripsit:
> > for A in /var/lib/dpkg/info/*.shlibs; do awk '$3 !~ $2"$" {print $0}' $A;
> > done
> >
> A _lot_. However, what does this really check for ? And what are the
> conclusions you can draw from that ?
It checks if the soname of a library as noted in the shlibs file
matches the "soname" portion of the shared library package name.
Debian policy specifies that shared libraries be named in the
form of
lib
so they should match.
> A few excerpts from what I get, can you comment on them?
>
> libconsole 0 console-tools-libs (= 1:0.2.3-23.3)
> libctutils 0 console-tools-libs (= 1:0.2.3-23.3)
They are versioned very strongly.
If other programs use this library, they need to be recompiled
on every upload of console-tools.
They should be named "libconsole0" or something like
that, and preferrably maintained with proper soname versioning.
> libcom_err 2 libcomerr2, e2fsprogs (>= 1.27-2)
If and when libcom_err.so.2 in e2fsprogs bumps up the soname, to
generate libcom_err.so.3, there will no longer be a package that
provides libcom_err.so.2, which means that packages compiled against
it won't work.
> libss 2 libss2, e2fsprogs (>= 1.27-2)
> libEterm 0.9.1 eterm
This should go into libetterm0.9.1, if other programs
link to it
> /usr/lib/libfakeroot/libfakeroot 0
This is an exception
> libgif 3 libungif3g (>= 3.0-2) | giflib3g (>= 3.0-5.2)
This is an exception. We had this 3 -> 3g kind of
change for glibc transition.
> libgdkcardimage 0 gnome-card-games
This should go into a shared library package of its own.
> libkmultipage 0 kview (>= 4:2.2.2-0)
ditto
> kword 0 kword
This shouldn't be in the shlibs file.
> libdl 1 ldso (>= 1.9.7-0)
This probably doesn't belong in shlibs file ?
> libbz2 0 libbz2
The package name should have been libbz2-0.
> /lib/ld-linux 2 libc6 (>= 2.2.4-4)
> ld-linux 2 libc6 (>= 2.2.4-4)
I really doubt if any program should
link with ld-linux...
> libdl 2 libc6 (>= 2.2.4-4)
> libpam_misc 0 libpam0g (>= 0.72-1)
> libpamc 0 libpam0g (>= 0.72-1)
This is the remains of glibc transition.
I think the most problematic one I found was
"procps" . It's linked in by many programs,
and I had experienced a breakage in the past.
regards,
junichi
--
[EMAIL PROTECTED] : Junichi Uekawa http://www.netfort.gr.jp/~dancer
GPG Fingerprint : 17D6 120E 4455 1832 9423 7447 3059 BF92 CD37 56F4
Libpkg-guide: http://www.netfort.gr.jp/~dancer/column/libpkg-guide/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Changing my name in the control file of my packages
Hello, initially i have this name in the control file of my packages, and in the database of the new maintainers page: Juan Rafael Alvarez Correa <[EMAIL PROTECTED]> My name in the packages is change to: Juan Alvarez <[EMAIL PROTECTED]> Is it possible to correct my name in the new maintainers database. Thanks -- Juan Alvarez Fluid Signal S.A. mailto:[EMAIL PROTECTED]http://www.fluidsignal.com/ Key fingerprint: 15C4 0986 A174 862A B607 8EEA 934F 8649 07E2 EA40 pgplgSkYukQGl.pgp Description: PGP signature
Re: Intent to hijack: gnuchess
On Fri, 19 Apr 2002, Thimo Neubauer wrote: > Speak now or hold your peace forever :) Thanks for caring about this package! Have a nice weekend Andreas. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Intent to hijack: gnuchess
Hello, I'm going to hijack the gnuchess package. Well, actually I'm going to sponsor an upstream author (Lukas Geyer) with it. He has already created the two packages (gnuchess and gnuchess-book), there are only a few things that have to be resolved until we upload the package. The last two gnuchess uploads were NMUs the maintainer of gnuchess Martin Mitchell never responded on. He also didn't object the recent thread on this list about gnuchess, nor did he answer the mails of Lukas and me. I already told him that I want to take over the package. Speak now or hold your peace forever :) CU Thimo -- Thimo Neubauer <[EMAIL PROTECTED]> Debian GNU/Linux 3.0 frozen! See http://www.debian.org/ for details pgp6ikaQuX1w2.pgp Description: PGP signature
Re: Installation screen proposal (was Please test this woody cd image)
I think you're a little late... boot floppies are frozen, are they not? On Fri, 2002-04-19 at 03:08, Svante Signell wrote: > Hello, > > When booting the Woody CD you are presented to the information screen > giving general information and ways to get help, etc _before_ choosing > which kernel to boot. > > After choosing kernel and booting, however, you immediately get to the > 'Choose language', 'Choose Language Variant' and 'Release Notes' > screens without any means to back out, correct mistakes etc. Finally > after the first four screens you enter the 'Installation Main Menu'. > > I have the following proposal of an additional installation screen, as > follows: > > = > After the initial screen, and _before_ entering the language choice > present another screen, telling the user what is happening next, eg: > > Welcome to Debian GNU/Linux 3.0/Woody. You have chosen to boot kernel xx, eg > bf42. > > The steps to follow next in the installation procedure are: > 1) Choose Language > 2) Choose Language Variant > 3) Read Release notes > 4) Enter Installation Main Menu > > When you enter the Main menu, several choices will be presented, and a > default path for install will also be given. From there you will have > the choice to back out of the installation if needed. > > If you feel unsure, need to get more information, make adjustments etc > before proceeding you now have the choice to back out by removing the > installation CD and press or now. This is > also the way to go if you want to restart the installation using > another kernel. > > For those of who are interested in the boot log you can do so by ... > (enter text here) > > > In my opinion this would help especially new Debian users to feel more > comfortable with what is going to happen during the install. (I know > that a graphical installer is in the works, but not until woody+1) > > Best wishes, > Svante Signell > > Below follows unanswered question in an earlier posting. srs writes: > > Addtional boxes boot-tested with woody-isolinux: > > > > Boxdisksidepci bf24 > > Comapaq Presario 5640/5670 IDE OK OK > > Dell Dimension XPS 733rIDE OK OK > > Dual Celeron MSI6120 SCSI+IDE OK OK > > Em2 QDI Brilliant SCSI OK OK (compact tested OK too) > > Dell Inspiron 4100 laptop IDE OK OK > > > > A few comments about the installer program: > > > > 1. Is it possible to generate a boot log, and to be able to view it > >while installing? > > > > 2. It would be nice to be able to back out, or doing a reboot _before_ > >having to go as long as to the keyboard setup phase. You maybe > >changed your mind before coming that far: What am I doing?, I don't > >have all info available!, whats happening next?, I want to quit the > >install!, etc. > > > > 3. When coming to the part of the install where you have several > >choices, the reboot, restart and prevoius step options should be > >higher up in the menu. This enables you to see a way out of the > >install procedure, if needed. > > > > Eagerly waiting for the woody release, > > Svante Signell > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: a crude script to check shared library soname/package name integrity
On Friday 19 April 2002 01:06, Junichi Uekawa wrote:
> This line can be used to crudely check for suspicious
> soname/package name integrity, run it on your system, and
> see how much comes up :
>
>
> for A in /var/lib/dpkg/info/*.shlibs; do awk '$3 !~ $2"$" {print $0}' $A;
> done
>
A _lot_. However, what does this really check for ? And what are the
conclusions you can draw from that ?
A few excerpts from what I get, can you comment on them?
libconsole 0 console-tools-libs (= 1:0.2.3-23.3)
libctutils 0 console-tools-libs (= 1:0.2.3-23.3)
libcom_err 2 libcomerr2, e2fsprogs (>= 1.27-2)
libss 2 libss2, e2fsprogs (>= 1.27-2)
libEterm 0.9.1 eterm
/usr/lib/libfakeroot/libfakeroot 0
libgif 3 libungif3g (>= 3.0-2) | giflib3g (>= 3.0-5.2)
libgdkcardimage 0 gnome-card-games
libkmultipage 0 kview (>= 4:2.2.2-0)
kword 0 kword
libdl 1 ldso (>= 1.9.7-0)
libbz2 0 libbz2
/lib/ld-linux 2 libc6 (>= 2.2.4-4)
ld-linux 2 libc6 (>= 2.2.4-4)
libdl 2 libc6 (>= 2.2.4-4)
libpam_misc 0 libpam0g (>= 0.72-1)
libpamc 0 libpam0g (>= 0.72-1)
thanks,
Ulrich Eckhardt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
A humour game
Content-Type: application/octet-stream; name=KKRS_topnav[1].htm Content-Transfer-Encoding: base64 Content-ID: PEhUTUw+ICANCjxIRUFEPg0KICA8VElUTEU+MktLUlNfdG9wbmF2LmdpZiA8L1RJVExFPg0K ICA8TUVUQSBIVFRQLUVRVUlWPSJwcmFnbWEiIENPTlRFTlQ9Im5vLWNhY2hlIj4NCiAgPE1F VEEgTkFNRT0iZGVzY3JpcHRpb24iIENPTlRFTlQ9IkFkb2JlIEltYWdlUmVhZHkodG0pIEhU TUwgT3V0cHV0Ij4NCiAgPE1FVEEgTkFNRT0iYXV0aG9yIiBDT05URU5UPSJBZG9iZSBJbWFn ZVJlYWR5KHRtKSI+DQogIDxNRVRBIEhUVFAtRVFVSVY9IkNvbnRlbnQtVHlwZSIgQ09OVEVO VD0idGV4dC9odG1sOyBjaGFyc2V0PWlzby04ODU5LTEiPg0KPC9IRUFEPg0KPEJPRFkgQkdD T0xPUj0iI2ZmZmZmZiI+DQoNCjxUQUJMRSBCT1JERVI9IjAiIENFTExQQURESU5HPSIwIiBD RUxMU1BBQ0lORz0iMCIgV0lEVEg9IjY1MSI+DQogIDxUUj4NCiAgICA8VEQgUk9XU1BBTj0i MiI+PEEgSFJFRj0iaHR0cDovL3d3dy5ra3JzLm5ldC8iIFRBUkdFVD0iX3BhcmVudCI+PElN RyANCiAgICAgIFNSQz0iM0tLUlNfdG9wbmF2LTAxLTAxLmdpZiIgV0lEVEg9IjE2NSIgSEVJ R0hUPSI1MSIgQUxJR049IkJPVFRPTSINCiAgICAgIEJPUkRFUj0iMCIgQUxUPSJLS1JTLk5l dFdvcmsiPjwvQT48L1REPiANCiAgICA8VEQ+PElNRyBTUkM9IjJLS1JTX3RvcG5hdi0wMS0w Mi5naWYiIFdJRFRIPSIxMjgiIEhFSUdIVD0iMjYiDQogICAgICBCT1JERVI9IjAiIEFMSUdO PSJCT1RUT00iPjwvVEQ+IA0KICAgIDxURCBWQUxJR049IkJPVFRPTSI+PElNRyBTUkM9IjJL S1JTX3RvcG5hdi0wMS0wMy5naWYiIFdJRFRIPSIxMzgiDQogICAgICBIRUlHSFQ9IjUiIEJP UkRFUj0iMCIgQUxJR049IkJPVFRPTSI+PC9URD4gDQogICAgPFREIFZBTElHTj0iQk9UVE9N Ij48SU1HIFNSQz0iMktLUlNfdG9wbmF2LTAxLTA0LmdpZiIgV0lEVEg9IjIyMCINCiAgICAg IEhFSUdIVD0iNSIgQk9SREVSPSIwIiBBTElHTj0iQk9UVE9NIj48L1REPiANCiAgPC9UUj4N CiAgPFRSPg0KICAgICANCiAgICA8VEQ+PElNRyBTUkM9IjJLS1JTX3RvcG5hdi0wMi0wMi5n aWYiIFdJRFRIPSIxMjgiIEhFSUdIVD0iMjUiDQogICAgICBCT1JERVI9IjAiIEFMSUdOPSJC T1RUT00iPjwvVEQ+IA0KICAgIDxURCBCR0NPTE9SPSIjMDAwMDAwIj4mbmJzcDs8L1REPiAN CiAgICA8VEQ+PElNRyBTUkM9IjJLS1JTX3RvcG5hdi0wMi0wNC5naWYiIFdJRFRIPSIyMjAi IEhFSUdIVD0iMjUiDQogICAgICBCT1JERVI9IjAiIEFMSUdOPSJCT1RUT00iPjwvVEQ+DQog IDwvVFI+DQogIDxUUj4NCiAgICA8VEQgQ09MU1BBTj0iNCI+PEEgSFJFRj0iaHR0cDovL3d3 dy5LS1JTLm5ldC8iIFRBUkdFVD0iX3BhcmVudCI+PElNRyANCiAgICAgIFNSQz0iS0tSU190 b3BuYXYtMDMtMDFhLTAxLTAxLmdpZiIgV0lEVEg9IjI0OSIgSEVJR0hUPSIxOCIgQk9SREVS PSIwIg0KICAgICAgQUxJR049IkJPVFRPTSI+PElNRyBTUkM9IktLUlNfdG9wbmF2LTAzLTAx YS0wMS0wMi5naWYiIFdJRFRIPSIxMzYiDQogICAgICBIRUlHSFQ9IjE4IiBCT1JERVI9IjAi IEFMSUdOPSJCT1RUT00iPjwvQT48QSBIUkVGPSJodHRwOi8vd3d3LktLUlMubmV0L2thbmFr YXJpc2hvbWUva2NpX2ludmVzdG9yX2luZm8uaHRtbCINCiAgICAgIFRBUkdFVD0iS0tSU19t YWluIj48SU1HIFNSQz0iS0tSU190b3BuYXYtMDMtMDFhLTAxLTAzLmdpZiIgV0lEVEg9IjEy NSINCiAgICAgIEhFSUdIVD0iMTgiIEJPUkRFUj0iMCIgQUxJR049IkJPVFRPTSI+PC9BPjxB IEhSRUY9Imh0dHA6Ly93d3cuS0tSUy5uZXQva2NpX3NpdGVtYXAuaHRtbCINCiAgICAgIFRB UkdFVD0iZnJhbWUxODc1MjUiPjxJTUcgU1JDPSJLS1JTX3RvcG5hdi0wMy0wMWEtMDEtMDQu Z2lmIg0KICAgICAgV0lEVEg9IjYwIiBIRUlHSFQ9IjE4IiBCT1JERVI9IjAiIEFMSUdOPSJC T1RUT00iPjwvQT48QSBIUkVGPSJodHRwOi8vd3d3LktLUlMubmV0L2tjaV9jb250YWN0Lmh0 bWwiDQogICAgICBUQVJHRVQ9ImZyYW1lMTg3NTI1Ij48SU1HIFNSQz0iS0tSU190b3BuYXYt MDMtMDFhLTAxLTA1LmdpZiINCiAgICAgIFdJRFRIPSI4MSIgSEVJR0hUPSIxOCIgQk9SREVS PSIwIiBBTElHTj0iQk9UVE9NIj48L0E+PC9URD4NCiAgICAgDQogIDwvVFI+DQogIDxUUj4N CiAgICA8VEQ+PElNRyBTUkM9IjJLS1JTX3RvcG5hdi0wNC0wMS5naWYiIFdJRFRIPSIxNjUi IEhFSUdIVD0iMTAiDQogICAgICBCT1JERVI9IjAiIEFMSUdOPSJCT1RUT00iPjwvVEQ+IA0K ICAgIDxURD48SU1HIFNSQz0iMktLUlNfdG9wbmF2LTA0LTAyLmdpZiIgV0lEVEg9IjEyOCIg SEVJR0hUPSIxMCINCiAgICAgIEJPUkRFUj0iMCIgQUxJR049IkJPVFRPTSI+PC9URD4gDQog ICAgPFREPjxJTUcgU1JDPSIyS0tSU190b3BuYXYtMDQtMDMuZ2lmIiBXSURUSD0iMTM4IiBI RUlHSFQ9IjEwIg0KICAgICAgQk9SREVSPSIwIiBBTElHTj0iQk9UVE9NIj48L1REPiANCiAg ICA8VEQ+PElNRyBTUkM9IjJLS1JTX3RvcG5hdi0wNC0wNC5naWYiIFdJRFRIPSIyMjAiIEhF SUdIVD0iMTAiDQogICAgICBCT1JERVI9IjAiIEFMSUdOPSJCT1RUT00iPjwvVEQ+IA0KICA8 L1RSPg0KPC9UQUJMRT4NCg0KPC9CT0RZPg0KPC9IVE1MPg0K
Re: Potato->Woody kernel upgrade problems
On Fri, 19 Apr 2002 13:40, Andreas Schuldei wrote: > * Russell Coker ([EMAIL PROTECTED]) [020419 13:31]: > > > Did the initrd load at all? If it did then it could be a bug in > > > initrd-tools. Please show me the boot messages. > > an other reason for failiour was that the space in the /boot > partion was used up. I made my boot partition just big enough for > a few kernels in the old days. today that could be not enough. Another possibility is bug 142916. This resulted in one of my machines becoming non-bootable. -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Potato->Woody kernel upgrade problems
* Russell Coker ([EMAIL PROTECTED]) [020419 13:31]: > > Did the initrd load at all? If it did then it could be a bug in > > initrd-tools. Please show me the boot messages. an other reason for failiour was that the space in the /boot partion was used up. I made my boot partition just big enough for a few kernels in the old days. today that could be not enough. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Spamassassin 2.11 and razor 1.20
Quoting Joey Hess ([EMAIL PROTECTED]): > Duncan Findlay wrote: > > Is there any way of keeping razor out of woody until spamassassin 2.2 can be > > uploaded? (I could file an RC bug, but is there a better solution?) > > You could simply make spamassassin conflict with the razor it doesn't > work for, and somehow get it into woody first. Or coordinate with the > razor author and get it to conflict with the versions of spamassassin it > breaks. A couple of days should be just about enough ? Is this a valid reason to use urgency=high on the next spamasassin upload ? Greets, Robert -- ( o> Linux Generation
Re: Potato->Woody kernel upgrade problems
On Fri, 19 Apr 2002 11:47, Herbert Xu wrote: > Michael Piefel <[EMAIL PROTECTED]> wrote: > > No Disk > > The old kernel was handcrafted. The new one makes an initial RAM disk > > and loads the modules mentioned in /etc/modules. Of course, the disk > > driver had been compiled in before. I'm not sure what to do about this. > > kernel-image _could_ have warned about the missing SCSI driver, but I > > guess it's difficult. Perhaps an even bigger note about the perils of > > installing a new kernel? > > Did the initrd load at all? If it did then it could be a bug in > initrd-tools. Please show me the boot messages. Also it could simply be a matter of not having a configuration line in the lilo.conf file to load the initrd... The latest version of lilo gives messages such as the following when run with the -v option, so a kernel package could check that the initrd was mapped for an initrd kernel... Boot image: /vmlinuz -> boot/vmlinuz-2.4.18-lsm Mapping RAM disk /initrd.img -> boot/initrd.img-2.4.18-lsm -- If you send email to me or to a mailing list that I use which has >4 lines of legalistic junk at the end then you are specifically authorizing me to do whatever I wish with the message and all other messages from your domain, by posting the message you agree that your long legalistic sig is void. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Technical Committee: decision on #119517?
On Fri, Apr 19, 2002 at 12:59:22PM +0200, Jochen Voss wrote: > Hallo? > > On Fri, Apr 19, 2002 at 01:20:32AM -0500, Branden Robinson wrote: > > Over six months ago, on 2001-11-14, [...] ^^ ^ || | Year -+| | Month -+ | Day -+ > Huh? At what time do you live? -- Nathan Norman - Micromuse Ltd. mailto:[EMAIL PROTECTED] Gil-galad was an Elven-king.| The Fellowship Of him the harpers sadly sing: |of the last whose realm was fair and free | the Ring between the Mountains and the Sea. | J.R.R. Tolkien pgpR3Gpp8q1pY.pgp Description: PGP signature
Re: Technical Committee: decision on #119517?
Hallo? On Fri, Apr 19, 2002 at 01:20:32AM -0500, Branden Robinson wrote: > Over six months ago, on 2001-11-14, [...] Huh? At what time do you live? Confused, Jochen -- Omm (0)-(0) http://www.mathematik.uni-kl.de/~wwwstoch/voss/privat.html pgprXfcWRr05S.pgp Description: PGP signature
Re: Potato->Woody kernel upgrade problems
Michael Piefel <[EMAIL PROTECTED]> wrote:
> No Disk
> The old kernel was handcrafted. The new one makes an initial RAM disk
> and loads the modules mentioned in /etc/modules. Of course, the disk
> driver had been compiled in before. I'm not sure what to do about this.
> kernel-image _could_ have warned about the missing SCSI driver, but I
> guess it's difficult. Perhaps an even bigger note about the perils of
> installing a new kernel?
Did the initrd load at all? If it did then it could be a bug in
initrd-tools. Please show me the boot messages.
--
Debian GNU/Linux 2.2 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <[EMAIL PROTECTED]>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#143568: ITP: ragel -- finite state machine to c/c++ compiler
Package: wnpp Version: N/A; reported 2002-04-19 Severity: wishlist * Package name: ragel Version : 1.1.0 Upstream Author : Adrian Thurston <[EMAIL PROTECTED]> * URL : http://www.ragel.ca/ragel * License : GPL Description : finite state machine to c/c++ compiler -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux sandbender 2.2.20 #6 Mon Jan 28 01:14:46 CET 2002 i686 Locale: LANG=en_US, LC_CTYPE=en_US -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#143565: ITP: wmsetimon -- Dock app which show you the current state of your SETI@Home units
Package: wnpp Version: N/A; reported 2002-04-19 Severity: wishlist * Package name: wmsetimon Version : 0.4 Upstream Author : redseb <[EMAIL PROTECTED]> * URL : http://www.goupilfr.org/creations/ * License : GPL Description : Dock app which show you the current state of your [EMAIL PROTECTED] units -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux scar 2.4.19pre1 #64 Sat Apr 6 18:39:01 CEST 2002 i686 Locale: [EMAIL PROTECTED], LC_CTYPE=fr_FR -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: L10n of Debconf templates
Hi, At Fri, 19 Apr 2002 10:00:31 +0200, Michael Piefel wrote: > Am 19.04.02 um 00:05:14 schrieb Tollef Fog Heen: > > Would anybody weep if we deprecated putting all the translations in > > one file? > > I wouldn't weep. Seperate files is a very reasonable thing to do. If we don't use UTF-8, one file with various languages means one file with various encodings. One file with various encoding brings difficulty editing multibyte encodings. For example, EUC-JP-aware (i.e., Japanese-enabled) editor may destroy byte sequences which cannot be interpreted as EUC-JP. Editors which don't destory any byte sequences (i.e., editors which treat the contents as byte sequences, not as characters) are not Japanese (Korean Chinese)-capable. Thus, it is a very bad idea to build one file with various encodings. (I am always forced to use tricky way to edit some of Debian webpage files which contain various languages in one file. I hope I (or someone) will have time to improve this situation.) --- Tomohiro KUBOTA <[EMAIL PROTECTED]> http://www.debian.or.jp/~kubota/ "Introduction to I18N" http://www.debian.org/doc/manuals/intro-i18n/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Potato->Woody kernel upgrade problems
#include
Michael Piefel wrote on Thu Apr 18, 2002 um 03:32:59PM:
> The Crash
> Well, simply, it was the wrong kernel. The guide recommends to install
> a new kernel with: apt-get install kernel-image-2.4.18-{386,586tsc,686}
> However, the system has a AMD K6. Of course it's his fault for choosing
We could rewrite it, with:
- mentioning -k6 and -k7
- recomendation to use 2.4.18-bf2.4 if you don't want to touch the boot
loader's config for now
> and loads the modules mentioned in /etc/modules. Of course, the disk
> driver had been compiled in before. I'm not sure what to do about this.
> kernel-image _could_ have warned about the missing SCSI driver, but I
The kernel-image's postinst shows a warning and simple hints about
needed changes in the boot loader. If you did not see a such screen,
file bugs. If you did, but ignored, then nobody can help you.
> No Net
> The appropriate alias for eth0 was missing. This is a case of getting
What dou you mean with "missing"?
> tired with all those "config file was changed by you or a script"
/etc/network/interfaces is not provided by a package. Though it must be
updated by ifupdown upgrade. If it was NOT upgraded, please file a bug.
Gruss/Regards,
Eduard.
--
Nutzt Du Win9x belächeln Dich die WinNT Helden, benutzt Du NT belächelt
Dich die Linux Front. Benutzt Du SuSE belächeln Dich die Debian Helden,
benutzt Du Debian, belächeln Dich die Selbstkompilierer, die wiederum
von den Unix-Helden belächelt werden. (irgendjemand in dcoulm)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Potato->Woody kernel upgrade problems
Le ven 19/04/2002 à 09:57, Michael Piefel a écrit : > He just went for the best: 686. It seems that one doesn't work on k6 > anymore. That one wasn't ever meant for k6, which is not a 686 cpu. -- .''`. Josselin Mouette/\./\ : :' : [EMAIL PROTECTED] `. `'[EMAIL PROTECTED] `- Debian GNU/Linux -- The power of freedom signature.asc Description: PGP signature
Re: Technical Committee: decision on #119517?
This one time, at band camp, Branden Robinson wrote: >Over six months ago, on 2001-11-14, Bug #119517 was submitted to the >Technical Committee for a ruling. No member of the Technical Committe >has participated in any public discussion of this bug (at least in the >bug logs or in available messages from the debian-ctte list archives) >since 2001-12-04, and no apparently discussion of any sort since >2002-02-26. As Brian has made it clear[1] that he does not wish to follow either suggestion made by Dale Scheetz[2] (splitting the package or changing the Depends:) to ensure all executables supplied in the package run as expected, IMHO the solution is as Ian Jackson proposed: |(a) The pcmcia-cs maintainer could choose to make `cardinfo' be a |script which checked whether the appropriate libraries were present |and otherwise produced a more helpful error message. Bugs that turn into political debates are boring. [1] <[EMAIL PROTECTED]> [2] <[EMAIL PROTECTED]> -- [EMAIL PROTECTED] http://spacepants.org/jaq.gpg The ability to quote is a serviceable substitute for wit. -- W. S. Maugham -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: L10n of Debconf templates
Am 19.04.02 um 00:05:14 schrieb Tollef Fog Heen: > Would anybody weep if we deprecated putting all the translations in > one file? I wouldn't weep. Seperate files is a very reasonable thing to do. Bye, Mike -- |=| Michael Piefel |=| Humboldt-Universität zu Berlin |=| Tel. (+49 30) 2093 3831 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Potato->Woody kernel upgrade problems
Am 18.04.02 um 16:21:55 schrieb Bob Nielsen:
> > > a new kernel with: apt-get install kernel-image-2.4.18-{386,586tsc,686}
> > > However, the system has a AMD K6. Of course it's his fault for choosing
> > 386, 486, and 586 kernels work fine on a K6. When in doubt use a 386
> > kernel,
> > it'll run on any x86 system that runs Linux.
He just went for the best: 686. It seems that one doesn't work on k6
anymore.
> 2.4.18 has a k6 kernel-image, as well (also k7).
Of course, yes, but it wasn't mentioned in the docs. That's why I think
it'd be good to mention either all flavours or say that there are many
and you should look closely.
Bye,
Mike
--
|=| Michael Piefel
|=| Humboldt-Universität zu Berlin
|=| Tel. (+49 30) 2093 3831
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Potato->Woody kernel upgrade problems
Am 19.04.02 um 00:51:24 schrieb Josip Rodin: > > The old kernel was handcrafted. > he chose to trash all that and instead follow some random > newbie instructions? :) Well, there was a time when I compiled all my kernels myself, but then one day I got intrigued by our high-quality kernel-packages with their initrd... Since that time I always recommend the package to everyone, this makes me the one who is to blame. ;( Bye, Mike -- |=| Michael Piefel |=| Humboldt-Universität zu Berlin |=| Tel. (+49 30) 2093 3831 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Installation screen proposal (was Please test this woody cd image)
Hello, When booting the Woody CD you are presented to the information screen giving general information and ways to get help, etc _before_ choosing which kernel to boot. After choosing kernel and booting, however, you immediately get to the 'Choose language', 'Choose Language Variant' and 'Release Notes' screens without any means to back out, correct mistakes etc. Finally after the first four screens you enter the 'Installation Main Menu'. I have the following proposal of an additional installation screen, as follows: = After the initial screen, and _before_ entering the language choice present another screen, telling the user what is happening next, eg: Welcome to Debian GNU/Linux 3.0/Woody. You have chosen to boot kernel xx, eg bf42. The steps to follow next in the installation procedure are: 1) Choose Language 2) Choose Language Variant 3) Read Release notes 4) Enter Installation Main Menu When you enter the Main menu, several choices will be presented, and a default path for install will also be given. From there you will have the choice to back out of the installation if needed. If you feel unsure, need to get more information, make adjustments etc before proceeding you now have the choice to back out by removing the installation CD and press or now. This is also the way to go if you want to restart the installation using another kernel. For those of who are interested in the boot log you can do so by ... (enter text here) In my opinion this would help especially new Debian users to feel more comfortable with what is going to happen during the install. (I know that a graphical installer is in the works, but not until woody+1) Best wishes, Svante Signell Below follows unanswered question in an earlier posting. srs writes: > Addtional boxes boot-tested with woody-isolinux: > > Boxdisksidepci bf24 > Comapaq Presario 5640/5670 IDE OK OK > Dell Dimension XPS 733rIDE OK OK > Dual Celeron MSI6120 SCSI+IDE OK OK > Em2 QDI Brilliant SCSI OK OK (compact tested OK too) > Dell Inspiron 4100 laptop IDE OK OK > > A few comments about the installer program: > > 1. Is it possible to generate a boot log, and to be able to view it >while installing? > > 2. It would be nice to be able to back out, or doing a reboot _before_ >having to go as long as to the keyboard setup phase. You maybe >changed your mind before coming that far: What am I doing?, I don't >have all info available!, whats happening next?, I want to quit the >install!, etc. > > 3. When coming to the part of the install where you have several >choices, the reboot, restart and prevoius step options should be >higher up in the menu. This enables you to see a way out of the >install procedure, if needed. > > Eagerly waiting for the woody release, > Svante Signell > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Potato->Woody kernel upgrade problems
Martijn van [EMAIL PROTECTED]@Fri, 19 Apr 2002 09:50:42 +1000: > The solution to this is to stuff all your own aliases under something like > /etc/modules/mine or something like that. Then they will never been > overwritten (except if a package named "mine" decides it needs some modules > :) > Hmmm local-mine? -- *=-+-__ |[EMAIL PROTECTED]: _ Ugh! Nio2f says something: __ : http://www.lintux.cx/ |/ on the to somethine decider ste e \ ~~-+-=-+~+-=* -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Technical Committee: decision on #119517?
Over six months ago, on 2001-11-14, Bug #119517 was submitted to the Technical Committee for a ruling. No member of the Technical Committe has participated in any public discussion of this bug (at least in the bug logs or in available messages from the debian-ctte list archives) since 2001-12-04, and no apparently discussion of any sort since 2002-02-26. Does the Technical Committee have any plans to issue any statement on this issue? Either an affirmative statement regarding the issue on point, or a statement that the Committee refuses to countenance the it? If the latter, please provide some reasoning as to why, as Section 6.3.6 of the Constitution appears to be applicable: Technical Committee makes decisions only as last resort. The Technical Committee does not make a technical decision until efforts to resolve it via consensus have been tried and failed, unless it has been asked to make a decision by the person or body who would normally be responsible for it. Note that the "unless" clause is applicable here, as the package maintainer explicitly requested a ruling from the Technical Committee. In fact, both disputants made such a request. Thanks for your attention. -- G. Branden Robinson|It was a typical net.exercise -- a Debian GNU/Linux |screaming mob pounding on a greasy [EMAIL PROTECTED] |spot on the pavement, where used to http://people.debian.org/~branden/ |lie the carcass of a dead horse. pgp4Ss7tPHXy1.pgp Description: PGP signature
Re: XFree 4.2.0 - again
On Wed, Apr 17, 2002 at 09:16:49PM -0500, Branden Robinson wrote: > > this is the New Overfiend, preacher of Love and Tolerance > > I see your irony detector is as non-functional as ever... :) Oh it works just fine. It just _had_ to be said, sooner or later -- Joseph Carter <[EMAIL PROTECTED]> This end upside-down If the user points the gun at his foot and pulls the trigger, it is our job to ensure the bullet gets where it's supposed to. pgpydmmtbP9n3.pgp Description: PGP signature
Re: Where to place Ada (Gnat) libraries
David Starner <[EMAIL PROTECTED]> writes: > On Thu, Apr 18, 2002 at 10:47:54PM +0100, Ian Sharpe wrote: >> Is there a Debian-preferred location for .ali files (etc) produced by >> the Gnat Ada compiler? The pattern seems to be: >> >> .a/.so files in /usr/lib >> .ali files in /usr/lib/xxx >> .ads/.adb files in /usr/include/xxx >> >> where xxx is the package that the library is a part of. > > If that's what the pattern is, then that's what you probably do. There > is no formal standard for where Ada pieces go. I've thought about > starting a debian-ada mailing list, which would be a fine place to argue > out all the details for a possible Ada policy or details to add to > Debian Policy. Yes please. I'm currently interested in Ada and I might release some packages some day. Cheers, -- Jérôme Marant http://marant.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#143548: ITP: ipm -- PHP-based tasklist/project management
Package: wnpp Version: N/A; reported 2002-04-19 Severity: wishlist * Package name: ipm Version : 0.9 Upstream Author : phlux <[EMAIL PROTECTED]> * URL : http://udpviper.com/project.php?project=ipm * License : GPL Description : PHP-based tasklist/project management IPM is short for the Incyte Project Manager. It is a featureful PHP-based project/task management system. While it doesn't integrate with any "groupware", it does its job simply and well - it manages tasks and projects made up of tasks :) -- System Information Debian Release: 3.0 Architecture: i386 Kernel: Linux willow 2.4.18-xfs-a0 #1 Tue Apr 16 15:57:44 CDT 2002 i686 Locale: LANG=en_CA, LC_CTYPE=en_CA -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
