Opened 13 years ago
Last modified 6 years ago
#30165 assigned update
freedink, freedink-data: update to latest version
Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | |
Keywords: | Cc: | chrstphrchvz (Christopher Chavez) | |
Port: | freedink, freedink-data |
Description
The freedink port is currently at 1.08.20090120 but 1.08.20101114 is available.
The freedink-data port is currently at 1.08.20081130 but 1.08.20100103 is available.
The ports should be updated.
Change History (6)
comment:1 Changed 6 years ago by chrstphrchvz (Christopher Chavez)
comment:2 Changed 6 years ago by pmetzger (Perry E. Metzger)
Owner: | verginegiovanni@… deleted |
---|---|
Status: | new → assigned |
comment:3 Changed 6 years ago by chrstphrchvz (Christopher Chavez)
Sorry for the confusion—this ticket should not be assigned, but I guess this ticket wasn't assigned to begin with, but somehow had an owner (which I thought meant it was automatically assigned; I guess that's a newer Trac feature).
comment:4 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
When a ticket is created its status is "new". When I created the ticket I set its owner to the person who had agreed to maintain the port. That person no longer maintains the ports; see #57920. Therefore the owner of this ticket was changed to empty. In Trac, changing the owner of a ticket (even to empty) changes the ticket's status to "assigned". I know of no way to set a ticket status back to "new" (short of modifying the Trac database by hand, which we don't really want to do).
comment:5 Changed 6 years ago by ryandesign (Ryan Carsten Schmidt)
Actually Trac has customizable workflows; we could probably fix this. I filed #58000.
comment:6 Changed 6 years ago by chrstphrchvz (Christopher Chavez)
Cc: | chrstphrchvz added |
---|
freedink is still being updated in 2019.
If and when these ports are updated/readopted, someone might want to inform the freedink mailing list so they might update their site's remarks about using it on MacPorts.