2011/2/9 Ryan Hill dirtye...@gentoo.org
On Tue, 08 Feb 2011 09:52:55 +0100
Paweł Hajdan, Jr. phajdan...@gentoo.org wrote:
It seems that with glibc-2.13 there are some serious compatibility
issues. There are good warnings on the planet
(http://psykil.livejournal.com/340806.html), but not
On Wed, 9 Feb 2011 13:32:36 +0100
Francesco R viv...@gmail.com wrote:
Since the upgrade I do get portage emerging text files .sh, .conf and
such as file of the exact same size but filled of \0, luckily most
upgrade fails.
I've seen similar issue in bug #353907 [1] but there they blame
2011/2/9 Michał Górny mgo...@gentoo.org
On Wed, 9 Feb 2011 13:32:36 +0100
Francesco R viv...@gmail.com wrote:
Since the upgrade I do get portage emerging text files .sh, .conf and
such as file of the exact same size but filled of \0, luckily most
upgrade fails.
I've seen similar issue
Francesco R posted on Wed, 09 Feb 2011 13:32:36 +0100 as excerpted:
2011/2/9 Ryan Hill dirtye...@gentoo.org
On Tue, 08 Feb 2011 09:52:55 +0100
Paweł Hajdan, Jr. phajdan...@gentoo.org wrote:
It seems that with glibc-2.13 there are some serious compatibility
issues. [H]ow about creating
On Tue, 08 Feb 2011 09:52:55 +0100
Paweł Hajdan, Jr. phajdan...@gentoo.org wrote:
It seems that with glibc-2.13 there are some serious compatibility
issues. There are good warnings on the planet
(http://psykil.livejournal.com/340806.html), but not every ~arch user
reads the planet, so how
