#27645 closed defect (fixed)
timedrive should use python27
| Reported by: | ryandesign (Ryan Carsten Schmidt) | Owned by: | nerdling (Jeremy Lavergne) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.9.2 |
| Keywords: | Cc: | andreas.wilm@…, jmroot (Joshua Root) | |
| Port: | timedrive |
Description
timedrive should be updated to use python27 since its dependency duplicity was updated to do so in r71676.
See the mailing list.
Change History (10)
comment:1 Changed 14 years ago by nerdling (Jeremy Lavergne)
| Status: | new → assigned |
|---|
comment:3 Changed 14 years ago by nerdling (Jeremy Lavergne)
I'm in the process of getting my main OS back on its feet (10.6.5 ruined the ethernet drivers). Ryan, if you have time would you care to do take care of this one?
comment:4 Changed 14 years ago by nerdling (Jeremy Lavergne)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
Updated in r74556: this doesn't stop python26 from being installed since other dependencies have the old dependency as well.
comment:5 Changed 14 years ago by jmroot (Joshua Root)
Probably would have been easier to change duplicity back to python26 instead.
comment:6 follow-up: 8 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
It's not like there was anything complicated about r74556; looks like the easiest kind of change to me. And isn't it a good idea to push things toward newer versions, rather than stagnate with older ones?
comment:7 Changed 14 years ago by nerdling (Jeremy Lavergne)
| Cc: | jmr@… added |
|---|
This sort of upgrade should become a ripple effect regardless of when it happens. One of timedrive dependencies started using python27. Now it uses python27. Now the rest of the dependencies should start upgrading as well.
I might just open a ticket whenever I find a dependency of my ports pulling in an off-version of python.
comment:8 follow-up: 9 Changed 14 years ago by jmroot (Joshua Root)
Replying to ryandesign@…:
And isn't it a good idea to push things toward newer versions, rather than stagnate with older ones?
Whatever, just pick one version across the board. Changing things over one at a time so multiple versions get installed in the interim is lame. And make sure the new version actually works (#27801).
comment:9 follow-up: 10 Changed 14 years ago by nerdling (Jeremy Lavergne)
Replying to jmr@…:
Whatever, just pick one version across the board. Changing things over one at a time so multiple versions get installed in the interim is lame.
May I cite this ticket as permission for updating packages maintained by others?
Replying to jmr@…:
And make sure the new version actually works (#27801).
From the fine ticket, "Might be a PytQt bug instead."
comment:10 Changed 14 years ago by jmroot (Joshua Root)
Replying to snc@…:
May I cite this ticket as permission for updating packages maintained by others?
No. Ask the maintainer's permission and wait 3 days as usual.
From the fine ticket, "Might be a PytQt bug instead."
The precise location of the fault is irrelevant. The change caused the port to stop working. (Unless it works for you, in which case you should probably mention that on the other ticket.)
Alrighty. Will do Sunday.