September 2008 - macports-tickets - lists.macosforge.org

[MacPorts] #16199: MacPorts-1-1.6.0 postflight shell recognition failure
by MacPorts 20 Dec '09

20 Dec '09

#16199: MacPorts-1-1.6.0 postflight shell recognition failure -----------------------------------------------------------+---------------- Reporter: nick.colclasure(a)mac.com | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.6.0 Keywords: MacPorts-1-1.6.0 shell recognition postflight | -----------------------------------------------------------+---------------- {{{ % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 7254 100 7254 0 0 8476 0 --:--:-- --:--:-- --:--:-- 19737 The MacPorts Project, postflight script version 1.6.1: checking the shell environment for user "root". '''Unknown shell (sh)! Please set your MacPorts compatible environment manually.''' Synchronizing the MacPorts installation with the project's rsync server... Synchronizing local ports tree from rsync://rsync.macports.org/release/ports/ receiving file list ... done sent 32 bytes received 323800 bytes 23987.56 bytes/sec total size is 18646973 speedup is 57.58 MacPorts base version 1.600 installed receiving file list ... done sent 32 bytes received 6472 bytes 1858.29 bytes/sec total size is 3962384 speedup is 609.22 Downloaded MacPorts base version 1.600 The MacPorts installation is not outdated and so was not updated selfupdate done! Successful! }}} I ran basename $SHELL and it returned bash. -- Ticket URL: <http://trac.macports.org/ticket/16199> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 10

[MacPorts] #16146: port gohome spews lots of errors if port doesn't have homepage variable
by MacPorts 20 Dec '09

20 Dec '09

#16146: port gohome spews lots of errors if port doesn't have homepage variable -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- `port gohome` returns lots of lines of errors if the port doesn't define the `homepage` variable. Yes, that variable is required according to `port lint`, but it would still be nice if this error spew could be reduced down to just one line: {{{ $ port gohome arts can't read "portinfo(homepage)": no such element in array while executing "set homepage $portinfo(homepage)" ("gohome" arm line 5) invoked from within "switch -- $action { cat { # Copy the portfile to standard output set f [open $portfile RDONLY]..." invoked from within "if {[file readable $portfile]} { switch -- $action { cat { # Copy the portfile to standard output ..." ("uplevel" body line 25) invoked from within "uplevel 1 $block" (procedure "foreachport" line 16) invoked from within "foreachport $portlist { # If we have a url, use that, since it's most specific, otherwise try to map the portname to a url if {$portur..." (procedure "action_portcmds" line 12) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 86) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command # Exit immediately, by default, unless..." (file "/mp/bin/port" line 3207) }}} I'm using MacPorts trunk @38780. -- Ticket URL: <http://trac.macports.org/ticket/16146> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #15913: ui_init modifications patch for macports.tcl
by MacPorts 20 Dec '09

20 Dec '09

#15913: ui_init modifications patch for macports.tcl ---------------------------------+------------------------------------------ Reporter: armahg(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: base | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ This patch is to allow users of the MacPorts Tcl API to redefine the default ui_init procedure found in macports.tcl. MacPorts.Framework needs this capability for its redefinition of ui_init which enables the sending of NSNotifications to clients of the framework in parallel with ui_$priority messages during port activity. -- Ticket URL: <http://trac.macports.org/ticket/15913> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #15906: "port -d upgrade apr" fails with internal error
by MacPorts 20 Dec '09

20 Dec '09

#15906: "port -d upgrade apr" fails with internal error --------------------------------+------------------------------------------- Reporter: stephen(a)xemacs.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: | --------------------------------+------------------------------------------- port version 1.700 (trunk)[[BR]] svn revision 38128 {{{ Error: Target org.macports.fetch returned: couldn't fork child process: resource temporarily unavailable Warning: the following items did not execute (for apr): org.macports.archive org.macports.fetch org.macports.extract org.macports.checksum org.macports.patch org.macports.configure org.macports.build org.macports.destroot DEBUG: invalid command name "ui_prefix" while executing "ui_prefix $priority" invoked from within "set prefix [ui_prefix $priority]" ("uplevel" body line 2) invoked from within "uplevel 1 $body" Error: Unable to upgrade port: 1 chibi:MacPorts steve$ }}} -- Ticket URL: <http://trac.macports.org/ticket/15906> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 9

[MacPorts] #15806: port lint should warn if port uses "configure {}" instead of "use_configure no"
by MacPorts 20 Dec '09

20 Dec '09

#15806: port lint should warn if port uses "configure {}" instead of "use_configure no" -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: base | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- "`port lint`" should issue a warning if a port uses an empty configure phase like "`configure {}`" and should suggest the use of "`use_configure no`" instead. -- Ticket URL: <http://trac.macports.org/ticket/15806> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3

[MacPorts] #15530: port build: assembled command missing parallel build argument
by MacPorts 20 Dec '09

20 Dec '09

#15530: port build: assembled command missing parallel build argument -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: afb(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- I have `buildmakejobs` set to `2` and `buildnicevalue` set to `1` in my `macports.conf`. I'm using MacPorts trunk (@37400), Xcode 2.4.1, Mac OS X 10.4.11, MacBook Pro. When I build e.g. apr with debug output I see this: {{{ ---> Building apr with target all DEBUG: Executing org.macports.build (apr) DEBUG: port allows a parallel build DEBUG: Environment: "MACOSX_DEPLOYMENT_TARGET"='10.4' DEBUG: Assembled command: 'cd "/mp/var/macports/build/_Users_rschmidt_macports_dports_devel_apr/work/apr-1.2.12" && nice -n 1 make all' }}} The problem is it doesn't show the `-j2` argument to the make command, but the port does allow parallel building, and I can tell from my CPU monitor that the port is building in parallel. So it seems the command it says it assembled isn't the command it's actually running. In r36907 it was working properly: {{{ DEBUG: Assembled command: 'cd "/mp/var/macports/build/_Users_rschmidt_macports_dports_devel_apr/work/apr-1.2.12" && nice -n 1 make -j2 all' [snip proper build output] }}} In r36913 and r36914 port no longer builds, and `-j2` has disappeared from the advertised assembled command: {{{ DEBUG: Assembled command: 'cd "/mp/var/macports/build/_Users_rschmidt_macports_dports_devel_apr/work/apr-1.2.12" && make all' make: *** No rule to make target `all'. Stop. Error: Target org.macports.build returned: shell command "nice -n 1 cd "/mp/var/macports/build/_Users_rschmidt_macports_dports_devel_apr/work/apr-1.2.12" && make all -j2" returned error 2 }}} In r36915 it builds but `-j2` is still absent from the command shown: {{{ DEBUG: Assembled command: 'cd "/mp/var/macports/build/_Users_rschmidt_macports_dports_devel_apr/work/apr-1.2.12" && nice -n 1 make all' [snip proper build output] }}} We should fix this, but I'm also curious why the command we're running isn't the command we're printing. Why don't the two come from the same variable? -- Ticket URL: <http://trac.macports.org/ticket/15530> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #15515: "port provides" broken in trunk
by MacPorts 20 Dec '09

20 Dec '09

#15515: "port provides" broken in trunk -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- "`port provides`" seems to be broken in trunk (@37376). Not sure yet when this problem appeared. This is with Mac OS X 10.4.11 and Xcode 2.4.1 on Intel. {{{ $ /mp/bin/port provides foo list must have an even number of elements while executing "array set portspec { foo }" ("uplevel" body line 1) invoked from within "uplevel 1 "array set portspec { $portspec }"" (procedure "foreachport" line 6) invoked from within "foreachport $portlist { set file [compat filenormalize $portname] if {[file exists $file]} { if {![file isdirectory $file]..." (procedure "action_provides" line 9) invoked from within "$action_proc $action $portlist [array get global_options]" (procedure "process_cmd" line 86) invoked from within "process_cmd $remaining_args" invoked from within "if { [llength $remaining_args] > 0 } { # If there are remaining arguments, process those as a command # Exit immediately, by default, unless..." (file "/mp/bin/port" line 3165) $ }}} -- Ticket URL: <http://trac.macports.org/ticket/15515> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 4

[MacPorts] #15488: wrap text to terminal width
by MacPorts 20 Dec '09

20 Dec '09

#15488: wrap text to terminal width -------------------------------------+-------------------------------------- Reporter: ryandesign(a)macports.org | Owner: raimue(a)macports.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.7.0 Keywords: | -------------------------------------+-------------------------------------- MacPorts base in trunk now wraps output to 80 characters, but the terminal window is not necessarily 80 characters wide. It may be wider or narrower. As a first step, I'd like to see the wrap-to width moved into a variable/constant that's defined only once. Magic numbers in source are bad. Next step would be to wrap to the actual terminal width (if output is to a terminal) or not wrap at all (if output is to a file or pipe). Rainer, since you've been working on some stuff near this the past few days, maybe you could at least take care of abstracting the wrap-to width into a variable? -- Ticket URL: <http://trac.macports.org/ticket/15488> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 7

[MacPorts] #15485: RFE: Use distfiles mirror and fallback also for URLs with tags
by MacPorts 20 Dec '09

20 Dec '09

#15485: RFE: Use distfiles mirror and fallback also for URLs with tags ---------------------------------------+------------------------------------ Reporter: raimue(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: ports | Version: 1.7.0 Keywords: distfiles mirror fallback | ---------------------------------------+------------------------------------ If a URL in `master_sites` has a tag, the distfiles mirror and the fallback sites are not considered. For example: {{{ master_sites http://foo.example.org/:tag1 http://bar.example.org/:tag2 distfiles foo:tag1 bar:tag2 }}} In this example, `foo` should be downloaded from `foo.example.org`, `tag2` from `bar.example.org`. But the distfiles mirror and the fallback site are not added. -- Ticket URL: <http://trac.macports.org/ticket/15485> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 5

[MacPorts] #15433: RFE: Eliminate duplicates in portlist
by MacPorts 19 Dec '09

19 Dec '09

#15433: RFE: Eliminate duplicates in portlist ---------------------------------+------------------------------------------ Reporter: raimue(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org Type: enhancement | Status: new Priority: Normal | Milestone: MacPorts base enhancements Component: base | Version: 1.6.0 Keywords: | ---------------------------------+------------------------------------------ See the following output: {{{ $ port echo name:vim or description:vim p5-text-vimcolor vim vim-app vim2html p5-text-vimcolor vim-app vim2html }}} It should be avoided to list ports twice or more times here. -- Ticket URL: <http://trac.macports.org/ticket/15433> MacPorts <http://www.macports.org/> Ports system for Mac OS

1 3