Hi:
I've ended up with an svn conflict--just in the capitalization of the
directory name, if I'm reading this right.
SixBare:mp-trunk-ports craigtreleaven$ svn status
? sysutils/MacPorts_daemondo
! C sysutils/macports_daemondo
> local add, incoming add upon update
I tried:
o
+version 1.1
+revision 20141017
+categories sysutils
+platforms darwin
+supported_archs x86_64
+license BSD
+maintainers cogeco.ca:ctreleaven openmaintainer
+
+description HACK to get daemondo into mpkg
+long_
Hi all,
I would like to declare py26-mapnik (0.7.1) port obsolete and replaced by
mapnik (2.2.0). Is there still any good reason to keep the old version around,
or can I proceed?
Thanks!
~petr
___
macports-dev mailing list
macports-dev@lists.maco
> On Oct 17, 2014, at 1:33 PM, p...@macports.org wrote:
>
> Revision
> 126921
> Author
> p...@macports.org
> Date
> 2014-10-17 11:33:53 -0700 (Fri, 17 Oct 2014)
> Log Message
>
> py-tvdb: update to version 1.9, github portgroup, categories and license
> update, closes #39708
> --- trunk/dport
:sw=4:ts=4:sts=4
> +
> +PortSystem 1.0
> +
> +nameMacPorts_daemondo
> +version 1.1
> +revision20141017
> +categories sysutils
> +platforms darwin
> +supported_archs x86_64
> +license
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hallo,
MacPorts schrieb:
> I guess, this port now definitely qualifies as abandoned.
Ups, there had been a new version. Missed that one.
> james, please confirm, that you are still available as maintainer and
> I will commit the changes.
It's openm
Hi Larry,
Thanks for the pointer. I’ll try to get it right next time!
Cheers!
Frank
On Oct 15, 2014, at 9:00 PM, Lawrence Velázquez wrote:
> It's not necessary to revbump the original Portfile, since nothing's changed
> there. It's only necessary that the revision be increased in the gravey
On 10/17/14, Ryan Schmidt wrote:
>
> On Oct 17, 2014, at 1:29 PM, Eric Gallager wrote:
>
>> On 10/16/14, Ryan Schmidt wrote:
>>>
>>> For example, we should inform users of 10.9.4 and earlier that they
>>> should update.
>>
>> Update from 10.9.4 to 10.9.5, or to 10.10?
>
> To 10.9.5.
>
OK, phew, t
On Oct 17, 2014, at 1:29 PM, Eric Gallager wrote:
> On 10/16/14, Ryan Schmidt wrote:
>>
>> For example, we should inform users of 10.9.4 and earlier that they should
>> update.
>
> Update from 10.9.4 to 10.9.5, or to 10.10?
To 10.9.5.
___
macports
On 10/16/14, Ryan Schmidt wrote:
>
> On Oct 16, 2014, at 12:50 PM, Joshua Root wrote:
>>
>> So Yosemite is out today. Might as well tag a new release before I build
>> the pkg. Is there anything critical that needs to go onto the branch
>> first?
>
> Could we update the checks in configure.ac that
On 2014-10-18 04:56 , James Berry wrote:
> Given that the outdated pseudo port now returns all ports where the
> darwin version doesn’t match the current version, is it true that
> Migration of ports (following update of MacPorts) is as simple as:
>
> sudo port upgrade outdated
>
> This has worke
If there are missing dependencies, then the rebuild order may not be done
correctly.
Trace mode or making a re-install list are the workarounds, as far as I know.
On Oct 17, 2014, at 13:56, James Berry wrote:
> Given that the outdated pseudo port now returns all ports where the darwin
> versi
Given that the outdated pseudo port now returns all ports where the darwin
version doesn’t match the current version, is it true that Migration of ports
(following update of MacPorts) is as simple as:
sudo port upgrade outdated
This has worked well for me in the last few OS updates, inc
13 matches
Mail list logo