Bug#231538: *sigh*
GOTO Masanori wrote: That would only help mips. I wonder what a mips machine would need with an i486 emulator. For IA-32 we would have to patch 2.4.18, but we cannot properly update those packages in woody without people losing their modules (would hurt a bit on laptops...). So that's a no-go. So you don't have any intenstion to install new 2.4 kernel with i486 emulation patch. Exactly, since this would harm all notebook users. Hence, the upgrade directory for real 80386 machines. What does it mean? I thought that I've explained this already: I have another solution to propose: Provide an upgrade-for-real-i386 directory, including a README and kernel packages to install before upgrading to sarge. We've done a similar thing from bo-potato or something. This will require coordination with the release manager and the ftpmasters to provide dists/sarge/main/upgrade-i386 which should contain the kernel packages and a readme file. If there is no plan to support upgrade-path for i386 machines, then I Nobody said that there is no plan to support an upgrade-path for i386 machines. We just cannot simply replace the kernel in the stable distribution anymore due to fucked up dependencies and kernel vulnerabilities. put the message Use woody-proposed-updates 2.4.24 kernel at libc6.preinst for 80386 machine. Then, we don't need to change the current woody kernels. I think it's the simplest fix. Is it OK? No. Packages will eventually vanish from the proposed-updates directory. We'll need an upgrade-i386 directory as we've had a couple of releases before. Regards, Joey -- Whenever you meet yourself you're in a time loop or in front of a mirror. Please always Cc to me when replying to me on the lists. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Votre mail a Club-Internet
Cher(e) internaute, Nous avons bien reçu le courrier électronique que vous nous avez envoyé. Nous recevons actuellement beaucoup de demandes par mail, aussi nous vous remercions de votre patience si la réponse à votre question tardait à vous parvenir. Vous allez recevoir bientôt un second accusé de réception avec une référence qui nous permettra d'identifier votre demande et vous assurer ainsi un suivi personnel. Soyez certain de tous nos efforts pour vous répondre le plus rapidement possible. N'oubliez pas que vous pouvez par vous-même gérer votre compte et trouver des réponses techniques en utilisant les sites ci-dessous : http://www.club-internet.fr/moncompte http://www.club-internet.fr/assistance Cordialement, Le Service Clients de Club Internet. --- Extrait de votre message / Sample of your mail -- From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Cc: M-Id: [EMAIL PROTECTED] Date: Tue, 30 Mar 2004 11:14:24 +0200 Subject: Re: approved This is a multi-part message in MIME format. --=_NextPart_000_0016=_NextPart_000_0016 Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: 7bit I have attached your document. +++ Attachment: No Virus found +++ Panda AntiVirus - www.pandasoftware.com --=_NextPart_000_0016=_NextPart_000_0016 Content-Type: application/octet-stream; name=word document.zip Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=word document.zip -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#231538: *sigh*
At Tue, 30 Mar 2004 10:46:25 +0200, Martin Schulze wrote: GOTO Masanori wrote: That would only help mips. I wonder what a mips machine would need with an i486 emulator. For IA-32 we would have to patch 2.4.18, but we cannot properly update those packages in woody without people losing their modules (would hurt a bit on laptops...). So that's a no-go. So you don't have any intenstion to install new 2.4 kernel with i486 emulation patch. Exactly, since this would harm all notebook users. Hence, the upgrade directory for real 80386 machines. What does it mean? I thought that I've explained this already: I have another solution to propose: Provide an upgrade-for-real-i386 directory, including a README and kernel packages to install before upgrading to sarge. We've done a similar thing from bo-potato or something. This will require coordination with the release manager and the ftpmasters to provide dists/sarge/main/upgrade-i386 which should contain the kernel packages and a readme file. That's nice solution if it's acceptable. If there is no plan to support upgrade-path for i386 machines, then I Nobody said that there is no plan to support an upgrade-path for i386 machines. We just cannot simply replace the kernel in the stable distribution anymore due to fucked up dependencies and kernel vulnerabilities. put the message Use woody-proposed-updates 2.4.24 kernel at libc6.preinst for 80386 machine. Then, we don't need to change the current woody kernels. I think it's the simplest fix. Is it OK? No. Packages will eventually vanish from the proposed-updates directory. We'll need an upgrade-i386 directory as we've had a couple of releases before. Ah, I understand why my proposal is not good. Martin, thanks for pointing it out. So... I don't add use woody-proposed-updates message into libc6.preinst, I keep them as the current one. I think Bug#231538 can be closed when 2.3.2.ds1-12 is released. But the current thread is useful for keeping discussing to make dists/sarge/main/upgrade-i386 for the near future sarge release. I would clone this bug and reassign it to ftp.debian.org or ftp-master. Nathanael, OK? Regards, -- gotom -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Piece jointe refusee par le serveur anti-virus de l'academie de Poitiers (Probablement un virus) (Attachment Removal)
eManager Notification * The following mail was blocked since it contains sensitive content. Source mailbox: [EMAIL PROTECTED] Destination mailbox(es): [EMAIL PROTECTED] Policy: Attachment Removal Attachment file name: your_letter.pif - application/octet-stream Action: Replaced with text Les extensions suivantes sont refusees: .exe .bat .com .dll .vbs .vbe .vb .hta .js .jse .scr .pif .lnk .shs .shb. Si vous voulez quand meme faire parvenir ce fichier, veuillez le compresser ou le renommer et prevenez votre correspondant. *** End of message * Received: from ac-poitiers.fr (APoitiers-106-1-21-200.w81-53.abo.wanadoo.fr [81.53.186.200]) by matrix3.ac-poitiers.fr (Postfix) with ESMTP id 3E0BC118073 for [EMAIL PROTECTED]; Tue, 30 Mar 2004 16:19:42 +0200 (CEST) From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Re: Your letter Date: Tue, 30 Mar 2004 16:17:34 +0200 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0003_3917.7B99 X-Priority: 3 X-MSMail-Priority: Normal Message-Id: [EMAIL PROTECTED]
Bug#240901: acknowledged by developer (Re: Bug#240901: (no subject))
According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=140891msg=47 upstream glibc maintainers seem to strongly disagree, so I am closing this bugreport. Yes, but in that bug report en_AU (libc6 version 2.2.5-4) had also no AM/PM text. And this has now changed, hence my bug report. I was wondering if it could be change for en_GB. Unless I'm missing something en_AU as now more reason to use AM/PM than en_GB -- OoberMick It's a secret to everybody. -- The Legend of Zelda pgp0.pgp Description: PGP signature
Bug#240901: acknowledged by developer (Re: Bug#240901: (no subject))
On Tue, Mar 30, 2004 at 07:00:38PM +0100, Michael Graham wrote: According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=140891msg=47 upstream glibc maintainers seem to strongly disagree, so I am closing this bugreport. Yes, but in that bug report en_AU (libc6 version 2.2.5-4) had also no AM/PM text. And this has now changed, hence my bug report. I was wondering if it could be change for en_GB. I was not referring to the bugreport, but this specific message, in particular: Not filling in the am/pm strings is a mean to say that the people in the country the locale is fow are not to backward as to use the am/pm format anymore. This definitely is the case for the UK. Unless I'm missing something en_AU as now more reason to use AM/PM than en_GB Some people argued that 12 hour format with am/pm is the most popular in Australia. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#235759: Comentar on which replacement for German quotes
On Mon, Mar 29, 2004 at 11:02:11PM +0200, Denis Barbier wrote: On Mon, Mar 29, 2004 at 02:47:42AM +0200, Adrian Bunk wrote: [...] I am a bit surprised that this discussion and all patches sent only cover de_DE, although there are altogether three common de_ locales plus two others the locales package supports. If you fix this issue, it should be properly fixed for all de_ locales. All de_* locales include (either directly or indirectly) de_DE in their LC_CTYPE section, so this change propagates to all de_* locales. Thanks for the explanation. This means only cases like the different quote in the Swiss locale need to be handled. Denis cu Adrian -- Is there not promise of rain? Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. Only a promise, Lao Er said. Pearl S. Buck - Dragon Seed -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
get p0rn at nocost
Title: New Details Completely Fr'ee Di'gital Ca'ble Fr'ee PP'V, Sp'orts, Mo'vies and mo're! To find out more, cl'ick image or Visit us Here. dragonfly gilligan reprimand stooge hastings florist candela naive captor millstone retina belladonna edition drub courtney pickett certify togs signet elusive metaphoric phonic pleiades geyser attach company croatia o'clock selena kiosk enfant amongst presentational misogyny malocclusion lip counterpoise dispersal larkspur simpleminded boastful beatitude codeword draw baldwin flyer baritone toastmaster tommy interception apogee member buzzer citadel dairy hap wier beetle converse setback viii evolutionary nerve baylor plebian staunton handicraftsman wangle corroborate biennium casserole endogamous backlog augite cardinal czar holocaust gradate constantinople colonel darken cohesion doolittle hitch elijah turbojet daisy anastigmatic makeup jeopard roof apace bewail cornish psychiatrist carport cherry suggestive tattler brandenburg hester afterthought come decimal lucifer casey misshapen jed saturater exhaustion heisenberg affirm indigo austenite enumerate briton appertain petroglyph brad cuckoo diabetic deregulate playwriting milan desmond charlie spiral clare ajar conservatism oakley aspirant eucharist caldera cottonwood spiny wabash entendre tecum coffee fennel limitation conversion disney admitted collage schloss
Bug#240901: acknowledged by developer (Re: Bug#240901: (no subject))
On Tue, Mar 30, 2004 at 10:16:53PM +0200, Denis Barbier wrote: On Tue, Mar 30, 2004 at 07:00:38PM +0100, Michael Graham wrote: Denis Barbier wrote: According to http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=140891msg=47 upstream glibc maintainers seem to strongly disagree, so I am closing this bugreport. Yes, but in that bug report en_AU (libc6 version 2.2.5-4) had also no AM/PM text. And this has now changed, hence my bug report. I was wondering if it could be change for en_GB. I was not referring to the bugreport, but this specific message, in particular: Not filling in the am/pm strings is a mean to say that the people in the country the locale is fow are not to backward as to use the am/pm format anymore. This definitely is the case for the UK. Judging by the writing the author of that text isn't a native speaker of English, so I'm not sure where this information comes from. While the AM/PM format is inferior to the 24-hour format in many ways, it is most certainly false to claim that people in the UK do not use the AM/PM format. AM/PM is still significantly more common than 24-hour in UK everyday speech, signs, written communication, and so on, and I think the onus ought to be on the author of the above to back up his extremely surprising statement with facts. To take an example, Hansard, the official records of parliamentary debates in the House of Commons, records times in the AM/PM format: http://www.parliament.the-stationery-office.co.uk/pa/cm200304/cmhansrd/cm040329/debtext/40329-06.htm#40329-06_time0 -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: powerpc64 gcc compiler ...
Sven Luther writes: First, i found that this gcc-3.4 package in experimental wasn't yet built on powerpc, which i did. It did output lot of FAILs in the tests later on, but i am not sure this is worrying or not. Please have a look at http://gcc.gnu.org/ml/gcc-testresults/ and compare. It builds simple binaries without problems. But it didn't build the biarch toolchain, so it was of no use for me. After a bit of investigation, i found out that : --target=powerpc64-linux --with-cpu=default32 both s390 and sparc build the 32bit compiler and patch gcc/config.gcc to include the 64bit specific Makefile chunks. At least this installs things in a arch-linux subdirectory, not arch-linux64. I don't know if there other changes building this way. Look at the -biarch patches in debian/patches. I don't really know what the plans are for ppc64 support, but i hear that biarch userland is a post sarge issue. Also, i understood that we will not switch over to gcc 3.4 for sarge, which is the reason why it is in experimental currently. Or maybe it would be possible to have gcc 3.4 in unstable and later sarge, without it necessarily being the default ? not one more compiler in sarge. If we want to have 3.4 in sarge, we should drop 3.2 first. If 3.4 is released, built for all Debian architectures and no regressions found for packages which replace their 3.3 counterparts, then lets propose this to debian-release ... Upstream development asked/proposed Linux distributions to include a libstdc++6 in current releases. What i am trying to do, and what would be nice, would be to have at least ppc64 kernels for the sarge release, since some boxes may need this and will have trouble with 32bit kernels. Don't know if this is realistic, but it seems to me that only gcc support is needed in order to achieve that. I hear that a 64bit procps and module-init-tools will be needed too, and probably a libncurses, which may be a problem, but let's worry about this later. well, you need a lib64c6-dev as well. Unsure how much prepared the glibc sources are and if the glibc maintainers are willing to include such packages for sarge. Anyway, my question here is if you would consider it reasonable to enable the powerpc biarch toolchain, and have it default to 32bit for gcc 3.4 ? This should cause no problem for ordinary powerpc, but would allow to build ppc64 stuff with the same toolchain. Am i correct with this assumption ? I will try tomorrow to build this, but would it make sense to enable this in the experimental powerpc packages ? And what about the not gcc or cxx compilers ? Including your patches is ok, enable it by default not, as lib64c6-dev is missing as a build dependency. To disable the runtime lib64raries you do not want add a patch like sparc-config-ml or s390-config-ml. At least for gcj you you have to do some extra configury, as it builds the gtk based peer classes, for which you don't have dependent lib64raries. Matthias -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#240901: acknowledged by developer (Re: Bug#240901: (no subject))
reopen 240901 thanks On Wed, Mar 31, 2004 at 02:23:13AM +0100, Colin Watson wrote: [...] I was not referring to the bugreport, but this specific message, in particular: Not filling in the am/pm strings is a mean to say that the people in the country the locale is fow are not to backward as to use the am/pm format anymore. This definitely is the case for the UK. Judging by the writing the author of that text isn't a native speaker of English, so I'm not sure where this information comes from. While the AM/PM format is inferior to the 24-hour format in many ways, it is most certainly false to claim that people in the UK do not use the AM/PM format. AM/PM is still significantly more common than 24-hour in UK everyday speech, signs, written communication, and so on, and I think the onus ought to be on the author of the above to back up his extremely surprising statement with facts. To take an example, Hansard, the official records of parliamentary debates in the House of Commons, records times in the AM/PM format: http://www.parliament.the-stationery-office.co.uk/pa/cm200304/cmhansrd/cm040329/debtext/40329-06.htm#40329-06_time0 Ok, reopening this bugreport then. But note that one has now to convince upstream or Debian glibc maintainers. Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#240901: acknowledged by developer (Re: Bug#240901: (no subject))
Processing commands for [EMAIL PROTECTED]: reopen 240901 Bug#240901: (no subject) Bug reopened, originator not changed. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#40263: i gtota kon.w..
ONLY REAL SUPER VIAGDRA CALLED CIADLIS IS EFFECTIVE! Annual Sale: ONLY $3 per dose Check out our website with disscounts and get your fdree bonus pillls http://waffle.mybestchoice.net/sv/index.php?pid=eph2660
