Frank Terbeck wrote:
[...]
#!/bin/zsh -f
if [[ -o interactive ]]; then
[...]
This wasn't the smartest idea ever. Since this is a script, it's
obviously not interactive invocation, which means that the test always
fails. Oh well. I guess we can just warn upon every invocation
interactive or
Hi,
Frank Terbeck wrote:
Frank Terbeck wrote:
[...]
#!/bin/zsh -f
if [[ -o interactive ]]; then
[...]
This wasn't the smartest idea ever. Since this is a script, it's
obviously not interactive invocation, which means that the test always
fails.
Noticed that, too. :-)
Oh well. I
At 12:12 +0200 10 Oct 2014, Axel Beckert a...@debian.org wrote:
That's how I committed it last night:
https://anonscm.debian.org/cgit/collab-maint/zsh.git/commit/?id=438969ffb81fd46b514d42a77b74890a7b4f778f
Shouldn't the #! line use zsh5 explicitly? Otherwise it doesn't seem
like this would
At 06:44 -0400 10 Oct 2014, I wrote:
At 12:12 +0200 10 Oct 2014, Axel Beckert a...@debian.org wrote:
That's how I committed it last night:
https://anonscm.debian.org/cgit/collab-maint/zsh.git/commit/?id=438969ffb81fd46b514d42a77b74890a7b4f778f
Shouldn't the #! line use zsh5 explicitly?
Hi Aaron,
Aaron Schrab wrote:
At 12:12 +0200 10 Oct 2014, Axel Beckert a...@debian.org wrote:
That's how I committed it last night:
https://anonscm.debian.org/cgit/collab-maint/zsh.git/commit/?id=438969ffb81fd46b514d42a77b74890a7b4f778f
Shouldn't the #! line use zsh5 explicitly?
Yes, we
On 2014-10-10 13:09 +0200, Axel Beckert wrote:
Aaron Schrab wrote:
At 12:12 +0200 10 Oct 2014, Axel Beckert a...@debian.org wrote:
That's how I committed it last night:
https://anonscm.debian.org/cgit/collab-maint/zsh.git/commit/?id=438969ffb81fd46b514d42a77b74890a7b4f778f
Shouldn't the
Hi Sven,
Sven Joachim wrote:
https://anonscm.debian.org/cgit/collab-maint/zsh.git/commit/?id=438969ffb81fd46b514d42a77b74890a7b4f778f
Shouldn't the #! line use zsh5 explicitly?
Yes, we just noticed it, too, and fixed it:
Hi Sven,
Sven Joachim wrote:
A few rough ideas to make this easier for the user:
* Use Pre-Depends in zsh + zsh-common relationship
* Maybe add some hack in the preinst script
How about adding a symlink /bin/zsh4 - zsh5 in the zsh package? Not
extremely pretty, but it should work.
On 2014-10-09 18:12 +0200, Axel Beckert wrote:
Sven Joachim wrote:
A few rough ideas to make this easier for the user:
* Use Pre-Depends in zsh + zsh-common relationship
* Maybe add some hack in the preinst script
How about adding a symlink /bin/zsh4 - zsh5 in the zsh package? Not
Axel Beckert wrote:
Sven Joachim wrote:
[...]
How about adding a symlink /bin/zsh4 - zsh5 in the zsh package? Not
extremely pretty, but it should work.
What about putting a shell script at /bin/zsh4 which more or less
looks this?
#!/bin/sh
echo $0 is deprecated, please switch to
Hi,
Frank Terbeck wrote:
Axel Beckert wrote:
Sven Joachim wrote:
[...]
How about adding a symlink /bin/zsh4 - zsh5 in the zsh package? Not
extremely pretty, but it should work.
What about putting a shell script at /bin/zsh4 which more or less
looks this?
#!/bin/sh
On 2013-05-11 16:13 +0200, Axel Beckert wrote:
Aaron Schrab wrote:
As far as I can tell, it's just caused by how dpkg works.
As it's supposed to do, dpkg first unpacked the new version of zsh
and removed the old version along with doing the same for the other
packages being upgraded in
Hi,
Sven Joachim wrote:
There is also the rather worrisome problem that users who have zsh as
their login shell will not be able to log in during that period.
I don't think that users should expect a system to be pretty usable
during a dist-upgrade.
A few rough ideas to make this easier for
Control: severity -1 important
Hi Aaron,
Aaron Schrab wrote:
Today I upgraded my zsh package from 4.3.17-1 to 5.0.2-3, along with a
somewhat large number of packages. Because there were quite a few
packages being upgraded at once, there was a significant amount of time
between when the
At 11:23 +0200 11 May 2013, Axel Beckert a...@debian.org wrote:
Not nice, indeed. I though have no immediate idea what could have
caused this. I though think that this issue, if not caused by other
issues, is quite important to fix.
As far as I can tell, it's just caused by how dpkg works.
As
Hi Aaron,
Aaron Schrab wrote:
As far as I can tell, it's just caused by how dpkg works.
As it's supposed to do, dpkg first unpacked the new version of zsh
and removed the old version along with doing the same for the other
packages being upgraded in that run. Only once that was done did it
Package: zsh
Version: 5.0.2-3
Severity: normal
Dear Maintainer,
Today I upgraded my zsh package from 4.3.17-1 to 5.0.2-3, along with a
somewhat large number of packages. Because there were quite a few
packages being upgraded at once, there was a significant amount of time
between when the
17 matches
Mail list logo
