readline

[Thomas De Contes]

hi :-)


+ port -u upgrade outdated
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Computing dependencies for readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Applying patches to readline
Error: Target org.macports.patch returned: shell command " cd "/Users/
thomas/Documents/prgm/bin/autoinstall/macports/var/macports/build/
_Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sourc
es_rsync.macports.org_release_ports_devel_readline/work/readline-6.0"  
&& /usr/bin/patch -p0 < '/Users/thomas/Documents/prgm/bin/autoinstall/
macports/var/macports/sources/rsync.macports.org/release/ports/devel/
readline/files/patch-shobj-conf.diff'" returned error 1
Command output: patching file support/shobj-conf
Hunk #1 FAILED at 152.
Hunk #2 FAILED at 176.
2 out of 2 hunks FAILED -- saving rejects to file support/shobj-conf.rej

Error: Unable to upgrade port: 1


what's the problem ?


--
Téléassistance / Télémaintenance
http://www.portparallele.com/ThomasDECONTES/

_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Ryan Schmidt-24]

On Oct 10, 2009, at 20:49, Thomas De Contes wrote:

> + port -u upgrade outdated
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> --->  Computing dependencies for readline
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> --->  Applying patches to readline
> Error: Target org.macports.patch returned: shell command " cd "/
> Users/thomas/Documents/prgm/bin/autoinstall/macports/var/macports/
> build/
> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline
> /work/readline-6.0" && /usr/bin/patch -p0 < '/Users/thomas/Documents/
> prgm/bin/autoinstall/macports/var/macports/sources/
> rsync.macports.org/release/ports/devel/readline/files/patch-shobj-
> conf.diff'" returned error 1
> Command output: patching file support/shobj-conf
> Hunk #1 FAILED at 152.
> Hunk #2 FAILED at 176.
> 2 out of 2 hunks FAILED -- saving rejects to file support/shobj-
> conf.rej
>
> Error: Unable to upgrade port: 1

Since the first thing shown for readline is "Applying patches" instead  
of "Fetching" or "Extracting", this suggests you had previously  
started installing readline and cancelled it just after it finished  
the patch phase but before it recorded that it had finished the patch  
phase. So now it's trying to apply the patches a second time, and  
failing, because they are already applied.

In those situations you usually see the message "Reversed (or  
previously applied) patch detected! Assume -R? [n]". But the readline  
port not only applies patchfiles to the source files, it also has a  
post-patch step which does a reinplace on shobj-conf. Therefore the  
way the file looks now is not exactly the way it would look after only  
applying the patches, therefore the patch program doesn't know what to  
do.

The solution should be to clean the port, selfupdate to make sure you  
have the latest MacPorts and port definitions, and try again. This is  
probably the first step you should try any time any port fails.

sudo port clean readline
sudo port selfupdate
sudo port upgrade readline


_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Thomas De Contes]

Le 11 oct. 09 à 12:59, Ryan Schmidt a écrit :

> On Oct 10, 2009, at 20:49, Thomas De Contes wrote:
>
>> + port -u upgrade outdated
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> --->  Computing dependencies for readline
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> --->  Applying patches to readline
>> Error: Target org.macports.patch returned: shell command " cd "/
>> Users/thomas/Documents/prgm/bin/autoinstall/macports/var/macports/
>> build/
>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_so
>> urces_rsync.macports.org_release_ports_devel_readline/work/
>> readline-6.0" && /usr/bin/patch -p0 < '/Users/thomas/Documents/
>> prgm/bin/autoinstall/macports/var/macports/sources/
>> rsync.macports.org/release/ports/devel/readline/files/patch-shobj-
>> conf.diff'" returned error 1
>> Command output: patching file support/shobj-conf
>> Hunk #1 FAILED at 152.
>> Hunk #2 FAILED at 176.
>> 2 out of 2 hunks FAILED -- saving rejects to file support/shobj-
>> conf.rej
>>
>> Error: Unable to upgrade port: 1
>
> Since the first thing shown for readline is "Applying patches"  
> instead of "Fetching" or "Extracting", this suggests you had  
> previously started installing readline and cancelled it just after  
> it finished the patch phase but before it recorded that it had  
> finished the patch phase. So now it's trying to apply the patches a  
> second time, and failing, because they are already applied.

no, it made an error, and i just run it again

> The solution should be to clean the port, selfupdate to make sure  
> you have the latest MacPorts and port definitions, and try again.  
> This is probably the first step you should try any time any port  
> fails.
>
> sudo port clean readline
> sudo port selfupdate
> sudo port upgrade readline


i did
port clean readline
and then :

+ port selfupdate
...
+ port -u upgrade outdated
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Computing dependencies for readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Fetching readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Verifying checksum(s) for readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Extracting readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Applying patches to readline
Error: Target org.macports.patch returned: could not set group for  
file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/
macports/build/
_Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sourc
es_rsync.macports.org_release_ports_devel_readline/work/readline-6.0/
support/shobj-conf": not owner
Error: Unable to upgrade port: 1


--
Téléassistance / Télémaintenance
http://www.portparallele.com/ThomasDECONTES/

_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Ryan Schmidt-24]

On Oct 11, 2009, at 09:43, Thomas De Contes wrote:

> Le 11 oct. 09 à 12:59, Ryan Schmidt a écrit :
>
>> On Oct 10, 2009, at 20:49, Thomas De Contes wrote:
>>
>>> + port -u upgrade outdated
>>> MacPorts running without privileges. You may be unable to complete  
>>> certain actions (eg install).
>>> --->  Computing dependencies for readline
>>> MacPorts running without privileges. You may be unable to complete  
>>> certain actions (eg install).
>>> MacPorts running without privileges. You may be unable to complete  
>>> certain actions (eg install).
>>> MacPorts running without privileges. You may be unable to complete  
>>> certain actions (eg install).
>>> MacPorts running without privileges. You may be unable to complete  
>>> certain actions (eg install).
>>> --->  Applying patches to readline
>>> Error: Target org.macports.patch returned: shell command " cd "/
>>> Users/thomas/Documents/prgm/bin/autoinstall/macports/var/macports/
>>> build/
>>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline
>>> /work/readline-6.0" && /usr/bin/patch -p0 < '/Users/thomas/
>>> Documents/prgm/bin/autoinstall/macports/var/macports/sources/
>>> rsync.macports.org/release/ports/devel/readline/files/patch-shobj-
>>> conf.diff'" returned error 1
>>> Command output: patching file support/shobj-conf
>>> Hunk #1 FAILED at 152.
>>> Hunk #2 FAILED at 176.
>>> 2 out of 2 hunks FAILED -- saving rejects to file support/shobj-
>>> conf.rej
>>>
>>> Error: Unable to upgrade port: 1
>>
>> Since the first thing shown for readline is "Applying patches"  
>> instead of "Fetching" or "Extracting", this suggests you had  
>> previously started installing readline and cancelled it just after  
>> it finished the patch phase but before it recorded that it had  
>> finished the patch phase. So now it's trying to apply the patches a  
>> second time, and failing, because they are already applied.
>
> no, it made an error, and i just run it again

Ah, ok. Still, the error you reported was caused by running it a  
second time without cleaning.

>> The solution should be to clean the port, selfupdate to make sure  
>> you have the latest MacPorts and port definitions, and try again.  
>> This is probably the first step you should try any time any port  
>> fails.
>>
>> sudo port clean readline
>> sudo port selfupdate
>> sudo port upgrade readline
>
>
> i did
> port clean readline
> and then :
>
> + port selfupdate
> ...
> + port -u upgrade outdated
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> --->  Computing dependencies for readline
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> --->  Fetching readline
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> --->  Verifying checksum(s) for readline
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> --->  Extracting readline
> MacPorts running without privileges. You may be unable to complete  
> certain actions (eg install).
> --->  Applying patches to readline
> Error: Target org.macports.patch returned: could not set group for  
> file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/
> macports/build/
> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline
> /work/readline-6.0/support/shobj-conf": not owner
> Error: Unable to upgrade port: 1

Ok, that's the first and real error, and is:

http://trac.macports.org/ticket/20896

As shown in the ticket, I identified the change that caused that  
problem. Joshua, what do you think we should do about this? We could  
apply the patch I supplied, which would revert one of your prior  
changes. Or we could try to figure out a way to allow your change  
while still avoiding this issue.


_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Thomas De Contes]

Le 11 oct. 09 à 22:23, Ryan Schmidt a écrit :

>
> On Oct 11, 2009, at 09:43, Thomas De Contes wrote:
>
>> no, it made an error, and i just run it again
>
> Ah, ok. Still, the error you reported was caused by running it a  
> second time without cleaning.

true (but it's unusual)

>
>
>> port clean readline
>> and then :
>>
>> + port selfupdate
>> ...
>> + port -u upgrade outdated
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> --->  Computing dependencies for readline
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> --->  Fetching readline
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> --->  Verifying checksum(s) for readline
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> --->  Extracting readline
>> MacPorts running without privileges. You may be unable to complete  
>> certain actions (eg install).
>> --->  Applying patches to readline
>> Error: Target org.macports.patch returned: could not set group for  
>> file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/
>> macports/build/
>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_so
>> urces_rsync.macports.org_release_ports_devel_readline/work/
>> readline-6.0/support/shobj-conf": not owner
>> Error: Unable to upgrade port: 1
>
> Ok, that's the first and real error, and is:
>
> http://trac.macports.org/ticket/20896
>
> As shown in the ticket, I identified the change that caused that  
> problem. Joshua, what do you think we should do about this? We  
> could apply the patch I supplied, which would revert one of your  
> prior changes. Or we could try to figure out a way to allow your  
> change while still avoiding this issue.

any news ?

is it possible to upgrade readline nevertheless ?


--
Téléassistance / Télémaintenance
http://www.portparallele.com/ThomasDECONTES/

_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Ryan Schmidt-24]

>>> --->  Applying patches to readline
>>> Error: Target org.macports.patch returned: could not set group for  
>>> file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/var/
>>> macports/build/
>>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync.macports.org_release_ports_devel_readline
>>> /work/readline-6.0/support/shobj-conf": not owner
>>> Error: Unable to upgrade port: 1
>>
>> Ok, that's the first and real error, and is:
>>
>> http://trac.macports.org/ticket/20896
>>
>> As shown in the ticket, I identified the change that caused that  
>> problem. Joshua, what do you think we should do about this? We  
>> could apply the patch I supplied, which would revert one of your  
>> prior changes. Or we could try to figure out a way to allow your  
>> change while still avoiding this issue.
>
>
> any news ?
>
> is it possible to upgrade readline nevertheless ?

You could apply the patch I attached to that ticket, and rebuild  
MacPorts.

I would like to resolve this issue for MacPorts 1.8.2, and am awaiting  
feedback on whether or not this patch should be applied or if there is  
another solution.

Or you could reinstall MacPorts so it's installed as root.

_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Thomas De Contes]

Le 15 oct. 09 à 18:37, Ryan Schmidt a écrit :

>> is it possible to upgrade readline nevertheless ?
>
> You could apply the patch I attached to that ticket, and rebuild  
> MacPorts.
>
> I would like to resolve this issue for MacPorts 1.8.2, and am  
> awaiting feedback on whether or not this patch should be applied or  
> if there is another solution.


thank you :-)

is there a date for MacPorts 1.8.2 ?


--
Téléassistance / Télémaintenance
http://www.portparallele.com/ThomasDECONTES/

_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Ryan Schmidt-24]

On Oct 26, 2009, at 09:55, Thomas De Contes wrote:

>
> Le 15 oct. 09 à 18:37, Ryan Schmidt a écrit :
>
>>> is it possible to upgrade readline nevertheless ?
>>
>> You could apply the patch I attached to that ticket, and rebuild  
>> MacPorts.
>>
>> I would like to resolve this issue for MacPorts 1.8.2, and am  
>> awaiting feedback on whether or not this patch should be applied or  
>> if there is another solution.
>
>
> thank you :-)
>
> is there a date for MacPorts 1.8.2 ?

No, and we have not yet decided whether the patch I provided in that  
ticket is the correct solution to the problem.


_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Kevin Reid-2]

On Oct 15, 2009, at 12:37, Ryan Schmidt wrote:

>>>> --->  Applying patches to readline
>>>> Error: Target org.macports.patch returned: could not set group  
>>>> for file "/Users/thomas/Documents/prgm/bin/autoinstall/macports/
>>>> var/macports/build/
>>>> _Users_thomas_Documents_prgm_bin_autoinstall_macports_var_macports_sources_rsync
>>>> .macports.org_release_ports_devel_readline/work/readline-6.0/
>>>> support/shobj-conf": not owner
>>>> Error: Unable to upgrade port: 1
>>>
>>> Ok, that's the first and real error, and is:
>>>
>>> http://trac.macports.org/ticket/20896
> ...
> You could apply the patch I attached to that ticket, and rebuild  
> MacPorts.

I'm having what looks like this same problem, after having just  
selfupdated MacPorts.


bash-3.2$ port upgrade readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Computing dependencies for readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Fetching readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Verifying checksum(s) for readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Extracting readline
MacPorts running without privileges. You may be unable to complete  
certain actions (eg install).
--->  Applying patches to readline
Error: Target org.macports.patch returned: could not set group for  
file "/Stuff/ports/var/macports/build/
_Stuff_ports_var_macports_sources_rsync
.macports.org_release_ports_devel_readline/work/readline-6.0/support/
shobj-conf": not owner
Error: Unable to upgrade port: 1
bash-3.2$ locate portutil.tcl


I tried applying your patch, but it didn't apply cleanly and the code  
looks different (there is no "file copy -force" in src/port1.0/
portutil.tcl).

Any updated recommendations?

--
Kevin Reid                                  <http://switchb.org/kpreid/>




_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Joshua Root-8]

On 2009-12-15 14:58 , Kevin Reid wrote:

> On Oct 15, 2009, at 12:37, Ryan Schmidt wrote:
>>>> http://trac.macports.org/ticket/20896
>> ...
>> You could apply the patch I attached to that ticket, and rebuild
>> MacPorts.
>
> I'm having what looks like this same problem, after having just
> selfupdated MacPorts.
>
>
> bash-3.2$ port upgrade readline

...

> --->  Applying patches to readline
> Error: Target org.macports.patch returned: could not set group for file
> "/Stuff/ports/var/macports/build/_Stuff_ports_var_macports_sources_rsync.macports.org_release_ports_devel_readline/work/readline-6.0/support/shobj-conf":
> not owner
> Error: Unable to upgrade port: 1
> bash-3.2$ locate portutil.tcl
>
>
> I tried applying your patch, but it didn't apply cleanly and the code
> looks different (there is no "file copy -force" in
> src/port1.0/portutil.tcl).
>
> Any updated recommendations?

Ignore the patches attached to the ticket. Comment 15 links to a change
in trunk which may fix the problem, but nobody affected by it has yet
tested and confirmed or denied this.

- Josh
_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Kevin Reid-2]

On Dec 14, 2009, at 23:24, Joshua Root wrote:

>> bash-3.2$ port upgrade readline
> ...
>> --->  Applying patches to readline
>> Error: Target org.macports.patch returned: could not set group for  
>> file
>> "/Stuff/ports/var/macports/build/
>> _Stuff_ports_var_macports_sources_rsync
>> .macports.org_release_ports_devel_readline/work/readline-6.0/
>> support/shobj-conf":
>> not owner
>> Error: Unable to upgrade port: 1
>> bash-3.2$ locate portutil.tcl
>>
>>
>> I tried applying your patch, but it didn't apply cleanly and the code
>> looks different (there is no "file copy -force" in
>> src/port1.0/portutil.tcl).
>>
>> Any updated recommendations?
>
> Ignore the patches attached to the ticket. Comment 15 links to a  
> change
> in trunk which may fix the problem, but nobody affected by it has yet
> tested and confirmed or denied this.

Suppose that I need to get this working again ASAP, i.e. before the  
next release.

Assuming the change does fix the problem what would I do? Apply http://trac.macports.org/changeset/59597 
  to the code I have now? Switch to trunk (how)?

--
Kevin Reid                                  <http://switchb.org/kpreid/>




_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Joshua Root-8]

On 2009-12-15 16:01 , Kevin Reid wrote:

> On Dec 14, 2009, at 23:24, Joshua Root wrote:
>>> bash-3.2$ port upgrade readline
>> ...
>>> --->  Applying patches to readline
>>> Error: Target org.macports.patch returned: could not set group for file
>>> "/Stuff/ports/var/macports/build/_Stuff_ports_var_macports_sources_rsync.macports.org_release_ports_devel_readline/work/readline-6.0/support/shobj-conf":
>>>
>>> not owner
>>> Error: Unable to upgrade port: 1
>>> bash-3.2$ locate portutil.tcl
>>>
>>>
>>> I tried applying your patch, but it didn't apply cleanly and the code
>>> looks different (there is no "file copy -force" in
>>> src/port1.0/portutil.tcl).
>>>
>>> Any updated recommendations?
>>
>> Ignore the patches attached to the ticket. Comment 15 links to a change
>> in trunk which may fix the problem, but nobody affected by it has yet
>> tested and confirmed or denied this.
>
>
> Suppose that I need to get this working again ASAP, i.e. before the next
> release.
>
> Assuming the change does fix the problem what would I do? Apply
> http://trac.macports.org/changeset/59597 to the code I have now? Switch
> to trunk (how)?

If the fix is correct, either of those would probably work.

<http://trac.macports.org/wiki/howto/RunningTrunk>

- Josh
_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Raphael Straub]

Joshua Root wrote:
> On 2009-12-15 14:58 , Kevin Reid wrote:
>> Assuming the change does fix the problem what would I do? Apply
>> http://trac.macports.org/changeset/59597 to the code I have now? Switch
>> to trunk (how)?
>
> If the fix is correct, either of those would probably work.

I had the same problem as Kevin. After applying changeset 59597 manually to MacPorts (version 1.8.1) and recompiling MacPorts, readline installs perfectly.

So, your fix works for me. Thanks, Joshua!

Regards,
        Raphael

_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

[Joshua Root-8]

On 2009-12-16 04:30 , Raphael Straub wrote:
> I had the same problem as Kevin. After applying changeset 59597 manually to MacPorts (version 1.8.1) and recompiling MacPorts, readline installs perfectly.
>
> So, your fix works for me. Thanks, Joshua!

Thanks for testing. The fix is now on the 1.8 branch.

- Josh
_______________________________________________
macports-users mailing list
macports-users@...
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users