#36935 closed defect (fixed)
leafnode: sed: RE error: illegal byte sequence
| Reported by: | dave@… | Owned by: | krischik@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.1.2 |
| Keywords: | mountainlion | Cc: | ryandesign (Ryan Carsten Schmidt) |
| Port: | leafnode |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
(log converted to attachment:main.log by admin)
I'm going to try with gsed installed now.
Attachments (1)
Change History (10)
comment:1 Changed 11 years ago by dave@…
comment:2 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Description: | modified (diff) |
|---|---|
| Keywords: | mountainlion added |
| Owner: | changed from macports-tickets@… to krischik@… |
| Port: | leafnode added |
| Summary: | leafnode doesn't build → leafnode: sed: RE error: illegal byte sequence |
Please attach logs instead of pasting them. When pasting console output, remember to use WikiFormatting. Remember to fill in the Port field and to Cc the maintainer of that port.
The error you encountered is a common one on Mountain Lion, for which we have a simple solution we normally use. I'll see if it'll work in this case.
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
Fixed in r99548.
comment:4 Changed 11 years ago by dave@…
Sorry about the bad report. At least on some of those points, I actually know better. However, IMO, it's unreasonable to ask bug reporters to look up the port maintainer, since you can associate them with the component in Trac and have them Cc'd automatically.
comment:5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
We do ask reporters to look up and Cc port maintainers, because we do not yet have a way to do so automatically (part of #15210).
comment:6 follow-up: 7 Changed 11 years ago by dave@…
It's very strange to hear that, because Boost's trac installation does *exactly* that. Trac's "component" field lets you associate a mainainer, and that person is automatically Cc'd.
comment:7 Changed 11 years ago by mf2k (Frank Schima)
Replying to dave@…:
It's very strange to hear that, because Boost's trac installation does *exactly* that. Trac's "component" field lets you associate a mainainer, and that person is automatically Cc'd.
The "Component" field has nothing to do with the maintainer if the Component is "ports". In that case it is the specific port that matters, which Trac knows nothing about.
comment:8 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Further ideas on how we could implement this desirable feature are welcome, but the discussion should probably move to the macports-dev mailing list.
comment:9 Changed 11 years ago by dave@…
Only one so I'll post it here and then begone. The easiest way is to fix it by using "component" to select the port going forward. It's been too many years, but writing trac scripts to update existing tickets is not that hard, if you want to do that too.
Works if you install gsed before building