On May 16, 2012, at 1:03 AM, Clemens Lang wrote:
> Maybe we should push this as 2.1.1 as a quick fix, before too many
> builds fail because of a broken dependency and trac is being flooded
> with tickets?
I think that is a good idea!
___
macports-dev ma
Updating MacPorts I ran into an issues uninstalling iso-code. I tried to
uninstall manually to get a better log telling what dependency prevented it
from being uninstalled:
jaspersmbp:~ jasper$ sudo port uninstall iso-codes @3.34_0
Password:
an invalid entry was passed
while executing
"$depend
I've noticed these two new lines in my output:
---> Updating database of binaries: 100.0%
---> Scanning binaries for linking errors: 100.0%
My problem is with the progress of the percentages in combination with
updating ports automatically using a script in periodic daily logging to
syslog. That
I just updated to the latest release and set buildfromsource to always, then
removed cloog and then updated all outdated ports. At the end of the update it
downloaded binaries for cloog instead of compiling them.
Blair
___
macports-dev mailing list
m
On May 15, 2012, at 6:44 PM, Clemens Lang wrote:
> On Tue, May 15, 2012 at 06:05:45PM -0700, Bradley Giesbrecht wrote:
>> I do not recall why but at some point I needed "perl5.12 +threads
>> +shared" and after upgrading perl5.12 with these variants NONE of my
>> perl modules were found. It was
> This question has been asked a couple of times on this list now and I
> have yet to hear a reason for why our perl isn't always +threads and
> +shared other than "I think I once knew somebody who back in the old
> days had some unspecified specified problem with perl +threads/+shared."
> ;)
> I'l
On May 15, 2012, at 9:01 p.m., Bjarne D Mathiesen wrote:
> So - my question still stands : are you interested in me doing the basic
> hard work in making ports that are hardcoded to a specific Perl5 version
> independent of which version is installed or the major one ???
Wasn't this the way thin
On Tue, May 15, 2012 at 06:05:45PM -0700, Bradley Giesbrecht wrote:
> I do not recall why but at some point I needed "perl5.12 +threads
> +shared" and after upgrading perl5.12 with these variants NONE of my
> perl modules were found. It was required that I reinstall all perl
> modules.
>
> Would
On May 15, 2012, at 3:35 PM, Bjarne D Mathiesen wrote:
> Daniel J. Luke wrote:
>> On May 15, 2012, at 6:09 PM, Bjarne D Mathiesen wrote:
>>> ports can be made independent of which version of Perl is installed or
>>> the major one by
>>
>>
>> In my opinion, we would be better served by just choo
I'ld like to return to my orignal problem :
making ports independent of which version of Perl is installed
-or-
the major one
Previously, the discussion rapidly deteriorated into quite other
problems having not that much to do with the subject of the thread.
The points pre
Lawrence Velázquez wrote:
> On May 15, 2012, at 7:12 p.m., Bjarne D Mathiesen wrote:
>
>> One idea might be to first of all transition Perl to using the select
>> system. I can see some point in the future where we might want to keep
>> at least two version of Perl that can live on the system and
On May 15, 2012, at 7:12 p.m., Bjarne D Mathiesen wrote:
> One idea might be to first of all transition Perl to using the select
> system. I can see some point in the future where we might want to keep
> at least two version of Perl that can live on the system and work
> independently of each othe
Lawrence Velázquez wrote:
> On May 15, 2012, at 6:35 p.m., Bjarne D Mathiesen wrote:
>
>> Daniel J. Luke wrote:
>>> On May 15, 2012, at 6:09 PM, Bjarne D Mathiesen wrote:
ports can be made independent of which version of Perl is installed or
the major one by
>>>
>>>
>>> In my opinion, we
Hi,
On Wed, May 16, 2012 at 12:09:41AM +0200, Marko Käning wrote:
> ---> Scanning binaries for linking errors: 100.0%
> ---> Found 14 broken file(s), matching files to ports
> ---> Found 4 broken port(s), determining rebuild order
> ---> Rebuilding in order
> phonon @4.6.0
> kdelibs
On May 15, 2012, at 6:35 p.m., Bjarne D Mathiesen wrote:
> Daniel J. Luke wrote:
>> On May 15, 2012, at 6:09 PM, Bjarne D Mathiesen wrote:
>>> ports can be made independent of which version of Perl is installed or
>>> the major one by
>>
>>
>> In my opinion, we would be better served by just cho
Daniel J. Luke wrote:
> On May 15, 2012, at 6:09 PM, Bjarne D Mathiesen wrote:
>> ports can be made independent of which version of Perl is installed or
>> the major one by
>
>
> In my opinion, we would be better served by just choosing one version of perl
> (which would be 5.14 right now) as ou
On May 15, 2012, at 3:14 PM, Daniel J. Luke wrote:
> On May 15, 2012, at 6:09 PM, Bjarne D Mathiesen wrote:
>> ports can be made independent of which version of Perl is installed or
>> the major one by
>
>
> In my opinion, we would be better served by just choosing one version of perl
> (which
On May 15, 2012, at 6:09 PM, Bjarne D Mathiesen wrote:
> ports can be made independent of which version of Perl is installed or
> the major one by
In my opinion, we would be better served by just choosing one version of perl
(which would be 5.14 right now) as our 'perl', and possibly offering ol
Hi Clemens,
On May 15, 2012, at 11:16 PM, Clemens Lang wrote:
> If you haven't rebuilt already, can you try again with trunk as of
> r93129 and see if the rebuild order is better?
yes, I tested it with this version pulled via SVN:
---
markos-imac:base_2_1 marko$ svn log -l 1
--
As already used in p5-dbd-mysql and proposed by me in
https://trac.macports.org/ticket/34461
https://trac.macports.org/ticket/34357
ports can be made independent of which version of Perl is installed or
the major one by
1) setting a portgroup:
PortGroup perl5 1.0
2) ch
Hi,
On Tue, May 15, 2012 at 09:38:51PM +0200, Marko Käning wrote:
> since kdelibs4 is build after kde4-runtime, kdepimlibs4, and
> kmymoney4, although these ports depend on kdelibs4.
> I would have expected to see kdelibs4 build first followed by
> kde4-runtime, kdepimlibs4 and then kmymoney4.
If
On May 15, 2012, at 14:58, Craig Treleaven wrote:
> My adventure continues...I'm trying to follow the cpan2port how-to
> (https://trac.macports.org/wiki/howto/cpan2port) but it is not working for me.
>
> I tried to generate both the ports I need in one run but it must write one
> over top of th
On 2012-5-16 06:09 , Joshua Root wrote:
> On 2012-5-16 06:01 , Arno Hautala wrote:
>> On 5/15/12, C D wrote:
>>>
>>> Then there might be a bug: following the procedure in
>>> https://trac.macports.org/wiki/howto/ShareArchives2, I have set up a local
>>> archive repository, which I access through
On May 15, 2012, at 15:02, Marko Käning wrote:
> On May 15, 2012, at 9:49 PM, Ryan Schmidt wrote:
>>> Edit the appropriate setting in macports.conf; it's at the bottom of
>>> MacPorts 2.1.0's macports.conf.default.
> Oh, I see my mistake now. I only checked the macports.conf for an appropriate
>
On Tue, May 15, 2012 at 09:38:51PM +0200, Marko Käning wrote:
> I would have expected to see kdelibs4 build first followed by
> kde4-runtime, kdepimlibs4 and then kmymoney4.
And you're right, this is not the best rebuild order. This might be a
bug; I'm currently investigating.
--
Clemens Lang
_
On 2012-5-16 06:01 , Arno Hautala wrote:
> On 5/15/12, C D wrote:
>>
>> Then there might be a bug: following the procedure in
>> https://trac.macports.org/wiki/howto/ShareArchives2, I have set up a local
>> archive repository, which I access through the URL http://localhost:6227/ .
>> When this U
On May 15, 2012, at 9:49 PM, Ryan Schmidt wrote:
>> Edit the appropriate setting in macports.conf; it's at the bottom of
>> MacPorts 2.1.0's macports.conf.default.
Oh, I see my mistake now. I only checked the macports.conf for an appropriate
flag…
Thanks for pointing that out!
(Thanks Brad also!
On 5/15/12, C D wrote:
>
> Then there might be a bug: following the procedure in
> https://trac.macports.org/wiki/howto/ShareArchives2, I have set up a local
> archive repository, which I access through the URL http://localhost:6227/ .
> When this URL is put into ${prefix}/etc/archive_sites.conf,
Hi:
My adventure continues...I'm trying to follow the cpan2port how-to
(https://trac.macports.org/wiki/howto/cpan2port) but it is not
working for me.
I tried to generate both the ports I need in one run but it must
write one over top of the other. Output from the script follows:
$ ./cpan
On May 15, 2012, at 12:48 PM, Marko Käning wrote:
>> It will ease the life of users a lot; port maintainers a little less so.
>> You still want to rev bump the dependents so users don't have to install
>> them multiple times.
> Well, I guess I've ran into this by now. :-)--->>> See the thread
On May 15, 2012, at 14:48, Marko Käning wrote:
>> Setting rev-upgrade to only report the breakage is a great way to know
>> what you have installed that needs rev bumping.
> How do I set it to report only?
Edit the appropriate setting in macports.conf; it's at the bottom of MacPorts
2.1.0's mac
> It will ease the life of users a lot; port maintainers a little less so.
> You still want to rev bump the dependents so users don't have to install
> them multiple times.
Well, I guess I've ran into this by now. :-)--->>> See the thread titled
"MacPorts 2.1.0: Weird rebuild order of "broken
On 2012-5-16 05:31 , Marko Käning wrote:
> Great job, Josh and all the other MacPorts devs!!!
>
>
> I just discovered messages like this also for my non-/opt/local installations:
> ---
> ---> Scanning binaries for linking errors: 100.0%
> ---> Found 19 broken file(s), matching files to ports
>
Ooops, just now I see that this rebuild order on "sudo port upgrade" is not
good:
---
---> Scanning binaries for linking errors: 100.0%
---> Found 19 broken file(s), matching files to ports
---> Found 6 broken port(s), determining rebuild order
---> Rebuilding in order
phonon @4.6.0
k
> Well, it looks like that this cool feature will ease the life of all port
> maintainers, since one doesn't need to think about all the revbumps for
> dependent ports anymore… (If I understood this right.) :-)
You can set it to reporting mode, rather than fixing it out from under you.
This way
Great job, Josh and all the other MacPorts devs!!!
I just discovered messages like this also for my non-/opt/local installations:
---
---> Scanning binaries for linking errors: 100.0%
---> Found 19 broken file(s), matching files to ports
---> Found 6 broken port(s), determining rebuild order
-
On 15/mag/2012, at 17:36, Bradley Giesbrecht wrote:
> Nice!
> Thanks Joshua!
>
>
> On May 15, 2012, at 8:29 AM, Joshua Root wrote:
>
>> The MacPorts Project is happy to announce that the 2.1.0 version has now
>> been released. It is available via the usual methods:
>>
>> - selfupdate if you alr
Nice!
Thanks Joshua!
On May 15, 2012, at 8:29 AM, Joshua Root wrote:
> The MacPorts Project is happy to announce that the 2.1.0 version has now
> been released. It is available via the usual methods:
>
> - selfupdate if you already have MacPorts installed
> - package installers for 10.5 [1], 10
> HDF5 takes a very conservative approach and checks compiled with /
> running with version numbers at launch. It's software designed for
> maintaining huge and potentially expensive / impossible to replace
> scientific data, so they go with error out and print a message rather
> than any tiny chan
On Tue, May 15, 2012 at 8:32 AM, Jeremy Lavergne
wrote:
>> I tried
>> uninstalling and re-installing h5py, which used to work, but now that
>> we have binary packages, this no longer works
>
> `port -s ...` will make MacPorts work with sources only, rather than pulling
> binary packages if availa
> I tried
> uninstalling and re-installing h5py, which used to work, but now that
> we have binary packages, this no longer works
`port -s ...` will make MacPorts work with sources only, rather than pulling
binary packages if available.
Also, the library version mismatch shouldn't be an issue if
Hi,
The py-h5py port depends on the hdf5-18 port. The hdf5-18 port was
recently updated to 1.8.9, but h5py, when compiled, remembers what
version of HDF5 it was compiled with, and raises a big error if there
is a version mismatch (causing an abort trap):
---
Warning! ***HDF5 library version mism
On Tue, May 15, 2012 at 04:39:54AM -0700, m...@macports.org wrote:
> Revision: 93110
> https://trac.macports.org/changeset/93110
> Author: m...@macports.org
> Date: 2012-05-15 04:39:53 -0700 (Tue, 15 May 2012)
> Log Message:
> ---
> gtk3: PortGroup xcodeversion 1.0
That log
43 matches
Mail list logo
