June 2015 - macports-tickets - lists.macosforge.org

Re: [MacPorts] #43260: [NEW] docker
by MacPorts 08 Jun '15

08 Jun '15

#43260: [NEW] docker -------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: docker | -------------------------+-------------------------------- Comment (by pixilla@…): Replying to [comment:18 ajdudman@…]: > Here is my try at writing the Portfile. I also read the homebrew formula first. I recoded pixilla's suggestion above. The docker project is progressing rapidly. This one is for version 1.6.2, but 1.7.0 release candidates are being worked on now. In your Portfile you are erroring if "${os.major} < 11". Snow Leopard is darwin 10 and will hit this block. My example should be correct. -- Ticket URL: <https://trac.macports.org/ticket/43260#comment:19> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #47991: rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-45/rsync/clientserver.c(105) [receiver=2.6.9]
by MacPorts 08 Jun '15

08 Jun '15

#47991: rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-45/rsync/clientserver.c(105) [receiver=2.6.9] --------------------------------+-------------------------------- Reporter: tom.laceyjohnson@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: MacPorts Future Component: ports | Version: 2.3.3 Keywords: rsync, selfupdate | Port: --------------------------------+-------------------------------- rsync: failed to connect to rsync.macports.org: Operation timed out (60) rsync error: error in socket IO (code 10) at /SourceCache/rsync/rsync-45/rsync/clientserver.c(105) [receiver=2.6.9] Command failed: /usr/bin/rsync -rtzv --delete-after rsync://rsync.macports.org/release/tarballs/base.tar /opt/local/var/macports/sources/rsync.macports.org/release/tarballs Exit code: 10 Error: Error synchronizing MacPorts sources: command execution failed To report a bug, follow the instructions in the guide: http://guide.macports.org/#project.tickets Error: /opt/local/bin/port: port selfupdate failed: Error synchronizing MacPorts sources: command execution failed -- Ticket URL: <https://trac.macports.org/ticket/47991> MacPorts <https://www.macports.org/> Ports system for OS X

1 1

Re: [MacPorts] #41895: ghostscript @9.10: missing font packages
by MacPorts 08 Jun '15

08 Jun '15

#41895: ghostscript @9.10: missing font packages --------------------------+------------------------ Reporter: gdasnon@… | Owner: takanori@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: ghostscript | --------------------------+------------------------ Comment (by ionic@…): Replying to [comment:11 mojca@…]: > What *I* don't know why installing those fonts should have any influence whatsoever. I don't know. It's working on Debian, and Debian has those fonts, so... I assumed that would fix it. Must be `$SOMETHING` else and I have no idea what exactly, off-hand... > But why did you install the std fonts in a different way than `ghostscript-fonts-other-6.0.tar.gz`? Shouldn't the two be installed in some similar fashion? Because Debian does so. They install the "other" fonts in a special directory only for ghostscript and the "std" fonts in a shared "fontcache" directory. Probably so that other programs can use the fonts, too. I don't know why the "other" fonts don't also get installed in the shared "fontcache" directory, though. Maybe I should take a look at other packagers, like FreeBSD ports, arch and Fedora to see how they do it. -- Ticket URL: <https://trac.macports.org/ticket/41895#comment:12> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #41895: ghostscript @9.10: missing font packages
by MacPorts 08 Jun '15

08 Jun '15

#41895: ghostscript @9.10: missing font packages --------------------------+------------------------ Reporter: gdasnon@… | Owner: takanori@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: ghostscript | --------------------------+------------------------ Comment (by mojca@…): Replying to [comment:9 ionic@…]: > Hm, so I have included the std fonts in what seems to be an okay fashion (such that they are picked up by fontcache as well), but it doesn't fix the user's problem. The accented characters are still not showing up. > > I don't have any idea what is different NOW, though. What *I* don't know why installing those fonts should have any influence whatsoever. > I'll commit the changes I have made hoping it wasn't a total waste of time. If you don't see them fit for prime time, feel free to remove them again (and revbump the port.) > > Committed as r137290 (even though it doesn't fix this problem...) Thank you. But why did you install the std fonts in a different way than `ghostscript-fonts-other-6.0.tar.gz`? Shouldn't the two be installed in some similar fashion? -- Ticket URL: <https://trac.macports.org/ticket/41895#comment:11> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #41895: ghostscript @9.10: missing font packages
by MacPorts 08 Jun '15

08 Jun '15

#41895: ghostscript @9.10: missing font packages --------------------------+------------------------ Reporter: gdasnon@… | Owner: takanori@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: ghostscript | --------------------------+------------------------ Changes (by ionic@…): * cc: ionic@… (added) -- Ticket URL: <https://trac.macports.org/ticket/41895#comment:10> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

Re: [MacPorts] #41895: ghostscript @9.10: missing font packages
by MacPorts 08 Jun '15

08 Jun '15

#41895: ghostscript @9.10: missing font packages --------------------------+------------------------ Reporter: gdasnon@… | Owner: takanori@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.2.1 Resolution: | Keywords: Port: ghostscript | --------------------------+------------------------ Comment (by ionic@…): Hm, so I have included the std fonts in what seems to be an okay fashion (such that they are picked up by fontcache as well), but it doesn't fix the user's problem. The accented characters are still not showing up. I don't have any idea what is different NOW, though. I'll commit the changes I have made hoping it wasn't a total waste of time. If you don't see them fit for prime time, feel free to remove them again (and revbump the port.) Committed as r137290 (even though it doesn't fix this problem...) -- Ticket URL: <https://trac.macports.org/ticket/41895#comment:9> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #47542: poppler 0.32.0 has a wrong dependency on openjpeg15
by MacPorts 08 Jun '15

08 Jun '15

#47542: poppler 0.32.0 has a wrong dependency on openjpeg15 --------------------------------+-------------------------------- Reporter: jc@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: poppler openjpeg15 | Port: --------------------------------+-------------------------------- poppler compiles on my mac if I remove the openjpeg15 port, and fails if it is present. Yet the poppler port requires openjpeg15, and then fails installing. -- Ticket URL: <https://trac.macports.org/ticket/47542> MacPorts <https://www.macports.org/> Ports system for OS X

1 15

Re: [MacPorts] #43260: [NEW] docker
by MacPorts 08 Jun '15

08 Jun '15

#43260: [NEW] docker -------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: docker | -------------------------+-------------------------------- Comment (by ajdudman@…): Here is my try at writing the Portfile. I also read the homebrew formula first. I recoded pixilla's suggestion above. The docker project is progressing rapidly. This one is for version 1.6.2, but 1.7.0 release candidates are being worked on now. -- Ticket URL: <https://trac.macports.org/ticket/43260#comment:18> MacPorts <https://www.macports.org/> Ports system for OS X

1 0

[MacPorts] #46079: [NEW] libyal/libcsystem
by MacPorts 08 Jun '15

08 Jun '15

#46079: [NEW] libyal/libcsystem ------------------------+-------------------------------- Reporter: jul_bsd@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: libcsystem ------------------------+-------------------------------- Library for cross-platform C system functions Part of multiples libyal dependencies to plaso (#42394), grr (#42692), ... -- Ticket URL: <https://trac.macports.org/ticket/46079> MacPorts <https://www.macports.org/> Ports system for OS X

1 3

[MacPorts] #47790: update pstree to 2.39
by MacPorts 08 Jun '15

08 Jun '15

#47790: update pstree to 2.39 ----------------------+-------------------------------- Reporter: hans@… | Owner: macports-tickets@… Type: update | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.3 Keywords: haspatch | Port: pstree ----------------------+-------------------------------- Update pstree to version 2.39: * instead of a ./configure that >>'s a Makefile, have minimal Makefile and set use_configure no * drop the destroot commands in Portfile and just make destroot with the Makefile * pstree has a manpage, so just install that instead of copying the README * drop the clang fix as http://llvm.org/pr10514 is fixed -- Ticket URL: <https://trac.macports.org/ticket/47790> MacPorts <https://www.macports.org/> Ports system for OS X

1 3