Bug#116507: Restore vital organs that shrink with age

2004-10-20 Thread logan marshall 
As we stand on the brink of a new era with the regard aging, the
possibilities are endless. We are engaged in scientific studies that are
pushing beyond the barrier.
Hold on to your young body as long as you can

check out this new lifespan enhancement 
http://ond.Q.qualityproductkingdom.com/s/


Thanks to your formula, I am no longer a slave to diets! I have been eating
moderately and exercising. My energy seems to be so much higher and I no
longer feel like I need a nap in the middle of the day. I just feel great
all over! I told several of my friends about the spray. Caroline Lee , Lake
George, NY 



cool idea but no, link and address above

We included in our review a small subset of trials that assessed the value
of addition of an aminoglycoside in Gram positive infections  . We should
never had met! retorted the Demon, showing great excitement
Oh, I didn't seek your acquaintance, said Rob.

Bug#276983: same as #275911

2004-10-20 Thread Gabor Melis 
On second thought this is the same es 275911. I checked with strace -p and 
downgraded to the version mentioned there and it works now.

Sorry, Gabor

Bug#116507: The easist way to [refinance]

2004-10-20 Thread Robert Hurley 

Hi,

Your Application has been Pre-Approved on Tuesday, October 19th 2004.
   
Your MRTG process is ready for rates starting at 2.75% Fixed. 
Please use our secure site to fill-out your application.
  
http://lcf.xolwed.com/azgme


Good-bye,
Robert Hurley
http://an.xolwed.com

Bug#6682: the size of your manhood

2004-10-20 Thread lilliana diaz 
male enhancement and performance system

90% of males were interested in improving their sexual stamina,
performance, and the size of their manhood. Are you one of the 90%?

I'm 67 years old. I was very wary of putting my details on the Internet,
but I am very pleased that it worked out for me. Your product arrived only 2
days after I placed the order, and the packaging was very discreet, which
was perfect for me. I was shocked at how quickly the pills took effect, and
I did attempt the exercises as well, which I found simple and easy to
understand. I now have loads of energy, and feel like a new man. I can't
thank you enough! Ronald, Phoenix

check out the only Male Enhancement formula with a free DVD

http://www.glowproduction.com/lg/



no, then link above




I told you to keep it, answered Rob. I don't want it
The Demon staggered back as if he had been struck

Bug#275157: xfonts-base could Suggests: xfonts-base-transcoded

2004-10-20 Thread Branden Robinson 
On Mon, Oct 18, 2004 at 03:06:09PM +0200, Loïc Minier wrote:
> Branden Robinson <[EMAIL PROTECTED]> - Mon, Oct 18, 2004:
> 
> > >  I wish xfonts-base would suggest xfonts-base-transcoded to ease its
> > >  discovery.
> > >  The same applies to xfonts-100dpi and xfonts-75dpi of course.
> > Why aren't the references in each package's extended description
> > sufficient?
> 
>  It would permit the package management program to offer the choice
>  instead of forcing the user to search manually for the name of the
>  package (after reading the complete description carefully).
> 
>  Strictly speaking, this is not a bug, I just wish it would be easier to
>  see the fonts.
>Usually, xfonts-* are pulled in when you install an X server and you
>  suddenly see dozens of packages that are going to get installed; most
>  users will respect the choices of their package manager and just have a
>  look to check nothing is overkill for them or wether something is
>  suggested that they could miss.
> 
>  So I see the Suggests: as a hint for the package manager to offer the
>  packages to the user when he installs a X server.  Alternatively, a
>  Enhances: on the *-transcoded size could provide the same suggestion,
>  but I think package manager are not suggesting package B when B
>  enhances A and you install A.

Okay.  This is a reasonable suggestion.  I think wishlist bugs are best
accompanied by a rationale instead of just tersely stating "do this"; don't
you?  :)

-- 
G. Branden Robinson|  We either learn from history or,
Debian GNU/Linux   |  uh, well, something bad will
[EMAIL PROTECTED] |  happen.
http://people.debian.org/~branden/ |  -- Bob Church


signature.asc
Description: Digital signature

Bug#273202: xterm: Chinese characters don't always line wrap

2004-10-20 Thread Branden Robinson 
retitle 273202 xterm: double-wide characters don't always line-wrap
thanks

On Mon, Oct 18, 2004 at 04:27:55PM -0400, Andrew Moise wrote:
>   It's not strictly unprintable characters that cause this -- I have
> these fonts installed, and the characters print correctly on my system. 
> The line wrapping malfunction I describe still happens, though.

Ah, my bad.

If my new title for the bug is inaccurate, please let me know.

-- 
G. Branden Robinson| Religious bondage shackles and
Debian GNU/Linux   | debilitates the mind and unfits it
[EMAIL PROTECTED] | for every noble enterprise.
http://people.debian.org/~branden/ | -- James Madison


signature.asc
Description: Digital signature

Bug#276793: marked as done (xlibs: xfree86/pc104/uk not supported)

2004-10-20 Thread Debian Bug Tracking System 
Your message dated Wed, 20 Oct 2004 11:42:46 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#276793: xserver-xfree86: Error activating XKB 
configuration reported at startup of GNOME session
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--
Received: (at submit) by bugs.debian.org; 16 Oct 2004 13:15:38 +
>From [EMAIL PROTECTED] Sat Oct 16 06:15:38 2004
Return-path: <[EMAIL PROTECTED]>
Received: from 82-43-72-5.cable.ubr06.croy.blueyonder.co.uk 
(home.chandlerfamily.org.uk) [82.43.72.5] 
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CIoPG-0001H0-00; Sat, 16 Oct 2004 06:15:34 -0700
Received: from rabbit.home ([192.168.0.25] helo=rabbit)
by home.chandlerfamily.org.uk with smtp (Exim 4.34)
id 1CIoPE-00083G-Hh; Sat, 16 Oct 2004 14:15:32 +0100
Received: by rabbit (sSMTP sendmail emulation); Sat, 16 Oct 2004 14:15:25 +0100
From: "Alan Chandler" <[EMAIL PROTECTED]>
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: xserver-xfree86: Error activating XKB configuration reported at 
startup of
 GNOME session
Bcc: Alan Chandler <[EMAIL PROTECTED]>
X-Mailer: reportbug 2.99.6
Date: Sat, 16 Oct 2004 14:15:25 +0100
Message-Id: <[EMAIL PROTECTED]>
X-BadReturnPath: [EMAIL PROTECTED] rewritten as [EMAIL PROTECTED]
  using "From" header
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE 
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level: 

Package: xserver-xfree86
Version: 4.3.0.dfsg.1-8
Severity: normal


As I start up a Gnome Session from gdm, I am presented with an error dialog box 
which says

Error activating XKB configuration.
Probably internal X server problem.

X server version data:
The XFree86 Project, Inc
4031
You are using XFree 4.3.0.
There are known problems with complex XKB configurations.
Try using simpler configuration or taking more fresh version of XFree software.
If you report this situation as a bug, please include:
- The result of xprop -root | grep XKB
- The result of gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb


The results of these two commands are

xprop

[EMAIL PROTECTED]:~$ xprop -root|grep XKB
_XKB_RULES_NAMES_BACKUP(STRING) = "xfree86", "pc104", "uk", "", ""
_XKB_RULES_NAMES(STRING) = "xfree86", "pc104", "uk", "", ""


and gconftool-2

[EMAIL PROTECTED]:~$ gconftool-2 -R /desktop/gnome/peripherals/keyboard/xkb
 layouts = [uk]
 model = pc104
 overrideSettings = false
 options = []

I am not doing anything special with my keyboard - just the standard setup

(am running this on a Dell Latitude C400)




-- Package-specific info:
Contents of /var/lib/xfree86/X.roster:
xserver-xfree86

/etc/X11/X target unchanged from checksum in /var/lib/xfree86/X.md5sum.

X server symlink status:
lrwxrwxrwx  1 root root 20 Mar  7  2004 /etc/X11/X -> /usr/bin/X11/XFree86
-rwxr-xr-x  1 root root 1745484 Sep 28 13:09 /usr/bin/X11/XFree86

Contents of /var/lib/xfree86/XF86Config-4.roster:
xserver-xfree86

VGA-compatible devices on PCI bus:
:00:02.0 VGA compatible controller: Intel Corp. 82830 CGC [Chipset Graphics 
Controller] (rev 04)

/etc/X11/XF86Config-4 does not match checksum in 
/var/lib/xfree86/XF86Config-4.md5sum.

XFree86 X server configuration file status:
-rw-r--r--  1 root root 3236 Mar 23  2004 /etc/X11/XF86Config-4

Contents of /etc/X11/XF86Config-4:
# XF86Config-4 (XFree86 X Window System server configuration file)
#
# This file was generated by dexconf, the Debian X Configuration tool, using
# values from the debconf database.
#
# Edit this file with caution, and see the XF86Config-4 manual page.
# (Type "man XF86Config-4" at the shell prompt.)
#
# This file is automatically updated on xserver-xfree86 package upgrades *only*
# if it has not been modified since the last upgrade of the xserver-xfree86
# package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following commands as root:
#
#   cp /etc/X11/XF86Config-4 /etc/X11/XF86Config-4.custom
#   md5sum /etc/X11/XF86Config-4 > /var/lib/xfree86/XF86Config-4.md5sum
#   dpkg-reconfigure xserver-xfree86

Section "Files"
FontPath"unix/:7100"# local font server
FontPath"/var/lib/defoma/x-ttcidfont-c

Bug#275180: Acknowledgement (xserver-xfree86: compile error (missing file Xrender.h))

2004-10-20 Thread Branden Robinson 
On Mon, Oct 18, 2004 at 01:31:17PM +0100, Luke Kenneth Casson Leighton wrote:
>  the only possible thing that's "odd" is that this is a system
>  on which i have never actually run X at the console: it's a server
>  system on which i always run X to another display.
> 
>  so i've never run dpkg-reconfigure xserver-xfree86 and i don't even
>  have an /etc/X11/XF86Config-4 file on it.
> 
>  it's my build server, not a desktop machine.

This is completely irrelevant; you don't need to have configured the
XFree86 X server to build the xfree86 source package.

-- 
G. Branden Robinson|  "There is no gravity in space."
Debian GNU/Linux   |  "Then how could astronauts walk
[EMAIL PROTECTED] |   around on the Moon?"
http://people.debian.org/~branden/ |  "Because they wore heavy boots."


signature.asc
Description: Digital signature

Processed: Re: Bug#273202: xterm: Chinese characters don't always line wrap

2004-10-20 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> retitle 273202 xterm: double-wide characters don't always line-wrap
Bug#273202: xterm: unprintable multibyte characters not line-wrapped
Changed Bug title.

> thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

Processed: retitle 275329 to xdm: creates utmp entry but doesn't delete it

2004-10-20 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

> # Automatically generated email from bts, devscripts version 2.8.5
> retitle 275329 xdm: creates utmp entry but doesn't delete it
Bug#275329: xdm creates utmp entry but doesn't delete it
Changed Bug title.

>
End of message, stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)

add jonas@kley.ch to your blackhole backlash blacklist

2004-10-20 Thread Branden Robinson 
<[EMAIL PROTECTED]>: host mail-fwd.mx.hostcenter.com[204.202.241.5] said: 554
denied by spamd (in reply to RCPT TO command)

Content-Description: Undelivered Message
From: Branden Robinson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Bug#252895: /usr/X11R6/bin/xfontsel: [xfontsel] crash
Date: Mon, 18 Oct 2004 07:18:52 -0500
Message-ID: <[EMAIL PROTECTED]>

-- 
G. Branden Robinson|   I'm a firm believer in not drawing
Free Software Developer|   trend lines before you have data
[EMAIL PROTECTED]  |   points.
http://deadbeast.net/~branden/ |   -- Tim Ottinger


signature.asc
Description: Digital signature

Bug#234556: [Crusoe CMS bug] Getting a CMS 4.5 for your laptop...

2004-10-20 Thread Emmanuel Fleury 
On Wed, 2004-10-20 at 15:04, Siward de Groot wrote:
> 
> Under dutch law it would be the responsibility of the seller
>   (the shop where you bought it) to sell good quality products,
>   and if they do not, then you can prosecute them to get your rights.

The problem is that the seller will complain to Sony which will complain
to Transmeta. It can take forever. I just took a short-cut.

But, you are definitely right about something.

I don't know who's legal responsibility this bug is... 
but I assumed that neither the Sony people. 

> The seller can not reasonably be expected to provide firmware updates
>   if Transmeta doesnt create these,
>   he does however have the possibility to exchange the laptop with one
>   that does not have this brokenness (probably a more modern one).

I'm not sure, I want another laptop... Mine is really good and the ones
that they are selling now are not really fitting to me like this one is.

> This is dutch law ; however, it also seems reasonable,
>   so i would not be surprised if the country of purchase had similar laws.
> Maybe debian-legal would be interested in this problem.

This would be really interesting. I don't really know what to do with
this CMS firmware locked down in the machine with this encryption
around.

> > My first error was to claim that I had a problem with Linux and not with
> > Windows XP.
> 
> No, you did it right.

Then, what I did wrong was to ask people to lie about it, as you say
later. :-/

> > 2) Complain about a bug _in_Windows_XP_
> 
> You are asking them to become liars.

Yes, sorry. I though it was a good idea. You're very likely right.

> Also, if the bug is in xp, then clearly it is not responsibility of sony.
> They are uncooperative, so it is not easy to get your right.
> I think it would be smart to see how strong your legal position is.
> If you can not get results through the judicial system
>   (whether by warning of possibility to sue or by actually sueing),
>   then it would be right to warn fellow transmeta fans to
>   not buy this transmeta/sony machine because it is buggy.

Hum, I would prefer to not be that extreme... :-/

Actually, this advertising just brought me some feed-back from a guy in
a company which is selling thin clients running with a dual boot Windows
XP and Linux (see:
http://www.teco-ia.com.tw/PDF/TR5670-XP-Quick%20spec.pdf).

He does encounter the exact same problem with the X server.

Maybe, this will force Transmeta to admit that there is a serious bug
here and make them delivering a patch...

I mean, how long can they try to pretend there is no bug ?

> If you let yourself be railroaded into more lies,
>   it can only harm your case, in my opinion.

And I think you're right about it.


>   but as i understand it even transmeta doesnt exactly know where the bug is. 

In a matter of fact, the CMS 4.4 and 4.5 seems to be exempted of this
bug (even if they don't know exactly where is the bug causing this crash
of X). So, an update of the CMS should be enough to fix the bug.

> Plus that they don't want to spend very much money on supporting an old chip; 

Well, as I told you before some companies are still saling products with
this CMS.

>   it might be cheaper for them to
>   supply all people experiencing this bug with a new laptop.

This, I don't know.

My guess is that paying somebody to make a working patch to update the
CMS should be cheaper than offering to replace all the hardware to all
the owners of hardware with CMS 4.3.x that request it.

Regards
-- 
Emmanuel Fleury

Computer Science Department, |  Office: B1-201
Aalborg University,  |  Phone:  +45 96 35 72 23
Fredriks Bajersvej 7E,   |  Fax:+45 98 15 98 89
9220 Aalborg East, Denmark   |  Email:  [EMAIL PROTECTED]

Bug#164034: account update

2004-10-20 Thread Guillermo Cobb 
most dealers purchase their extended warranties from 3rd partiy
  sources. by going directly to one of those sources, you can s a v e
  yourself hun:dreds of dol:lars for the same or even better exten:ded
  warranty covera:ge.
  Start sa:ving N0W!!! Fi:ll out the f:orm below.

  http://www.wheelzloanz.net

Bug#234556: [Crusoe CMS bug] Getting a CMS 4.5 for your laptop...

2004-10-20 Thread Siward de Groot 
On Wednesday 20 October 2004 11:42, Emmanuel Fleury wrote:
> Hi all,
>
> It's a long time that I have started hunting the bug of the Xserver on
> my Vaio PCG-C1MZX and the final result is here:
> http://www.cs.auc.dk/~fleury/bug_cms/
>
> Is it satisfactory ???
>
> I don't think so because the bug can appear in any other software and it
> will start again. Moreover, I know that the CMS (Code Morphing Software)
> 4.4 and 4.5 are not buggy. So, having an update would solve the problem
> at once (and get better performance for the machine).
>
> But, now it is a matter to convince Sony that we really need this patch
> (no need to contact Transmeta because they will just say that it's not
> their business). So, I tried...

Under dutch law it would be the responsibility of the seller
  (the shop where you bought it) to sell good quality products,
  and if they do not, then you can prosecute them to get your rights.

You bought computer hardware,
  and i expect that there was no term in the sales contract that says that
  this hardware is only fit for use with some software,
  therefore you could not reasonably expect that it would not work with X,
  therefore the seller is responsible for having delivered goods that
are broken.
The seller can not reasonably be expected to provide firmware updates
  if Transmeta doesnt create these,
  he does however have the possibility to exchange the laptop with one
  that does not have this brokenness (probably a more modern one).
If the seller were to offer you this,
  then you would have to accept a replacement that
  has the same value as your laptop would have without the bug.
If the seller does not offer you this,
  then the sales contract can be undone, and you get your money back
  (the money you have right to get back is
 original salesprice * unused fraction of laptop lifetime).

This is dutch law ; however, it also seems reasonable,
  so i would not be surprised if the country of purchase had similar laws.
Maybe debian-legal would be interested in this problem.

> We do not confirm any problems for the CPU on the original shipping
> condition, Japanese OS. Thus, we are afraid we do no have an exact plan
> for firmware update.

Thus they intimidated you,
  therefore you can not be held responsable for lying to them.

> Changing the OS is 100% on your responsibility, and it would be
> basically out of support except repair work service for hardware
> problem.

Nonsense. they need to deliver non-broken goods.

> My first error was to claim that I had a problem with Linux and not with
> Windows XP.

No, you did it right.

> I love the trick about the "Service Pack 2". :)

The news about "service" pack 2 is probably good for free software,
  but it has nothing to do with this transmeta-sony-computershop-you thing.

> 2) Complain about a bug _in_Windows_XP_

You are asking them to become liars.
Also, if the bug is in xp, then clearly it is not responsibility of sony.
They are uncooperative, so it is not easy to get your right.
I think it would be smart to see how strong your legal position is.
If you can not get results through the judicial system
  (whether by warning of possibility to sue or by actually sueing),
  then it would be right to warn fellow transmeta fans to
  not buy this transmeta/sony machine because it is buggy.
Publicity caused by this could be reason for somebody to
  do something about it,
  but you must not threaten them with destroying their good name ;
  Warning them of the danger to lose their good name, however,
  would be very correct.
If you let yourself be railroaded into more lies,
  it can only harm your case, in my opinion.
The danger that asking others to lie could lead to sony getting a bad
  impression of the free software community is not very big,
  even if they found your email in debian's public archives.

> My hope is that if enough people are mentioning this bug, Sony will
> decide to ask Transmeta to release an update.

That would be nice if it happened,
  but as i understand it even transmeta doesnt exactly know where the bug is. 
Plus that they don't want to spend very much money on supporting an old chip; 
  it might be cheaper for them to
  supply all people experiencing this bug with a new laptop.

I dont have a transmeta chip in my pc,
  so it is really none of my business,
  but i think lying is counterproductive if you have an alternative,
  and it is your right to get a good machine.
Just my 2 cents.

I wish you good luck.

Siward de Groot

Bug#86184: today's hot stock

2004-10-20 Thread admigf 
HOT STOCKS ALERT: Rincon Resources (OTC: RIRI), a gold exploration and
development company.

++

Rincon Resources (OTC: RIRI)

Current price : u0.13
Short term target: k0.50

++


ABOUT RINCON RESOURCES, Inc.

Rincon Resources is a newly formed junior gold exploration company focused
on the acquisition, discovery and development of gold and precious metals
projects worldwide. The Company recognizes the potential of long-term
growth in the gold sector, as recent gold price increases will continue
fueled by high demand.


Rincon Resources (OTC: RIRI) has recently acquired the 'Tudor Gold Property'.
The Tudor Property is located in Tudor and Grimsthorpe Townships in the
Madoc-Bancroft region of eastern Ontario, Canada. The property consists
of 22 contiguous unpatented mining claims containing 60 units covering
approximately 2965 acres of land. The Tudor Property is crossed by a
series of rhyolite tuffaceous units which extend over 20 kilometres (12.4
miles) through Tudor, Grimsthorpe and Cashel Townships. On the property,


entire length of the property and averages 1 to 125 metres (410 ft) wide.
In a 3.5 kilometre (2.2 miles) section where the rhyolite unit averages
50 to 125 metres (164 - 410 ft) wide, a series of en echelon fractures
ranging 0.5 to 22 metres (1.6 - 72.2 ft) wide form the gold structure
called the "Main Prospect." Typical gold-bearing rhyolite is mylonitized,


pyrite.
In August, Rincon Resources initiated a series of exploration programs
for the Tudor Property which focused on the Main Prospect and Vardy -

- - Homestake -- Hodgson Zone's. Mr. Graeme F. Scott President of Rincon
states, "The exploration focus of Rincon for Phase 1 will be to initially
confirm and validate the historical data and move towards evaluating
new gold occurrences in a comprehensive manner. Mapping, sampling, prospecting,


to a Phase 2 -- 'sizable drill program.' From historical data, Rincon
is confident that a resource exists in the Main Prospect and this resource
will be enhanced by gold mineralization in the Vardy -- Homestake --
Hodgson Zones." An initial drill program will test depth extensions and
lateral continuity of the gold-bearing structures in the Main Prospect
and the results will initiate the formation of a database for tonnage
and grade calculations.


We have heard that the results of the exploration programs are excellent!
We expect a continuous flow of huge news announcements detailing the
highly profitable chain of events to follow for RIRI in the near future.
We can state from our judicious research that we are not alone in viewing
RIRI as one of those extremely rare opportunities where the impact of
a major news event simultaneously boosts the value of a company while
ultimately providing substantial reward for its shareholders.

ajjtxq

Bug#261251: [Crusoe CMS bug] Getting a CMS 4.5 for your laptop...

2004-10-20 Thread Emmanuel Fleury 
Hi all,

It's a long time that I have started hunting the bug of the Xserver on
my Vaio PCG-C1MZX and the final result is here:
http://www.cs.auc.dk/~fleury/bug_cms/

Is it satisfactory ???

I don't think so because the bug can appear in any other software and it
will start again. Moreover, I know that the CMS (Code Morphing Software)
4.4 and 4.5 are not buggy. So, having an update would solve the problem
at once (and get better performance for the machine).

But, now it is a matter to convince Sony that we really need this patch
(no need to contact Transmeta because they will just say that it's not
their business). So, I tried...

I went through http://www.sony.net/SonyInfo/Support/ (For the Fujitsu
owner, you should find the equivalent with Google)

I selected "Japan" because my machine is a Japanese import and the
support is only in Japan.

And I sent this mail:

**

Hi,

I own a Vaio PCG-C1MZX (japanese import) with a Transmeta Crusoe
processor. I discovered a bug in the firmware of the Transmeta processor
(see: http://www.cs.auc.dk/~fleury/bug_cms/index.html). Actually, a lot
of customers seems to have the exact same problem (I can produce a list
of the one I know and probably contact some others).

I also know that the versions 4.4.x and upper of the firmware are not
buggy.

So, I would like to know when an upgrade of the firmware will be
available.

My Serial Number is: 28379010-1100213
My UUID: fa9a2c80-bf92-11d3-826b-080046476aa3

**

You can find your serial number in the BIOS (press  at boot time)
or written on the back of your laptop.

Then, I got this answer:

**

We do not confirm any problems for the CPU on the original shipping
condition, Japanese OS. Thus, we are afraid we do no have an exact plan
for firmware update.

Below URL shows all update programs we are providing for your model.
(All programs are for original Japanese OS, and no verification for
other OS)

http://vcl.vaio.sony.co.jp/support/note/pcg-c1mzx.html#download

For your information, Please understand we can provide the support for
the PC only under the original condition (with Japanese OS). Note that
unique functions of VAIO such as bundled software, Hotkey, Jog Dial,
Memory stick, and so on may not work well on different OS. We are afraid
Changing the OS is 100% on your responsibility, and it would be
basically out of support except repair work service for hardware
problem.

**

My first error was to claim that I had a problem with Linux and not with
Windows XP. So, I had to change a bit my formulation of the problem. I
admit that I made up a little story just to justify the update (I guess
Windows XP must have some problems also, I guess that if we compile the
Xserver for Windows Xp we will have some kind of problems as well).

**

Dear Sony Vaio Tech support,

Thank you for the link of the firmware updates.

I solved several problems in my Windows XP with this.

I perfectly understand that you cannot support all the operating
systems. And I take the whole responsibility for the Linux part of my
Vaio. 

Unfortunately, the bug of the CMS (which is OS independant and that I
experiment also under Windows XP from time to time) isn't solved from
these updates. My Windows XP is still randomly refusing to boot from
time to time and only a hard reboot can solve the problem (actually
applying service pack 2 made it worst).

Could you be kind enough to tell me where I can get an upgrade of the
Transmeta firmware for Windows XP for this bug ?

Note: The description of the problem is mainly formulated for Linux,
only because as I have access to the sources, it allows me to figure out
what was going wrong with the machine.

I would like to thank you in advance for your reply

**

I love the trick about the "Service Pack 2". :)

Then I got this reply:

**

Thank you for your kind understanding.

Unfortunately, we do not have any information of the plan to release
Transmeta firmware for XP.

We would like to help you, but we are afraid we have no information for
your question, [where I can get an upgrade of the Transmeta firmware for
Windows XP for this bug?]

We are deeply sorry, but please understand it.

**

The FAQ is totally useless because it covers only computers which have
to be repaired... and in our case we need an update of the firmware.

So, I tried again:

**

Dear Sony Vaio Tech-support,

Thanks for your reply.

On Tue, 2004-10-19 at 11:43, [EMAIL PROTECTED] wrote:
> 
> Unfortunately, we do not have any information of the plan
>  to release Transmeta firmware for XP.
> 
> We would like to help you, 
> but we are afraid we have no information for your question, 
> [where I can get an upgrade of the Transmeta
>  firmware for Windows XP for this bug?]

Could give me a way to contact somebody which can do something to fix
this annoying bug in XP ?

I am no Windows XP expert, but I can try to provide a full description
of the bug and maybe some logs if I c

Bug#234556: [Crusoe CMS bug] Getting a CMS 4.5 for your laptop...

2004-10-20 Thread Emmanuel Fleury 
Hi all,

It's a long time that I have started hunting the bug of the Xserver on
my Vaio PCG-C1MZX and the final result is here:
http://www.cs.auc.dk/~fleury/bug_cms/

Is it satisfactory ???

I don't think so because the bug can appear in any other software and it
will start again. Moreover, I know that the CMS (Code Morphing Software)
4.4 and 4.5 are not buggy. So, having an update would solve the problem
at once (and get better performance for the machine).

But, now it is a matter to convince Sony that we really need this patch
(no need to contact Transmeta because they will just say that it's not
their business). So, I tried...

I went through http://www.sony.net/SonyInfo/Support/ (For the Fujitsu
owner, you should find the equivalent with Google)

I selected "Japan" because my machine is a Japanese import and the
support is only in Japan.

And I sent this mail:

**

Hi,

I own a Vaio PCG-C1MZX (japanese import) with a Transmeta Crusoe
processor. I discovered a bug in the firmware of the Transmeta processor
(see: http://www.cs.auc.dk/~fleury/bug_cms/index.html). Actually, a lot
of customers seems to have the exact same problem (I can produce a list
of the one I know and probably contact some others).

I also know that the versions 4.4.x and upper of the firmware are not
buggy.

So, I would like to know when an upgrade of the firmware will be
available.

My Serial Number is: 28379010-1100213
My UUID: fa9a2c80-bf92-11d3-826b-080046476aa3

**

You can find your serial number in the BIOS (press  at boot time)
or written on the back of your laptop.

Then, I got this answer:

**

We do not confirm any problems for the CPU on the original shipping
condition, Japanese OS. Thus, we are afraid we do no have an exact plan
for firmware update.

Below URL shows all update programs we are providing for your model.
(All programs are for original Japanese OS, and no verification for
other OS)

http://vcl.vaio.sony.co.jp/support/note/pcg-c1mzx.html#download

For your information, Please understand we can provide the support for
the PC only under the original condition (with Japanese OS). Note that
unique functions of VAIO such as bundled software, Hotkey, Jog Dial,
Memory stick, and so on may not work well on different OS. We are afraid
Changing the OS is 100% on your responsibility, and it would be
basically out of support except repair work service for hardware
problem.

**

My first error was to claim that I had a problem with Linux and not with
Windows XP. So, I had to change a bit my formulation of the problem. I
admit that I made up a little story just to justify the update (I guess
Windows XP must have some problems also, I guess that if we compile the
Xserver for Windows Xp we will have some kind of problems as well).

**

Dear Sony Vaio Tech support,

Thank you for the link of the firmware updates.

I solved several problems in my Windows XP with this.

I perfectly understand that you cannot support all the operating
systems. And I take the whole responsibility for the Linux part of my
Vaio. 

Unfortunately, the bug of the CMS (which is OS independant and that I
experiment also under Windows XP from time to time) isn't solved from
these updates. My Windows XP is still randomly refusing to boot from
time to time and only a hard reboot can solve the problem (actually
applying service pack 2 made it worst).

Could you be kind enough to tell me where I can get an upgrade of the
Transmeta firmware for Windows XP for this bug ?

Note: The description of the problem is mainly formulated for Linux,
only because as I have access to the sources, it allows me to figure out
what was going wrong with the machine.

I would like to thank you in advance for your reply

**

I love the trick about the "Service Pack 2". :)

Then I got this reply:

**

Thank you for your kind understanding.

Unfortunately, we do not have any information of the plan to release
Transmeta firmware for XP.

We would like to help you, but we are afraid we have no information for
your question, [where I can get an upgrade of the Transmeta firmware for
Windows XP for this bug?]

We are deeply sorry, but please understand it.

**

The FAQ is totally useless because it covers only computers which have
to be repaired... and in our case we need an update of the firmware.

So, I tried again:

**

Dear Sony Vaio Tech-support,

Thanks for your reply.

On Tue, 2004-10-19 at 11:43, [EMAIL PROTECTED] wrote:
> 
> Unfortunately, we do not have any information of the plan
>  to release Transmeta firmware for XP.
> 
> We would like to help you, 
> but we are afraid we have no information for your question, 
> [where I can get an upgrade of the Transmeta
>  firmware for Windows XP for this bug?]

Could give me a way to contact somebody which can do something to fix
this annoying bug in XP ?

I am no Windows XP expert, but I can try to provide a full description
of the bug and maybe some logs if I c

Re: xfree86_4.1.0-16woody4_alpha.changes REJECTED

2004-10-20 Thread Jeroen van Wolffelaar 
(replying to my own mail at gun^Wflamethrower-point)

On Mon, Oct 18, 2004 at 03:02:47PM +0200, Jeroen van Wolffelaar wrote:
> On Mon, Oct 18, 2004 at 07:44:29AM -0500, Branden Robinson wrote:
> > Is there a FAQ somewhere that will tell me why I always get "REJECTED"
> > mails from katie after submitting security-fixed packages to the Debian
> > Security Team?
> > 
> > I get one for each architecture.
> > 
> > I seem to remember asking Debian Installer
> > <[EMAIL PROTECTED]> before, but never getting an answer.
> 
> The problem is that stable-security is a separate archive, and requires
> a sourceful upload. Give the '-sa' option to dpkg-buildpackage to
> overrule the heuristic that says only -1 and -0 packages need to have
> their source included.

Branden Robinson told me that however he did prepare the upload, it was
his understanding that the security team would not use it as-is, but
rebuild it. They didn't, and due to Branden's assumption, he didn't
think he needed to follow the guidelines specific to how exactly to
dpkg-buildpackage the upload for security updates.
 
> Also see http://www.debian.org/doc/developers-reference/ch-pkgs#s-bug-security
> which says to simply mail updated packages to the security team, and to
> not normally upload them yourself.

So it was the security team who uploaded Branden's packages as-is. Sorry
for assuming wrong, but something like this is uncheckable as the
signature was Branden's.

> A subsection of this section has also the answer to your question:
> 
> | Unless the upstream source has been uploaded to security.debian.org
> | before (by a previous security update), build the upload with full
> | upstream source (dpkg-buildpackage -sa). If there has been a previous
> | upload to security.debian.org with the same upstream version, you may
> | upload without upstream source (dpkg-buildpackage -sd).

This text is by the way incomplete. It should say "If there has been a
previous upload ... same upstream version _since the latest point
release_, you may upload without upstream source". Or even better, just
change it to 'always use -sa', as having multiple security updates for
one package between the same point releases is rare, and even if so, the
extra bandwidth used during upload is neglectible (and it can't hurt).

--Jeroen

-- 
Jeroen van Wolffelaar
[EMAIL PROTECTED] (also for Jabber & MSN; ICQ: 33944357)
http://Jeroen.A-Eskwadraat.nl

X Strike Force XOrg SVN commit: r67 - / xorg-template xorg-template/trunk xorg-template/trunk/debian

2004-10-20 Thread X Strike Force SVN Repository Admin 
Author: fabbione
Date: 2004-10-20 03:11:37 -0500 (Wed, 20 Oct 2004)
New Revision: 67

Added:
   xorg-template/
   xorg-template/branches/
   xorg-template/tags/
   xorg-template/trunk/
   xorg-template/trunk/debian/
   xorg-template/trunk/debian/CHANGESETS
   xorg-template/trunk/debian/MANIFEST.any
   xorg-template/trunk/debian/TODO
   xorg-template/trunk/debian/changelog
   xorg-template/trunk/debian/compat
   xorg-template/trunk/debian/control
   xorg-template/trunk/debian/patches/
   xorg-template/trunk/debian/rules
Log:
Create standard template for xorg projects/packages.
NOTE: do NOT set the Id keyword on these files!


Added: xorg-template/trunk/debian/CHANGESETS
===
--- xorg-template/trunk/debian/CHANGESETS   2004-10-20 06:42:51 UTC (rev 66)
+++ xorg-template/trunk/debian/CHANGESETS   2004-10-20 08:11:37 UTC (rev 67)
@@ -0,0 +1,14 @@
+Changeset Log
+=
+
+$Id$
+
+This file identifies trunk revisions that should be handled (e.g., merged) as a
+unit.  Standalone updates to the TODO or CHANGESETS files are not recorded 
here.
+(It should always be safe to merge the latest version of TODO or CHANGESETS
+files anywhere.)
+
+* Import initial debian/* files
+
+
+vim:set ai et sts=4 sw=4 tw=80:

Added: xorg-template/trunk/debian/MANIFEST.any
===

Added: xorg-template/trunk/debian/TODO
===
--- xorg-template/trunk/debian/TODO 2004-10-20 06:42:51 UTC (rev 66)
+++ xorg-template/trunk/debian/TODO 2004-10-20 08:11:37 UTC (rev 67)
@@ -0,0 +1,20 @@
+To-Do List
+==
+
+$Id$
+
+As items are completed, move them to the CHANGESETS file.  The release manager
+has discretion to identify items that must be fixed for the next package
+release.
+
+Items under actual package version headings are listed in descending order of
+priority; that is, the most important items come first.
+
+6.8.1-1
+---
+
+* Add proper description to the package.
+* Add copyright file from xorg package (when ready).
+* debian/control needs a lot of love due to binary packages reorganization.
+
+vim:set ai et sts=4 sw=4 tw=80:

Added: xorg-template/trunk/debian/changelog
===
--- xorg-template/trunk/debian/changelog2004-10-20 06:42:51 UTC (rev 66)
+++ xorg-template/trunk/debian/changelog2004-10-20 08:11:37 UTC (rev 67)
@@ -0,0 +1,9 @@
[EMAIL PROTECTED]@ (6.8.1-0+SVN) unstable; urgency=low
+
+  * First release.
+
+ -- Fabio M. Di Nitto <[EMAIL PROTECTED]>  Wed, 22 Sep 2004 13:51:39 +0200
+
+  $Id$
+
+  vim:set ai et sts=2 sw=2 tw=78:

Added: xorg-template/trunk/debian/compat
===
--- xorg-template/trunk/debian/compat   2004-10-20 06:42:51 UTC (rev 66)
+++ xorg-template/trunk/debian/compat   2004-10-20 08:11:37 UTC (rev 67)
@@ -0,0 +1 @@
+4

Added: xorg-template/trunk/debian/control
===
--- xorg-template/trunk/debian/control  2004-10-20 06:42:51 UTC (rev 66)
+++ xorg-template/trunk/debian/control  2004-10-20 08:11:37 UTC (rev 67)
@@ -0,0 +1,12 @@
+Source: [EMAIL PROTECTED]@
+Section: x11
+Priority: optional
+Maintainer: Debian X Strike Force 
+Uploaders: Branden Robinson <[EMAIL PROTECTED]>, Fabio M. Di Nitto <[EMAIL 
PROTECTED]>
+Standards-Version: 3.6.1
+Build-Depends-Indep: dpkg (>= 1.7.0), dbs, debhelper (>= 4.1.16), xutils-devel 
(>= 6.8.1-0+SVN)
+
+Package: @FOO@
+Architecture: all|any
+Description: @BAR@
+ @BAZ@

Added: xorg-template/trunk/debian/rules
===
--- xorg-template/trunk/debian/rules2004-10-20 06:42:51 UTC (rev 66)
+++ xorg-template/trunk/debian/rules2004-10-20 08:11:37 UTC (rev 67)
@@ -0,0 +1,98 @@
+#!/usr/bin/make -f
+# Original by Fabio M. Di Nitto <[EMAIL PROTECTED]>
+# Licensed under the GNU General Public License, version 2.  See the file
+# /usr/share/common-licenses/GPL or .
+
+# $Id: rules 54 2004-10-19 08:45:53Z fabbione $
+
+# debhelper
+export DH_OPTIONS
+
+# Use the DBS archive/patch handling system.
+SCRIPT_DIR = /usr/share/dbs
+
+TAR_DIR = xc
+include $(SCRIPT_DIR)/dbs-build.mk
+
+SOURCE_TREE=build-tree/xc
+SOURCE_DIR=build-tree
[EMAIL PROTECTED]@
+
+# dpkg-arch rules
+ifeq (,$(DEB_BUILD_GNU_TYPE))
+  include $(SCRIPT_DIR)/dpkg-arch.mk
+endif
+
+# Determine our architecture.
+include /usr/share/xorg/dbuild-scripts/arch.mk
+
+# Import standard check-manifest.
+include /usr/share/xorg/dbuild-scripts/check-manifest.mk
+
+# Import anal patch-audit check.
+include /usr/share/xorg/dbuild-scripts/patch-audit.mk
+
+configure: $(STAMP_DIR)/configure
+$(STAMP_DIR)/configure: $(patched)
+   dh_testdir
+   abspath=`pwd` && \
+   cd $(SOURCE_TREE)/$(PROJECT_DIR) && \
+ imake -I/u

X Strike Force XFree86 SVN commit: r1967 - in trunk/debian: . patches

2004-10-20 Thread X Strike Force SVN Repository Admin 
Author: branden
Date: 2004-10-20 01:44:18 -0500 (Wed, 20 Oct 2004)
New Revision: 1967

Added:
   trunk/debian/patches/914_debian_Xserver_send_bugs_to_us.diff
Modified:
   trunk/debian/CHANGESETS
   trunk/debian/changelog
Log:
Replace XFree86 X server pre-release banner message with long boilerplate
that declaims the release as heavily modified by Debian, and directs users
to the Debian Bug Tracking System and the Debian X FAQ instead of XFree86
mailing lists; also replace an occurence of an XFree86 mailing list
address in a tseng driver message (patch #914).


Modified: trunk/debian/CHANGESETS
===
--- trunk/debian/CHANGESETS 2004-10-18 18:03:43 UTC (rev 1966)
+++ trunk/debian/CHANGESETS 2004-10-20 06:44:18 UTC (rev 1967)
@@ -190,4 +190,11 @@
 xconsole-related logic is not restored.  (Closes: #275329)
 1966
 
+Replace XFree86 X server pre-release banner message with long boilerplate
+that declaims the release as heavily modified by Debian, and directs users
+to the Debian Bug Tracking System and the Debian X FAQ instead of XFree86
+mailing lists; also replace an occurence of an XFree86 mailing list
+address in a tseng driver message (patch #914).
+1967
+
 vim:set ai et sts=4 sw=4 tw=80:

Modified: trunk/debian/changelog
===
--- trunk/debian/changelog  2004-10-18 18:03:43 UTC (rev 1966)
+++ trunk/debian/changelog  2004-10-20 06:44:18 UTC (rev 1967)
@@ -91,6 +91,12 @@
 xdm.install and MANIFEST.* files to ship Xreset script.  The old
 xconsole-related logic is not restored.  (Closes: #275329)
 
+  * Replace XFree86 X server pre-release banner message with long boilerplate
+that declaims the release as heavily modified by Debian, and directs users
+to the Debian Bug Tracking System and the Debian X FAQ instead of XFree86
+mailing lists; also replace an occurence of an XFree86 mailing list
+address in a tseng driver message (patch #914).
+
   Changes by Denis Barbier and Fabio M. Di Nitto:
 
   * Edit xc/programs/xkbcomp/symbols/pc/Imakefile so that the new pc/us_intl
@@ -161,7 +167,7 @@
 + Set UseBios default to "no" for PROSAVAGE_DDR and PROSAVAGE_DDRK, as
   described at http://www.probo.com/timr/savage40.html >.
 
- -- Branden Robinson <[EMAIL PROTECTED]>  Mon, 18 Oct 2004 12:57:18 -0500
+ -- Branden Robinson <[EMAIL PROTECTED]>  Wed, 20 Oct 2004 00:38:46 -0500
 
 xfree86 (4.3.0.dfsg.1-8) unstable; urgency=high
 

Added: trunk/debian/patches/914_debian_Xserver_send_bugs_to_us.diff
===
--- trunk/debian/patches/914_debian_Xserver_send_bugs_to_us.diff
2004-10-18 18:03:43 UTC (rev 1966)
+++ trunk/debian/patches/914_debian_Xserver_send_bugs_to_us.diff
2004-10-20 06:44:18 UTC (rev 1967)
@@ -0,0 +1,74 @@
+$Id$
+
+The XFree86 Project, Inc., is no longer Debian's upstream for the X Window
+System, and in any event our source tree is patched to the moon.  Don't
+send our users to XFree86's mailing list or private patch list.
+
+This patch by Branden Robinson.
+
+diff -urN xc/programs/Xserver/hw/xfree86~/common/xf86Init.c 
xc/programs/Xserver/hw/xfree86/common/xf86Init.c
+--- xc/programs/Xserver/hw/xfree86~/common/xf86Init.c  2004-10-19 
14:05:13.0 -0500
 xc/programs/Xserver/hw/xfree86/common/xf86Init.c   2004-10-19 
14:09:43.0 -0500
+@@ -1683,6 +1683,7 @@
+ #ifndef OSVENDOR
+ #define OSVENDOR ""
+ #endif
++/* PRE_RELEASE is unused in Debian. */
+ #ifndef PRE_RELEASE
+ #define PRE_RELEASE XF86_VERSION_SNAP
+ #endif
+@@ -1690,15 +1691,7 @@
+ static void
+ xf86PrintBanner()
+ {
+-#if PRE_RELEASE
+-  ErrorF("\n"
+-"This is a pre-release version of XFree86, and is not supported in any\n"
+-"way.  Bugs may be reported to XFree86@XFree86.Org and patches 
submitted\n"
+-"to [EMAIL PROTECTED]  Before reporting bugs in pre-release versions,\n"
+-"please check the latest version in the XFree86 CVS repository\n"
+-"(http://www.XFree86.Org/cvs).\n");
+-#endif
+-  ErrorF("\nXFree86 Version %d.%d.%d", XF86_VERSION_MAJOR, XF86_VERSION_MINOR,
++  ErrorF("XFree86 Version %d.%d.%d", XF86_VERSION_MAJOR, XF86_VERSION_MINOR,
+   XF86_VERSION_PATCH);
+ #if XF86_VERSION_SNAP > 0
+   ErrorF(".%d", XF86_VERSION_SNAP);
+@@ -1733,8 +1726,20 @@
+ #if defined(BUILDERSTRING)
+   ErrorF("%s \n",BUILDERSTRING);
+ #endif
+-  ErrorF("\tBefore reporting problems, check http://www.XFree86.Org/\n";
+-   "\tto make sure that you have the latest version.\n");
++  ErrorF("\n"
++"This version of XFree86 has been extensively modified by the Debian\n"
++"Project, and is not supported by the XFree86 Project, Inc., in any\n"
++"way.  Bugs should be reported to the Debian Bug Tracking System; see\n"
++"http://www.debian.org/Bugs/Reporting >.\n"
++"\n"
++"We strongly encourage the use of the \"reportbug\

X Strike Force XOrg SVN commit: r66 - in xorg-doc/trunk/debian: . patches

2004-10-20 Thread X Strike Force SVN Repository Admin 
Author: fabbione
Date: 2004-10-20 01:42:51 -0500 (Wed, 20 Oct 2004)
New Revision: 66

Added:
   xorg-doc/trunk/debian/patches/104_sparc_fix_GL_library.diff
Modified:
   xorg-doc/trunk/debian/CHANGESETS
Log:
* Import all xfree86/debian/patches related to xc/extras/


Including diff would make mail exceed size limit of 25 bytes.
Use "svn diff -r 65:66" to view diff.

X Strike Force XOrg SVN commit: r65 - in xorg-config/trunk/debian: . patches

2004-10-20 Thread X Strike Force SVN Repository Admin 
Author: fabbione
Date: 2004-10-20 00:20:35 -0500 (Wed, 20 Oct 2004)
New Revision: 65

Added:
   xorg-config/trunk/debian/patches/008_fix_xgetpw_macro.diff
Modified:
   xorg-config/trunk/debian/CHANGESETS
Log:
* Import all xfree86/debian/patches related to xc/include top level directory.



Modified: xorg-config/trunk/debian/CHANGESETS
===
--- xorg-config/trunk/debian/CHANGESETS 2004-10-20 03:42:41 UTC (rev 64)
+++ xorg-config/trunk/debian/CHANGESETS 2004-10-20 05:20:35 UTC (rev 65)
@@ -112,4 +112,7 @@
 * Add some *cough*extra*cough* depends.
 63
 
+* Import all xfree86/debian/patches related to xc/include top level directory.
+65
+
 vim:set ai et sts=4 sw=4 tw=80:

Added: xorg-config/trunk/debian/patches/008_fix_xgetpw_macro.diff
===
--- xorg-config/trunk/debian/patches/008_fix_xgetpw_macro.diff  2004-10-20 
03:42:41 UTC (rev 64)
+++ xorg-config/trunk/debian/patches/008_fix_xgetpw_macro.diff  2004-10-20 
05:20:35 UTC (rev 65)
@@ -0,0 +1,90 @@
+$Id$
+
+Fix the _XGetpwnam macro to be more consistent; this patch by Robert Millan.
+
+--- xc/include/Xos_r.h.old 2003-04-11 14:54:50.0 +0200
 xc/include/Xos_r.h 2003-04-11 12:56:19.0 +0200
+@@ -217,8 +217,8 @@
+  *
+  * typedef ... _Xgetpwparams;
+  *
+- * struct passwd* _XGetpwnam(const char *name, _Xgetpwparams);
+- * struct passwd* _XGetpwuid(uid_t uid, _Xgetpwparams);
++ * struct passwd* _XGetpwnam(const char *name, _Xgetpwparams, struct **dummy);
++ * struct passwd* _XGetpwuid(uid_t uid, _Xgetpwparams, struct **dummy);
+  */
+ 
+ #if defined(X_INCLUDE_PWD_H) && !defined(_XOS_INCLUDED_PWD_H)
+@@ -238,8 +238,8 @@
+ extern struct passwd *getpwuid(), *getpwnam();
+ # endif
+ typedef int _Xgetpwparams;/* dummy */
+-# define _XGetpwuid(u,p)  getpwuid((u))
+-# define _XGetpwnam(u,p)  getpwnam((u))
++# define _XGetpwuid(u,p,s)getpwuid((u))
++# define _XGetpwnam(u,p,s)getpwnam((u))
+ 
+ #elif !defined(XOS_USE_MTSAFE_PWDAPI) || defined(XNO_MTSAFE_PWDAPI)
+ /* UnixWare 2.0, or other systems with thread support but no _r API. */
+@@ -316,12 +316,12 @@
+ ((p).pwp = &(p).pws), \
+ 0 )
+ #endif
+-# define _XGetpwuid(u,p) \
++# define _XGetpwuid(u,p,s) \
+ ( (_Xos_processLock), \
+   (((p).pwp = getpwuid((u))) ? _Xpw_copyPasswd(p), 0 : 0), \
+   (_Xos_processUnlock), \
+   (p).pwp )
+-# define _XGetpwnam(u,p) \
++# define _XGetpwnam(u,p,s) \
+ ( (_Xos_processLock), \
+   (((p).pwp = getpwnam((u))) ? _Xpw_copyPasswd(p), 0 : 0), \
+   (_Xos_processUnlock), \
+@@ -336,21 +336,21 @@
+ } _Xgetpwparams;
+ # if defined(_POSIX_REENTRANT_FUNCTIONS) || !defined(SVR4) || defined(Lynx)
+ #  ifndef Lynx
+-#   define _XGetpwuid(u,p) \
+-((getpwuid_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf)) == -1) ? NULL : 
&(p).pws)
+-#   define _XGetpwnam(u,p) \
+-((getpwnam_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf)) == -1) ? NULL : 
&(p).pws)
++#   define _XGetpwuid(u,p,s) \
++((getpwuid_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf),(s)) == -1) ? NULL : 
&(p).pws)
++#   define _XGetpwnam(u,p,s) \
++((getpwnam_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf),(s)) == -1) ? NULL : 
&(p).pws)
+ #  else /* Lynx */
+-#   define _XGetpwuid(u,p) \
+-((getpwuid_r(&(p).pws,(u),(p).pwbuf,sizeof((p).pwbuf)) == -1) ? NULL : 
&(p).pws)
+-#   define _XGetpwnam(u,p) \
+-((getpwnam_r(&(p).pws,(u),(p).pwbuf,sizeof((p).pwbuf)) == -1) ? NULL : 
&(p).pws)
++#   define _XGetpwuid(u,p,s) \
++((getpwuid_r(&(p).pws,(u),(p).pwbuf,sizeof((p).pwbuf),(s)) == -1) ? NULL : 
&(p).pws)
++#   define _XGetpwnam(u,p,s) \
++((getpwnam_r(&(p).pws,(u),(p).pwbuf,sizeof((p).pwbuf),(s)) == -1) ? NULL : 
&(p).pws)
+ #  endif
+ # else /* SVR4 */
+-#  define _XGetpwuid(u,p) \
+-((getpwuid_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf)) == NULL) ? NULL : 
&(p).pws)
+-#  define _XGetpwnam(u,p) \
+-((getpwnam_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf)) == NULL) ? NULL : 
&(p).pws)
++#  define _XGetpwuid(u,p,s) \
++((getpwuid_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf),(s)) == NULL) ? NULL : 
&(p).pws)
++#  define _XGetpwnam(u,p,s) \
++((getpwnam_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf),(s)) == NULL) ? NULL : 
&(p).pws)
+ # endif /* SVR4 */
+ 
+ #else /* _POSIX_THREAD_SAFE_FUNCTIONS */
+@@ -367,10 +367,10 @@
+   struct passwd* pwp;
+ } _Xgetpwparams;
+ typedef int _Xgetpwret;
+-# define _XGetpwuid(u,p) \
++# define _XGetpwuid(u,p,s) \
+ ((getpwuid_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf),&(p).pwp) == -1) ? \
+  NULL : (p).pwp)
+-# define _XGetpwnam(u,p) \
++# define _XGetpwnam(u,p,s) \
+ ((getpwnam_r((u),&(p).pws,(p).pwbuf,sizeof((p).pwbuf),&(p).pwp) == -1) ? \
+  NULL : (p).pwp)
+ #endif /* X_INCLUDE_PWD_H */


Property changes on: xorg-config/trunk/debian/patches/008_fix_xgetpw_macro.diff
___
Name: svn:keywords
   + Id