-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
deb package install fails if /usr/bin/watchexec already exists #233
Comments
If
|
As a matter of fact, you're right ! LANG=C sudo dpkg -i watchexec-1.18.0-x86_64-unknown-linux-gnu.deb
(Reading database ... 524320 files and directories currently installed.)
Preparing to unpack watchexec-1.18.0-x86_64-unknown-linux-gnu.deb ...
Unpacking watchexec-cli (1.18.0) ...
dpkg: error processing archive watchexec-1.18.0-x86_64-unknown-linux-gnu.deb (--install):
trying to overwrite '/usr/bin/watchexec', which is also in package watchexec 1.15.1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
Errors were encountered while processing:
watchexec-1.18.0-x86_64-unknown-linux-gnu.deb |
Guess you need to uninstall the old one first, I'll make a note in the release. |
After proper upgrading, I'm left with:
The initial problem is gone though. |
That's probably the same underlying cause. Something to do with this? https://watchexec.github.io/docs/inotify-limits.html or other ulimits |
Yeah, I should check that. I already bumped that value years ago, I guess it was reset after a system upgrade. Thanks for your feedback ! |
There might be another problem.
(1,000,000)
whereas the number of files to watch is just find . -type f -name '*.md'|wc -l
4179 I should perhaps open a new issue for this ? |
Given the error code it's likely to be one of these two:
(from the inotify_init(2) manpage) So you'll need to check your system ulimits. Maybe try rebooting in the first instance? |
I'm about to file a new issue related to the This issue is now only about the deb package installation. |
I could upgrade flawlessly from v0.18.0 to v0.18.4 using the deb package, so it seems like this issue can be closed as well ! |
Using Watchexec 1.15.1, then 1.18.0 on Ubuntu 21.10.
I stumbled upon this error message when running the following command, which used to work fine:
Updated from v1.15.1 to v1.18.0 to no avail.
Suggested
RUST_LOG=1
didn't help.Adding
--verbose
to invocation didn't help either.Trying to increase verbosity as offered by latest release using
-vvv
failed withI'm not feeling lucky today !
Any thoughts ?
Cheers
The text was updated successfully, but these errors were encountered: