Mark Hattam | 1 Sep 01:58 2009
Picon
Picon

Re: [56661] trunk/dports/mail/maildrop/Portfile

On 31 Aug 2009, at 20:58, toby <at> macports.org wrote:

> Revision56661Authortoby <at> macports.orgDate2009-08-31 12:58:08 -0700  
> (Mon, 31 Aug 2009)Log Message
> fix #20970, i think there's a missing dependency declaration
> Modified Paths
> 	• trunk/dports/mail/maildrop/Portfile
> Diff
> Modified: trunk/dports/mail/maildrop/Portfile (56660 => 56661)
>
> --- trunk/dports/mail/maildrop/Portfile	2009-08-31 19:53:50 UTC (rev  
> 56660)
> +++ trunk/dports/mail/maildrop/Portfile	2009-08-31 19:58:08 UTC (rev  
> 56661)
>  <at>  <at>  -4,6 +4,7  <at>  <at> 
>
>  name			maildrop
>  version	 		2.2.0
> +revision		1
>  categories		mail
>  maintainers		tnpi.biz:matt
>  description		Mail delivery agent (MDA) with filtering abilities
>  <at>  <at>  -17,7 +18,7  <at>  <at> 
>  			rmd160 8c715af18693c375ca197450cdb57e39813ea8cd
>  configure.args		--mandir=${prefix}/share/man \
>  			--with-etcdir=${prefix}/etc \
> -			--enable-syslog=1
> +			--enable-syslog=1 --without-db
>  depends_lib     	port:pcre
>
(Continue reading)

Ryan Schmidt | 1 Sep 02:40 2009

Re: Trying to rebuild on 10.6

On Aug 31, 2009, at 17:31, Mark Hattam wrote:

> [Time Machined the 10.5.8 before I started ... whew !!]
>
> Installed Snowleopard on my 3GHz iMac
>
> installed XCode 3.2 from the SnowLeopard DVD
>
> installed SnowLeopard .dmg of MacPorts 1.8
>
> typed the suggested one line upgrade command from http://trac.macports.org/wiki/Migration
> sudo port upgrade --force installed
>
> it started OK, but then stopped ...
>
>
>
> --->  Activating libiconv  <at> 1.13_0
> --->  Cleaning libiconv
> --->  Computing dependencies for db46
> --->  Fetching db46
> --->  Verifying checksum(s) for db46
> --->  Extracting db46
> --->  Applying patches to db46
> --->  Configuring db46
> Error: Target org.macports.configure returned: configure failure:  
> shell command " cd "/opt/local/var/macports/build/ 
> _opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_db46 
> /work/db-4.6.21/build_unix" && ../dist/configure --prefix=/opt/local  
> --enable-cxx --enable-java --includedir=\${prefix}/include/db46 -- 
(Continue reading)

Ryan Schmidt | 1 Sep 02:41 2009

Re: [56661] trunk/dports/mail/maildrop/Portfile

On Aug 31, 2009, at 18:58, Mark Hattam wrote:

> On 31 Aug 2009, at 20:58, toby <at> macports.org wrote:
>
>> --- trunk/dports/mail/maildrop/Portfile	2009-08-31 19:53:50 UTC  
>> (rev 56660)
>> +++ trunk/dports/mail/maildrop/Portfile	2009-08-31 19:58:08 UTC  
>> (rev 56661)
>>  <at>  <at>  -4,6 +4,7  <at>  <at> 
>>
>> name			maildrop
>> version	 		2.2.0
>> +revision		1
>> categories		mail
>> maintainers		tnpi.biz:matt
>> description		Mail delivery agent (MDA) with filtering abilities
>>  <at>  <at>  -17,7 +18,7  <at>  <at> 
>> 			rmd160 8c715af18693c375ca197450cdb57e39813ea8cd
>> configure.args		--mandir=${prefix}/share/man \
>> 			--with-etcdir=${prefix}/etc \
>> -			--enable-syslog=1
>> +			--enable-syslog=1 --without-db
>> depends_lib     	port:pcre
>
>
> The upgrade didn't go very well :-((
>
> MacOSX 10.5.8 on 3 GHz iMac, MacPorts 1.8
>
> sudo port outdated
(Continue reading)

Randal L. Schwartz | 1 Sep 02:49 2009

any way to make --enforce-variants the default?


It seems like this new "--enforce-variants" switch is just
a pain.  In a cargo-cult way, I now have to include it on
every "upgrade", because it invariably breaks when I don't.
So then I wonder, why isn't it the default?

And I've run into a tougher place.  I tried to install something
new.  But that triggered the upgrade of something else, which then
failed because, yup, again, --enforce-variants isn't set.
But why (and how!) would I have set --enforce-variants
on "sudo port install gimp".  This is *not* making sense.

So, what's the purpose of this new switch, and when would you ever *not* use
it?

--

-- 
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn <at> stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Smalltalk/Perl/Unix consulting, Technical writing, Comedy, etc. etc.
See http://methodsandmessages.vox.com/ for Smalltalk and Seaside discussion
Mark Hattam | 1 Sep 03:02 2009
Picon
Picon

Re: Trying to rebuild on 10.6


On 1 Sep 2009, at 01:40, Ryan Schmidt wrote:

> On Aug 31, 2009, at 17:31, Mark Hattam wrote:
>
>> [Time Machined the 10.5.8 before I started ... whew !!]
>>
>> Installed Snowleopard on my 3GHz iMac
>>
>> installed XCode 3.2 from the SnowLeopard DVD
>>
>> installed SnowLeopard .dmg of MacPorts 1.8
>>
>> typed the suggested one line upgrade command from http://trac.macports.org/wiki/Migration
>> sudo port upgrade --force installed
>>
>> it started OK, but then stopped ...
>>
>>
>>
>> --->  Activating libiconv  <at> 1.13_0
>> --->  Cleaning libiconv
>> --->  Computing dependencies for db46
>> --->  Fetching db46
>> --->  Verifying checksum(s) for db46
>> --->  Extracting db46
>> --->  Applying patches to db46
>> --->  Configuring db46
>> Error: Target org.macports.configure returned: configure failure:  
>> shell command " cd "/opt/local/var/macports/build/ 
(Continue reading)

Ryan Schmidt | 1 Sep 03:06 2009

Re: Trying to rebuild on 10.6


On Aug 31, 2009, at 20:02, Mark Hattam wrote:

>
> On 1 Sep 2009, at 01:40, Ryan Schmidt wrote:
>
>> The solution is to upgrade grep (and gawk and gsed if you have  
>> them) first. Then clean db46 (or whatever other port you got stuck  
>> on) and try again. I will add this information to the Migration  
>> wiki page.
>
>
> I did try a few more upgrades for specific named ports rather than  
> "installed" ... but they all errored in much the same way. And so I  
> then started on the roll-back to 10.5.8 - TimeMachine did a good  
> job, although Mail insisted on rebuilding all my mailboxes (30 mins  
> for 1 million emails).
>
> my current "port installed" has amongst others ...
>
>  gawk  <at> 3.1.7_0 (active)
>  grep  <at> 2.5.4_0 (active)
>  gsed  <at> 4.2.1_0 (active)
>
> But gawk and gsed only got there by being dependents of something  
> else. grep I think I installed. Is there any way of determining  
> which ports were user-installed and which were only dependent- 
> installed?

Not at this time, unfortunately. There is a ticket for that feature  
(Continue reading)

Ryan Schmidt | 1 Sep 03:10 2009

Re: any way to make --enforce-variants the default?

Hi Randal,

On Aug 31, 2009, at 19:49, Randal L. Schwartz wrote:

> It seems like this new "--enforce-variants" switch is just
> a pain.  In a cargo-cult way, I now have to include it on
> every "upgrade", because it invariably breaks when I don't.
> So then I wonder, why isn't it the default?
>
> And I've run into a tougher place.  I tried to install something
> new.  But that triggered the upgrade of something else, which then
> failed because, yup, again, --enforce-variants isn't set.
> But why (and how!) would I have set --enforce-variants
> on "sudo port install gimp".  This is *not* making sense.
>
> So, what's the purpose of this new switch, and when would you ever  
> *not* use
> it?

My understanding is that --enforce-variants will cause ports to  
rebuild which MacPorts doesn't think need to be rebuild, but where the  
set of variants used when you originally installed it does not match  
the set of variants MacPorts would use if you installed it today. This  
can be either because someone added default variants (or applicable  
platform variants) to the port since you installed it, or because the  
port has a "darwin" variant. (MacPorts versions before 1.8.0 failed to  
record the "darwin" variant in the registry.)

I am curious to know what "breaks" and is "failing" for you. What  
error messages are you getting? I thought upgrading ports with -- 
(Continue reading)

Mark Hattam | 1 Sep 03:17 2009
Picon
Picon

Re: [56661] trunk/dports/mail/maildrop/Portfile

On 1 Sep 2009, at 01:41, Ryan Schmidt wrote:

> On Aug 31, 2009, at 18:58, Mark Hattam wrote:
>
>> On 31 Aug 2009, at 20:58, toby <at> macports.org wrote:
>>
>>> --- trunk/dports/mail/maildrop/Portfile	2009-08-31 19:53:50 UTC  
>>> (rev 56660)
>>> +++ trunk/dports/mail/maildrop/Portfile	2009-08-31 19:58:08 UTC  
>>> (rev 56661)
>>>  <at>  <at>  -4,6 +4,7  <at>  <at> 
>>>
>>> name			maildrop
>>> version	 		2.2.0
>>> +revision		1
>>> categories		mail
>>> maintainers		tnpi.biz:matt
>>> description		Mail delivery agent (MDA) with filtering abilities
>>>  <at>  <at>  -17,7 +18,7  <at>  <at> 
>>> 			rmd160 8c715af18693c375ca197450cdb57e39813ea8cd
>>> configure.args		--mandir=${prefix}/share/man \
>>> 			--with-etcdir=${prefix}/etc \
>>> -			--enable-syslog=1
>>> +			--enable-syslog=1 --without-db
>>> depends_lib     	port:pcre
>>
>>
>> The upgrade didn't go very well :-((
>>
>> MacOSX 10.5.8 on 3 GHz iMac, MacPorts 1.8
(Continue reading)

Mark Hattam | 1 Sep 03:23 2009
Picon
Picon

Re: Trying to rebuild on 10.6


On 1 Sep 2009, at 02:06, Ryan Schmidt wrote:

>
> On Aug 31, 2009, at 20:02, Mark Hattam wrote:
>
>>
>> On 1 Sep 2009, at 01:40, Ryan Schmidt wrote:
>>
>>> The solution is to upgrade grep (and gawk and gsed if you have  
>>> them) first. Then clean db46 (or whatever other port you got stuck  
>>> on) and try again. I will add this information to the Migration  
>>> wiki page.
>>
>>
>> I did try a few more upgrades for specific named ports rather than  
>> "installed" ... but they all errored in much the same way. And so I  
>> then started on the roll-back to 10.5.8 - TimeMachine did a good  
>> job, although Mail insisted on rebuilding all my mailboxes (30 mins  
>> for 1 million emails).
>>
>> my current "port installed" has amongst others ...
>>
>> gawk  <at> 3.1.7_0 (active)
>> grep  <at> 2.5.4_0 (active)
>> gsed  <at> 4.2.1_0 (active)
>>
>> But gawk and gsed only got there by being dependents of something  
>> else. grep I think I installed. Is there any way of determining  
>> which ports were user-installed and which were only dependent- 
(Continue reading)

Joshua Root | 1 Sep 03:28 2009

Re: any way to make --enforce-variants the default?

On 2009-9-1 10:49, Randal L. Schwartz wrote:
> It seems like this new "--enforce-variants" switch is just
> a pain.  In a cargo-cult way, I now have to include it on
> every "upgrade", because it invariably breaks when I don't.
> So then I wonder, why isn't it the default?
> 
> And I've run into a tougher place.  I tried to install something
> new.  But that triggered the upgrade of something else, which then
> failed because, yup, again, --enforce-variants isn't set.
> But why (and how!) would I have set --enforce-variants
> on "sudo port install gimp".  This is *not* making sense.
> 
> So, what's the purpose of this new switch, and when would you ever *not* use
> it?

It's for adding variants to ports that are already installed. That's the
only time you should ever have to use it. Example:

sudo port upgrade --enforce-variants foo +universal

which will rebuild foo and all its dependencies with +universal.

Warnings about not matching +darwin are usually purely cosmetic and are
caused by a bug in older MacPorts versions where that variant was not
being recorded in the registry. Warnings about other variants are
usually worth paying attention to. They tell you when you do something
like `port install gtk2 +quartz` when you already have cairo installed
without +quartz, which is not going to work.

Nothing should ever fail to upgrade due to not using --enforce-variants
(Continue reading)


Gmane