Control: close -1 Hi Dima,
Dima Kogan wrote: > > Additionally, what did pull in zsh-common? zsh 4.3.17-1 is not yet > > split up and has no dependency on zsh-common, not even an unversioned > > one. (Which probably means that zsh-common rather would need a > > "Conflicts: zsh (<< 5)", but fixing this three releases later seems > > ridiculous.) > > Just looked at the logs. aptitude tried to upgrade zsh to 5.4.2-3, which > pulled in zsh-common. During the upgrade something didn't go right, and > I guess zsh ended up at the old version, but zsh-common did get > installed. At least that explains it well. Thanks for checking. > OK. Before you mentioned it I didn't realize that this install was as > old as it apparently is, Ok. :-) > so maybe leaving it is ok. Upgrades such as this maybe aren't > common, but people do do them, Well, at least I prefer to do several upgrades in a row to avoid such problems. > and this harder dependency would save them time. I filed this bug in > case this missing dep was an oversight, but you clearly thought > about it, and if you think the downsides of adding such a dependency > outweigh the benefits, Definitely from my point of view. IMHO the versioned dependency from zsh to zsh-common should already suffice all these cases. > feel free to close this bug. Ok, thanks. Doing so. Regards, Axel -- ,''`. | Axel Beckert <a...@debian.org>, https://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 `- | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE