> On 24 Feb 2016, at 16:28, Ryan Schmidt <ryandes...@macports.org> wrote:
>
> On Feb 24, 2016, at 09:08, petr <9...@ingv.it> wrote:
>>
>>
>> Hi I am trying to install Macports on an old OS X 10.6 system, but have
>> difficulties to
?
Thanks a lot!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
> On 18 Feb 2016, at 11:32, Aljaž 'g5pw' Srebrnič <g...@macports.org> wrote:
>
> On 18 febbraio 2016 at 11:01:58, petr (9...@ingv.it) wrote:
>>
>> Hi all,
>>
>> I realise that there quite some inconsistency in the naming of select port
>> nami
these? Or are we free to pick anything we
like?
Should there be some recommendation?
Thanks!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
from perl5.16 to perl5.22 and very probably also changes the perl
path in some of the installed files.
Should I proceed or will you take care of it?
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/ma
for the clarification!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
The update to gsl @2.1 seems to have broken binary compatibility with dependent
ports. So they need to be revision bumped. I see this for `nco` and `qgis` but
there are very probably more. See below.
~petr
{{{
[...]
---> Installing gsl @2.1_0
---> Cleaning gsl
---> Remo
Looks like all changesets beyond r139798
(https://trac.macports.org/changeset/139798) are not visible and liked in Trac.
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Trac is seems to talk to us again.
Party!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
My commit passed after several retries, so probably the routing issues. Just
guessing …
Anyway, this apparent tendency that MacOSForge is disintegrating is becoming a
bit worrying. Are there any mitigation strategies around or are we still hoping
for better times?
~petr
On 25 Aug 2015
if { [llength
$remaining_args] 0 } { # If there are remai
ning arguments, process those as a command set exit_status [process_cmd
$remaining... (file /opt/local/bin/port line 5268)
Can anyone explain me what is going on? It looks like a problem not due to the
port itself.
Thanks!
~petr
to single out this part into a separate
port, if this is possible.
Cheers!
~petr
On 28 Jun 2015, at 11:14, Mojca Miklavec mo...@macports.org wrote:
On Sun, Jun 28, 2015 at 11:09 AM, Mojca Miklavec wrote:
One of things that I would like to get right are the variants to
switch between different
without.
I think it is worth documenting some of the point mention in this thread, as it
is not obvious when starting to get hands on a new portgroup.
~petr
On 22 Jun 2015, at 23:42, Lawrence Velázquez lar...@macports.org wrote:
On Jun 4, 2015, at 7:32 PM, Ryan Schmidt ryandes...@macports.org
Hi Lawrence,
Hi Mojca,
I also had this in mind for quite some while, however I got stuck on several
issues, when testing. So I wanted to get these fixed as well, but never found
the time.
On 22 Jun 2015, at 23:12, Lawrence Velázquez lar...@macports.org wrote:
On Jun 22, 2015, at 4:59 PM,
Hi all,
how would I make a recursive glob in TCL?
I need to change the permissions of a faulty distfile, where permissions are
set to restrictive?
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org
dependents.
~petr
https://trac.macports.org/changeset/136284
Index: /trunk/dports/print/ghostscript/Portfile
===
--- /trunk/dports/print/ghostscript/Portfile(revision 136283)
+++ /trunk/dports/print/ghostscript/Portfile
to build on the build slaves?
I saw this with ImageMagick, which was rev bumped, but (1) the upgrade order
has some influence, and (2) I have an non-default variants installation so I
need to build anyway from source. I guess, all is okay. I just missed the
second changeset.
~petr
not aware of any other document mentioning it.
BTW: Does this change require a entry in the changelog?
~petr
On 9 May 2015, at 17:20, Lawrence Velázquez lar...@macports.org wrote:
On May 9, 2015, at 11:18 AM, Lawrence Velázquez lar...@macports.org wrote:
Why? Some ports still install
[resend to list]
On 9 May 2015, at 17:20, Lawrence Velázquez lar...@macports.org wrote:
On May 9, 2015, at 11:18 AM, Lawrence Velázquez lar...@macports.org wrote:
Why? Some ports still install to share/examples.
Never mind, just saw #23280.
Ticket #47690 is more specific, it tracks
documentation. This all works
smoothly, but it would not create a consistent build across various installs.
Is there a canonical way to avoid such problems?
Thanks!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https
On 30 Apr 2015, at 14:38, Rainer Müller rai...@macports.org wrote:
On 2015-04-30 13:16, petr wrote:
I am not very familiar with base so far. Am I correct in the
assumption, that this inconsistency could be fixed by replacing
getdefaultportresourcepath with getportresourcepath
that
# the portfetch target will NOT append a subdirectory to
# the mirror site.
}}}
but I still do not understand which effect it will have if this tag was
appended. Can anybody comment on this!
Thanks!
~petr
___
macports-dev mailing list
macports-dev
Hi Rainer,
Hi all,
On 29 Apr 2015, at 19:04, Rainer Müller rai...@macports.org wrote:
On 2015-04-29 18:47, petr wrote:
I am trying to understand how the default livecheck mechanism and the
files in _resources/port1.0/livecheck, are supposed to work. I
somehow assumed the name of the tcl
Hi all,
I am wondering if there is a simple way to avoid fetching distfiles from the
macports mirrors. I would need to do this mainly for testing, or things like to
detect stealth updates or broken master_sites.
Thanks!
~petr
___
macports-dev
On 25 Apr 2015, at 17:49, Lawrence Velázquez lar...@macports.org wrote:
On Apr 25, 2015, at 5:49 AM, petr 9...@ingv.it wrote:
To my understanding the +clang3{0,1,2} refer to clang-3.{0,1,2} respectively.
Yup.
These clang ports are no obsolete.
Yup.
However, there are still quite
Hi all,
To my understanding the +clang3{0,1,2} refer to clang-3.{0,1,2} respectively.
These clang ports are no obsolete.
However, there are still quite some ports around with these variants, so I
guess these clang3{0,1,2} variants (and maybe others) should be removed?
~petr
.
If there are no objections I would proceed in some days.
Thanks!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
requires also a revision bump of the lib dependencies.
Cheers,
~petr
This is what I observed after upgrade:
--- Cleaning freeglut
--- Removing work directory for freeglut
--- Updating database of binaries
--- Scanning binaries for linking errors
Incompatible library version: /opt/local/bin/xterra
Hi all,
now that python 3.5 became available as alpha, wouldn't it make sense to start
activating py35 subports, to get them ready for the release later this year? I
would expect this to take some while, as we have to move through the dependency
tree.
Any thoughts?
~petr
/Portfile
M graphics/libgeotiff/Portfile
I omitted ncarg and qgis, which are not openmaintainer.
~petr
On 16 Mar 2015, at 17:49, Jeremy Huddleston Sequoia jerem...@apple.com wrote:
You need to revbump everything that links against libproj when its dylib id
changes, such as in this version
), that is vince.
~petr
On Mar 16, 2015, at 10:20, petr 9...@ingv.it wrote:
In r133984 I revision bumped some of the ports which needed a rebuild on my
installation.
M databases/spatialite-tools/Portfile
M databases/spatialite/Portfile
M python/py-spatialite/Portfile
with some
inappropriate manipulation to my local sandbox, which than got committed. Is it
possible to understand what exactly went wrong and how to avoid this? What are
the correct steps to correct such a situation?
~petr
On 30 Jan 2015, at 01:45, petr 9...@ingv.it wrote:
Hi list,
I would
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
It worked, but it seems to be down again. Ore is it only me?
~petr
On 19 Nov 2014, at 16:24, Shreeraj Karulkar skarul...@apple.com wrote:
Is its up now and in sync.
Shree Karulkar
Mac OS Forge
skarul...@apple.com
Work: 408.783.2992
Mobile: 650.270.7976
On Nov 19, 2014
On 19 Nov 2014, at 18:49, Shreeraj Karulkar skarul...@apple.com wrote:
Should be good now.
Yes, it looks good. Thanks!
~petr
Shree Karulkar
Mac OS Forge
skarul...@apple.com
Work: 408.783.2992
Mobile: 650.270.7976
On Nov 19, 2014, at 9:37 AM, Brandon Allbery allber
On 16 Nov 2014, at 02:08, Ryan Schmidt ryandes...@macports.org wrote:
On Nov 15, 2014, at 6:35 PM, p...@macports.org wrote:
Revision
128184
Author
p...@macports.org
Date
2014-11-15 16:35:39 -0800 (Sat, 15 Nov 2014)
Log Message
py-metar: correct livecheck
Modified Paths
•
to version 2.1.4
could become:
- gdal: Correct various bugs. Bump to revision 1.
and
- postgis2: Bump to version 2.1.4
respectively.
I believe there is also some policy on this.
Thanks, for considering this!
~petr
___
macports-dev mailing list
On 1 Nov 2014, at 11:55, Ryan Schmidt ryandes...@macports.org wrote:
On Nov 1, 2014, at 1:38 AM, take...@macports.org wrote:
Revision
127693
Author
take...@macports.org
Date
2014-10-31 23:38:02 -0700 (Fri, 31 Oct 2014)
Log Message
cdo: updated to 1.6.5.1
Modified:
-domain. (license Public Domain means This port
is under the license 'Public' and under the license 'Domain'.)
Okay, understand. Done in r126939.
Thanks!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org
the unsupported subport(s) around when updating makes no sense. Right?
Should I add I now?
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On 18 Oct 2014, at 17:45, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 18, 2014, at 9:19 AM, p...@macports.org wrote:
Revision
126965
Author
p...@macports.org
Date
2014-10-18 07:19:30 -0700 (Sat, 18 Oct 2014)
Log Message
py-mssql: update to 2.1.0, remove py24, py25 subport
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
Hi all,
is there a clever way to learn about a maintainers most recent activity?
I am using the Timeline, but this seems not very efficient. The tool is not
very responsive it seems limited to 90 days back.
Any hints?
~petr
___
macports-dev mailing
Hi all,
I get capture errors, when trying to submit a new ticket. Any idea what could
be going on?
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
On 11 Oct 2014, at 11:50, Aljaž Srebrnič a2pirates...@gmail.com wrote:
On 11/ott/2014, at 11:45, petr 9...@ingv.it wrote:
Hi all,
is there a clever way to learn about a maintainers most recent activity?
I am using the Timeline, but this seems not very efficient. The tool is not
very
On 11 Oct 2014, at 12:32, petr 9...@ingv.it wrote:
Hi all,
I get capture errors, when trying to submit a new ticket. Any idea what could
be going on?
~petr
Okay, I now understand what is going on here. Instead of compiling the whole
ticket at once, I subsequently completed
.
In any case, it wasn't suggested to get a local copy of the entire
repository; it was suggested to get a log of the repository.
Okay, Thanks!
I was not aware of this functionality.
~petr
___
macports-dev mailing list
macports-dev
On 11 Oct 2014, at 14:51, Ryan Schmidt ryandes...@macports.org wrote:
On Oct 11, 2014, at 5:32 AM, petr wrote:
I get capture errors, when trying to submit a new ticket. Any idea what
could be going on?
Something about the ticket may be matching our spam filter, which you can
view
creating an account?” and have all registrations
be approved by a Macports committer. But that would be a last resort only.
Involves some extra work. Is it less then marking spam?
Thank you,
Frank
~petr
[1] https://trac.macports.org/ticket/42484
for testing, as some very conservative Linux
distributions still support them for years to come.
When it comes to Py3, I usually provide only py33 and py34 subports for new.
Here I would propose to phase at least py31, but I do not thing py32 is very
useful by now neither.
~petr
On 16 Sep
future.` ?
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
???) or old unmaintained software. But this probably needs some more
attention and maybe some packages py27 subports may need to be added.
Should we use a ticket to track this process?
~petr
--- snip ---
port search `port echo name:py24 | sed 's/py24/py27/'` | grep 'No match'
No match for py27-apycot
to over some of your ports?
Thanks for clarifying?
~petr
[1]
https://trac.macports.org/query?status=!closedowner=mcalhoun%40macports.org
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman
, is there a way to avoid any build on the bots at all,
so we save such unnecessary tentatives?
Thanks!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Mojca,
thanks for looking up the details.
On 20 Aug 2014, at 11:31, Mojca Miklavec mo...@macports.org wrote:
On Wed, Aug 20, 2014 at 10:21 AM, petr wrote:
Hi all,
yesterday I had a look at some ports which require manual download
(py-nio/py-ngl).
Is this a technical issue
On 20 Aug 2014, at 11:31, Mojca Miklavec mo...@macports.org wrote:
On Wed, Aug 20, 2014 at 10:21 AM, petr wrote:
Hi all,
yesterday I had a look at some ports which require manual download
(py-nio/py-ngl).
Is this a technical issue or a licence limitation? It's not yet clear
to me
as with `nomaintainer` as well, or should this be
avoided? What to do with ports where the contributor does not assume
maintainership?
Any thoughts? Thanks!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org
On 24 Jul 2014, at 14:22, Ryan Schmidt ryandes...@macports.org wrote:
On Jul 24, 2014, at 7:13 AM, p...@macports.org wrote:
Revision
122588
Author
p...@macports.org
Date
2014-07-24 05:13:58 -0700 (Thu, 24 Jul 2014)
Log Message
zope-* : add modeline to all zope ports
But the
if someone who knows zope better would like to have a look at
these, or can judge that these are just is not used anymore.
Thanks!
~petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo
Hi Perry,
I am wondering if you are still active on Macports and the port you are
maintaining. There are several unacknowledged tickets regarding the ports you
maintain, so it would be great to understand if you are still interested in
these or if you retired.
Thanks!
~petre
Hi all,
I am not 100% sure if I need to bump revision, when removing a dependency.
The files installed by the port would not change, but to remove the extra
dependency from the registry I need the revision bump anyway, right?
~petr
___
macports-dev
it that if that, if there
are files in the directory file, `delete ${certdir}`, would fail but the error
is catched and no action is performed. On the contrary the `delete` alias
translates to `file delete -force` to remove the directory in any case?
Thanks!
~petr
it builds and it's committed to SVN
thanks a lot,
petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
}=${${_variableName}})
endforeach()
##
The zlib is there for reference (correctly filled).
So what can be wrong? Cmake or OpenCV pkg-config file?
thanks,
petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman
fixes applied locally. All will be part of next version.
Thanks for corrections.
p.
On Mar 3, 2012 (Saturday), at 8:55 PM, Ryan Schmidt wrote:
On Mar 3, 2012, at 13:13, pva...@macports.org wrote:
Revision: 90362
http://trac.macports.org/changeset/90362
Author:
hi all,
what's status now? Should I play with -devel still or will it be switched to
regular qt4-mac?
BTW is there any easy way how to replace qt4-mac with qt4-mac-devel without
uninstalling/deactivating all qt4 deps apps, please?
petr
On Dec 15, 2011 (Thursday), at 2:26 PM, Ryan Schmidt
hi all,
there is a compiler crash report for one of my apps. It's very strange - it
looks like it's a bug in the compiler.
GCC version used by reporter is
CXX compiler: /usr/bin/g++-4.0
It's a very old one. What is usual procedure to track these kind of bugs,
please?
thanks,
petr
Logs
-snowleopard-x86_64/builds/2998
The only thing changed in portfile was version and checksum...
thanks,
Petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
On Nov 13, 2011 (Sunday), at 9:03 PM, Jeremy Lavergne wrote:
The only thing changed in portfile was version and checksum...
The error:
DEBUG: Backtrace: error copying
/opt/local/var/macports/build/_Volumes_work_mports_dports_aqua_qlipper/qlipper/work/qlipper-1.8.2/qlipper.app:
no such
On Nov 14, 2011 (Monday), at 1:18 AM, Ryan Schmidt wrote:
On Nov 13, 2011, at 14:06, Petr Vanek wrote:
On Nov 13, 2011 (Sunday), at 9:03 PM, Jeremy Lavergne wrote:
The only thing changed in portfile was version and checksum...
The error:
DEBUG: Backtrace: error copying
/opt
On Nov 14, 2011 (Monday), at 6:48 AM, Joshua Root wrote:
On 2011-11-14 16:35 , Petr Vanek wrote:
On Nov 14, 2011 (Monday), at 1:18 AM, Ryan Schmidt wrote:
The buildbot has a case-sensitive filesystem. The file is Qlipper.app, not
qlipper.app.
thanks a lot. All is fixed now.
BTW
| `-- deploytest
|-- PkgInfo
`-- Resources
|-- empty.lproj
|-- qt.conf
`-- qt_menu.nib
|-- classes.nib
|-- info.nib
`-- keyedobjects.nib
and now it works.
Is it macports issue or should report it upstream?
thanks,
petr
-BEGIN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 10, 2010 (Friday), at 3:20 PM, Jan Gosmann wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 10.12.10 13:58, schrieb Petr Vanek:
I'm facing strange behavior of assistant, designer, and linguist since
upgrade from 4.6.x to 4.7.x
issue or
upstream one.
thanks,
petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
not be loaded
I don't know this library too much, but shouldn't be there something like Qt4
plugin for phonon as well? How to build it in macports?
cheers,
petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org
::createBackend() phonon backend plugin
could not be loaded
I don't know this library too much, but shouldn't be there something like
Qt4 plugin for phonon as well? How to build it in macports?
Hi Petr - Shortest answer is: I know this is an issue and I'm working on it.
I decided to go ahead
bundling scripts.
thanks,
petr
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
port is much better now.
petr
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQEcBAEBAgAGBQJMwbn0AAoJEC8yRjM4uE2t4s8IAKSAM3bcb+WRMmvOTwBal1g8
dGXiU6s66XLuFpMtnkSoRiTJFBIpktI6myY6/M1Dgf3IxiwJjnQmdO2FTT473DJ0
yQmAoMw7fTltW2zIg6LPXUXCdYG3qwjzOvso29ynlvBZrZ2sQJRi8+NQb2yjmzGr
OdhgNcdHX
versions?
cheers,
Petr
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (Darwin)
iQEcBAEBAgAGBQJMtxW3AAoJEC8yRjM4uE2tKfUH/A6qSmzKtGxqvt16CIXVWFca
Mtg9UkalnkTzChtbjFs1+Bq2Cg5hmktxPRcn9T2qiduyPTYdcW1q6yX7Invl2zsK
cRMDSgvgPdLquxvysNA7vhy7r9BsCN33XTcimLqdu1pTJ1vZ27Ij/ZrXLsZfXr5R
,
Petr Vanek
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
80 matches
Mail list logo
