This bug was fixed in the package apt - 2.0.5
---
apt (2.0.5) focal; urgency=medium
[ Julian Andres Klode ]
* private-search: Only use V.TranslatedDescription() if good (LP: #1877987)
* Implement update --error-on=any (Closes: #594813) (LP: #1693900)
* Include all
This bug was fixed in the package apt - 1.6.13
---
apt (1.6.13) bionic; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
(LP: #1918920)
[
This bug was fixed in the package apt - 2.1.10ubuntu0.3
---
apt (2.1.10ubuntu0.3) groovy; urgency=medium
[ David Kalnischkies ]
* Fix incorrect base64 encoding due to int promotion (LP: #1916050)
* Harden test for no new acquires after transaction abort (Closes: #984966)
The autopkgtests for apt have passed, so testing succeeded. I retried
the failures, I expect them to be unrelated: apport one already happened
with binutils/2.30-21ubuntu1~18.04.5, the i386 retry succeeded; and
reprotest fails in its normal way, a few retries should get it working.
** Tags
I tried the apt provided by focal-proposed. At least
sudo apt-get update -eany
gave exit status 100, if I disabled networking. Without -eany it gave 0.
I got the source code by 'apt source'.
I could not run test-apt-update-failure-propagation:
$ sudo
** Changed in: apt (Debian)
Status: Unknown => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693900
Title:
apt-get update should return exit code != 0 on error
To manage
Fixed in Ubuntu Hirsute.
---
apt (2.1.16) unstable; urgency=medium
[ Faidon Liambotis ]
* Various fixes to http and connect method
- basehttp: also consider Access when a Server's URI
- connect: convert a C-style string to std::string
- connect: use ServiceNameOrPort, not Port,
** Bug watch removed: github.com/moby/moby/issues #23910
https://github.com/moby/moby/issues/23910
** Bug watch removed: github.com/moby/libnetwork/issues #1654
https://github.com/moby/libnetwork/issues/1654
** Changed in: apt (Ubuntu Xenial)
Importance: Undecided => Wishlist
**
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu Xenial)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693900
Title:
** Bug watch added: Debian Bug tracker #594813
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594813
** Also affects: apt (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594813
Importance: Unknown
Status: Unknown
** Description changed:
[Impact]
There is no
Hello Jens, or anyone else affected,
Accepted apt into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/1.6.13 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jens, or anyone else affected,
Accepted apt into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.0.5 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Jens, or anyone else affected,
Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
** Changed in: apt (Ubuntu Groovy)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693900
Title:
apt-get update should return exit code != 0 on error
To manage
** Description changed:
+ [Impact]
+ There is no way for scripts to run apt update and be sure that it was
entirely successful.
+
+ We introduce a new flag, --error-mode=any
+
+ [Test plan]
+ We have included a test in the test-suite in
test-apt-update-failure-propagation that ensures that
Thanks Scott for digging out this bug again, I'll use it for SRUing.
** Changed in: apt (Ubuntu)
Status: Triaged => Fix Released
** Also affects: apt (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: apt (Ubuntu Xenial)
Importance: Undecided
Status:
For reference, ubuntu-devel post about '-o APT::Update::Error-Mode=any'
at https://lists.ubuntu.com/archives/ubuntu-devel/2021-February/041374.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Julian Andres Klode Is this something you'd be willing to reassess? I
saw your old message [1] on the Debian list that says:
> The question what a successful update is is complicated and depends
on the expections of the person using APT.
With that in mind, I'd say there are situations where
I can only tell you that either python or C++ should give you what you
need at the moment. You could potentially just parse Err lines, but
that's a bit hacky. As you mentioned, the output changed a bit.
Our functions return booleans every in the stack, it's unclear how and
if we can change that
juliank, Do you mean ppa-purge should be translated to completely
different programming language, and that I can not even rely on apt-get
outputting something that matches '^Err[ :]' to stdout in such cases?
Sounds difficult.
What do you mean by "Our results are boolean, we might not be able to
That's your opinion, and we already know it.
Whether we want to do it that or if it is technically feasible are
different questions. Fact is: Our results are boolean, we might not be
able to really influence the exit status.
I don't want to discuss this with you, I was just giving jarnos a hint
Actually this is the problem: Users think, their system is up-to-date,
but it is not for sure because a site failed to respond. Therefore only
if _all_ sites answered the request properly, apt-get should return 0.
If not, it should return a specified return code, which lets the callee
know, that
No, there are two different use cases here:
1. Did apt-get update (potentially) change something?
2. Did apt-get update (potentially) change everything?
In the general case, 1 is what you need to know. For example, a tool
that runs update and then upgrades your system: You don't want to
prevent
The bug/subject here is, that apt-get doesn't return a proper exit code,
not, what else one could use to workaround the bug.
Saying, that update from one of all (i.e. 1+) sites is sufficient is
like going to fly with a jet, where one of two engines is already broken
before it starts. Making this
You should probably use an API for that (like python-apt), rather than
the command-line tools. We will have to rework error handling if we ever
want to retry automatic updates on failures, but it's not entirely clear
how this will happen yet.
In any case, I do consider an update where not all
Because of this bug ppa-purge misbehaves (Bug #1514839). Should one
inspect the output of apt-get for '^Err:' (from standard output) or even
'^W:' (from standard error) to determine, if it updated the repositories
or not? Besides the output of `apt-get update` varies between versions
in supported
Well, it's more like "this site is temporarily unavailable, please try
again at a later time."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693900
Title:
apt-get update should return exit code !=
Hmmm, IMHO 'Err:' and 'W: Failed to fetch' indicate, that it was not
able to update properly and thus the result of the operation is
unreliable. So its like "your connection is secured, but may be not". I
guess most people wouldn't do any financial transaction when reading
this ... ;-)
--
You
Well, it did not fail, it re-used the existing information. Transient
network errors do not cause the update to fail, because they are
expected to be temporary. It's always been like this. I'm open to
possibly changing this, but such a change could cause huge issues.
** Changed in: apt (Ubuntu)
29 matches
Mail list logo
