<div dir="ltr"><div><div><div><div>Sorry, I guess filling disk is not such a bad thing after all. "Everyone else does it." <br><br></div>Disregard my sarcasm, you are of course right that the system is now designed to <br>withstand such poorly behaved applications.<br><br></div>I also thought configs were usually attached by reportbug, but in any case here is<br><br></div>$ cat /etc/apt/sources.list<br>deb <a href="http://ftp.citylink.co.nz/debian/">http://ftp.citylink.co.nz/debian/</a> testing main non-free contrib<br>deb-src <a href="http://ftp.citylink.co.nz/debian/">http://ftp.citylink.co.nz/debian/</a> testing main non-free contrib<br><br>deb <a href="http://security.debian.org/">http://security.debian.org/</a> jessie/updates main contrib non-free<br>deb-src <a href="http://security.debian.org/">http://security.debian.org/</a> jessie/updates main contrib non-free<br><br># jessie-updates, previously known as 'volatile'<br>deb <a href="http://ftp.citylink.co.nz/debian/">http://ftp.citylink.co.nz/debian/</a> jessie-updates main contrib non-free<br>deb-src <a href="http://ftp.citylink.co.nz/debian/">http://ftp.citylink.co.nz/debian/</a> jessie-updates main contrib non-free<br><br><br></div><div>$ cat ~/.aptitude/config<br>Aptitude "";<br>Aptitude::ProblemResolver "";<br>Aptitude::ProblemResolver::Trace-File "/tmp/aptitude.trace";<br>Aptitude::ProblemResolver::Remove-Level "10001";<br><br></div><div>I also attached the tarred remainder of the offending aptitude-trace directory in tmp. (Recall I had truncated the recursive directory at aptitude-trace-dumpubvton/usr/bin/X11/X11/X11/X11/X11 ).<br><br></div><div>After removing the <br></div><div>Aptitude::ProblemResolver::Trace-File "/tmp/aptitude.trace";<br></div><div>line, I went back in to aptitude to try the same thing again.<br><br></div><div>Upon starting, it immediately suggested 2 installs, 1 keep, 1 upgrade. Remember I had cancelled the pending actions. This action was not suggested last time I was in.<br></div><div>keep: libilmbase6v5<br></div><div>install: libilmbase12, libopenexr22<br></div><div>upgrade: libgeg-0.3-0<br><br></div><div>I entered ! to accept the suggestion, and verified that these actions are now pending, along with removal of libopenexr6v5 (libilmbase6v5 is also being removed because no longer used).<br><br></div><div>I also have a list of 34 packages being held back, including apt and apt-utils at 1.2.1. And 96 being automatically held, the list of which includes many xserver-xorg packages (and xserver-xorg-legacy at 2:1.173-2).<br><br></div><div>I tried hitting + on the Upgradeable line again, and this time the resolution was swift: Suggest 23 keeps. This was all the xserver-xorg packages again. I accepted. I hit the + sign again, and the same suggestion was offered again.<br><br></div><div>I think that must be where the recursiveness is coming in.<br><br></div><div>Let me know if there's something else I can try in this state.<br><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 12, 2016 at 12:57 AM, Manuel A. Fernandez Montecelo <span dir="ltr"><<a href="mailto:manuel.montezelo@gmail.com" target="_blank">manuel.montezelo@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Control: severity -1 minor<br>
<br>
<br>
Hi,<br>
<br>
2016-02-11 10:00 Chris Tillman:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Package: aptitude<br>
Version: 0.7.5-3<br>
Severity: critical<br>
Justification: breaks unrelated software<br>
</blockquote>
<br>
This is not a critical bug by any strectch, anymore than wget or any<br>
browser might break unrelated software if you download a partition<br>
without enough space (when other packages depend on empty space in that<br>
partition to work fine). Many packages use /tmp and can cause this<br>
problem under various circumstances, even with much smaller files.<br>
<br>
Simply downloading files in aptitude for an upgrade can fill up<br>
/var/cache/apt/archives, which might mean / and /tmp if it's a single<br>
partition, and aptitude never stopped to be released because of that<br>
behaviour.<br>
<br>
There is a simple workaround for that, I suspect, which is to use the<br>
defaults and not enable options related with trace-dumps.<br>
<br>
It would be useful though if you could mention the exact config or<br>
command line options that you enabled to make this happen.<br>
<br>
<br>
Cheers.<span class="HOEnZb"><font color="#888888"><br>
-- <br>
Manuel A. Fernandez Montecelo <<a href="mailto:manuel.montezelo@gmail.com" target="_blank">manuel.montezelo@gmail.com</a>><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature">Chris Tillman<br>Developer</div>
</div>