apt upgrade reporting in bytes and 10000+%

Multi tool use
I have a server running 16.04 and when I run apt upgrade
it doesn't report the correct package size or percentage:
76% [1 jenkins 35.5 MB/262 B 13457392%]
I've also noticed that download speeds are much slower than other servers from the same provider.
What could cause this and how do I fix it?
apt
add a comment |
I have a server running 16.04 and when I run apt upgrade
it doesn't report the correct package size or percentage:
76% [1 jenkins 35.5 MB/262 B 13457392%]
I've also noticed that download speeds are much slower than other servers from the same provider.
What could cause this and how do I fix it?
apt
Check the configuration and the sources.list. Try using the main repositories or nearer mirrors.
– EnzoR
Oct 2 '18 at 16:10
add a comment |
I have a server running 16.04 and when I run apt upgrade
it doesn't report the correct package size or percentage:
76% [1 jenkins 35.5 MB/262 B 13457392%]
I've also noticed that download speeds are much slower than other servers from the same provider.
What could cause this and how do I fix it?
apt
I have a server running 16.04 and when I run apt upgrade
it doesn't report the correct package size or percentage:
76% [1 jenkins 35.5 MB/262 B 13457392%]
I've also noticed that download speeds are much slower than other servers from the same provider.
What could cause this and how do I fix it?
apt
apt
asked Oct 2 '18 at 15:44
digitaldigital
1238
1238
Check the configuration and the sources.list. Try using the main repositories or nearer mirrors.
– EnzoR
Oct 2 '18 at 16:10
add a comment |
Check the configuration and the sources.list. Try using the main repositories or nearer mirrors.
– EnzoR
Oct 2 '18 at 16:10
Check the configuration and the sources.list. Try using the main repositories or nearer mirrors.
– EnzoR
Oct 2 '18 at 16:10
Check the configuration and the sources.list. Try using the main repositories or nearer mirrors.
– EnzoR
Oct 2 '18 at 16:10
add a comment |
1 Answer
1
active
oldest
votes
So in this peculiar case changing the source package location from https
to http
fixed the issue.
What likely happened is thatapt
went to determine how large the download is, which would be done by inspecting theContent-Length
header of the HTTP response, but it likely was a redirect (262 bytes) at which point the real download started which was much larger.
– Kristopher Ives
2 days 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%2f1080342%2fapt-upgrade-reporting-in-bytes-and-10000%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
So in this peculiar case changing the source package location from https
to http
fixed the issue.
What likely happened is thatapt
went to determine how large the download is, which would be done by inspecting theContent-Length
header of the HTTP response, but it likely was a redirect (262 bytes) at which point the real download started which was much larger.
– Kristopher Ives
2 days ago
add a comment |
So in this peculiar case changing the source package location from https
to http
fixed the issue.
What likely happened is thatapt
went to determine how large the download is, which would be done by inspecting theContent-Length
header of the HTTP response, but it likely was a redirect (262 bytes) at which point the real download started which was much larger.
– Kristopher Ives
2 days ago
add a comment |
So in this peculiar case changing the source package location from https
to http
fixed the issue.
So in this peculiar case changing the source package location from https
to http
fixed the issue.
answered 2 days ago
digitaldigital
1238
1238
What likely happened is thatapt
went to determine how large the download is, which would be done by inspecting theContent-Length
header of the HTTP response, but it likely was a redirect (262 bytes) at which point the real download started which was much larger.
– Kristopher Ives
2 days ago
add a comment |
What likely happened is thatapt
went to determine how large the download is, which would be done by inspecting theContent-Length
header of the HTTP response, but it likely was a redirect (262 bytes) at which point the real download started which was much larger.
– Kristopher Ives
2 days ago
What likely happened is that
apt
went to determine how large the download is, which would be done by inspecting the Content-Length
header of the HTTP response, but it likely was a redirect (262 bytes) at which point the real download started which was much larger.– Kristopher Ives
2 days ago
What likely happened is that
apt
went to determine how large the download is, which would be done by inspecting the Content-Length
header of the HTTP response, but it likely was a redirect (262 bytes) at which point the real download started which was much larger.– Kristopher Ives
2 days 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%2f1080342%2fapt-upgrade-reporting-in-bytes-and-10000%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
iY73sngnlTyP,a 293IQB,ndUXzFgPVVJWpN,ETjYIsZ 3j4mwAF,IKBIaf sYeT62GCK A4aXcAzRezsTnuym56zO,vVavI5p ad,XZ,sO
Check the configuration and the sources.list. Try using the main repositories or nearer mirrors.
– EnzoR
Oct 2 '18 at 16:10