‐‐‐ Original Message ‐‐‐
On Saturday, September 5, 2020 1:09 PM, Wols Lists
wrote:
> Isn't that how the web originally WAS designed? That the web-site sent
> content and the browser determined how it was displayed?
sort of. it was not very clear and they could've
gone either direction.
Long story short...
emerging portage with USE="-rsync-verify" also requires setting
sync-rsync-verify-metamanifest = no
in /etc/portage/repos.conf/gentoo.conf to actually function.
I assume that you have to set
sync-rsync-verify-metamanifest = yes
in /etc/portage/repos.conf/gentoo.conf *I
On 2020-09-05 11:43, Ashley Dixon wrote:
On Sat, Sep 05, 2020 at 10:47:34AM +0200, n952162 wrote:
gnokii wanted to emerge 6 packages and failed on the last:
It looks like this could be an ebuild error. Any hints, how to proceed?
gettext is not providing the codeset.m4 file, which was the file
On Sat, Sep 05, 2020 at 07:24:28AM -0500, Dale wrote:
> Some sites, not many tho, have a printable version. Gentoo for example
> has that. Another common type of site, recipes. I've seen a few that
> don't have printable versions but most do. Other than that, you are
> correct. This is why I o
On Sat, Sep 05, 2020 at 02:15:53PM +0200, n952162 wrote:
> That did the trick! And you did all the work for me :-) Thank you.
>
> Now, can I leave that at that or do you recommend that I remove that
> file and do what Nuno Silva recommended and emerge 0.6.31-r3?
Go ahead and follow Nuno's advi
Wols Lists wrote:
> On 03/09/20 18:44, Caveman Al Toraboran wrote:
>> i think this problem that we have could've been
>> avoided if the web was originally designed to only
>> deliver content, without any power to dictate
>> appearance, so that appearance is 100% a task that
>> a local client should
On 2020-09-05 11:43, Ashley Dixon wrote:
On Sat, Sep 05, 2020 at 10:47:34AM +0200, n952162 wrote:
gnokii wanted to emerge 6 packages and failed on the last:
It looks like this could be an ebuild error. Any hints, how to proceed?
gettext is not providing the codeset.m4 file, which was the file
On 2020-09-05 11:03, Ashley Dixon wrote:
On Sat, Sep 05, 2020 at 10:47:34AM +0200, n952162 wrote:
/txm1 /var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1 # less
/var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1/temp/autoconf.out//
//* autoconf *//
//* PWD:
/var/tmp/portage/app-mobil
On 2020-09-05, n952162 wrote:
> gnokii wanted to emerge 6 packages and failed on the last:
>
> /txm1 /var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1 # less
> /var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1/temp/autoconf.out//
> //* autoconf *//
> //* PWD:
> /var/tmp/portage/app-mob
On Sat, Sep 05, 2020 at 10:47:34AM +0200, n952162 wrote:
> gnokii wanted to emerge 6 packages and failed on the last:
> It looks like this could be an ebuild error. Any hints, how to proceed?
gettext is not providing the codeset.m4 file, which was the file to define
AM_LANGINFO_CODESET. Unfortuna
On 03/09/20 18:44, Caveman Al Toraboran wrote:
> i think this problem that we have could've been
> avoided if the web was originally designed to only
> deliver content, without any power to dictate
> appearance, so that appearance is 100% a task that
> a local client should choose.
Isn't that how
On Sat, Sep 05, 2020 at 10:47:34AM +0200, n952162 wrote:
> /txm1 /var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1 # less
> /var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1/temp/autoconf.out//
> //* autoconf *//
> //* PWD:
> /var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1/work/gnokii
gnokii wanted to emerge 6 packages and failed on the last:
/txm1 /var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1 # less
/var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1/temp/autoconf.out//
//* autoconf *//
//* PWD:
/var/tmp/portage/app-mobilephone/gnokii-0.6.31-r1/work/gnokii-0.6.3
13 matches
Mail list logo
