pacman: exists in filesystem
3
When installing a package with pacman, I am seeing:
error: failed to commit transaction (conflicting files)
station: /usr/bin/station exists in filesystem
How do I tell pacman to install the package anyway, overwriting the existing file(s)?
arch-linux manjaro pacman
edited Dec 30 '18 at 13:21
Jeff Schaller
39.9k1054126
asked Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
add a comment |
3
When installing a package with pacman, I am seeing:
error: failed to commit transaction (conflicting files)
station: /usr/bin/station exists in filesystem
How do I tell pacman to install the package anyway, overwriting the existing file(s)?
arch-linux manjaro pacman
edited Dec 30 '18 at 13:21
Jeff Schaller
39.9k1054126
asked Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
add a comment |
3
3
3
1
When installing a package with pacman, I am seeing:
error: failed to commit transaction (conflicting files)
station: /usr/bin/station exists in filesystem
How do I tell pacman to install the package anyway, overwriting the existing file(s)?
arch-linux manjaro pacman
edited Dec 30 '18 at 13:21
Jeff Schaller
39.9k1054126
asked Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
When installing a package with pacman, I am seeing:
error: failed to commit transaction (conflicting files)
station: /usr/bin/station exists in filesystem
How do I tell pacman to install the package anyway, overwriting the existing file(s)?
arch-linux manjaro pacman
arch-linux manjaro pacman
edited Dec 30 '18 at 13:21
Jeff Schaller
39.9k1054126
asked Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
edited Dec 30 '18 at 13:21
Jeff Schaller
39.9k1054126
asked Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
edited Dec 30 '18 at 13:21
Jeff Schaller
39.9k1054126
edited Dec 30 '18 at 13:21
Jeff Schaller
39.9k1054126
edited Dec 30 '18 at 13:21
Jeff Schaller
39.9k1054126
39.9k1054126
asked Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
asked Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
asked Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
6,69533593
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
3
Check what package includes the filename:
pacman -Qo filename
If it is another package, then file a bug report: packages which have conflicting files should mark themselves as CONFLICTS causing pacman to ask if you wish to replace the conflicting package.
If the files don't belong to any package, rename or delete them.
If you're sure you know what you're doing, you can use the --overwrite option, eg:
pacman -S package-name --overwrite /usr/bin/station
or
pacman -S package-name --overwrite '*'
The man page says:
--overwrite <glob>
Bypass file conflict checks and overwrite conflicting files. If the
package that is about to be installed contains files that are
already installed and match glob, this option will cause all those
files to be overwritten. Using --overwrite will not allow
overwriting a directory with a file or installing packages with
conflicting files and directories. Multiple patterns can be
specified by separating them with a comma. May be specified
multiple times. Patterns can be negated, such that files matching
them will not be overwritten, by prefixing them with an exclamation
mark. Subsequent matches will override previous ones. A leading
literal exclamation mark or backslash needs to be escaped.
answered Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
The Arch Wiki specifically recommends avoiding--overwriteexcept as a last resort. The correct approach is to move the conflicting file(s) and complete the install.
– jasonwryan
Dec 26 '18 at 17:23
Thanks, @jasonwryan, I've updated it. I actually had an AUR package conflicting with its own previously installed files - there may be some non-pacmanauto-update going on which I'm still looking into.
– Tom Hale
Dec 26 '18 at 21:27
It is a bad idea to use "*" as a glob, since it will overwrite absolutely anything including many things you didn't intend. The--overwriteoption was added to pacman, and--forcewas removed, specifically because greedily matching everything was too dangerous and users got into trouble, whereas globs allow matching only what you need and know is okay.
– eschwartz
Dec 30 '18 at 1:56
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490949%2fpacman-filename-exists-in-filesystem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
3
Check what package includes the filename:
pacman -Qo filename
If it is another package, then file a bug report: packages which have conflicting files should mark themselves as CONFLICTS causing pacman to ask if you wish to replace the conflicting package.
If the files don't belong to any package, rename or delete them.
If you're sure you know what you're doing, you can use the --overwrite option, eg:
pacman -S package-name --overwrite /usr/bin/station
or
pacman -S package-name --overwrite '*'
The man page says:
--overwrite <glob>
Bypass file conflict checks and overwrite conflicting files. If the
package that is about to be installed contains files that are
already installed and match glob, this option will cause all those
files to be overwritten. Using --overwrite will not allow
overwriting a directory with a file or installing packages with
conflicting files and directories. Multiple patterns can be
specified by separating them with a comma. May be specified
multiple times. Patterns can be negated, such that files matching
them will not be overwritten, by prefixing them with an exclamation
mark. Subsequent matches will override previous ones. A leading
literal exclamation mark or backslash needs to be escaped.
answered Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
The Arch Wiki specifically recommends avoiding--overwriteexcept as a last resort. The correct approach is to move the conflicting file(s) and complete the install.
– jasonwryan
Dec 26 '18 at 17:23
Thanks, @jasonwryan, I've updated it. I actually had an AUR package conflicting with its own previously installed files - there may be some non-pacmanauto-update going on which I'm still looking into.
– Tom Hale
Dec 26 '18 at 21:27
It is a bad idea to use "*" as a glob, since it will overwrite absolutely anything including many things you didn't intend. The--overwriteoption was added to pacman, and--forcewas removed, specifically because greedily matching everything was too dangerous and users got into trouble, whereas globs allow matching only what you need and know is okay.
– eschwartz
Dec 30 '18 at 1:56
add a comment |
3
Check what package includes the filename:
pacman -Qo filename
If it is another package, then file a bug report: packages which have conflicting files should mark themselves as CONFLICTS causing pacman to ask if you wish to replace the conflicting package.
If the files don't belong to any package, rename or delete them.
If you're sure you know what you're doing, you can use the --overwrite option, eg:
pacman -S package-name --overwrite /usr/bin/station
or
pacman -S package-name --overwrite '*'
The man page says:
--overwrite <glob>
Bypass file conflict checks and overwrite conflicting files. If the
package that is about to be installed contains files that are
already installed and match glob, this option will cause all those
files to be overwritten. Using --overwrite will not allow
overwriting a directory with a file or installing packages with
conflicting files and directories. Multiple patterns can be
specified by separating them with a comma. May be specified
multiple times. Patterns can be negated, such that files matching
them will not be overwritten, by prefixing them with an exclamation
mark. Subsequent matches will override previous ones. A leading
literal exclamation mark or backslash needs to be escaped.
answered Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
The Arch Wiki specifically recommends avoiding--overwriteexcept as a last resort. The correct approach is to move the conflicting file(s) and complete the install.
– jasonwryan
Dec 26 '18 at 17:23
Thanks, @jasonwryan, I've updated it. I actually had an AUR package conflicting with its own previously installed files - there may be some non-pacmanauto-update going on which I'm still looking into.
– Tom Hale
Dec 26 '18 at 21:27
It is a bad idea to use "*" as a glob, since it will overwrite absolutely anything including many things you didn't intend. The--overwriteoption was added to pacman, and--forcewas removed, specifically because greedily matching everything was too dangerous and users got into trouble, whereas globs allow matching only what you need and know is okay.
– eschwartz
Dec 30 '18 at 1:56
add a comment |
3
3
3
Check what package includes the filename:
pacman -Qo filename
If it is another package, then file a bug report: packages which have conflicting files should mark themselves as CONFLICTS causing pacman to ask if you wish to replace the conflicting package.
If the files don't belong to any package, rename or delete them.
If you're sure you know what you're doing, you can use the --overwrite option, eg:
pacman -S package-name --overwrite /usr/bin/station
or
pacman -S package-name --overwrite '*'
The man page says:
--overwrite <glob>
Bypass file conflict checks and overwrite conflicting files. If the
package that is about to be installed contains files that are
already installed and match glob, this option will cause all those
files to be overwritten. Using --overwrite will not allow
overwriting a directory with a file or installing packages with
conflicting files and directories. Multiple patterns can be
specified by separating them with a comma. May be specified
multiple times. Patterns can be negated, such that files matching
them will not be overwritten, by prefixing them with an exclamation
mark. Subsequent matches will override previous ones. A leading
literal exclamation mark or backslash needs to be escaped.
answered Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
Check what package includes the filename:
pacman -Qo filename
If it is another package, then file a bug report: packages which have conflicting files should mark themselves as CONFLICTS causing pacman to ask if you wish to replace the conflicting package.
If the files don't belong to any package, rename or delete them.
If you're sure you know what you're doing, you can use the --overwrite option, eg:
pacman -S package-name --overwrite /usr/bin/station
or
pacman -S package-name --overwrite '*'
The man page says:
--overwrite <glob>
Bypass file conflict checks and overwrite conflicting files. If the
package that is about to be installed contains files that are
already installed and match glob, this option will cause all those
files to be overwritten. Using --overwrite will not allow
overwriting a directory with a file or installing packages with
conflicting files and directories. Multiple patterns can be
specified by separating them with a comma. May be specified
multiple times. Patterns can be negated, such that files matching
them will not be overwritten, by prefixing them with an exclamation
mark. Subsequent matches will override previous ones. A leading
literal exclamation mark or backslash needs to be escaped.
answered Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
edited Dec 26 '18 at 21:26
answered Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
answered Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
answered Dec 26 '18 at 7:47
Tom HaleTom Hale
6,69533593
6,69533593
The Arch Wiki specifically recommends avoiding--overwriteexcept as a last resort. The correct approach is to move the conflicting file(s) and complete the install.
– jasonwryan
Dec 26 '18 at 17:23
Thanks, @jasonwryan, I've updated it. I actually had an AUR package conflicting with its own previously installed files - there may be some non-pacmanauto-update going on which I'm still looking into.
– Tom Hale
Dec 26 '18 at 21:27
It is a bad idea to use "*" as a glob, since it will overwrite absolutely anything including many things you didn't intend. The--overwriteoption was added to pacman, and--forcewas removed, specifically because greedily matching everything was too dangerous and users got into trouble, whereas globs allow matching only what you need and know is okay.
– eschwartz
Dec 30 '18 at 1:56
add a comment |
The Arch Wiki specifically recommends avoiding--overwriteexcept as a last resort. The correct approach is to move the conflicting file(s) and complete the install.
– jasonwryan
Dec 26 '18 at 17:23
Thanks, @jasonwryan, I've updated it. I actually had an AUR package conflicting with its own previously installed files - there may be some non-pacmanauto-update going on which I'm still looking into.
– Tom Hale
Dec 26 '18 at 21:27
It is a bad idea to use "*" as a glob, since it will overwrite absolutely anything including many things you didn't intend. The--overwriteoption was added to pacman, and--forcewas removed, specifically because greedily matching everything was too dangerous and users got into trouble, whereas globs allow matching only what you need and know is okay.
– eschwartz
Dec 30 '18 at 1:56
The Arch Wiki specifically recommends avoiding
--overwrite except as a last resort. The correct approach is to move the conflicting file(s) and complete the install.– jasonwryan
Dec 26 '18 at 17:23
The Arch Wiki specifically recommends avoiding
--overwrite except as a last resort. The correct approach is to move the conflicting file(s) and complete the install.– jasonwryan
Dec 26 '18 at 17:23
Thanks, @jasonwryan, I've updated it. I actually had an AUR package conflicting with its own previously installed files - there may be some non-
pacman auto-update going on which I'm still looking into.– Tom Hale
Dec 26 '18 at 21:27
Thanks, @jasonwryan, I've updated it. I actually had an AUR package conflicting with its own previously installed files - there may be some non-
pacman auto-update going on which I'm still looking into.– Tom Hale
Dec 26 '18 at 21:27
It is a bad idea to use "*" as a glob, since it will overwrite absolutely anything including many things you didn't intend. The
--overwrite option was added to pacman, and --force was removed, specifically because greedily matching everything was too dangerous and users got into trouble, whereas globs allow matching only what you need and know is okay.– eschwartz
Dec 30 '18 at 1:56
It is a bad idea to use "*" as a glob, since it will overwrite absolutely anything including many things you didn't intend. The
--overwrite option was added to pacman, and --force was removed, specifically because greedily matching everything was too dangerous and users got into trouble, whereas globs allow matching only what you need and know is okay.– eschwartz
Dec 30 '18 at 1:56
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f490949%2fpacman-filename-exists-in-filesystem%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
