Control: tags -1 - moreinfo
Control: close -1
2015-09-09 00:14 To Michael Rasmussen:
Control: retitle -1 aptitude: generic/problemresolver/solution.h:297: void
generic_solution<PackageUniverse>::solution_rep::decref() const [...]: Assertion
"refcount>0" failed
Control: tags -1 + moreinfo
Hi Michael,
2011-05-30 15:46 Michael Rasmussen:
Package: aptitude
Version: 0.6.4-1
Severity: important
# aptitude upgrade
Resolving dependencies...
Unable to resolve dependencies for the upgrade:
../../src/generic/problemresolver/solution.h:297: void
generic_solution<PackageUniverse>::solution_rep::decref() const [with
PackageUniverse = aptitude_universe]: Assertion "refcount>0" failed.
Unable to safely resolve dependencies, try running with --full-resolver.
# apt-get dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be REMOVED:
ntfsprogs
The following packages will be upgraded:
ntfs-3g
1 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
Need to get 0 B/303 kB of archives.
After this operation, 139 kB disk space will be freed.
Do you want to continue [Y/n]?
Triaging bugs for years, I think that I haven't seen this kind of
assertion failure before.
The system was using unstable and experimental, and more than 4 years
after the fact, trying to reproduce this bug would be quite difficult.
I will leave it open and with a different title in the case that we see
more issues in the future, so we can find previous occurrences more
easily.
My best guess is that there was some interaction with other components
at the time, e.g. apt and complex changes like multi-arch being added
around that time, that made this problem surface in aptitude, but I have
no clue about how to try to address it.
After 4 years without anybody else submitting similar reports,
revisiting many more triaged bugs and failing to find anything similar,
and several months with no occurrences after renaming this issue, I
think that it's safe to close this bug report.
In the case that it's still a latent problem, hopefully we will be able
to gather information to actually be able to do something about it, like
backtraces inside debuggers.
So closing now. Thanks for the report and sorry that it was not handled
in a more timely manner, at a time when such vital information could
have been gathered.
Cheers.
--
Manuel A. Fernandez Montecelo <manuel.montez...@gmail.com>
