why doesn't appstream have apt pdiff like structure?
1
Whenever I run apt update especially for those which have DEP 11 and are metadata never have pdiffs. Is this something which needs a feature in appstream (upstream) or it's a feature needed to be done in the apt implementation ?
Regular pdiff files (as an example) -
Get:30 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Contents (deb) 2019-02-01-0815.12.pdiff [91 B]
Get:30 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Contents (deb) 2019-02-01-0815.12.pdiff [91 B]
and Metadata DEP-11 files -
Get:50 http://cdn-fastly.deb.debian.org/debian unstable/main DEP-11 48x48 Icons [3,923 kB]
Get:51 http://cdn-fastly.deb.debian.org/debian unstable/main DEP-11 64x64 Icons [7,876 kB]
Why do they need such big heavy updates, this is when I just ran an update few hours back ?
debian apt appstream
asked Feb 1 at 14:07
shirishshirish
3,81263185
add a comment |
1
Whenever I run apt update especially for those which have DEP 11 and are metadata never have pdiffs. Is this something which needs a feature in appstream (upstream) or it's a feature needed to be done in the apt implementation ?
Regular pdiff files (as an example) -
Get:30 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Contents (deb) 2019-02-01-0815.12.pdiff [91 B]
Get:30 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Contents (deb) 2019-02-01-0815.12.pdiff [91 B]
and Metadata DEP-11 files -
Get:50 http://cdn-fastly.deb.debian.org/debian unstable/main DEP-11 48x48 Icons [3,923 kB]
Get:51 http://cdn-fastly.deb.debian.org/debian unstable/main DEP-11 64x64 Icons [7,876 kB]
Why do they need such big heavy updates, this is when I just ran an update few hours back ?
debian apt appstream
asked Feb 1 at 14:07
shirishshirish
3,81263185
1
What is yoursources.list? The examples you provide are of packages from buster/testing and sid/unstable. These different packages and repositories will have different types of metadata standards depending on who is the respective maintainer. According to this Debian Administration article not every package will be delivered via pdiff and pdiff is not always the most efficient way to deliver certain updates as well as the fact that with pdiffs you can have several updates per day.
– kemotep
Feb 1 at 15:49
My sources.list is partially made of buster and sid. Although that article dates back to 2006.
– shirish
Feb 1 at 16:15
1
I am not as familiar with Appstream however looking at their documentation (last updated in 2018) Appsteam is a distro-agnostic meta data specification to make handling packaging easier. There is no specification that packages packaged using this standard uses pdiffs. Looking to the Debian Policy (Also updated in 2018) on packaging also shows that there is no standard requiring the use of pdiffs.
– kemotep
Feb 1 at 16:42
1
I have also found this related APT backend information that says if a given package does not have the option to download as pdiff or fails to download as a pdiff the package will be downloaded in its entirety.
– kemotep
Feb 1 at 16:50
1
I do not mean to bombard you with information but I think this link also provides useful information on why a given package may or may not use pdiffs.
– kemotep
Feb 1 at 16:56
add a comment |
1
1
1
1
Whenever I run apt update especially for those which have DEP 11 and are metadata never have pdiffs. Is this something which needs a feature in appstream (upstream) or it's a feature needed to be done in the apt implementation ?
Regular pdiff files (as an example) -
Get:30 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Contents (deb) 2019-02-01-0815.12.pdiff [91 B]
Get:30 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Contents (deb) 2019-02-01-0815.12.pdiff [91 B]
and Metadata DEP-11 files -
Get:50 http://cdn-fastly.deb.debian.org/debian unstable/main DEP-11 48x48 Icons [3,923 kB]
Get:51 http://cdn-fastly.deb.debian.org/debian unstable/main DEP-11 64x64 Icons [7,876 kB]
Why do they need such big heavy updates, this is when I just ran an update few hours back ?
debian apt appstream
asked Feb 1 at 14:07
shirishshirish
3,81263185
Whenever I run apt update especially for those which have DEP 11 and are metadata never have pdiffs. Is this something which needs a feature in appstream (upstream) or it's a feature needed to be done in the apt implementation ?
Regular pdiff files (as an example) -
Get:30 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Contents (deb) 2019-02-01-0815.12.pdiff [91 B]
Get:30 http://cdn-fastly.deb.debian.org/debian buster/main amd64 Contents (deb) 2019-02-01-0815.12.pdiff [91 B]
and Metadata DEP-11 files -
Get:50 http://cdn-fastly.deb.debian.org/debian unstable/main DEP-11 48x48 Icons [3,923 kB]
Get:51 http://cdn-fastly.deb.debian.org/debian unstable/main DEP-11 64x64 Icons [7,876 kB]
Why do they need such big heavy updates, this is when I just ran an update few hours back ?
debian apt appstream
debian apt appstream
asked Feb 1 at 14:07
shirishshirish
3,81263185
asked Feb 1 at 14:07
shirishshirish
3,81263185
asked Feb 1 at 14:07
shirishshirish
3,81263185
asked Feb 1 at 14:07
shirishshirish
3,81263185
asked Feb 1 at 14:07
shirishshirish
3,81263185
3,81263185
1
What is yoursources.list? The examples you provide are of packages from buster/testing and sid/unstable. These different packages and repositories will have different types of metadata standards depending on who is the respective maintainer. According to this Debian Administration article not every package will be delivered via pdiff and pdiff is not always the most efficient way to deliver certain updates as well as the fact that with pdiffs you can have several updates per day.
– kemotep
Feb 1 at 15:49
My sources.list is partially made of buster and sid. Although that article dates back to 2006.
– shirish
Feb 1 at 16:15
1
I am not as familiar with Appstream however looking at their documentation (last updated in 2018) Appsteam is a distro-agnostic meta data specification to make handling packaging easier. There is no specification that packages packaged using this standard uses pdiffs. Looking to the Debian Policy (Also updated in 2018) on packaging also shows that there is no standard requiring the use of pdiffs.
– kemotep
Feb 1 at 16:42
1
I have also found this related APT backend information that says if a given package does not have the option to download as pdiff or fails to download as a pdiff the package will be downloaded in its entirety.
– kemotep
Feb 1 at 16:50
1
I do not mean to bombard you with information but I think this link also provides useful information on why a given package may or may not use pdiffs.
– kemotep
Feb 1 at 16:56
add a comment |
1
What is yoursources.list? The examples you provide are of packages from buster/testing and sid/unstable. These different packages and repositories will have different types of metadata standards depending on who is the respective maintainer. According to this Debian Administration article not every package will be delivered via pdiff and pdiff is not always the most efficient way to deliver certain updates as well as the fact that with pdiffs you can have several updates per day.
– kemotep
Feb 1 at 15:49
My sources.list is partially made of buster and sid. Although that article dates back to 2006.
– shirish
Feb 1 at 16:15
1
I am not as familiar with Appstream however looking at their documentation (last updated in 2018) Appsteam is a distro-agnostic meta data specification to make handling packaging easier. There is no specification that packages packaged using this standard uses pdiffs. Looking to the Debian Policy (Also updated in 2018) on packaging also shows that there is no standard requiring the use of pdiffs.
– kemotep
Feb 1 at 16:42
1
I have also found this related APT backend information that says if a given package does not have the option to download as pdiff or fails to download as a pdiff the package will be downloaded in its entirety.
– kemotep
Feb 1 at 16:50
1
I do not mean to bombard you with information but I think this link also provides useful information on why a given package may or may not use pdiffs.
– kemotep
Feb 1 at 16:56
1
1
What is your
sources.list? The examples you provide are of packages from buster/testing and sid/unstable. These different packages and repositories will have different types of metadata standards depending on who is the respective maintainer. According to this Debian Administration article not every package will be delivered via pdiff and pdiff is not always the most efficient way to deliver certain updates as well as the fact that with pdiffs you can have several updates per day.– kemotep
Feb 1 at 15:49
What is your
sources.list? The examples you provide are of packages from buster/testing and sid/unstable. These different packages and repositories will have different types of metadata standards depending on who is the respective maintainer. According to this Debian Administration article not every package will be delivered via pdiff and pdiff is not always the most efficient way to deliver certain updates as well as the fact that with pdiffs you can have several updates per day.– kemotep
Feb 1 at 15:49
My sources.list is partially made of buster and sid. Although that article dates back to 2006.
– shirish
Feb 1 at 16:15
My sources.list is partially made of buster and sid. Although that article dates back to 2006.
– shirish
Feb 1 at 16:15
1
1
I am not as familiar with Appstream however looking at their documentation (last updated in 2018) Appsteam is a distro-agnostic meta data specification to make handling packaging easier. There is no specification that packages packaged using this standard uses pdiffs. Looking to the Debian Policy (Also updated in 2018) on packaging also shows that there is no standard requiring the use of pdiffs.
– kemotep
Feb 1 at 16:42
I am not as familiar with Appstream however looking at their documentation (last updated in 2018) Appsteam is a distro-agnostic meta data specification to make handling packaging easier. There is no specification that packages packaged using this standard uses pdiffs. Looking to the Debian Policy (Also updated in 2018) on packaging also shows that there is no standard requiring the use of pdiffs.
– kemotep
Feb 1 at 16:42
1
1
I have also found this related APT backend information that says if a given package does not have the option to download as pdiff or fails to download as a pdiff the package will be downloaded in its entirety.
– kemotep
Feb 1 at 16:50
I have also found this related APT backend information that says if a given package does not have the option to download as pdiff or fails to download as a pdiff the package will be downloaded in its entirety.
– kemotep
Feb 1 at 16:50
1
1
I do not mean to bombard you with information but I think this link also provides useful information on why a given package may or may not use pdiffs.
– kemotep
Feb 1 at 16:56
I do not mean to bombard you with information but I think this link also provides useful information on why a given package may or may not use pdiffs.
– kemotep
Feb 1 at 16:56
add a comment |
0
active
oldest
votes
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%2f498144%2fwhy-doesnt-appstream-have-apt-pdiff-like-structure%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f498144%2fwhy-doesnt-appstream-have-apt-pdiff-like-structure%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
1
What is your
sources.list? The examples you provide are of packages from buster/testing and sid/unstable. These different packages and repositories will have different types of metadata standards depending on who is the respective maintainer. According to this Debian Administration article not every package will be delivered via pdiff and pdiff is not always the most efficient way to deliver certain updates as well as the fact that with pdiffs you can have several updates per day.– kemotep
Feb 1 at 15:49
My sources.list is partially made of buster and sid. Although that article dates back to 2006.
– shirish
Feb 1 at 16:15
1
I am not as familiar with Appstream however looking at their documentation (last updated in 2018) Appsteam is a distro-agnostic meta data specification to make handling packaging easier. There is no specification that packages packaged using this standard uses pdiffs. Looking to the Debian Policy (Also updated in 2018) on packaging also shows that there is no standard requiring the use of pdiffs.
– kemotep
Feb 1 at 16:42
1
I have also found this related APT backend information that says if a given package does not have the option to download as pdiff or fails to download as a pdiff the package will be downloaded in its entirety.
– kemotep
Feb 1 at 16:50
1
I do not mean to bombard you with information but I think this link also provides useful information on why a given package may or may not use pdiffs.
– kemotep
Feb 1 at 16:56