Debian packaging - config files get overwritten on update
Clash Royale CLAN TAG#URR8PPP
I found that in the packaging of ralph ng there seems to be an issue with Debian packaging. The desired behaviour would be that on first install a Debian menu prompt appears, to configure some database settings, on update those generated files should be left alone. Unfortunately the current behaviour is that the config files get overwritten on update.
Maybe anyone with packaging experience could have a quick look and point me in the right direction to fix this.
debian deb
edited Jan 15 at 9:07
Stephen Kitt
169k24382458
asked Jan 15 at 8:49
engelantengelant
11
add a comment |
I found that in the packaging of ralph ng there seems to be an issue with Debian packaging. The desired behaviour would be that on first install a Debian menu prompt appears, to configure some database settings, on update those generated files should be left alone. Unfortunately the current behaviour is that the config files get overwritten on update.
Maybe anyone with packaging experience could have a quick look and point me in the right direction to fix this.
debian deb
edited Jan 15 at 9:07
Stephen Kitt
169k24382458
asked Jan 15 at 8:49
engelantengelant
11
add a comment |
I found that in the packaging of ralph ng there seems to be an issue with Debian packaging. The desired behaviour would be that on first install a Debian menu prompt appears, to configure some database settings, on update those generated files should be left alone. Unfortunately the current behaviour is that the config files get overwritten on update.
Maybe anyone with packaging experience could have a quick look and point me in the right direction to fix this.
debian deb
edited Jan 15 at 9:07
Stephen Kitt
169k24382458
asked Jan 15 at 8:49
engelantengelant
11
I found that in the packaging of ralph ng there seems to be an issue with Debian packaging. The desired behaviour would be that on first install a Debian menu prompt appears, to configure some database settings, on update those generated files should be left alone. Unfortunately the current behaviour is that the config files get overwritten on update.
Maybe anyone with packaging experience could have a quick look and point me in the right direction to fix this.
debian deb
debian deb
edited Jan 15 at 9:07
Stephen Kitt
169k24382458
asked Jan 15 at 8:49
engelantengelant
11
edited Jan 15 at 9:07
Stephen Kitt
169k24382458
asked Jan 15 at 8:49
engelantengelant
11
edited Jan 15 at 9:07
Stephen Kitt
169k24382458
edited Jan 15 at 9:07
Stephen Kitt
169k24382458
edited Jan 15 at 9:07
Stephen Kitt
169k24382458
169k24382458
asked Jan 15 at 8:49
engelantengelant
11
asked Jan 15 at 8:49
engelantengelant
11
asked Jan 15 at 8:49
engelantengelant
11
11
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
The “right direction” involves giving due consideration to all the advice in the debconf-devel manpage, in particular the “Config file handling” section which gives a detailed example of handling this exact situation:
- the
configscript needs to read the existing configuration file, if any; - the
postinstscript needs to handle missing entries in the configuration file, if any.
It would perhaps be better to use dbconfig-common in this case; that deals with configuring database connections and a variety of other related database-handling tasks.
The postinst should also be fixed to avoid writing to standard output, since that can confuse debconf.
answered Jan 15 at 9:06
Stephen KittStephen Kitt
169k24382458
Thanks for your input. I'll check out your links and see if I'm able to fix it from here on by myself.
– engelant
Jan 15 at 9:32
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
);
);
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%2f494554%2fdebian-packaging-config-files-get-overwritten-on-update%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
The “right direction” involves giving due consideration to all the advice in the debconf-devel manpage, in particular the “Config file handling” section which gives a detailed example of handling this exact situation:
- the
configscript needs to read the existing configuration file, if any; - the
postinstscript needs to handle missing entries in the configuration file, if any.
It would perhaps be better to use dbconfig-common in this case; that deals with configuring database connections and a variety of other related database-handling tasks.
The postinst should also be fixed to avoid writing to standard output, since that can confuse debconf.
answered Jan 15 at 9:06
Stephen KittStephen Kitt
169k24382458
Thanks for your input. I'll check out your links and see if I'm able to fix it from here on by myself.
– engelant
Jan 15 at 9:32
add a comment |
The “right direction” involves giving due consideration to all the advice in the debconf-devel manpage, in particular the “Config file handling” section which gives a detailed example of handling this exact situation:
- the
configscript needs to read the existing configuration file, if any; - the
postinstscript needs to handle missing entries in the configuration file, if any.
It would perhaps be better to use dbconfig-common in this case; that deals with configuring database connections and a variety of other related database-handling tasks.
The postinst should also be fixed to avoid writing to standard output, since that can confuse debconf.
answered Jan 15 at 9:06
Stephen KittStephen Kitt
169k24382458
Thanks for your input. I'll check out your links and see if I'm able to fix it from here on by myself.
– engelant
Jan 15 at 9:32
add a comment |
The “right direction” involves giving due consideration to all the advice in the debconf-devel manpage, in particular the “Config file handling” section which gives a detailed example of handling this exact situation:
- the
configscript needs to read the existing configuration file, if any; - the
postinstscript needs to handle missing entries in the configuration file, if any.
It would perhaps be better to use dbconfig-common in this case; that deals with configuring database connections and a variety of other related database-handling tasks.
The postinst should also be fixed to avoid writing to standard output, since that can confuse debconf.
answered Jan 15 at 9:06
Stephen KittStephen Kitt
169k24382458
The “right direction” involves giving due consideration to all the advice in the debconf-devel manpage, in particular the “Config file handling” section which gives a detailed example of handling this exact situation:
- the
configscript needs to read the existing configuration file, if any; - the
postinstscript needs to handle missing entries in the configuration file, if any.
It would perhaps be better to use dbconfig-common in this case; that deals with configuring database connections and a variety of other related database-handling tasks.
The postinst should also be fixed to avoid writing to standard output, since that can confuse debconf.
answered Jan 15 at 9:06
Stephen KittStephen Kitt
169k24382458
answered Jan 15 at 9:06
Stephen KittStephen Kitt
169k24382458
answered Jan 15 at 9:06
Stephen KittStephen Kitt
169k24382458
answered Jan 15 at 9:06
Stephen KittStephen Kitt
169k24382458
169k24382458
Thanks for your input. I'll check out your links and see if I'm able to fix it from here on by myself.
– engelant
Jan 15 at 9:32
add a comment |
Thanks for your input. I'll check out your links and see if I'm able to fix it from here on by myself.
– engelant
Jan 15 at 9:32
Thanks for your input. I'll check out your links and see if I'm able to fix it from here on by myself.
– engelant
Jan 15 at 9:32
Thanks for your input. I'll check out your links and see if I'm able to fix it from here on by myself.
– engelant
Jan 15 at 9:32
add a comment |
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.
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%2f494554%2fdebian-packaging-config-files-get-overwritten-on-update%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