Hello Macports list,
I'm having trouble upgrading package boost using the command, port upgrade
outdated.
It looks like my system is not able to download the full package form the
repository.
The download seems to get almost half way then aborts goes to the next
repo source.
Anyone else see
On Apr 23, 2015, at 6:37 PM, wilson wnorth...@gmail.com wrote:
Hello Macports list,
I'm having trouble upgrading package boost using the command, port upgrade
outdated.
It looks like my system is not able to download the full package form the
repository.
The download seems to get
, at 6:37 PM, wilson wnorth...@gmail.com wrote:
Hello Macports list,
I'm having trouble upgrading package boost using the command, port
upgrade outdated.
It looks like my system is not able to download the full package form
the repository.
The download seems to get almost half way
On Dec 19, 2013, at 2:49 PM, Michael Dickens michae...@macports.org wrote:
Hi Jerry - I just updated my 10.9 boot to 10.9.1, then updated MacPorts
to latest; Xcode did not change. Then uninstalled octave and reinstalled
it. No issues for me. Just a guess: Your MacPorts install is out of
On Dec 19, 2013, at 15:00, Jerry wrote:
On Dec 19, 2013, at 1:40 AM, Ryan Schmidt wrote:
MacPorts should not be supplying -arch flags to compilers like fortran that
do not understand them.
MacPorts bases its decision on whether -arch flags are supported on the
value of
On Dec 19, 2013, at 2:49 PM, Michael Dickens michae...@macports.org wrote:
Hi Jerry - I just updated my 10.9 boot to 10.9.1, then updated MacPorts
to latest; Xcode did not change. Then uninstalled octave and reinstalled
it. No issues for me. Just a guess: Your MacPorts install is out of
On Dec 20, 2013, at 2:38 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Dec 19, 2013, at 15:00, Jerry wrote:
On Dec 19, 2013, at 1:40 AM, Ryan Schmidt wrote:
MacPorts should not be supplying -arch flags to compilers like fortran that
do not understand them.
MacPorts bases its
On Dec 20, 2013, at 04:36, Jerry wrote:
On Dec 20, 2013, at 2:38 AM, Ryan Schmidt wrote:
I don’t know how far the problem reaches.
I did see in your output that you’re using gcc45. Any particular reason? The
default is now gcc48; you could try that instead. That may help; parts of
gcc
On Dec 20, 2013, at 05:01, Jerry wrote:
On Dec 20, 2013, at 3:43 AM, Ryan Schmidt wrote:
On Dec 20, 2013, at 04:36, Jerry wrote:
Also: Can you comment on Michael's suggestion?
Michael suggested you install the octave port with the variants you
need/want. You appear to have been
On Dec 18, 2013, at 21:12, Jerry lancebo...@qwest.net wrote:
Hi list,
I ran port upgrade outdated today and it errored out on octave with this:
--- Configuring octave
Error: Failed to configure octave, consult
/opt/local/var/macports/build
On Dec 19, 2013, at 1:40 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Dec 18, 2013, at 21:12, Jerry lancebo...@qwest.net wrote:
Hi list,
I ran port upgrade outdated today and it errored out on octave with this:
--- Configuring octave
Error: Failed to configure octave
Hi Jerry - I just updated my 10.9 boot to 10.9.1, then updated MacPorts
to latest; Xcode did not change. Then uninstalled octave and reinstalled
it. No issues for me. Just a guess: Your MacPorts install is out of
date. Try:
{{{
sudo port clean octave
sudo port selfupdate
sudo port install octave
On Aug 15, 2013, at 15:04, Ryan Schmidt wrote:
Unless you or someone can show us the logs of why this failed, we cannot
resolve the problem. I can try to build the port on my Snow Leopard system
later on, if nobody else reproduces the problem by then. The problem is I
usually do not
On Aug 15, 2013, at 08:04, Ryan Schmidt wrote:
On Aug 15, 2013, at 07:57, René J.V. Bertin wrote:
Unrelated similar symptoms: on my 10.6.8 system port upgrade outdated also
failed, specifically on llvm-3.3 . My default compiler is Apple's gcc-4.2 .
I finally managed to bootstrap
Unrelated similar symptoms: on my 10.6.8 system port upgrade outdated also
failed, specifically on llvm-3.3 . My default compiler is Apple's gcc-4.2 . I
finally managed to bootstrap the upgrade process by using macports-gcc-4.7 to
build first clang-3.3 and then llvm-3.3 . As a result I don't
On Aug 15, 2013, at 07:57, René J.V. Bertin wrote:
Unrelated similar symptoms: on my 10.6.8 system port upgrade outdated also
failed, specifically on llvm-3.3 . My default compiler is Apple's gcc-4.2 . I
finally managed to bootstrap the upgrade process by using macports-gcc-4.7 to
build
not sure whether this should be reported via the ticket system:
I just tried to `upgrade outdated' after a `selfupdate' and this failed
with:
sudo port upgrade outdated
--- Fetching archive for apr
--- Attempting to fetch apr-1.4.8_0.darwin_12.x86_64.tbz2 from
http
On Wed, Aug 14, 2013 at 7:13 AM, j. van den hoff
veedeeh...@googlemail.comwrote:
--- Cleaning apr-util
Error: arpack: Variant openmpi conflicts with gcc43
Error: Unable to open port: Error evaluating variants
To report a bug, follow the instructions in the guide:
On Wed, 14 Aug 2013 16:07:11 +0200, Brandon Allbery allber...@gmail.com
wrote:
On Wed, Aug 14, 2013 at 7:13 AM, j. van den hoff
veedeeh...@googlemail.comwrote:
--- Cleaning apr-util
Error: arpack: Variant openmpi conflicts with gcc43
Error: Unable to open port: Error evaluating variants
To
On Aug 14, 2013, at 09:18, j. van den hoff wrote:
On Wed, 14 Aug 2013 16:07:11 +0200, Brandon Allbery wrote:
The openmpi variant used to incorrectly allow that, but openmpi is itself a
(wrapper around a) compiler so you must either consistently use it
everywhere or risk odd build issues due
Hi Arno,
I see the following error in the log. Where is portsign.sh? What is it
for? Thanks.
/usr/local/bin/periodic-port.sh: line 43: /usr/local/bin/portsign.sh:
No such file or directory
On Sat, Apr 27, 2013 at 9:47 PM, Arno Hautala a...@alum.wpi.edu wrote:
The basics are that the shell
On Tue, Apr 30, 2013 at 12:32 PM, Peng Yu pengyu...@gmail.com wrote:
I see the following error in the log. Where is portsign.sh? What is it
for? Thanks.
If you read the message you're replying to...
You can remove the reference to portsign.sh, unless you want to
share your compiled ports
Hi,
I have the following crontab entry
/tmp$ sudo crontab -l
0 1 * * * sudo nice /opt/local/bin/bash -c set -v; ((echo '== port
selfupdate =='; /opt/local/bin/port selfupdate) (echo '== port
upgrade outdated =='; /opt/local/bin/port upgrade outdated))
/tmp/portupdate.log 21
But I always see
On Apr 27, 2013, at 08:10, Peng Yu wrote:
I have the following crontab entry
/tmp$ sudo crontab -l
0 1 * * * sudo nice /opt/local/bin/bash -c set -v; ((echo '== port
selfupdate =='; /opt/local/bin/port selfupdate) (echo '== port
upgrade outdated =='; /opt/local/bin/port upgrade outdated
) (echo '== port
upgrade outdated =='; /opt/local/bin/port upgrade outdated))
/tmp/portupdate.log 21
But I always see the following error message.
/tmp$ cat portupdate.log
== port selfupdate ==
--- Updating MacPorts base sources using rsync
Error: /opt/local/bin/port: port selfupdate
On Apr 27, 2013, at 13:39, Stephen Rasku wrote:
Can you even run sudo inside a cron entry? You won't be able to
automatically enter the password.
There would have to be an entry in /etc/sudoers negating the need for typing a
password for this command.
You might have to put the entry into
On Sat, Apr 27, 2013 at 04:16:50PM -0500, Ryan Schmidt wrote:
And running MacPorts via root instead of via sudo will currently cause some
problems:
http://trac.macports.org/ticket/34221
You could use the workaround I proposed in
Hi,
Where should I put these files and what commands shall be used to load them?
On Sat, Apr 27, 2013 at 8:55 PM, Arno Hautala a...@alum.wpi.edu wrote:
I use the following launchd task [1] and shell script [2] to automate
weekly updates.
You can remove the reference to portsign.sh, unless
The basics are that the shell script goes in /usr/local/bin (or
anywhere else really, just make sure you edit the plist to point to
where the script is). The plist goes in `/Library/LaunchDaemons/`,
should be owned by root:admin and have 644 permissions. You can then
load the service with:
On 15/03/2013, Lawrence Velázquez lar...@macports.org wrote:
On Mar 14, 2013, at 11:59 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Mar 14, 2013, at 20:38, Sam Kuper wrote:
I had a Macbook running OS X 10.6.8 crash just now due to a TLB
invalidation IPI timeout.
What do you mean
On Mar 14, 2013, at 9:38 PM, Sam Kuper sam.ku...@uclmail.net wrote:
(c) which additional step(s) I ought to take to ensure the integrity
of the Macports installation and of the installed ports.
Not MacPorts-specific, but you should probably run Disk Utility to repair the
consistency of your
On Mar 15, 2013, at 08:07, Lawrence Velázquez wrote:
On Mar 14, 2013, at 9:38 PM, Sam Kuper wrote:
(c) which additional step(s) I ought to take to ensure the integrity
of the Macports installation and of the installed ports.
Not MacPorts-specific, but you should probably run Disk Utility
On Mar 15, 2013, at 10:42 AM, Ryan Schmidt ryandes...@macports.org wrote:
On Mar 15, 2013, at 08:07, Lawrence Velázquez wrote:
On Mar 14, 2013, at 9:38 PM, Sam Kuper wrote:
(c) which additional step(s) I ought to take to ensure the integrity
of the Macports installation and of the
On 15/03/2013, Lawrence Velázquez lar...@macports.org wrote:
On Mar 14, 2013, at 9:38 PM, Sam Kuper sam.ku...@uclmail.net wrote:
(c) which additional step(s) I ought to take to ensure the integrity
of the Macports installation and of the installed ports.
Not MacPorts-specific, but you should
Dear all,
I had a Macbook running OS X 10.6.8 crash just now due to a TLB
invalidation IPI timeout.
On that Macbook, I had recently run sudo port selfupdate, which
completed without errors, and had then executed sudo port upgrade
outdated, which was in the middle of running.
The Macbook has now
run sudo port selfupdate, which
completed without errors, and had then executed sudo port upgrade
outdated, which was in the middle of running.
The Macbook has now been rebooted and appears to be running OK, but
I'm not sure what caused the crash. At this point, I've no reason to
believe
On Mar 14, 2013, at 11:59 PM, Ryan Schmidt ryandes...@macports.org wrote:
On Mar 14, 2013, at 20:38, Sam Kuper wrote:
I had a Macbook running OS X 10.6.8 crash just now due to a TLB
invalidation IPI timeout.
What do you mean crash? Do you mean a kernel panic that forced you to
restart
On 22.01.13 00:22, Jeremy Lavergne wrote:
Thanks for the explanation Jeremy.
I posted a ticket # 37733
Is it all OK like that?
Yup, the ticket is a good start.
In the ticket, you show us
Error: The following dependencies were not installed: ffmpeg
Error: Unable to upgrade port: 1 Error
How can I get a fresh log for strigi? Pardon, but I have never had issues
with MacPorts before, and do not know much more that the two commands I used
above, and to install a port like midnight commander mc. I actually wanted to
install digikam, but got stuck with the upgrade outdated.
On Jan 22, 2013, at 10:13, lllact...@gmx.net wrote:
On 22.01.13 00:22, Jeremy Lavergne wrote:
Thanks for the explanation Jeremy.
I posted a ticket # 37733
Is it all OK like that?
Yup, the ticket is a good start.
In the ticket, you show us
Error: The following dependencies were
MacPorts hasn't gotten to rebuilding strigi yet; it got stuck on strigi's
dependency ffmpeg.
Ah, thanks Ryan. I'm misreading the logs again.
___
macports-users mailing list
macports-users@lists.macosforge.org
On 22.01.13 17:20, Jeremy Lavergne wrote:
MacPorts hasn't gotten to rebuilding strigi yet; it got stuck on strigi's
dependency ffmpeg.
Ah, thanks Ryan. I'm misreading the logs again.
I replied to Ticket #37733. I did a clean rebuild for strigi, but then
read this post and followed Ryan's
port upgrade outdated
# sudo port upgrade outdated
--- Computing dependencies for libunistring
--- Fetching archive for libunistring
--- Attempting to fetch
libunistring-0.9.3_0+universal.darwin_11.i386-x86_64.tbz2 from
http://mse.uk.packages.macports.org/sites/packages.macports.org
On 21.01.13 20:18, Jeremy Lavergne wrote:
:debug:main Executing org.macports.main (ffmpeg)
:debug:main Skipping completed org.macports.archivefetch (ffmpeg)
:debug:main Skipping completed org.macports.fetch (ffmpeg)
:debug:main Skipping completed org.macports.checksum (ffmpeg)
:debug:main
Looking at the MacPorts for submitting tickets, there is a suggestion to run
for Is the problem with a 'port upgrade' operation?:
... try a 'port uninstall foo' and then reinstall. You might also want to
run 'port -nR upgrade --force foo' to rebuild ports depending upon port foo.
(
On 21.01.13 21:54, Jeremy Lavergne wrote:
Looking at the MacPorts for submitting tickets, there is a suggestion to run for
Is the problem with a 'port upgrade' operation?:
... try a 'port uninstall foo' and then reinstall. You might also want to run
'port -nR upgrade --force foo' to rebuild
Thanks for the explanation Jeremy.
I posted a ticket # 37733
Is it all OK like that?
Yup, the ticket is a good start.
In the ticket, you show us
Error: The following dependencies were not installed: ffmpeg
Error: Unable to upgrade port: 1 Error rebuilding strigi
Sounds like we might
I was able to get this to work by following the steps in
https://trac.macports.org/wiki/Migration
Thanks a lot for the help
___
macports-users mailing list
macports-users@lists.macosforge.org
On Jan 10, 2013, at 16:44, Achilles Vassilicos wrote:
I was able to get this to work by following the steps in
https://trac.macports.org/wiki/Migration
Thanks a lot for the help
I meant to respond earlier and apologize: I confused you with someone else! The
screenshot I was talking
On 1/10/13 8:49 PM, Ryan Schmidt wrote:
On Jan 10, 2013, at 16:44, Achilles Vassilicos wrote:
I was able to get this to work by following the steps in
https://trac.macports.org/wiki/Migration
Thanks a lot for the help
I meant to respond earlier and apologize: I confused you with someone
During execution of sudo port upgrade outdeted I encountered error
messages shown at the end. Specifically:
1. Errors with various versions of docbook-xml
2. Error with gcc42 telling me to uninstall and reinstall g95
I don't know how to proceed.
I am running OS X 10.8.2 and Xcode 4.5.2. Any
On Jan 8, 2013, at 11:54, Achilles Vassilicos wrote:
During execution of sudo port upgrade outdeted I encountered error messages
shown at the end. Specifically:
1. Errors with various versions of docbook-xml
--- Activating docbook-xml-4.2 @5.0_1
Error: org.macports.activate for port
, but it does not seem to
have cleaned everything. Where might be remnants of the old Xcode that
may need to be cleaned manually?
BTW, after uninstalling the old Xcode with the above command, the commands
sudo port -v selfupdate
sudo port upgrade outdated
worked and have seemed to find Xcode 4.5.2
On Jan 8, 2013, at 14:17, Achilles Vassilicos wrote:
Error: The installed version of Xcode (2.0orlower) is too old to use on the
installed OS version. Version 4.1 or later is recommended on Mac OS X 10.8.
Are the new Xcode's command line tools installed properly? Open Xcode.app,
visit the
On Jan 8, 2013, at 15:36, Eneko Gotzon Ares wrote:
On Jan 8, 2013, at 9:19 PM, Ryan Schmidt wrote:
Open Xcode.app, visit the Preferences window, go to the Downloads section,
and install or update the command line tools from there.
Every time I try to get that Download section, I cannot
On 1/8/13 6:15 PM, Ryan Schmidt wrote:
On Jan 8, 2013, at 15:36, Eneko Gotzon Ares wrote:
On Jan 8, 2013, at 9:19 PM, Ryan Schmidt wrote:
Open Xcode.app, visit the Preferences window, go to the Downloads section, and
install or update the command line tools from there.
Every time I try to
On Jan 8, 2013, at 17:57, Achilles Vassilicos wrote:
On 1/8/13 6:15 PM, Ryan Schmidt wrote:
On Jan 8, 2013, at 15:36, Eneko Gotzon Ares wrote:
On Jan 8, 2013, at 9:19 PM, Ryan Schmidt wrote:
Open Xcode.app, visit the Preferences window, go to the Downloads section,
and install or update
On Jan 8, 2013, at 14:17, Achilles Vassilicos wrote:
What's happening is that I had an older version of Xcode installed before
installing Xcode 4.5.2 after upgrading to Mountain Lion from Snow Leopard. I
did a
sudo /Developer/Library/uninstall-devtools –mode=all
which removed the
qt4-mac,
sudo port upgrade outdated will still try to upgrade qt4-mac. Is there
anything that I am overlooking? If I type sudo port -v uninstall qt4-mac it
claims that it is already uninstalled.
Thanks,
Gunther
___
macports-users mailing list
macports
, even after I do this followed by a sudo port clean --all
qt4-mac, sudo port upgrade outdated will still try to upgrade qt4-mac. Is
there anything that I am overlooking? If I type sudo port -v uninstall
qt4-mac it claims that it is already uninstalled.
Sounds like you have successfully
Just checked the ticket #34599 that was related to mine and decided to do a
selfupdate and sudo port upgrade outdated and I got this:
jaspersmbp:wpscan jasper$ sudo port selfupdate
--- Updating MacPorts base sources using rsync
MacPorts base version 2.1.1 installed,
MacPorts base version 2.1.1
on
a selfupdate. So you probably need to wait a bit longer.
I could be wrong though ;)
Dom
Am 11.06.2012 um 13:07 schrieb Jasper Frumau jasperfru...@gmail.com:
Just checked the ticket #34599 that was related to mine and decided to do a
selfupdate and sudo port upgrade outdated and I got
jasperfru...@gmail.com:
Just checked the ticket #34599 that was related to mine and decided to do
a selfupdate and sudo port upgrade outdated and I got this:
jaspersmbp:wpscan jasper$ sudo port selfupdate
--- Updating MacPorts base sources using rsync
MacPorts base version 2.1.1 installed
On 6/11/12, Jasper Frumau jasperfru...@gmail.com wrote:
On Mon, Jun 11, 2012 at 6:19 PM, Dominik Reichardt
domi...@gmail.comwrote:
That just means there was nothing outdated to upgrade at the moment (I
think this error message could use some fine tuning though).
I see. Did not know that.
Just 'port outdated' will also work.
--
Damon McDougall
d.mcdoug...@warwick.ac.uk (mailto:d.mcdoug...@warwick.ac.uk)
http://damon-is-a-geek.com
B2.39
Mathematics Institute
University of Warwick
Coventry
West Midlands
CV4 7AL
United Kingdom
On Monday, 11 June 2012 at 15:38, Arno Hautala
On Jun 11, 2012, at 7:07 a.m., Jasper Frumau wrote:
Just checked the ticket #34599 that was related to mine and decided to do a
selfupdate and sudo port upgrade outdated and I got this:
jaspersmbp:wpscan jasper$ sudo port selfupdate
--- Updating MacPorts base sources using rsync
MacPorts
On Jun 11, 2012, at 13:58, Lawrence Velázquez wrote:
On Jun 11, 2012, at 7:07 a.m., Jasper Frumau wrote:
Just checked the ticket #34599 that was related to mine and decided to do a
selfupdate and sudo port upgrade outdated and I got this:
jaspersmbp:wpscan jasper$ sudo port selfupdate
On Jun 11, 2012, at 4:29 PM, Ryan Schmidt ryandes...@macports.org wrote:
If you don't already have the port installed, MacPorts will tell you it can't
upgrade a port you don't have installed.
I assumed he had it installed already, since he was trying to upgrade outdated
ports.
And if you
On Jun 11, 2012, at 15:50, Lawrence Velázquez wrote:
Hm. When running upgrade installed, I've definitely seen MacPorts rebuild
ports that were not listed as outdated. (That is, upgrade outdated did
nothing, but upgrade installed did something. I saw this recently with
cloog and isl.) Of
On Tue, Jun 12, 2012 at 1:58 AM, Lawrence Velázquez
larry.velazq...@gmail.com wrote:
On Jun 11, 2012, at 7:07 a.m., Jasper Frumau wrote:
Just checked the ticket #34599 that was related to mine and decided to do
a selfupdate and sudo port upgrade outdated and I got this:
jaspersmbp:wpscan
a selfupdate and sudo port upgrade outdated and I got this:
jaspersmbp:wpscan jasper$ sudo port selfupdate
--- Updating MacPorts base sources using rsync
MacPorts base version 2.1.1 installed,
MacPorts base version 2.1.1 downloaded.
--- Updating the ports tree
--- MacPorts base is already
updated. To upgrade your installed ports, you should run
port upgrade outdated
punkish@dyn-72-33-42-202 ~/Data/pgdump$sudo port upgrade outdated
Error: No ports matched the given expression
$
___
macports-users mailing list
macports-users
..
Total number of ports parsed:0
Ports successfully parsed:0
Ports failed:0
Up-to-date ports skipped:14346
--- MacPorts base is already the latest version
The ports tree has been updated. To upgrade your installed ports, you should
run
port upgrade outdated
and sudo port upgrade outdated and I got this:
jaspersmbp:wpscan jasper$ sudo port selfupdate
--- Updating MacPorts base sources using rsync
MacPorts base version 2.1.1 installed,
MacPorts base version 2.1.1 downloaded.
--- Updating the ports tree
--- MacPorts base is already the latest
On Jun 11, 2012, at 5:08 p.m., Ryan Schmidt wrote:
One possibility is that some of the installed (but not outdated) ports had
build dependencies that you had subsequently uninstalled. Asking MacPorts to
upgrade those ports would reinstall those build dependencies.
Maybe, although I feel
After performing a selfupdate and successfully upgrading the MacPorts system, I
then ran 'sudo port upgrade outdated' with the following errors. How do I fix
this mess?
--- Updating database of binaries: 100.0%
--- Scanning binaries for linking errors: 100.0%
--- Found 7 broken file(s
On Jun 9, 2012, at 1:08 p.m., Mark Brethen wrote:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gtk2-aurora/gtk2-aurora/main.log
On Jun 9, 2012, at 12:46 PM, Lawrence Velázquez wrote:
On Jun 9, 2012, at 1:08 p.m., Mark Brethen wrote:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_ports_gnome_gtk2-aurora/gtk2-aurora/main.log
On Jun 9, 2012, at 13:05, Mark Brethen wrote:
From the gtk2-aurora log:
:info:build In file included from ./src/animation.c:10:
:info:build /opt/local/include/glib-2.0/glib/gtimer.h:28:2: error: #error
Only glib.h can be included directly.
:info:build #error Only glib.h can be included
Hi, I've a problem running 'port upgrade outdated' on my intel mac (10.7.3)
(Xcode 4.3)
Has anyone experienced this problem? Do I need to reinstall macports?
clivesmac:~ cliveriches$ sudo port upgrade outdated
--- Computing dependencies for ncurses
--- Configuring ncurses
Error: Target
On Mar 8, 2012, at 17:33, Clive Riches wrote:
I've already ran sudo port clean nurses without success. Where do I find
details to install Xcode correctly? I installed it from App store - doesn't
it install it correctly?
Read this:
On Nov 7, 2011, at 14:12, Jeremy Lavergne wrote:
Error: Unable to upgrade port: couldn't open
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_sqlite3/sqlite3/work/.macports.sqlite3.state:
permission denied
I'd first try `sudo port
On 8 Nov 2011, at 15:02, Ryan Schmidt wrote:
On Nov 7, 2011, at 14:12, Jeremy Lavergne wrote:
Error: Unable to upgrade port: couldn't open
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_sqlite3/sqlite3/work/.macports.sqlite3.state:
Error: Unable to upgrade port: couldn't open
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_databases_sqlite3/sqlite3/work/.macports.sqlite3.state:
permission denied
I'd first try `sudo port clean sqlite3`.
While I don't think this has anything to do with this thread...
On Oct 10, 2011, at 19:15, Jeremy Lavergne wrote:
Have we completely dropped the ball on informing users to run selfupdate
twice?
When you selfupdate *from* MacPorts 2.0.2 or later you'll be told to run
selfupdate a second
On Oct 14, 2011, at 20:12, Ryan Schmidt wrote:
I feel that, if that's the case, we should start ensuring that selfupdate
can run itself twice (looks a file to signal do selfupdate).
That would be a possible enhancement, but of course, it won't help anybody
upgrading *from* any existing
On Oct 14, 2011, at 9:46 PM, Ryan Schmidt wrote:
But be sure you understand what the problem is. Prior to MacPorts 2.0.2,
selfupdate did this:
1. The old version of MacPorts runs sync to download the new portfiles
2. The old MacPorts indexes those new ports
3. The old MacPorts downloads
On Oct 14, 2011, at 21:02, Daniel J. Luke wrote:
On Oct 14, 2011, at 9:46 PM, Ryan Schmidt wrote:
But be sure you understand what the problem is. Prior to MacPorts 2.0.2,
selfupdate did this:
1. The old version of MacPorts runs sync to download the new portfiles
2. The old MacPorts indexes
On 2011-10-15 13:20 , Ryan Schmidt wrote:
On Oct 14, 2011, at 21:02, Daniel J. Luke wrote:
On Oct 14, 2011, at 9:46 PM, Ryan Schmidt wrote:
But be sure you understand what the problem is. Prior to MacPorts 2.0.2,
selfupdate did this:
1. The old version of MacPorts runs sync to download the
Eek!
I did the following on both my Mac Mini and my laptop (both running Lion)
sudo port selfupdate
sudo port upgrade outdated
This moved me to macports 2.0.3.
Immediately after those two commands I tried to do a couple more port
operations but got this message:-
mainmini:~ david
On Mon, Oct 10, 2011 at 20:11, David Herron da...@davidherron.com wrote:
mainmini:~ david$ sudo port install nodejs npm
sudo: unknown uid: 501
mainmini:~ david$ sudo port install nodejs npm
sudo: unknown uid: 501
Obviously the error is coming from sudo and it didn't even get to
On Jul 9, 2011, at 15:26, Larry Moore wrote:
Machine BW Mac 450Mz 640Mb ram
Mac OS 10.4.11
sudo port upgrade outdated fails, log attached:
_opt_local_var_macports_sources_rsync.macports.org_release_ports_x11_mesa
https://trac.macports.org/ticket/29860
On May 28, 2011, at 21:28, Peng Yu wrote:
The GNU FTP server seems to have problems for some users (including me) and
randomly disconnects in a way that MacPorts doesn't detect that this has
happened (and MacPorts continues waiting forever for data that will never
arrive). You could cancel
Hi,
'port upgrade outdated' stops at gcc44. Does anyone know why this
happens and how to fix it?
$sudo port upgrade outdated
Password:
--- Computing dependencies for gcc44
--- Fetching gcc44
--- Attempting to fetch gcc-core-4.4.6.tar.bz2 from
ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.4.6
On Sat, May 28, 2011 at 08:45:55AM -0500, Peng Yu wrote:
Hi,
'port upgrade outdated' stops at gcc44. Does anyone know why this
happens and how to fix it?
If no error is reported then I think that one just takes a very long time to
update.
Patience et langeur de temps applies to cpu cycles
,
'port upgrade outdated' stops at gcc44. Does anyone know why this
happens and how to fix it?
If no error is reported then I think that one just takes a very long time
to update.
Patience et langeur de temps applies to cpu cycles as well as to rage.
Richard
$sudo port
On May 28, 2011, at 08:45, Peng Yu wrote:
'port upgrade outdated' stops at gcc44. Does anyone know why this
happens and how to fix it?
$sudo port upgrade outdated
Password:
--- Computing dependencies for gcc44
--- Fetching gcc44
--- Attempting to fetch gcc-core-4.4.6.tar.bz2 from
Dear Peng,
Do a direct download from ftp://gcc.gnu.org/pub/gcc/releases/gcc-4.4.6/ and put
it in the appropriate directory under /opt/local. Look and you'll find it. After
completion of the placement of that file into the proper directory, try your
update command again.
If that URL
On Sat, May 28, 2011 at 1:53 PM, Ryan Schmidt ryandes...@macports.org wrote:
On May 28, 2011, at 08:45, Peng Yu wrote:
'port upgrade outdated' stops at gcc44. Does anyone know why this
happens and how to fix it?
$sudo port upgrade outdated
Password:
--- Computing dependencies for gcc44
by 5.8 being deactivated, so all you have to do is retry activating
5.12, or just run port upgrade outdated again etc. Anyway, clearly
this was not an ideal way to have the upgrade go!
Scott
___
macports-users mailing list
macports-users
1 - 100 of 202 matches
Mail list logo
