How can I disable automatic update for a single snap in Ubuntu?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
The recommended way for a system wide installation of Intellij idea is to use snap. When I do that, snap updates the IDE installation which is a big problem for me because updating the development environment causes issues for me and as a developer I'd like strict control of my development environment.
If I disable snap, then I cannot even start the IDE. Google searches return nothing but meaningless long flame wars or complete suspension/disabling of snap.
Is there any way of simply telling snap not to update a piece of software while keeping all else up to date?. I'm using Ubuntu 18.04
snap
add a comment |
The recommended way for a system wide installation of Intellij idea is to use snap. When I do that, snap updates the IDE installation which is a big problem for me because updating the development environment causes issues for me and as a developer I'd like strict control of my development environment.
If I disable snap, then I cannot even start the IDE. Google searches return nothing but meaningless long flame wars or complete suspension/disabling of snap.
Is there any way of simply telling snap not to update a piece of software while keeping all else up to date?. I'm using Ubuntu 18.04
snap
add a comment |
The recommended way for a system wide installation of Intellij idea is to use snap. When I do that, snap updates the IDE installation which is a big problem for me because updating the development environment causes issues for me and as a developer I'd like strict control of my development environment.
If I disable snap, then I cannot even start the IDE. Google searches return nothing but meaningless long flame wars or complete suspension/disabling of snap.
Is there any way of simply telling snap not to update a piece of software while keeping all else up to date?. I'm using Ubuntu 18.04
snap
The recommended way for a system wide installation of Intellij idea is to use snap. When I do that, snap updates the IDE installation which is a big problem for me because updating the development environment causes issues for me and as a developer I'd like strict control of my development environment.
If I disable snap, then I cannot even start the IDE. Google searches return nothing but meaningless long flame wars or complete suspension/disabling of snap.
Is there any way of simply telling snap not to update a piece of software while keeping all else up to date?. I'm using Ubuntu 18.04
snap
snap
asked 12 hours ago
mahonyamahonya
1204
1204
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
You can not. The only thing you can do is delay the update.
From the manual:
Automatic refresh
By design, non-devmode snaps installed from the store are automatically updated on a regular cadence. By default, the snapd daemon checks for updates 4 times each day.
Controlling refresh frequency
Sometimes the user wishes to have snaps refresh at known times, rather than the default. This can be achieved with the snap set system refresh.timer command. The user can specify a range of days or times when they’d prefer refreshes to occur. The following example sets the snapd daemon to refresh snaps only between 4AM and 7AM and between 7PM and 10:10PM.
snap set system refresh.timer=4:00-7:00,19:00-22:10
In theory you could alter the refresh frequency ever day where you keep moving the update moment into the future but this will not work. The snap will get updated at some point (and just ignore your refresh frequency).
See this discussion and the topics from niemeyer.
In that same link post #9 from mwinter (2017) would suggest 2 things:
Me (personally) could do this. But then I rather dislike doing any [additional] filtering on a router as this could cause issues in the future… It also blocks other snap’s and potential more (not sure what all would be at the same location)
Another (in my opinion simpler) solution is to download the snap and install it locally - not from store.
- block using a firewall rule. That would kill all snap updates. Not a single one.
- remove the snap installed from the store and use a locally installed one.
I accepted your answer since it is a definitive answer to my question but this design is ridiculous. I saw the discussion you mentioned and no one seems to consider the case where the user may want absolute control of updates. Especially for development environment components it is common for same set of tools to be used for years as per company policy etc. I guess I'll have to stop using snap for intellij idea and leave with the inconvenience in exchange for control.
– mahonya
9 hours ago
1
you are not alone there. a solution where you use a hammer to kill a fly: create a firewall rule to block the update of snaps.
– Rinzwind
7 hours ago
ah, that's a very interesting idea, can I block an update for individual snaps? Being lazy here, I don't know how snap works, but if it does not use a single public repo like most package managers, I may have a chance.
– mahonya
7 hours ago
thanks, I'll try to do some searching as well.
– mahonya
6 hours ago
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
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%2faskubuntu.com%2fquestions%2f1131182%2fhow-can-i-disable-automatic-update-for-a-single-snap-in-ubuntu%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
You can not. The only thing you can do is delay the update.
From the manual:
Automatic refresh
By design, non-devmode snaps installed from the store are automatically updated on a regular cadence. By default, the snapd daemon checks for updates 4 times each day.
Controlling refresh frequency
Sometimes the user wishes to have snaps refresh at known times, rather than the default. This can be achieved with the snap set system refresh.timer command. The user can specify a range of days or times when they’d prefer refreshes to occur. The following example sets the snapd daemon to refresh snaps only between 4AM and 7AM and between 7PM and 10:10PM.
snap set system refresh.timer=4:00-7:00,19:00-22:10
In theory you could alter the refresh frequency ever day where you keep moving the update moment into the future but this will not work. The snap will get updated at some point (and just ignore your refresh frequency).
See this discussion and the topics from niemeyer.
In that same link post #9 from mwinter (2017) would suggest 2 things:
Me (personally) could do this. But then I rather dislike doing any [additional] filtering on a router as this could cause issues in the future… It also blocks other snap’s and potential more (not sure what all would be at the same location)
Another (in my opinion simpler) solution is to download the snap and install it locally - not from store.
- block using a firewall rule. That would kill all snap updates. Not a single one.
- remove the snap installed from the store and use a locally installed one.
I accepted your answer since it is a definitive answer to my question but this design is ridiculous. I saw the discussion you mentioned and no one seems to consider the case where the user may want absolute control of updates. Especially for development environment components it is common for same set of tools to be used for years as per company policy etc. I guess I'll have to stop using snap for intellij idea and leave with the inconvenience in exchange for control.
– mahonya
9 hours ago
1
you are not alone there. a solution where you use a hammer to kill a fly: create a firewall rule to block the update of snaps.
– Rinzwind
7 hours ago
ah, that's a very interesting idea, can I block an update for individual snaps? Being lazy here, I don't know how snap works, but if it does not use a single public repo like most package managers, I may have a chance.
– mahonya
7 hours ago
thanks, I'll try to do some searching as well.
– mahonya
6 hours ago
add a comment |
You can not. The only thing you can do is delay the update.
From the manual:
Automatic refresh
By design, non-devmode snaps installed from the store are automatically updated on a regular cadence. By default, the snapd daemon checks for updates 4 times each day.
Controlling refresh frequency
Sometimes the user wishes to have snaps refresh at known times, rather than the default. This can be achieved with the snap set system refresh.timer command. The user can specify a range of days or times when they’d prefer refreshes to occur. The following example sets the snapd daemon to refresh snaps only between 4AM and 7AM and between 7PM and 10:10PM.
snap set system refresh.timer=4:00-7:00,19:00-22:10
In theory you could alter the refresh frequency ever day where you keep moving the update moment into the future but this will not work. The snap will get updated at some point (and just ignore your refresh frequency).
See this discussion and the topics from niemeyer.
In that same link post #9 from mwinter (2017) would suggest 2 things:
Me (personally) could do this. But then I rather dislike doing any [additional] filtering on a router as this could cause issues in the future… It also blocks other snap’s and potential more (not sure what all would be at the same location)
Another (in my opinion simpler) solution is to download the snap and install it locally - not from store.
- block using a firewall rule. That would kill all snap updates. Not a single one.
- remove the snap installed from the store and use a locally installed one.
I accepted your answer since it is a definitive answer to my question but this design is ridiculous. I saw the discussion you mentioned and no one seems to consider the case where the user may want absolute control of updates. Especially for development environment components it is common for same set of tools to be used for years as per company policy etc. I guess I'll have to stop using snap for intellij idea and leave with the inconvenience in exchange for control.
– mahonya
9 hours ago
1
you are not alone there. a solution where you use a hammer to kill a fly: create a firewall rule to block the update of snaps.
– Rinzwind
7 hours ago
ah, that's a very interesting idea, can I block an update for individual snaps? Being lazy here, I don't know how snap works, but if it does not use a single public repo like most package managers, I may have a chance.
– mahonya
7 hours ago
thanks, I'll try to do some searching as well.
– mahonya
6 hours ago
add a comment |
You can not. The only thing you can do is delay the update.
From the manual:
Automatic refresh
By design, non-devmode snaps installed from the store are automatically updated on a regular cadence. By default, the snapd daemon checks for updates 4 times each day.
Controlling refresh frequency
Sometimes the user wishes to have snaps refresh at known times, rather than the default. This can be achieved with the snap set system refresh.timer command. The user can specify a range of days or times when they’d prefer refreshes to occur. The following example sets the snapd daemon to refresh snaps only between 4AM and 7AM and between 7PM and 10:10PM.
snap set system refresh.timer=4:00-7:00,19:00-22:10
In theory you could alter the refresh frequency ever day where you keep moving the update moment into the future but this will not work. The snap will get updated at some point (and just ignore your refresh frequency).
See this discussion and the topics from niemeyer.
In that same link post #9 from mwinter (2017) would suggest 2 things:
Me (personally) could do this. But then I rather dislike doing any [additional] filtering on a router as this could cause issues in the future… It also blocks other snap’s and potential more (not sure what all would be at the same location)
Another (in my opinion simpler) solution is to download the snap and install it locally - not from store.
- block using a firewall rule. That would kill all snap updates. Not a single one.
- remove the snap installed from the store and use a locally installed one.
You can not. The only thing you can do is delay the update.
From the manual:
Automatic refresh
By design, non-devmode snaps installed from the store are automatically updated on a regular cadence. By default, the snapd daemon checks for updates 4 times each day.
Controlling refresh frequency
Sometimes the user wishes to have snaps refresh at known times, rather than the default. This can be achieved with the snap set system refresh.timer command. The user can specify a range of days or times when they’d prefer refreshes to occur. The following example sets the snapd daemon to refresh snaps only between 4AM and 7AM and between 7PM and 10:10PM.
snap set system refresh.timer=4:00-7:00,19:00-22:10
In theory you could alter the refresh frequency ever day where you keep moving the update moment into the future but this will not work. The snap will get updated at some point (and just ignore your refresh frequency).
See this discussion and the topics from niemeyer.
In that same link post #9 from mwinter (2017) would suggest 2 things:
Me (personally) could do this. But then I rather dislike doing any [additional] filtering on a router as this could cause issues in the future… It also blocks other snap’s and potential more (not sure what all would be at the same location)
Another (in my opinion simpler) solution is to download the snap and install it locally - not from store.
- block using a firewall rule. That would kill all snap updates. Not a single one.
- remove the snap installed from the store and use a locally installed one.
edited 6 hours ago
answered 12 hours ago
RinzwindRinzwind
209k28403537
209k28403537
I accepted your answer since it is a definitive answer to my question but this design is ridiculous. I saw the discussion you mentioned and no one seems to consider the case where the user may want absolute control of updates. Especially for development environment components it is common for same set of tools to be used for years as per company policy etc. I guess I'll have to stop using snap for intellij idea and leave with the inconvenience in exchange for control.
– mahonya
9 hours ago
1
you are not alone there. a solution where you use a hammer to kill a fly: create a firewall rule to block the update of snaps.
– Rinzwind
7 hours ago
ah, that's a very interesting idea, can I block an update for individual snaps? Being lazy here, I don't know how snap works, but if it does not use a single public repo like most package managers, I may have a chance.
– mahonya
7 hours ago
thanks, I'll try to do some searching as well.
– mahonya
6 hours ago
add a comment |
I accepted your answer since it is a definitive answer to my question but this design is ridiculous. I saw the discussion you mentioned and no one seems to consider the case where the user may want absolute control of updates. Especially for development environment components it is common for same set of tools to be used for years as per company policy etc. I guess I'll have to stop using snap for intellij idea and leave with the inconvenience in exchange for control.
– mahonya
9 hours ago
1
you are not alone there. a solution where you use a hammer to kill a fly: create a firewall rule to block the update of snaps.
– Rinzwind
7 hours ago
ah, that's a very interesting idea, can I block an update for individual snaps? Being lazy here, I don't know how snap works, but if it does not use a single public repo like most package managers, I may have a chance.
– mahonya
7 hours ago
thanks, I'll try to do some searching as well.
– mahonya
6 hours ago
I accepted your answer since it is a definitive answer to my question but this design is ridiculous. I saw the discussion you mentioned and no one seems to consider the case where the user may want absolute control of updates. Especially for development environment components it is common for same set of tools to be used for years as per company policy etc. I guess I'll have to stop using snap for intellij idea and leave with the inconvenience in exchange for control.
– mahonya
9 hours ago
I accepted your answer since it is a definitive answer to my question but this design is ridiculous. I saw the discussion you mentioned and no one seems to consider the case where the user may want absolute control of updates. Especially for development environment components it is common for same set of tools to be used for years as per company policy etc. I guess I'll have to stop using snap for intellij idea and leave with the inconvenience in exchange for control.
– mahonya
9 hours ago
1
1
you are not alone there. a solution where you use a hammer to kill a fly: create a firewall rule to block the update of snaps.
– Rinzwind
7 hours ago
you are not alone there. a solution where you use a hammer to kill a fly: create a firewall rule to block the update of snaps.
– Rinzwind
7 hours ago
ah, that's a very interesting idea, can I block an update for individual snaps? Being lazy here, I don't know how snap works, but if it does not use a single public repo like most package managers, I may have a chance.
– mahonya
7 hours ago
ah, that's a very interesting idea, can I block an update for individual snaps? Being lazy here, I don't know how snap works, but if it does not use a single public repo like most package managers, I may have a chance.
– mahonya
7 hours ago
thanks, I'll try to do some searching as well.
– mahonya
6 hours ago
thanks, I'll try to do some searching as well.
– mahonya
6 hours ago
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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.
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%2faskubuntu.com%2fquestions%2f1131182%2fhow-can-i-disable-automatic-update-for-a-single-snap-in-ubuntu%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