Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Remove use of CURLOPT_CLOSEPOLICY #169

Open
dg0yt opened this issue Aug 31, 2024 · 0 comments
Open

Remove use of CURLOPT_CLOSEPOLICY #169

dg0yt opened this issue Aug 31, 2024 · 0 comments

Comments

@dg0yt
Copy link

dg0yt commented Aug 31, 2024

Cf. curl/curl#14747.
@dg0yt dg0yt mentioned this issue Sep 10, 2024
Open
@sim590 sim590 mentioned this issue Nov 3, 2024
Merged
sim590 added a commit to sim590/dpaste that referenced this issue Nov 3, 2024
@sim590
http_client: working around the current build issue in curlpp header (#…
2027a82 
…22)

A patched version of curlpp/Options.hpp has been added to the repositiory in which
the faulty `ClosePolicy` definition was removed. Some other definitions were also
removed in order to get a minimal list of deprecated definitions warnings.

See the following links for references about the issue worked around:

jpbarrette/curlpp#171
jpbarrette/curlpp#169
sim590 added a commit to sim590/dpaste that referenced this issue Nov 26, 2024
@sim590
dpaste: version 0.4.1
7a56e2b 
* workaround current curlpp related errors. See:
  * jpbarrette/curlpp#171
  * jpbarrette/curlpp#169
* fix a few build toolchain issues
* fix wrong encryption scheme being displayed (CBC -> GCM)
* update and fix typos in manpage
This was referenced Nov 27, 2024
Closed
Closed
sgallou added a commit that referenced this issue Jan 14, 2025
@sgallou
Merge pull request #171 from brunotl/master
d080e30 
fix issue #169
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dg0yt