From mboxrd@z Thu Jan 1 00:00:00 1970 X-Received: by 10.236.229.233 with SMTP id h99mr16161944yhq.42.1425691977626; Fri, 06 Mar 2015 17:32:57 -0800 (PST) X-BeenThere: voidlinux@googlegroups.com Received: by 10.182.102.1 with SMTP id fk1ls201446obb.47.gmail; Fri, 06 Mar 2015 17:32:57 -0800 (PST) X-Received: by 10.182.58.34 with SMTP id n2mr162149obq.12.1425691977457; Fri, 06 Mar 2015 17:32:57 -0800 (PST) Date: Fri, 6 Mar 2015 17:32:56 -0800 (PST) From: Logen Kain To: voidlinux@googlegroups.com Message-Id: <8ec6b78c-38dd-4434-88d3-e980257de266@googlegroups.com> Subject: unresolved shlibs MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_1500_163957231.1425691976812" ------=_Part_1500_163957231.1425691976812 Content-Type: multipart/alternative; boundary="----=_Part_1501_407662316.1425691976812" ------=_Part_1501_407662316.1425691976812 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit So after updating today I suddenly have a ton of "unresolved shilbs" when I try to update. Such as: python-2.7.9_6: broken, unresolvable shlib `libgdbm_compat.so.4' Am I alone in this? ------=_Part_1501_407662316.1425691976812 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 7bit
So after updating today I suddenly have a ton of "unresolved shilbs" when I try to update. Such as:
python-2.7.9_6: broken, unresolvable shlib `libgdbm_compat.so.4'

Am I alone in this?
------=_Part_1501_407662316.1425691976812-- ------=_Part_1500_163957231.1425691976812--