Re: Problems with debconf in postinst

[Steve Langasek]

On Fri, Mar 23, 2007 at 05:58:09PM +0100, Jan Hauke Rahm wrote:
> Maybe you don't like me or my package but I try again... ;) Would
> someone please help me? It's a problem with the postinst-scipt. It just
> failes and I guess it's because of misuse of debconf or something like that.
> The script itself is very short, it's just asking to do something or
> not. I set DEBCONF_DEBUG=developer in the script but it didn't help me much.

> So then, the package is small, no very difficult stuff in there and if I
> used it right it's lintian- and linda-clean, too. :)

> The ITP bug can be found here [0] and the dsc-file is here [1].

> --- Original Message ---
> > Hey mentors!
> > 
> > I packaged Avelsieve (i set an ITP a few days ago) but when installing
> > it the postinst-script fails due to a debconf error. I would like you to
> > have a look at it because it's my first package.
> > You can find it here: http://downloads.jhr-online.de/avelsieve/

FWIW, you're likely to get better feedback if you help make it easier for
people to see the problem you're having.  What is the debconf error that you
get?  What is the postinst code that's failing?  (I've downloaded your
diff.gz at this point, but I don't see any obvious errors in it...)

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
[EMAIL PROTECTED]   http://www.debian.org/


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ITA/RFS: libspf2 -- Sender Policy Framework library, written in C

[Magnus Holmgren]

On Friday 23 March 2007 20:53, Mike Hommey wrote:
> On Fri, Mar 23, 2007 at 08:23:38PM +0100, Magnus Holmgren
> <[EMAIL PROTECTED]> wrote: (...)
>
> Have not taken a look at the package, but does the short description
>
> > Description: Sender Policy Framework library, written in C
>
> really have to say "written in C" ?

Perhaps not. But it was like that when I got it. :-)

Possibly it should say what it does instead of simply what SPF stands for.

-- 
Magnus Holmgren[EMAIL PROTECTED]
   (No Cc of list mail needed, thanks)


pgprzGeApiUBk.pgp
Description: PGP signature

Re: ITA/RFS: libspf2 -- Sender Policy Framework library, written in C

[Magnus Holmgren]

On Friday 23 March 2007 20:50, Martin Zobel-Helas wrote:
> Hi,
>
> I am a bit irritated by the following sentence in README.Debian-source:
> | It's completely out of date anyway.
>
> Could you please explain?

Well, it is. It's an expired I-D from 2004, and nowadays there's even a real 
RFC. But I could change the wording.

-- 
Magnus Holmgren[EMAIL PROTECTED]
   (No Cc of list mail needed, thanks)


pgpSAgOjgFqEZ.pgp
Description: PGP signature

Re: ITA/RFS: libspf2 -- Sender Policy Framework library, written in C

[Mike Hommey]

On Fri, Mar 23, 2007 at 08:23:38PM +0100, Magnus Holmgren <[EMAIL PROTECTED]> 
wrote:
(...)

Have not taken a look at the package, but does the short description

> Description: Sender Policy Framework library, written in C

really have to say "written in C" ?

Mike


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: ITA/RFS: libspf2 -- Sender Policy Framework library, written in C

[Martin Zobel-Helas]

Hi, 

I am a bit irritated by the following sentence in README.Debian-source:

| It's completely out of date anyway.

Could you please explain?

Greetings
Martin

-- 
[EMAIL PROTECTED] /root]# man real-life
No manual entry for real-life


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

ITA/RFS: libspf2 -- Sender Policy Framework library, written in C

[Magnus Holmgren]

retitle 372629 ITA: libspf2 -- Sender Policy Framework library, written in C
owner 372629 [EMAIL PROTECTED]
thanks

I have created a new version of libspf2 and intend to adopt it if I can find a 
sponsor (and/or co-maintainer). It fixes (hopefully) all outstanding bugs 
except one. 20_64bit_types.patch may need some testing. I hope that some DD 
is interested enough in SPF to take the time, and that he or she will find 
the package satisfactory.

The dsc, for download with e.g. dget, is at

 ftp://ftp.kibibyte.se/debian/pool/main/libs/libspf2/libspf2_1.2.5.dfsg-1.dsc

Description: Sender Policy Framework library, written in C
 libspf2 implements the Sender Policy Framework, a part of the SPF/SRS
 protocol pair. libspf2 is a library which allows email systems such
 as Sendmail, Postfix, Exim, Zmailer and MS Exchange to check SPF
 records and make sure that the email is authorized by the domain name
 that it is coming from. This prevents email forgery, commonly used by
 spammers, scammers and email viruses/worms.
 
  Homepage: http://www.libspf2.org/

License: GPL/BSD

Changelog entry:
  * New maintainer (Closes: #372629).
  * Repacked .orig.tar.gz without non-free (and obsolete) IETF Internet
Draft (Closes: #393390).
  * Merge updates from Ubuntu:
- Add debian/compat and Build-depend on debhelper >= 5.
- Add alternatives handling for /usr/bin/spfquery (Closes: #306875).
  - Conflict on libmail-spf-query-perl << 1:1.999.1-3.
  - Add postinst and prerm scripts.
- debian/copyright: update author address.
- debian/control: add final newline.
  * debian/control: 
* Change description of spfquery (Closes: #410592).
* Add homepage to package descriptions.
  * Reduce Debian diff by changing line endings with sed instead.
  * Further reduce Debian diff by eliminating config.sub and config.guess
from there. Build-depend on autotools-dev to ensure up-to-date
versions instead.
  * The autogenerated spf_lib_version.h was put in the wrong directory,
while there was a static spf_lib_version.h in the right directory.
Fix that with some rules in debian/rules.
  * Use simple-patchsys.mk to manage patches.
  * Apply 20_64bit_types.patch to hopefully prevent segfaults on 64-bit
architectures (Closes: #392793). Thanks to Thomas Jacob, Carsten
Koch-Mauthe and Herbert Straub.
  * debian/watch: added.
  * Update Standards-Version to 3.7.2 without changes.
  * Apply 20_spf_dns_include_std_headers.patch: Include arpa/nameser.h and
netdb.h from spf_dns.h instead of defining the constants needed unless
certain HAVE_ macros are defined (Closes: #405885).

-- 
Magnus Holmgren[EMAIL PROTECTED]
   (No Cc of list mail needed, thanks)


pgpSKTQ6FXThn.pgp
Description: PGP signature

Re: Using debconf to notify of serious postinst problems

[Colin Turner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Russ,

>> The problem is, as indicated in the comments, I wanted to use a "note"
>> template to warn / email the user if the credentials were wrong, before
>> trying to do what I could. Adding the input causes a lintian warning.
> 
> Other people have given you good suggestions, but I did want to mention
> that the lintian warning is just because lintian can't easily tell the
> difference between valid uses of debconf in postinst and prompting in
> postinst instead of config.  For cases where one is intentionally
> prompting in postinst on the basis of information that isn't available
> before that point, a lintian override is appropriate.

Thanks, notwithstanding all the helpful comments before, it's very
helpful to get an answer to that core issue too!

Thanks again,

CT.

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGBA0h0SwfPjLnaZYRAkP6AJ45tbuR7VEu8jeRhdMRZR8nZ32YBACfU2z+
8DzpXnxf9NamvE4jnlVfBa8=
=Ygim
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Using debconf to notify of serious postinst problems

[Russ Allbery]

Colin Turner <[EMAIL PROTECTED]> writes:

> 2. Using debconf to notify in postinst

> Part of the install is to create a database with given credentials and
> import a schema. I have debconf prompting for values and I'm
> successfully using these in the postinst script.

> My problem/worry is this. I am asking for the root MySQL password - if
> it is known - and letting the user know I'll purge this value straight
> after database creation and so on.

> Then, in postinst, I try to test the credentials before I go further

> -=-

>   if [ "$have_password" = "yes" ]
> then
> set +e
> # try a trivial query, logging in as MySQL root
> command_result=`echo "SELECT VERSION()" | mysql -h $data_hostname -u
> root --password=$root_db_password 2>&1`
> if [ "$?" -ne 0 ]
> then
>   # We don't have valid root credentials
>   have_password="no"
>   # Warn the user it's all gone fubar - but this makes lintian mad,
> remove for now
>   echo "WARNING! Invalid MySQL root credentials ..."
>   #db_input high opus/invalid_root_password || true
>   #db_go
> fi
>   fi

> -=-

> The problem is, as indicated in the comments, I wanted to use a "note"
> template to warn / email the user if the credentials were wrong, before
> trying to do what I could. Adding the input causes a lintian warning.

Other people have given you good suggestions, but I did want to mention
that the lintian warning is just because lintian can't easily tell the
difference between valid uses of debconf in postinst and prompting in
postinst instead of config.  For cases where one is intentionally
prompting in postinst on the basis of information that isn't available
before that point, a lintian override is appropriate.

-- 
Russ Allbery ([EMAIL PROTECTED])   


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Problems with debconf in postinst

[Jan Hauke Rahm]

Maybe you don't like me or my package but I try again... ;) Would
someone please help me? It's a problem with the postinst-scipt. It just
failes and I guess it's because of misuse of debconf or something like that.
The script itself is very short, it's just asking to do something or
not. I set DEBCONF_DEBUG=developer in the script but it didn't help me much.

So then, the package is small, no very difficult stuff in there and if I
used it right it's lintian- and linda-clean, too. :)

The ITP bug can be found here [0] and the dsc-file is here [1].

So, anyone? :)

Hauke

[0] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=414179
[1] http://downloads.jhr-online.de/avelsieve/avelsieve_1.9.7-1.dsc

--- Original Message ---
> Hey mentors!
> 
> I packaged Avelsieve (i set an ITP a few days ago) but when installing
> it the postinst-script fails due to a debconf error. I would like you to
> have a look at it because it's my first package.
> You can find it here: http://downloads.jhr-online.de/avelsieve/
> 
> Thanks a lot!
> 
> Hauke




signature.asc
Description: OpenPGP digital signature

Re: Using debconf to notify of serious postinst problems

[Colin Turner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Roberto,

Roberto C. Sánchez wrote:
> On Fri, Mar 23, 2007 at 01:42:30PM +, Colin Turner wrote:
>> 2. Using debconf to notify in postinst
>>
> Hi.  I'm not sure of the details of your software (I've not looked at
> it), but I will offer my recommendation as to the database issue.
> 
> Consider that installation may happen unattended.  If so, how will the
> admin be prompted?  I am not up to speed on my debconf-fu.  However, I
> would recommend that you differentiate between an interactive and a
> non-interactive installation.  In either case, you should include a
> script in some place like /usr/share/doc/opus/scripts (or something like
> that) called schema.mysql (or just .sql if it is generic enough to work
> on other servers).

I guess I was thinking that a) it's not unusual for dist-upgrades and so
on to halt on postinst due to config files and other issues and b)
debconf can send notes as emails if it doesn't show them to the end
user. I wasn't sure though, hence the question :-).

Nevertheless, that's a good idea. I already place the schema in
/usr/share/doc/sql_patch/ and that's where my shell script installs it
from. I can add manual instructions too. Neil's suggestion
(dbconfig-common) might take care of all of this anyway.

> You may also want to consider adding a /etc/defaults/opus with an
> "ENABLED=YES|NO" sort of option and have the startup or init script
> check that.  Then if the install is unattended, the admin has to go in
> later, create the databases and set the ENABLED variable in the defaults
> file.

That's a very good plan indeed. I'll look at that along with Neil's
suggestions.

Thanks for your time!

CT.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGA+c80SwfPjLnaZYRApGzAJ9GR6yGEqGFnnOYiDNNyv84jYnL9QCfflsM
ojd/PX34RqYdYkNyMke01cY=
=whSn
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Using debconf to notify of serious postinst problems

[Roberto C . Sánchez]

On Fri, Mar 23, 2007 at 01:42:30PM +, Colin Turner wrote:
> 
> 2. Using debconf to notify in postinst
> 
> Part of the install is to create a database with given credentials and
> import a schema. I have debconf prompting for values and I'm
> successfully using these in the postinst script.
> 
> My problem/worry is this. I am asking for the root MySQL password - if
> it is known - and letting the user know I'll purge this value straight
> after database creation and so on.
> 
Hi.  I'm not sure of the details of your software (I've not looked at
it), but I will offer my recommendation as to the database issue.

Consider that installation may happen unattended.  If so, how will the
admin be prompted?  I am not up to speed on my debconf-fu.  However, I
would recommend that you differentiate between an interactive and a
non-interactive installation.  In either case, you should include a
script in some place like /usr/share/doc/opus/scripts (or something like
that) called schema.mysql (or just .sql if it is generic enough to work
on other servers).

You may also want to consider adding a /etc/defaults/opus with an
"ENABLED=YES|NO" sort of option and have the startup or init script
check that.  Then if the install is unattended, the admin has to go in
later, create the databases and set the ENABLED variable in the defaults
file.

Regards,

-Roberto

-- 
Roberto C. Sánchez
http://people.connexer.com/~roberto
http://www.connexer.com


signature.asc
Description: Digital signature

Re: Using debconf to notify of serious postinst problems

[Colin Turner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Neil,

Neil Williams wrote:

>> Debian, since I am the upstream author too. It seems clear that Debian
>> still wants an original tarball created. Should I strip the "debian"
>> directory from my source code when creating the tarball?
> 
> Yes. If this package has any prospect of being useful outside Debian,
> create an upstream location (SourceForge etc.) and REMOVE debian/ from
> the distributed tarball. It is fine to keep debian/ in
> CVS/SVN/whatever - you can always use that for your own packaging.

Super, thanks for clearing that up. I have my own upstream location I
can use, and I'll add such tarballs there.

>> 2. Using debconf to notify in postinst
>>
>> Part of the install is to create a database with given credentials and
>> import a schema. I have debconf prompting for values and I'm
>> successfully using these in the postinst script.
> 
> There are handlers for this kind of operation - take a look at the
> source code for serendipity as an off-the-cuff example.

Just downloaded the .deb initially to look in the control directory.
That's a very interesting example, I'll certainly look more closely
since it's been quite a massive PITA implementing this will shell script
piping to mysql. Thanks for that. I'm looking through the source now.

>> Any help is welcome, the full source is visible here:

> You should provide the location to the build .dsc file normally, Debian
> is not usually concerned with creating a package from your CVS, the
> package is built from a tarball that you build/export from your CVS.

Thanks, I understood that, I just haven't uploaded the .deb .dsc files
anywhere yet, I wanted to resolve the above issues first.

Thanks again for that,

CT.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGA+F60SwfPjLnaZYRAiC/AKDLbhIBqPLE/2JO8JibEvNChEG6tACfZsUh
/TXzBeJeH/ek1uX1S96kaQ8=
=En3X
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Using debconf to notify of serious postinst problems

[Neil Williams]

On Fri, 23 Mar 2007 13:42:30 +
Colin Turner <[EMAIL PROTECTED]> wrote:

> I'm busy packaging my own software (OPUS, ITP Bug#415241) for
> submission, and I'm most of the way there. I have two questions
> though:
>
> 1. Original tarballs
>
> There obviously isn't an original tarball that I have patched for
> Debian, since I am the upstream author too. It seems clear that Debian
> still wants an original tarball created. Should I strip the "debian"
> directory from my source code when creating the tarball?

Yes. If this package has any prospect of being useful outside Debian,
create an upstream location (SourceForge etc.) and REMOVE debian/ from
the distributed tarball. It is fine to keep debian/ in
CVS/SVN/whatever - you can always use that for your own packaging.

If you are creating a package that is Debian-specific (something based
on dpkg or apt or only functional with .deb files etc.), then you can
consider a native package, hosted at e.g. alioth and then you do keep
the debian/ with the package.

> 2. Using debconf to notify in postinst
>
> Part of the install is to create a database with given credentials and
> import a schema. I have debconf prompting for values and I'm
> successfully using these in the postinst script.

There are handlers for this kind of operation - take a look at the
source code for serendipity as an off-the-cuff example.

> Any help is welcome, the full source is visible here:
>
> http://foss.ulster.ac.uk/cgi-bin/viewcvs.cgi/?root=opus
>
> if anyone wants to see more of the debian directory.

You should provide the location to the build .dsc file normally, Debian
is not usually concerned with creating a package from your CVS, the
package is built from a tarball that you build/export from your CVS.

--


Neil Williams
=
http://www.data-freedom.org/
http://www.nosoftwarepatents.com/
http://www.linux.codehelp.co.uk/



pgpZ9Xals7vN3.pgp
Description: PGP signature

Using debconf to notify of serious postinst problems

[Colin Turner]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi All,

I'm busy packaging my own software (OPUS, ITP Bug#415241) for
submission, and I'm most of the way there. I have two questions though:

1. Original tarballs

There obviously isn't an original tarball that I have patched for
Debian, since I am the upstream author too. It seems clear that Debian
still wants an original tarball created. Should I strip the "debian"
directory from my source code when creating the tarball?

2. Using debconf to notify in postinst

Part of the install is to create a database with given credentials and
import a schema. I have debconf prompting for values and I'm
successfully using these in the postinst script.

My problem/worry is this. I am asking for the root MySQL password - if
it is known - and letting the user know I'll purge this value straight
after database creation and so on.

Then, in postinst, I try to test the credentials before I go further

- -=-

  if [ "$have_password" = "yes" ]
then
set +e
# try a trivial query, logging in as MySQL root
command_result=`echo "SELECT VERSION()" | mysql -h $data_hostname -u
root --password=$root_db_password 2>&1`
if [ "$?" -ne 0 ]
then
  # We don't have valid root credentials
  have_password="no"
  # Warn the user it's all gone fubar - but this makes lintian mad,
remove for now
  echo "WARNING! Invalid MySQL root credentials ..."
  #db_input high opus/invalid_root_password || true
  #db_go
fi
  fi

- -=-

The problem is, as indicated in the comments, I wanted to use a "note"
template to warn / email the user if the credentials were wrong, before
trying to do what I could. Adding the input causes a lintian warning.
It's not *really* an input since it's just a warning screen, but is this
really bad form. Is there a better alternative?

I considered putting the test in the config script, but I thought I
couldn't rely on a dependent package being operational at that stage?

Any help is welcome, the full source is visible here:

http://foss.ulster.ac.uk/cgi-bin/viewcvs.cgi/?root=opus

if anyone wants to see more of the debian directory.

Thanks,

CT.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGA9lG0SwfPjLnaZYRAj9TAKDnqwqPQ3aXesT3IHMBSFt3yQI5YQCfWaZd
2H69NMpXJZ8Kkz2ZQ6S+5BU=
=nwyo
-END PGP SIGNATURE-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

RFS: ipp2p

[Rasmus Bøg Hansen]

Dear mentors,

I am looking for a sponsor for my package "ipp2p".

* Package name: ipp2p
  Version : 0.8.2-1
  Upstream Author : IPP2P team
* URL : http://www.ipp2p.org/
* License : GPL
  Section : net

It builds these binary packages:
ipp2p  - An extension to netfilter that recognizes P2P (iptables extension
ipp2p-source - An extension to netfilter that recognizes P2P traffic (kernel 
source)

The package is lintian and linda clean.

The upload would fix these bugs: 408258

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/i/ipp2p
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/i/ipp2p/ipp2p_0.8.2-1.dsc

I would be glad if someone uploaded this package for me.

Kind regards
 Rasmus Bøg Hansen

-- 
Rasmus Bøg Hansen   || [EMAIL PROTECTED]
Harrestrupvang 13A, 2th || http://www.zz9.dk
2500 Valby  || 

RFS: sigit (updated package)

[Rasmus Bøg Hansen]

Dear mentors,

I am looking for a sponsor for the new version 0.3.2-2
of my package "sigit". My sponsor has been unresponsive for a couple
of weeks, so I guess she is too busy at the time being.

It builds these binary packages:
sigit  - A small utility to change signatures randomly

The upload will fix bug #414543.

The package is lintian clean.

The package can be found on mentors.debian.net:
- URL: http://mentors.debian.net/debian/pool/main/s/sigit
- Source repository: deb-src http://mentors.debian.net/debian unstable main 
contrib non-free
- dget http://mentors.debian.net/debian/pool/main/s/sigit/sigit_0.3.2-2.dsc

I would be glad if someone uploaded this package for me.

Kind regards
 Rasmus Bøg Hansen

-- 
Rasmus Bøg Hansen   || [EMAIL PROTECTED]
Harrestrupvang 13A, 2th || http://www.zz9.dk
2500 Valby  || 

Re: RFS: wmsysmon (updated package)

[Nico Golde]

Hi,
* Luca Bedogni <[EMAIL PROTECTED]> [2007-03-23 12:35]:
> I am looking for a sponsor for the new version 0.7.7-6
> of my package "wmsysmon".
> 
> It builds these binary packages:
> wmsysmon   - WindowMaker dock-app for monitoring your system
> 
> The package is lintian clean.

W: wmsysmon: unquoted-string-in-menu-item /usr/share/menu/wmsysmon needs:2
W: wmsysmon: unquoted-string-in-menu-item /usr/share/menu/wmsysmon section:2

Please fix this and I will sponsor the upload.
Please mail me in private then.
Kind regards
Nico
-- 
Nico Golde - http://www.ngolde.de
JAB: [EMAIL PROTECTED] - GPG: 0x73647CFF
Forget about that mouse with 3/4/5 buttons,
gimme a keyboard with 103/104/105 keys!


pgpJdBt6PdOSn.pgp
Description: PGP signature

Re: As persuasive

[GCindy Marian]

We told you watch NNYR Yesterday
+25% in 1 day
It.s only just begun
Northamerican Energy Group Corp.
Symbol : NNYR
5 day Expected : $0.50 ( 500% profit )

Get in tomorrow or get left out!!

This is going to double in next 2 days
Real Comp with Real Products
Get in tomorrow or be left out!!

in the first half one night after getting just one first-half assist against  came together for them.   Anthony drew the foul and some of the loudest cheers  defense.  ''That team can blow you out and they can score in bunches,'' he said Iverson scored 44 points and dished out 15 assists in leading the Nuggets to  every shot in the world,'' Suns coach Mike D'Antoni said. ''They are hard to D'Antoni said. ''We're in a little bit of a funk right now. Discombobulated. We basket made it 111-73 heading into the fourth quarter.   ''That's another   Iverson said. ''To win four games in a row, you get a certain swagger about points - since their 129-127 double-overtime win at Dallas on Wednesday night. after firing Brian Ellerbe.  He inherited a mess, stemming from the Ed Martin 

- Original Message - 
From: "GCindy Marian" <[EMAIL PROTECTED]>

To: 
Sent: Thursday, March 22, 2007 8:27 PM
Subject: As persuasive



Check this company out
Northamerican E n e r g y Group Corp
SYm-N.N.Y.R
Cannot go wrong at 8 cents
Expected : .70 ( 1000 percent return!! )



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]