Re: Portmanager loop when trying to upgrade perl
On Sat, 3 May 2008 13:35:10 -0400 Sahil Tandon [EMAIL PROTECTED] wrote: Hi. I'm running FreeBSD 6.1. I have never had a problem with portmanager until today. I was trying to update amavisd-new. When I issued the upgrade command, portmanager started to update perl5.8. Everything was going fine until I realized it was looping. After the 3rd strike, I was told to look at the log. I am not able to glean much in the way of solutions, so hoping someone with a similar experience can help. I did see prior threads about the looping problem but I am still unable to update perl. What version of portmanager are you running? The last one is '0.4.1.9' I believe. It might have been nice if you had also posted any pertinent portions of the log file also. There was a looping problem in a very old version of portmanager; however, supposedly it had been corrected. Portmanager will not update itself if I remember correctly. I believe you have to do it manually. I might suggest the following. Assuming you have the latest version of portmanager: 1) Update your ports tree 2) Clean out '/usr/ports/distfiles' Not really necessary; however, it cannot hurt. 3) If available, run: portsclean -CDLP 4) Run: portmanager -u -p -y -l Good Luck! -- Gerard [EMAIL PROTECTED] Ban the bomb. Save the world for conventional warfare. signature.asc Description: PGP signature
Re: Portmanager loop when trying to upgrade perl
* Gerard [EMAIL PROTECTED] [2008-05-03 14:47:56 -0400]: On Sat, 3 May 2008 13:35:10 -0400 Sahil Tandon [EMAIL PROTECTED] wrote: Hi. I'm running FreeBSD 6.1. I have never had a problem with portmanager until today. I was trying to update amavisd-new. When I issued the upgrade command, portmanager started to update perl5.8. Everything was going fine until I realized it was looping. After the 3rd strike, I was told to look at the log. I am not able to glean much in the way of solutions, so hoping someone with a similar experience can help. I did see prior threads about the looping problem but I am still unable to update perl. What version of portmanager are you running? The last one is '0.4.1.9' I believe. It might have been nice if you had also posted any pertinent portions of the log file also. There was a looping problem in a very old version of portmanager; however, supposedly it had been corrected. Portmanager will not update itself if I remember correctly. I believe you have to do it manually. Sorry for not posting the log file; I meant to do this and forgot: autoConflicts 0 autoMoved 0 backUp 0 buildDependsAreLeaves 0 forced 0 interactive0 log1 pmMode 1 pristine 0 resume 0 Sat May 3 09:55:47 2008 perl-5.8.8_1/lang/perl5.8 MISSING perl-5.8.8_1 /lang/perl5.8 Sat May 3 10:06:45 2008 perl-5.8.8_1/lang/perl5.8 MISSING perl-5.8.8_1 /lang/perl5.8 Sat May 3 10:06:46 2008 perl-5.8.8_1/lang/perl5.8 make Strike 2 Sat May 3 10:25:21 2008 perl-5.8.8_1/lang/perl5.8 MISSING perl-5.8.8_1 /lang/perl5.8 Sat May 3 10:25:40 2008 perl-5.8.8_1/lang/perl5.8 make Strike 3, marking port as ignore/looping Sat May 3 10:25:40 2008 portmanager 0.4.1_9 INFO: finished with some ports not updated if --log was used see /var/log/portmanager.log Assuming you have the latest version of portmanager: I do: portmanager-0.4.1_9 1) Update your ports tree I did, via portsnap update. 2) Clean out '/usr/ports/distfiles' Not really necessary; however, it cannot hurt. Done. 3) If available, run: portsclean -CDLP Tried this. 4) Run: portmanager -u -p -y -l Will try this, though I am a bit reluctant to do an all-out update of everything! For what it's worth, I had a perl module installed via CPAN (instead of the ports tree, because the port does not exist), about which portmanager seems to complain. The port was for Net-DNS-Async. portmanager asks me to pkg_delete and re-install. I will try that and perhaps perl will then build/update properly. -- Sahil Tandon [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
I had (have?) several packages in the ports collection that needed updating, and recently someone in the list was talking about using portmanager -u to save on problems with updating; it doesn't touch the ports database, it won't mess up the collection, it walks dependencies automagically, etc...should be as easy as portmanager -u and letting it do it's magic, correct? I read the same thing, and thought I'd give it a shot. On the Dell 2650 this is running on (FBSD 4.9) *seems* to keep recompiling xfree86-4-server. Is there a way to tell if it is stuck in a loop? I had to stop it yesterday after it had been upgrading for several hours. The same thing happened to me. Not sure where it was stuck but I was getting a distinct sense of deja-vu watching the output (I don't really mean deja-vu but I can't think of a better way to say it). I left it for 30 hours, and then cancelled it. I'm going to try and run it again today, I'd like to know also if it will eventually get out of the loop, i.e if it is really a loop or something different. sorry that this post doesn't really help the situation cali ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
cali wrote: The same thing happened to me. Not sure where it was stuck but I was getting a distinct sense of deja-vu watching the output (I don't really mean deja-vu but I can't think of a better way to say it). I left it for 30 hours, and then cancelled it. I'm going to try and run it again today, I'd like to know also if it will eventually get out of the loop, i.e if it is really a loop or something different. I get that whenever I install X, there seem to be chunks of X that produce an effrct like watching a looping tape! - Mike Woods IT Technician ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
On Jan 26, 2005, at 4:38 AM, cali wrote: I had (have?) several packages in the ports collection that needed updating, and recently someone in the list was talking about using portmanager -u to save on problems with updating; it doesn't touch the ports database, it won't mess up the collection, it walks dependencies automagically, etc...should be as easy as portmanager -u and letting it do it's magic, correct? I read the same thing, and thought I'd give it a shot. On the Dell 2650 this is running on (FBSD 4.9) *seems* to keep recompiling xfree86-4-server. Is there a way to tell if it is stuck in a loop? I had to stop it yesterday after it had been upgrading for several hours. The same thing happened to me. Not sure where it was stuck but I was getting a distinct sense of deja-vu watching the output (I don't really mean deja-vu but I can't think of a better way to say it). I left it for 30 hours, and then cancelled it. I'm going to try and run it again today, I'd like to know also if it will eventually get out of the loop, i.e if it is really a loop or something different. sorry that this post doesn't really help the situation Actually the developer for portmanager contacted me about it. He asked for some logfiles, and I didn't think the list wanted a 300k zip file mass mailed so I was privately emailing him about the situation. He's looking into it and hoped to have a fix soon. He's been wonderful with response time to this error and I was glad to help with any logs or testing I could. He had hoped to have a fix in there soon, but I don't know if he found answers yet as to what caused the loop. -Bart ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
On Tuesday 25 January 2005 07:07 am, Bart Silverstrim wrote: I had (have?) several packages in the ports collection that needed updating, and recently someone in the list was talking about using portmanager -u to save on problems with updating; it doesn't touch the ports database, it won't mess up the collection, it walks dependencies automagically, etc...should be as easy as portmanager -u and letting it do it's magic, correct? On the Dell 2650 this is running on (FBSD 4.9) *seems* to keep recompiling xfree86-4-server. Is there a way to tell if it is stuck in a loop? I had to stop it yesterday after it had been upgrading for several hours. Can someone take a look at this status output and tell me if I need to do something to get a successful portmanager run, or verify that letting it go will eventually untangle whatever it's doing? The portmanager -s shows: # portmanager -s - --- --- PMGRrStatus 0.2.4_0 info: Creating inital data bases - --- --- awk: cmd. line:1: fatal: cannot open file `/usr/local/etc/portmanager/pm-020.conf' for reading (No such file or directory) You exposed a bug here, I'll look into it today. Portmanager should abort if this file is missing. What it is supposed to do is copy /usr/local/etc/portmanager/pm-020.conf.SAMPLE to /usr/local/etc/portmanager/pm-020.conf when it is missing so I will have to fix this, for now will you please do it manually? [snip] OLD p5-Convert-TNEF-0.17 built with old dependency p5-Mail-Tools-1.64, current dependency is p5-Mail-Tools-1.65 OLD p5-Digest-MD5-2.33 built with old dependency p5-Digest-1.08, current dependency is p5-Digest-1.10 OLD mod_php3-3.0.18_4 built with old dependency apache-1.3.31_6, current dependency is apache-1.3.33_1 OLD tcplist-2.2_1 built with old dependency lsof-4.72.2, current dependency is lsof-4.74 OLD squidGuard-1.2.0_1 built with old dependency squid-2.5.7_1, current dependency is squid-2.5.7_8 - --- --- status report finished = === === After you copy /usr/local/etc/portmanager/pm-020.conf.SAMPLE to /usr/local/etc/portmanager/pm-020.conf I would like to see a couple of cycles of portmanager -u output if you don't mind. Just run assuming your shell is tcsh portmanager -u portmanager.log if bash then portmanager -u 21 portmanager.log then monitor it with tail -f portmanager.log I just need to see where the loop occurs. I've been planning to post a patch tonight anyways and if there is something here to be fixed I'd like to include it in the patch. Thank you. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
On Wednesday 26 January 2005 05:38 am, Bart Silverstrim wrote: On Jan 26, 2005, at 4:38 AM, cali wrote: I had (have?) several packages in the ports collection that needed updating, and recently someone in the list was talking about using portmanager -u to save on problems with updating; it doesn't touch the ports database, it won't mess up the collection, it walks dependencies automagically, etc...should be as easy as portmanager -u and letting it do it's magic, correct? I read the same thing, and thought I'd give it a shot. On the Dell 2650 this is running on (FBSD 4.9) *seems* to keep recompiling xfree86-4-server. Is there a way to tell if it is stuck in a loop? I had to stop it yesterday after it had been upgrading for several hours. The same thing happened to me. Not sure where it was stuck but I was getting a distinct sense of deja-vu watching the output (I don't really mean deja-vu but I can't think of a better way to say it). I left it for 30 hours, and then cancelled it. I'm going to try and run it again today, I'd like to know also if it will eventually get out of the loop, i.e if it is really a loop or something different. sorry that this post doesn't really help the situation Actually the developer for portmanager contacted me about it. He asked for some logfiles, and I didn't think the list wanted a 300k zip file mass mailed so I was privately emailing him about the situation. He's looking into it and hoped to have a fix soon. He's been wonderful with response time to this error and I was glad to help with any logs or testing I could. He had hoped to have a fix in there soon, but I don't know if he found answers yet as to what caused the loop. -Bart Thanks Bart for your patience, this one required me to set up XFree86-4 on a FreeBSD 4.11 machine and back date all of the ports. So now I know that on December 1st, 2004 /usr/ports/graphics/xfree86-dri and /usr/ports/graphics/dri both existed and both report their name as dri-5.0.2,2 on that date. This caused portmanager to loop so I have duplicated the problem which means it can be fixed. I still need to move the ports forward to the current date before I have a certain fix but right now I think the quick work around will be to go into each of these directories (graphics/dri and graphics/xfree86-dri) and manually de-install them. Then let portmanager pull back in the correct one. That worked for the ports as they existed on December 1st, 2004 but I still need to verify it works for the current date. When I have a certain fix I'll post it here and cc everyone in this thread, and when I have a fix in portmanager so this won't happen again I'll cc everyone again. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
On Jan 26, 2005, at 10:40 AM, Michael C. Shultz wrote: Thanks Bart for your patience, this one required me to set up XFree86-4 on a FreeBSD 4.11 machine and back date all of the ports. Perfectly understandable and I thank you for the efforts you're going through to get portmanager updated so quickly. So now I know that on December 1st, 2004 /usr/ports/graphics/xfree86-dri and /usr/ports/graphics/dri both existed and both report their name as dri-5.0.2,2 on that date. This caused portmanager to loop so I have duplicated the problem which means it can be fixed. I still need to move the ports forward to the current date before I have a certain fix but right now I think the quick work around will be to go into each of these directories (graphics/dri and graphics/xfree86-dri) and manually de-install them. Then let portmanager pull back in the correct one. That worked for the ports as they existed on December 1st, 2004 but I still need to verify it works for the current date. So for a quick fix at the moment, I should just go into /usr/ports/graphics/dri and /usr/ports/graphics/xfree86-dri and run make deinstall, then run portmanager -u and it should install the proper version for the dependancies, correct? Thanks again! -Bart ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: portmanager loop?
On Wednesday 26 January 2005 05:38 am, Bart Silverstrim wrote: On Jan 26, 2005, at 4:38 AM, cali wrote: I had (have?) several packages in the ports collection that needed updating, and recently someone in the list was talking about using portmanager -u to save on problems with updating; it doesn't touch the ports database, it won't mess up the collection, it walks dependencies automagically, etc...should be as easy as portmanager -u and letting it do it's magic, correct? I read the same thing, and thought I'd give it a shot. On the Dell 2650 this is running on (FBSD 4.9) *seems* to keep recompiling xfree86-4-server. Is there a way to tell if it is stuck in a loop? I had to stop it yesterday after it had been upgrading for several hours. The same thing happened to me. Not sure where it was stuck but I was getting a distinct sense of deja-vu watching the output (I don't really mean deja-vu but I can't think of a better way to say it). I left it for 30 hours, and then cancelled it. I'm going to try and run it again today, I'd like to know also if it will eventually get out of the loop, i.e if it is really a loop or something different. sorry that this post doesn't really help the situation Actually the developer for portmanager contacted me about it. He asked for some logfiles, and I didn't think the list wanted a 300k zip file mass mailed so I was privately emailing him about the situation. He's looking into it and hoped to have a fix soon. He's been wonderful with response time to this error and I was glad to help with any logs or testing I could. He had hoped to have a fix in there soon, but I don't know if he found answers yet as to what caused the loop. -Bart Thanks Bart for your patience, this one required me to set up XFree86-4 on a FreeBSD 4.11 machine and back date all of the ports. So now I know that on December 1st, 2004 /usr/ports/graphics/xfree86-dri and /usr/ports/graphics/dri both existed and both report their name as dri-5.0.2,2 on that date. This caused portmanager to loop so I have duplicated the problem which means it can be fixed. I still need to move the ports forward to the current date before I have a certain fix but right now I think the quick work around will be to go into each of these directories (graphics/dri and graphics/xfree86-dri) and manually de-install them. Then let portmanager pull back in the correct one. That worked for the ports as they existed on December 1st, 2004 but I still need to verify it works for the current date. When I have a certain fix I'll post it here and cc everyone in this thread, and when I have a fix in portmanager so this won't happen again I'll cc everyone again. -Mike Did you receive the email I sent you from home last night regarding the issues I encountered? Apologies if you have replied to my home email address. I was in work early this morning, and haven't been able to check it. Mick Walker NAAFI Finance International ** This email and any files transmitted with it are confidential, and may be subject to legal privilege, and are intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error or think you may have done so, you may not peruse, use, disseminate, distribute or copy this message. Please notify the sender immediately and delete the original e-mail from your system. Computer viruses can be transmitted by e-mail. Recipients should check this e-mail for the presence of viruses. The Capita Group and its subsidiaries accept no liability for any damage caused by any virus transmitted by this e-mail. *** ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
On Wednesday 26 January 2005 07:49 am, you wrote: On Jan 26, 2005, at 10:40 AM, Michael C. Shultz wrote: Thanks Bart for your patience, this one required me to set up XFree86-4 on a FreeBSD 4.11 machine and back date all of the ports. Perfectly understandable and I thank you for the efforts you're going through to get portmanager updated so quickly. So now I know that on December 1st, 2004 /usr/ports/graphics/xfree86-dri and /usr/ports/graphics/dri both existed and both report their name as dri-5.0.2,2 on that date. This caused portmanager to loop so I have duplicated the problem which means it can be fixed. I still need to move the ports forward to the current date before I have a certain fix but right now I think the quick work around will be to go into each of these directories (graphics/dri and graphics/xfree86-dri) and manually de-install them. Then let portmanager pull back in the correct one. That worked for the ports as they existed on December 1st, 2004 but I still need to verify it works for the current date. So for a quick fix at the moment, I should just go into /usr/ports/graphics/dri and /usr/ports/graphics/xfree86-dri and run make deinstall, then run portmanager -u and it should install the proper version for the dependancies, correct? That works on December 1st, I'm not certain about the current date yet. Further info, on December 1st /usr/ports/graphics/dri is the correct dri for XFree86-4. I have all of this running on a AMD450 so it is a bit slow, my guess is I'll have solid answers in about 4 hours and the quick fix will probably be to de-install graphics/xfree86-dri then run portmanager -u. Thanks again! Welcome -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
On Wednesday 26 January 2005 08:27 am, you wrote: On Jan 26, 2005, at 11:07 AM, Michael C. Shultz wrote: That works on December 1st, I'm not certain about the current date yet. Further info, on December 1st /usr/ports/graphics/dri is the correct dri for XFree86-4. I have all of this running on a AMD450 so it is a bit slow, my guess is I'll have solid answers in about 4 hours and the quick fix will probably be to de-install graphics/xfree86-dri then run portmanager -u. I'm about to try it... I went into /usr/ports/graphics/xfree86-dri and ran make deinstall, it said that the package wasn't installed. I went into ../dri and ran make deinstall, it deinstalled dri-6.2_2,2 about to run portupgrade -u now... Cross yer' fingers! :-) -Bart Bart, here is what I think will happen based on what I see here, I think it will get past XFree-4-servers ok, but the next program that needs dri is going to bring the wrong one back in and so the looping will start on something else. If I were you I would hold off updating for now until I can give you a certain fix. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
On Wednesday 26 January 2005 08:50 am, you wrote: On Jan 26, 2005, at 11:36 AM, Michael C. Shultz wrote: Bart, here is what I think will happen based on what I see here, I think it will get past XFree-4-servers ok, but the next program that needs dri is going to bring the wrong one back in and so the looping will start on something else. If I were you I would hold off updating for now until I can give you a certain fix. Is there an easy way to check what is depending on the dri? My system said it only had the one installed...most likely meaning that just dri is causing the looping (correct?). Or it is the two dri's having the same version reported? I have both currently off the system. At any rate it got past the first loop stage, and it managed to update a few more ports. If it starts with looping again, I won't be any worse off than I was before (hopefully); I'd kill the looping again when it isn't at a installing set of outputs and let you know where it stalled again. Thanks for the updates... -Bart OK, hope it works for you. wrapper-1.0_3 also has a dependency on dri. I can now verify this is how things are supposed to be as of today: mike@/usr/ports/x11-servers/XFree86-4-Servermake all-depends-list /usr/ports/graphics/xfree86-dri mike@/usr/ports/x11/wrappermake all-depends-list /usr/ports/graphics/xfree86-dri As long as you don't see /usr/ports/graphics/dri being built you will be OK. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
To keep everyone informed, here is how portmanager's looping problem
with XFree86 is going to be handled:
portmanager version 0.2.4_1
Adding three strikes checking. When make is run on a port
it gets 1 strike, if it's made a second time it gets 2 strikes and a
warning will be printed, if it tries to build a 3rd time it gets marked
as ignore and no more attempts will be made to build it. At the end
of a portmanager -u run every port that was ignored and why it was
ignored is listed. This change doesn't solve the problem, but makes it
managable and I will have it posted before the day is over.
portmanager version 0.2.5
When a port has a second strike placed against it, instead of getting
its dependencies from /var/db/{portname}/+CONTENTS (which is very fast)
the port's dependencies will be retrieved by running make
all-depends-list in the port's directory (horribly slow) . I expect
this to be a clean fix for the looping problem but may take a few days
for codeing and testing before I can release this version.
-Mike
ps. Comments or other suggestions will be highly appreciated.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
I'd like to report a similar problem with the linux_base system. My
box has been recompiling linux_base-rh-7.3 for 12 hours now! :-)
The three strikes method sounds like a good temporary fix to the
problem. Please let us know when you get it posted!
--
Alan Gerber
Michael C. Shultz wrote:
To keep everyone informed, here is how portmanager's looping problem
with XFree86 is going to be handled:
portmanager version 0.2.4_1
Adding three strikes checking. When make is run on a port
it gets 1 strike, if it's made a second time it gets 2 strikes and a
warning will be printed, if it tries to build a 3rd time it gets marked
as ignore and no more attempts will be made to build it. At the end
of a portmanager -u run every port that was ignored and why it was
ignored is listed. This change doesn't solve the problem, but makes it
managable and I will have it posted before the day is over.
portmanager version 0.2.5
When a port has a second strike placed against it, instead of getting
its dependencies from /var/db/{portname}/+CONTENTS (which is very fast)
the port's dependencies will be retrieved by running make
all-depends-list in the port's directory (horribly slow) . I expect
this to be a clean fix for the looping problem but may take a few days
for codeing and testing before I can release this version.
-Mike
ps. Comments or other suggestions will be highly appreciated.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
On Wednesday 26 January 2005 06:11 pm, Alan Gerber wrote: I'd like to report a similar problem with the linux_base system. My box has been recompiling linux_base-rh-7.3 for 12 hours now! :-) The three strikes method sounds like a good temporary fix to the problem. Please let us know when you get it posted! -- Alan Gerber The patch is being tested now and so far its working. It stops the looping at the third attempt like planned. I just need let portmanager -u finish so I know there are no surprises at the end. I promise I'll post it tonight when this run is done. I'll reply somewhere in this thread when I have a PR number and will cc everyone who is in this thread as well. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: portmanager loop?
I've submitted a PR for the interim fix to portmanager's looping problem here is the link: http://www.freebsd.org/cgi/query-pr.cgi?pr=76739 If anyone is in a hurry I will be glad to send the patch as an email attachment, all you need to do is create a /usr/ports/sysutils/portmanager/files directory and then drop it in there. The patch is about 1000 lines so it is probably too long to send to this list. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
