Ticket #766 (assigned defect)

Opened 14 years ago

Last modified 10 years ago

debathena-pyhesiodfs should stop using macathena as an upstream

Reported by: kaduk Owned by: jdreed
Priority: trivial Milestone: The Distant Future
Component: -- Keywords:
Cc: Fixed in version:
Upstream bug:


And get rid of that ugly 0.0 version number
So sayeth geofft (and I can't check if we have another ticket right now).

Change History

comment:1 Changed 14 years ago by quentin

By which you mean you want to fork it? That seems silly.

comment:2 Changed 14 years ago by jdreed

I think geofft mainly objects to the version number. Forking is probably stupid, but I see three potential solutions:

  • Macathena and Debathena come to an amicable resolution whereby it moves to Debathena as upstream
  • Macathena and Debathena work together to come up with a neutral "SIPB" repo where stuff like this can live (and things like nss_nonlocal can joint it)
  • Stop caring

comment:3 Changed 11 years ago by jdreed

  • Status changed from new to assigned
  • Owner set to achernya

achernya apparently talked to quentin about this?

comment:4 Changed 11 years ago by jdreed

  • Owner changed from achernya to jdreed

OK, the long awaited rewrite of pyhesiodfs for locker support. This can be deployed ~now, so that it can be in place for the liblocker rewrite.

Available for pre-review on the 'jdreed' branch of my github clone ( https://github.com/jdreed/pyhesiodfs/tree/jdreed)

comment:5 Changed 10 years ago by jdreed

OK, this is now in our upstream. People should look at it.

Note: See TracTickets for help on using tickets.