On 10/29/16 7:19 AM, Clemens Lang wrote:
> On Fri, Oct 28, 2016 at 07:58:16AM -0700, David Evans wrote:
>> Considering that this is a significant event, I'd appreciate it (and
>> others might as well) if a specific date & time, expressed in UTC,
>> could be published today for the disabling of subv
On Fri, Oct 28, 2016 at 07:58:16AM -0700, David Evans wrote:
> Considering that this is a significant event, I'd appreciate it (and
> others might as well) if a specific date & time, expressed in UTC,
> could be published today for the disabling of subversion write access.
We'll try to keep write
On 10/28/16 7:18 AM, Rainer Müller wrote:
> On 2016-10-28 16:02, Craig Treleaven wrote:
>>> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
>>> ...
>>> Migration Timeline
>>> ==
>>> The switch to Git will happen on the weekend of October 29th/30th. ...
>>
>> Is this still on track
On 2016-10-28 16:02, Craig Treleaven wrote:
>> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
>> ...
>> Migration Timeline
>> ==
>> The switch to Git will happen on the weekend of October 29th/30th. ...
>
> Is this still on track?
Yes, expect Subversion to go read-only this wee
> On Oct 28, 2016, at 9:02 AM, Craig Treleaven wrote:
>
>> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
>> ...
>> Migration Timeline
>> ==
>> The switch to Git will happen on the weekend of October 29th/30th. ...
>
> Is this still on track?
Yes.
_
> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
> ...
> Migration Timeline
> ==
> The switch to Git will happen on the weekend of October 29th/30th. ...
Is this still on track?
Craig
___
macports-users mailing list
macports-users@lis
> On Oct 22, 2016, at 9:40 AM, Marko Käning wrote:
>
>> On 22 Oct 2016, at 15:34 , Ryan Schmidt wrote:
>>
>> as well as the "hub" command line program in the "hub" port.
>
> Exactly, that’s the one I meant. Perhaps it’s worth mentioning it on the
> wiki page.
I've added several tools to the l
On 22 Oct 2016, at 15:34 , Ryan Schmidt wrote:
> There's the "git" command line program in the "git" port,
:-) Hahaha. Yes, of course! ;-)
> as well as the "hub" command line program in the "hub" port.
Exactly, that’s the one I meant. Perhaps it’s worth mentioning it on the
wiki page. Haven’t
> On Oct 22, 2016, at 7:49 AM, Marko Käning wrote:
>
> Hi Clemens,
>
> On 22 Oct 2016, at 14:41 , Clemens Lang wrote:
>> Developers will merge them, either using the command line client, or the
>> GitHub UI. We haven't decided and documented which merge method to use,
>> although I'd prefer th
On 22 Oct 2016, at 14:49 , Joshua Root wrote:
> Please see the Migration Timeline section in the first message in this
> thread. Developers cannot yet push to the git repos.
yes, I figured that now.
OK, awaiting you guys’ decisions on the new workflow.
___
Hi Clemens,
On 22 Oct 2016, at 14:41 , Clemens Lang wrote:
> Developers will merge them, either using the command line client, or the
> GitHub UI. We haven't decided and documented which merge method to use,
> although I'd prefer the rebase.
ok, I see.
BTW, you’ve mentioned in some thread latel
On 2016-10-22 23:31 , Marko Käning wrote:
Hi Clemens,
great to see the GitHub conversion progressing this rapidly! Thumbs up from
me!!!
When reading the WorkingWithGit wiki page [1] I saw how port contributors can
post
their suggestions to MacPorts via "Pull Requests”, yet it does not get cl
Hi,
On Sat, Oct 22, 2016 at 02:31:32PM +0200, Marko Käning wrote:
> When reading the WorkingWithGit wiki page [1] I saw how port
> contributors can post their suggestions to MacPorts via "Pull
> Requests”, yet it does not get clear from that text how those PRs will
> then actually be included into
Hi Clemens,
great to see the GitHub conversion progressing this rapidly! Thumbs up from
me!!!
When reading the WorkingWithGit wiki page [1] I saw how port contributors can
post
their suggestions to MacPorts via "Pull Requests”, yet it does not get clear
from
that text how those PRs will then
Hi,
On Sat, Oct 22, 2016 at 07:54:20AM -0400, Richard Cobbe wrote:
> Is there/will there be a story for people who cannot use rsync to pull
> down updates because they're behind a restrictive proxy?
>
> This affects one of the three computers on which I maintain a MacPorts
> installation. I curr
> On Oct 22, 2016, at 6:54 AM, Richard Cobbe wrote:
>
> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
>> Hello MacPorts users and developers,
>>
>> MacPorts will be moving to GitHub soon. We're sending this email to
>> inform you about changes in how you access the MacPorts repo
> On 22 Oct 2016, at 12:54 pm, Richard Cobbe wrote:
>
>> On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
>> Hello MacPorts users and developers,
>>
>> MacPorts will be moving to GitHub soon. We're sending this email to
>> inform you about changes in how you access the MacPorts re
On Fri, Oct 21, 2016 at 08:12:59PM +0200, Clemens Lang wrote:
> Hello MacPorts users and developers,
>
> MacPorts will be moving to GitHub soon. We're sending this email to
> inform you about changes in how you access the MacPorts repositories and
> bug tracker. Additionally, this email contains in
On 2016-10-21, at 8:03 PM, Lawrence Velázquez wrote:
>> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote:
>>
>>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote:
>>>
On Oct 21, 2016, at 10:20 PM, Craig Treleaven
wrote:
Also, is the consensus that a graphical user
On 2016-10-21, at 8:03 PM, Lawrence Velázquez wrote:
>> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote:
>>
>>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote:
>>>
On Oct 21, 2016, at 10:20 PM, Craig Treleaven
wrote:
Also, is the consensus that a graphical user
> On Oct 21, 2016, at 10:55 PM, Ryan Schmidt wrote:
>
>> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote:
>>
>>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven
>>> wrote:
>>>
>>> Also, is the consensus that a graphical user interface over git
>>> more likely to be harmful than helpful?
> On Oct 21, 2016, at 9:47 PM, Lawrence Velázquez wrote:
>
>> On Oct 21, 2016, at 10:20 PM, Craig Treleaven
>> wrote:
>>
>> However, would it be possible to add a tangible example of updating
>> a port to that page?
>>
>> I know a little bit about Subversion and less about Git. I would li
> On Oct 21, 2016, at 10:20 PM, Craig Treleaven wrote:
>
> However, would it be possible to add a tangible example of updating
> a port to that page?
>
> I know a little bit about Subversion and less about Git. I would like
> to see a soup-to-nuts example of cloning the ports tree, updating
>
> On Oct 21, 2016, at 2:12 PM, Clemens Lang wrote:
>
> Hello MacPorts users and developers,
>
> ... Please read through
> https://trac.macports.org/wiki/WorkingWithGit
> which contains a number of guidelines for working with the MacPorts Git
> repositories.
>
The Working with Git page is pretty
Thank you Clemens. That is great.
Cheers,
Joe
On Fri, Oct 21, 2016 at 11:12 AM, Clemens Lang wrote:
> Hello MacPorts users and developers,
>
> MacPorts will be moving to GitHub soon. We're sending this email to
> inform you about changes in how you access the MacPorts repositories and
> bug tr
Hello MacPorts users and developers,
MacPorts will be moving to GitHub soon. We're sending this email to
inform you about changes in how you access the MacPorts repositories and
bug tracker. Additionally, this email contains information on planned
downtimes.
Action Required: GitHub Accounts
t;>>>
>>>>> Ok, but the activation conflict is resolved?
>>>>>
>>>>>> I activated gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3 (which are still
>>>>>> installed) and kmoney4 opened as before.
>>>>>>
>>>&g
ed gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3 (which are still
>>>>> installed) and kmoney4 opened as before.
>>>>>
>>>>> I uninstalled gpgme @1.7.0_0 and kdepimlibs4 @4.14.3_4, then did a self
>>>>> update and upgrade outdated. After the u
the process again failed at
>>>> rebuilding kmymoney4.
>>>
>>> Ok, but the activation conflict is resolved?
>>>
>>>> I activated gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3 (which are still
>>>> installed) and kmoney4 opened as before.
; Ok, but the activation conflict is resolved?
>>
>>> I activated gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3 (which are still
>>> installed) and kmoney4 opened as before.
>>>
>>> I uninstalled gpgme @1.7.0_0 and kdepimlibs4 @4.14.3_4, then did a self
>>&g
t;> Thank you for your suggestion. I followed the steps as suggested (using the
>> correct spelling for the upgrade step) but the process again failed at
>> rebuilding kmymoney4.
>
> Ok, but the activation conflict is resolved?
>
>> I activated gpgme @1.6.0_2 and kd
Hi Stanton,
I’ve added you to my ticket [1] which documents that the port currently doesn’t
configure due to qgpgme with stock kdelibs4 installed.
Greets,
Marko
[1] https://trac.macports.org/ticket/52471
___
macports-users mailing list
macports-user
; rebuilding kmymoney4.
Ok, but the activation conflict is resolved?
> I activated gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3 (which are still
> installed) and kmoney4 opened as before.
>
> I uninstalled gpgme @1.7.0_0 and kdepimlibs4 @4.14.3_4, then did
;>> Supposedly fixed now but I haven't synced and tested myself yet. Have you
>>> done sync/selfupdate recently?
>>>
>>> Jonathan
>>>
>>>
>>>> On 9/29/16 13:00 , macports-users-requ...@lists.macosforge.org wrote:
>>>> Da
nathan
>>
>>
>>> On 9/29/16 13:00 , macports-users-requ...@lists.macosforge.org wrote:
>>> Date: Thu, 29 Sep 2016 09:41:30 -0500
>>> From: Stanton Sanderson
>>> To: MacPorts Users
>>> Subject: kmymoney4 broken after update
>>> Mess
>> On 9/29/16 13:00 , macports-users-requ...@lists.macosforge.org wrote:
>> Date: Thu, 29 Sep 2016 09:41:30 -0500
>> From: Stanton Sanderson
>> To: MacPorts Users
>> Subject: kmymoney4 broken after update
>> Message-ID:
>> Content-Type: text/plain; char
16 09:41:30 -0500
From: Stanton Sanderson
To: MacPorts Users
Subject: kmymoney4 broken after update
Message-ID:
Content-Type: text/plain; charset=utf-8
OS- El Capitan
Kmymoney4 is broken after yesterday updating yesterday (and again today). The
message received
is
Error rebuilding kmym
re Could NOT find QGpgme (missing: _QGPGME_EXTRA_LIBRARY)
>> :info:configure Call Stack (most recent call first):
>> :info:configure
>> /opt/local/share/cmake-3.6/Modules/FindPackageHandleStandardArgs.cmake:388
>> (_FPHSA_FAILURE_MESSAGE)
>> :info:configure /opt/l
ank you for your suggestion. I followed the steps as suggested (using the
correct spelling for the upgrade step) but the process again failed at
rebuilding kmymoney4. I activated gpgme @1.6.0_2 and kdepimlibs4 @4.14.3_3
(which are still installed) and kmoney4 opened as before.
I uninstalled gpgm
(_FPHSA_FAILURE_MESSAGE)
> :info:configure /opt/local/share/apps/cmake/modules/FindQGpgme.cmake:43
> (find_package_handle_standard_args)
> :info:configure CMakeLists.txt:72 (find_package)
> :i..
> ——
> A few days ago, one of updated ports would not install (gpgme ? ), citing
andardArgs.cmake:388
(_FPHSA_FAILURE_MESSAGE)
:info:configure /opt/local/share/apps/cmake/modules/FindQGpgme.cmake:43
(find_package_handle_standard_args)
:info:configure CMakeLists.txt:72 (find_package)
:i..
——
A few days ago, one of updated ports would not install (gpgme ? ), citing a
conflict but sugg
On 28 Aug, 2016, at 13:16EDT, Rainer Müller wrote:
> No, verification of PGP signatures is not provided by base. gpg is not
> available on an standard OS X install. Adding that as a requirement just
> to verify the distfile would be quite heavy.
Oh, absolutely! I wasn’t suggesting making it a req
On 2016-08-28 18:46, Gabriel Rosenkoetter wrote:
> Apologies if this is a common question (if there’s a way to search PiperMail
> archives that isn’t “download all of them and use grep locally”, I’ve never
> known what it was), but I didn’t see an explicit facility to list a
> cryptographic sign
Thank you both for your responses! (Sorry it took me a bit to follow through on
them; my day job intervened.)
> On 21 August 2016 at 13:32, Yongwei Wu wrote:
>> Maybe the following two links?
>>
>> https://trac.macports.org/wiki/howto/InstallingOlderPort
>> https://guide.macports.org/#developmen
gt;> The note in that bug report about the upstream bug is exactly correct, and
>> the fix is available in the relatively recently (April 2016, I think) 2.7.2
>> upstream release.
>>
>> I think this should be relatively simple to fix, and I'd like to
version (2.7).
>
> The note in that bug report about the upstream bug is exactly correct, and
> the fix is available in the relatively recently (April 2016, I think) 2.7.2
> upstream release.
>
> I think this should be relatively simple to fix, and I'd like to learn how
>
learn how to
do that and contribute the update. Any pointers where I should start reading?
(Yes, I could go slog through the whole of the relevant documentation, but I
do, as I'm sure you all do, have a day job, so a shove in the right direction
may help.)
(I do also have some other sugges
On Fri, May 27, 2016 at 6:05 AM, Bjarne D Mathiesen <
macint...@mathiesen.info> wrote:
> On the other hand, my Xcode 4.0.1 on my 64bit 10.6.8 hasn't given me any
> problems at all !?! but I chose to downgrade anyway ;-)
>
I ran with that configuration for several years and never saw a problem. I
Bjarne D Mathiesen wrote:
> Ryan Schmidt wrote:
>>
>>> To downgrade to 3.2.6 will it be as simple as dumping the /Developer
>>> directory, downloading Xcode 3.2.6 and trying kerberos5 again? Or will I
>>> need to uninstall all ports and start over?
>>
>> Follow the Xcode uninstallation instruc
Ryan Schmidt wrote:
>
>> To downgrade to 3.2.6 will it be as simple as dumping the /Developer
>> directory, downloading Xcode 3.2.6 and trying kerberos5 again? Or will I
>> need to uninstall all ports and start over?
>
> Follow the Xcode uninstallation instructions provided by Apple in the Abo
Terry Barnum wrote:
> It's a Macmini1,1 which I don't believe can run anything later.
I've got one of those too. It's true, that it the max OS X is 10.6.8
!!!BUT!!! you can upgrade the CPU to a
Intel Core 2 Duo T7200 / 2 GHz Processor
and thus be able to run 10.7; and using a hack, you can
t;
>
>>> If using gcc-4.2 works where llvm-gcc-4.2 failed, we should update the port
>>> to blacklist llvm-gcc-4.2.
>>
>> If I can downgrade easily I'll report back if gcc-4.2 works.
Thank you Ryan. Finally had some time to spend on this. Downgrading Xcode di
ut
Xcode.pdf file. There's a script your run in the terminal, which knows what all
needs to be deleted. Then, since you're going to downgrade, you restart the
computer before reinstalling the older Xcode.
You don't need to reinstall MacPorts or all ports. There may be one or two
po
grade to 3.2.6 will it be as simple as dumping the /Developer directory,
downloading Xcode 3.2.6 and trying kerberos5 again? Or will I need to uninstall
all ports and start over?
> If using gcc-4.2 works where llvm-gcc-4.2 failed, we should update the port
> to blacklist llvm-gcc-4.2.
Hi,
On Sun, Apr 03, 2016 at 11:00:24AM +0200, Kurt Pfeifle wrote:
> On Sun, Apr 3, 2016 at 3:17 AM, Clemens Lang wrote:
> > On Sat, Apr 02, 2016 at 10:59:11PM +0200, Kurt Pfeifle wrote:
> > > Maybe I can convince MacPorts developers to change where they
> > > fetch their own sources? I'm not sure
On May 2, 2016, at 1:39 PM, Terry Barnum wrote:
> A kerberos5 update (1.13.2_1 -> 1.14.2.0) failed when doing a 'port upgrade
> outdated' so I tried 'port upgrade --force kerberos5' but after all the
> dependencies were reebuilt it still failed. This is on a
On Tue, May 3, 2016 at 11:16 AM, Richard L. Hamilton
wrote:
> I don't know if you have a /usr/bin/gcc-4.2 that's different from
> /usr/bin/llvm-gcc-4.2, but I did. That might vary according to the history
> of Xcode versions installed, or some such.
>
There are gcc packages in MacPorts, and onc
May 2, 2016, at 14:39, Terry Barnum wrote:
>
> A kerberos5 update (1.13.2_1 -> 1.14.2.0) failed when doing a 'port upgrade
> outdated' so I tried 'port upgrade --force kerberos5' but after all the
> dependencies were reebuilt it still failed. This is on a Macmini
A kerberos5 update (1.13.2_1 -> 1.14.2.0) failed when doing a 'port upgrade
outdated' so I tried 'port upgrade --force kerberos5' but after all the
dependencies were reebuilt it still failed. This is on a Macmini1,1 (1.83GHz
Core Duo) running MacPorts 2.3.4 on OS X 10.6.8
pdated.
At this time, nobody has signed up to be sunwait's MacPorts maintainer. If
you're interested in sunwait, you could help the process along by providing a
patch in the ticket to update the port. If you're interested in being the
maintaine
Is there any chance of MacPorts providing the latest version of sunwait? The
version on MacPorts is woefully out of date and the original authors web site
says he is no longer working on it and has passed responsibility to Ian Craig
here;- https://sourceforge.net/projects/sunwait4windows/
On Sun, Apr 3, 2016 at 3:17 AM, Clemens Lang wrote:
>
> On Sat, Apr 02, 2016 at 10:59:11PM +0200, Kurt Pfeifle wrote:
> > Maybe I can convince MacPorts developers to change where they fetch
> > their own sources?
> > I'm not sure if it indeed is so -- but the last sentence seems to
> > suggest to
Hi,
On Sat, Apr 02, 2016 at 10:59:11PM +0200, Kurt Pfeifle wrote:
> Maybe I can convince MacPorts developers to change where they fetch
> their own sources?
> I'm not sure if it indeed is so -- but the last sentence seems to
> suggest to me that MacPorts still fetches GS source tarball from
> Sour
a checksum issue.
>
> That's https://trac.macports.org/ticket/51019. Upstream re-packaged the
> files we downloaded, but they forgot to update the SHA1SUMS file, so I
> did hold off accepting the change until they confirmed.
>
> > I wonder whether there might be some way for
ning, but there's
> still a checksum issue.
That's https://trac.macports.org/ticket/51019. Upstream re-packaged the
files we downloaded, but they forgot to update the SHA1SUMS file, so I
did hold off accepting the change until they confirmed.
> I wonder whether there might be some
On 01/04/2016 10:02, Carlo Tambuatco wrote:
> From latest upgrade of outdated ports:
>
> ---> Computing dependencies for ghostscript
> ---> Verifying checksums for ghostscript
> Error: Checksum (rmd160) mismatch for ghostscript-9.19.tar.gz
> Error: Checksum (sha256) mismatch for ghostscript-9.19
>From latest upgrade of outdated ports:
---> Computing dependencies for ghostscript
---> Verifying checksums for ghostscript
Error: Checksum (rmd160) mismatch for ghostscript-9.19.tar.gz
Error: Checksum (sha256) mismatch for ghostscript-9.19.tar.gz
Error: org.macports.checksum for port ghostscri
I updated dovecot2 from 2.2.19_1 to 2.2.22_0 but had to back out because of
errors about dovecot2-antispam 0.0-51_12 ABI being incompatible. Will
dovecot2-antispam be updated or is there a workaround?
> Mar 21 14:05:31 mail dovecot[16635]: imap(u...@domain.com): Error: Couldn't
> load required
On Dec 06 18:45:11, h...@stare.cz wrote:
> > On Nov 26 20:20:28, nore...@macports.org wrote:
> > > #49821: libsndfile - update to 1.0.26
> > > -+
> > > Reporter: hans@??? | Owner: macports-tick
> On Dec 6, 2015, at 11:45 AM, Jan Stary wrote:
>
>> On Nov 26 20:20:28, nore...@macports.org wrote:
>>> #49821: libsndfile - update to 1.0.26
>>> -+
>>> Reporter: hans@??? | Owner: macp
> On Nov 26 20:20:28, nore...@macports.org wrote:
> > #49821: libsndfile - update to 1.0.26
> > -+
> > Reporter: hans@??? | Owner: macports-tickets@???
> > Type: update | Status:
-- --
??: "Ryan Schmidt";;
: 2015??9??22??(??) 1:36
??: ""<275438...@qq.com>;
: "MacPorts Users";
: Re: fail to update the port of paparazzi and fail to install the port of
i
;> > macport.However ,it gets error while it is updating with"sudo port self
>> > update".Meanwhile,it can't install paparazzi-tools since the ivy-c can't
>> > be installed.
>>
>> > :info:build 'g++'-I../src -o ivyth
On Sep 21, 2015, at 11:26 AM, 心如烛光 wrote:
> I wanna reinstall the paparazzi for my osx(10.8.5) with macport.However
> ,it gets error while it is updating with"sudo port self update".Meanwhile,it
> can't install paparazzi-tools since the ivy-c can't be installe
Hi,everybody!
I wanna reinstall the paparazzi for my osx(10.8.5) with macport.However ,it
gets error while it is updating with"sudo port self update".Meanwhile,it can't
install paparazzi-tools since the ivy-c can't be installed.
The message of the selfupdate:
$:s
On Thu, 3 Sep 2015, Ryan Schmidt wrote:
> > Same Lynx version on FreeBSD works OK, so Macports' is busted.
>
> Does FreeBSD use ncurses 5 or 6?
Aha! It's (currently) using 5.9 (I did see that later reply). So yep, it
appears to be a problem with the way that Lynx uses Ncurses 6.
And I can't
On Sep 3, 2015, at 3:04 PM, Dave Horsfall wrote:
> Same Lynx version on FreeBSD works OK, so Macports' is busted.
Does FreeBSD use ncurses 5 or 6?
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists.macosforge.org/mailma
On Thu, 3 Sep 2015, David Vergnaud wrote:
> So now I'm annoyed that lynx got broken and surprised that the situation
> doesn't seem consistent.
Hmmm... Busted here too (2.8.8rel.2 on 10.10.5).
Lynxlet still works, though, but I can't tell what version it is.
Same Lynx version on FreeBSD works
On Sep 3, 2015, at 10:05 AM, David Vergnaudwrote:
> I've just run a "port upgrade outdated" on my Yosemite 10.10.5 iMac. Quite
> honestly, I can't remember when was the last time I did, but I think it can't
> have been that long since I got the Mac only a few months ago and that's got
> to be
Last post left out OS 10.10.5, MacBook Air, all OS and developer updates
applied.
On my iMac running the same OS, mariadb successfully updated to 5.5.43_2.
(Recap- fetch of upgrade to mariadb 5.5.43_2 stops at 99.9%, tries next site,
gets
the same results, repeats until it gives up.)
Stan
__
Yes, these are the DNS settings for me too.
On Mon, Jul 13, 2015 at 6:53 PM, Brandon Allbery
wrote:
> On Mon, Jul 13, 2015 at 8:59 AM, mohit rastogi
> wrote:
>
>> rsync: getaddrinfo: rsync.macports.org
>>
>> 873: nodename nor servname provided, or not known
>
> Check your DNS config. (I keep 8.
On Mon, Jul 13, 2015 at 8:59 AM, mohit rastogi
wrote:
> rsync: getaddrinfo: rsync.macports.org
>
> 873: nodename nor servname provided, or not known
Check your DNS config. (I keep 8.8.8.8 and 8.8.4.4 around as backup DNS, as
my provider sometimes screws up their DNS.)
--
brandon s allbery kf8
> On Jun 8, 2015, at 7:32 AM, Jan Stary wrote:
>
> On Jun 08 14:27:33, h...@stare.cz wrote:
>> On Jun 08 02:32:01, nore...@macports.org wrote:
>>> #47790: pstree: update to 2.39
>>> -+--
>>> Reporter: hans
On Jun 8, 2015, at 8:32 AM, Jan Stary wrote:
> Are the ports that install no libraries supposed to say so?
Yes. This prevents MacPorts from rebuilding them as +universal if
a dependent's architecture doesn't match.
> From the top of my head, there are many ports that don't.
Those ports are wro
On Jun 08 14:27:33, h...@stare.cz wrote:
> On Jun 08 02:32:01, nore...@macports.org wrote:
> > #47790: pstree: update to 2.39
> > -+--
> > Reporter: hans@??? | Owner: mww@???
> > Type: update | Status: clo
(ping)
On May 21 13:54:29, nore...@macports.org wrote:
> #47790: update pstree to 2.39
> -+--
> Reporter: hans@??? | Owner: mww@???
> Type: update | Status: new
> Priority: Normal | Milestone:
> Component: po
ping
> On Apr 26 19:40:17, nore...@macports.org wrote:
> > #46947: sox: please update to @14.4.2
> > -+
> > Reporter: mopihopi@??? | Owner: hans@???
> > Type: update | Status: new
> > Pr
That was a while ago.
On Mar 22, 2015, at 2:35 PM, Ryan Schmidt wrote:
>
> On Mar 22, 2015, at 8:33 AM, Mark Brethen wrote:
>
>> I switched to this mirror because of all the connection problems with the
>> main. What do I do now?
>
> You've been having connection problems with the main serv
On Mar 22, 2015, at 8:33 AM, Mark Brethen wrote:
> I switched to this mirror because of all the connection problems with the
> main. What do I do now?
You've been having connection problems with the main server?
___
macports-users mailing list
macpo
Nevermind, I forgot to use 'sudo'. It's funny how much you can overlook when
you've been away from it for awhile.
On Mar 22, 2015, at 8:33 AM, Mark Brethen wrote:
> ###
>
> This mirror is managed by Pacific Northwest
###
This mirror is managed by Pacific Northwest National Labratory.
It is located in Richland, WA.
If you have any questions, or problems, please email:
mirror at pnnl dot gov
##
On Thu, Feb 26, 2015 at 3:55 PM, Jan Stary wrote:
> Why is it then that e.g. gperf, xz, gettext, expat etc
> are not checked in the "complete hierarchy of dependencies"?
>
gperf is a build dependency for libiconv, so is not needed at any time
other than while libiconv is being built from source.
On Feb 26 15:38:53, rai...@macports.org wrote:
> On 2015-02-26 15:19, Jan Stary wrote:
> > Going through the log of the build,
> > I see that it not only checks for the libraries
> > mentioned as dependencies in the Portfile,
> > but also checks for ncurses and libiconv.
> >
> > I don't see them m
On 2015-02-26 15:19, Jan Stary wrote:
> Going through the log of the build,
> I see that it not only checks for the libraries
> mentioned as dependencies in the Portfile,
> but also checks for ncurses and libiconv.
>
> I don't see them mentioned anywhere in SoX;
> is this somehow internal to macpo
Going through the log of the build,
I see that it not only checks for the libraries
mentioned as dependencies in the Portfile,
but also checks for ncurses and libiconv.
I don't see them mentioned anywhere in SoX;
is this somehow internal to macports?
The resulting sox binary does not depend on th
t
>> should have been, that would explain the problem.
>
> do we still have a chance to somehow figure out whether this was indeed the
> case?
>
> Do I need to resurrect the old configuration in a VM and then retry the update
> on it? If so, which versions should I chec
ll have a chance to somehow figure out whether this was indeed the
case?
Do I need to resurrect the old configuration in a VM and then retry the update
on it? If so, which versions should I check and how is that achieved?
Greets,
Marko
___
macports-user
Hi,
- On 24 Feb, 2015, at 15:58, Mihai Moldovan io...@macports.org wrote:
> Have you tried running ,,port rev-upgrade''? Issues like these should be
> caught by rev-upgrade.
Rev-upgrade checks dylib version numbers, not actual symbol names. If the
symbol was removed, but the compatibility ve
Hi Daniel,
On 24 Feb 2015, at 20:58 , Daniel J. Luke wrote:
> even if it was, you'd want to revbump it.
yes, indeed, you are right! One shouldn’t rely on rev-upgrade, as people
might have disabled it locally for some reason.
As I said: I am sorry, as this was absolutely an avoidable oversight
> On Feb 24, 2015, at 2:34 PM, Marko Käning wrote:
> Obviously rev-upgrade wasn’t handling this as it is supposed to do,
> for whatever reason. So, I think, I should give kmymoney4 a revbump!
even if it was, you'd want to revbump it.
--
Daniel J. Luke
1 - 100 of 704 matches
Mail list logo