Opened 10 years ago
Closed 3 years ago
#45104 closed update (fixed)
ocaml-ocamlnet @3.7.3_0: update available to 3.7.6
Reported by: | piotr@… | Owned by: | pmetzger (Perry E. Metzger) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | ||
Port: | ocaml-ocamlnet |
Description
The build fails because of an illegal sequence of characters in src/netstring/netencoding.mli on line 123
The following patch fixes the issue:
--- src/netstring/netencoding.mli.orig 2014-09-19 19:57:18.000000000 -0700 +++ src/netstring/netencoding.mli 2014-09-19 19:57:42.000000000 -0700 @@ -120,7 +120,7 @@ * to ensure that all output lines have a length <= 76 bytes. * * Note unsafe characters: - * As recommended by RFC 2045, the characters [!#$\@[]^`{|}~] + * As recommended by RFC 2045, the characters [!#$\@[]^`{}~]| * and the double quotes * are additionally represented as hex tokens. * Furthermore, the letter 'F' is considered as unsafe if it
Change History (8)
comment:1 Changed 10 years ago by piotr@…
Cc: | piotr@… added |
---|
comment:2 Changed 10 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | piotr@… removed |
---|---|
Owner: | changed from macports-tickets@… to landonf@… |
Is this problem already known to the developers of ocaml-ocamlnet? If not, please report it to them.
comment:3 Changed 10 years ago by piotr@…
There is no need to inform the maintainers. The version in macports is outdated. In the upstream version is 3.7.6 and the affected line is as follows:
As recommended by RFC 2045, the characters [!#$\@[]^`|{}~]
So it is not affected by this particular bug. We can either apply the proposed patch or consider updating to the current version of ocamlnet.
comment:4 Changed 10 years ago by larryv (Lawrence Velázquez)
Summary: | ocaml-ocamlnet build fails due to an invalid character sequence in a comment → ocaml-ocamlnet @3.7.3_0: update available to 3.7.6 |
---|---|
Type: | defect → update |
Version: | 2.3.1 |
comment:5 Changed 10 years ago by piotr@…
3 months later and the package is still not compiling even though a fix is avalable. Is there a reason why?
comment:6 Changed 8 years ago by mf2k (Frank Schima)
Owner: | landonf@… deleted |
---|---|
Status: | new → assigned |
comment:7 Changed 6 years ago by pmetzger (Perry E. Metzger)
Owner: | set to pmetzger |
---|
comment:8 Changed 3 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Note: See
TracTickets for help on using
tickets.
Cc Me!