Opened 5 years ago

Closed 5 years ago

#58977 closed defect (fixed)

serf0 @0.7.2_3: buckets/ssl_buckets.c incomplete definition of type 'struct bio_st'

Reported by: rseichter (Ralph Seichter) Owned by: yan12125 (Chih-Hsuan Yen)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc:
Port: serf0

Description

Build log (attached) shows in buckets/ssl_buckets.c

Attachments (1)

main.log (32.4 KB) - added by rseichter (Ralph Seichter) 5 years ago.

Download all attachments as: .zip

Change History (9)

Changed 5 years ago by rseichter (Ralph Seichter)

Attachment: main.log added

comment:1 Changed 5 years ago by yan12125 (Chih-Hsuan Yen)

Owner: set to yan12125
Status: newassigned

comment:2 Changed 5 years ago by yan12125 (Chih-Hsuan Yen)

serf0 is really old. Could you use serf1 instead?

comment:3 Changed 5 years ago by rseichter (Ralph Seichter)

I did not choose serf0 myself, it was referenced during port upgrade outdated.

> port echo depof:serf0
apr
apr-util
openssl

Not much I can do about that, or is there?

comment:4 Changed 5 years ago by yan12125 (Chih-Hsuan Yen)

Hi, depof shows what serf0 needs. If you want to see what needs serf0, the following command is a possible way:

port dependents serf0

comment:5 Changed 5 years ago by rseichter (Ralph Seichter)

> port dependents serf0
serf0 has no dependents.  

Weird. I did not install serf0 manually, and nothing currently installed on my machine appears to need it. A vestigal dependency of subversion, perhaps?

> port dependents serf1
subversion depends on serf1
subversion-perlbindings-5.26 depends on serf1

In any case, I uninstalled serf0 for now. It might not be worth investigating this any further, if serf0 is indeed not used by other ports anymore.

comment:6 Changed 5 years ago by yan12125 (Chih-Hsuan Yen)

Resolution: wontfix
Status: assignedclosed

A vestigal dependency of subversion, perhaps?

Most likely. subversion switched from serf0 to serf1 some time ago (1). In this case the old dependency will not be removed automatically.

It might not be worth investigating this any further, if serf0 is indeed not used by other ports anymore.

I believe that is the case as no ports depend on serf0 now. I will propose to remove serf0 in the future.

(1) https://github.com/macports/macports-ports/commit/084f841767836d720502f150dfbb4406b0d4bb9e

comment:7 Changed 5 years ago by yan12125 (Chih-Hsuan Yen)

Resolution: wontfix
Status: closedreopened

Reopen until serf0 is mark as obsoleted.

comment:8 Changed 5 years ago by Chih-Hsuan Yen <yan12125@…>

Resolution: fixed
Status: reopenedclosed

In 2e3d038636c6b4d5813c208dfedd3a2254be111a/macports-ports (master):

serf0: obsoleted

Closes: #58977

Note: See TracTickets for help on using tickets.