debian packaging: forward-port a package from xenial to bionic
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I am running xenial on my dev machine, but would like to provide a version of a package I maintain in a PPA for newer releases such as bionic. When I try and just update the debian/changelog file to specify 'bionic', I (predictably) get this error:
E: light changes: bad-distribution-in-changes-file bionic
Is it possible to "forward-port" a package or do I need to upgrade my dev machine before I can provide a version of my package on a newer release?
apt package-management upgrade debuild changelog
asked Jun 15 '18 at 5:14
kgilmerkgilmer
61
add a comment |
I am running xenial on my dev machine, but would like to provide a version of a package I maintain in a PPA for newer releases such as bionic. When I try and just update the debian/changelog file to specify 'bionic', I (predictably) get this error:
E: light changes: bad-distribution-in-changes-file bionic
Is it possible to "forward-port" a package or do I need to upgrade my dev machine before I can provide a version of my package on a newer release?
apt package-management upgrade debuild changelog
asked Jun 15 '18 at 5:14
kgilmerkgilmer
61
add a comment |
I am running xenial on my dev machine, but would like to provide a version of a package I maintain in a PPA for newer releases such as bionic. When I try and just update the debian/changelog file to specify 'bionic', I (predictably) get this error:
E: light changes: bad-distribution-in-changes-file bionic
Is it possible to "forward-port" a package or do I need to upgrade my dev machine before I can provide a version of my package on a newer release?
apt package-management upgrade debuild changelog
asked Jun 15 '18 at 5:14
kgilmerkgilmer
61
I am running xenial on my dev machine, but would like to provide a version of a package I maintain in a PPA for newer releases such as bionic. When I try and just update the debian/changelog file to specify 'bionic', I (predictably) get this error:
E: light changes: bad-distribution-in-changes-file bionic
Is it possible to "forward-port" a package or do I need to upgrade my dev machine before I can provide a version of my package on a newer release?
apt package-management upgrade debuild changelog
apt package-management upgrade debuild changelog
asked Jun 15 '18 at 5:14
kgilmerkgilmer
61
asked Jun 15 '18 at 5:14
kgilmerkgilmer
61
asked Jun 15 '18 at 5:14
kgilmerkgilmer
61
asked Jun 15 '18 at 5:14
kgilmerkgilmer
61
asked Jun 15 '18 at 5:14
kgilmerkgilmer
61
61
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I achieved this by using the "copy package" feature in launchpad.net. When you copy a package you're able to specify the distro version as target. I was never able to "cross build" a package from one distro version to another locally.
answered Apr 7 at 5:28
kgilmerkgilmer
61
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%2f1046750%2fdebian-packaging-forward-port-a-package-from-xenial-to-bionic%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
I achieved this by using the "copy package" feature in launchpad.net. When you copy a package you're able to specify the distro version as target. I was never able to "cross build" a package from one distro version to another locally.
answered Apr 7 at 5:28
kgilmerkgilmer
61
add a comment |
I achieved this by using the "copy package" feature in launchpad.net. When you copy a package you're able to specify the distro version as target. I was never able to "cross build" a package from one distro version to another locally.
answered Apr 7 at 5:28
kgilmerkgilmer
61
add a comment |
I achieved this by using the "copy package" feature in launchpad.net. When you copy a package you're able to specify the distro version as target. I was never able to "cross build" a package from one distro version to another locally.
answered Apr 7 at 5:28
kgilmerkgilmer
61
I achieved this by using the "copy package" feature in launchpad.net. When you copy a package you're able to specify the distro version as target. I was never able to "cross build" a package from one distro version to another locally.
answered Apr 7 at 5:28
kgilmerkgilmer
61
answered Apr 7 at 5:28
kgilmerkgilmer
61
answered Apr 7 at 5:28
kgilmerkgilmer
61
answered Apr 7 at 5:28
kgilmerkgilmer
61
61
add a comment |
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%2f1046750%2fdebian-packaging-forward-port-a-package-from-xenial-to-bionic%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
