Am Mon, 27 Feb 2017 21:00:40 -0700
schrieb the...@sys-concept.com:
> On 02/27/2017 02:11 PM, Alan McKinnon wrote:
> > On 27/02/2017 22:14, the...@sys-concept.com wrote:
> >> When will they drop the dev-lang/php-5.6.30 from the portage?
> >
> > If you copy the ebuild into your local overlay, t
> On 23 Feb 2017, at 22:21, R0b0t1 wrote:
>
> However it's gotten to the point where not even building on-device
> works. I'm experiencing breakage in a lot of core packages that may or
> may not be related to portage. What is the best way to ask for help?
> The users on the forums and IRC do no
On 02/27/2017 02:11 PM, Alan McKinnon wrote:
> On 27/02/2017 22:14, the...@sys-concept.com wrote:
>> When will they drop the dev-lang/php-5.6.30 from the portage?
>
> If you copy the ebuild into your local overlay, then never
>
I'll do it just in case but eventually I'll be force to upgrade.
I'v
On 02/27/2017 03:44 PM, kelly hirai wrote:
> corbin,
>
> i've finally discovered the problem with this.
>
> it turns out that there were a set of stale .so files in
> /usr/iocal/bin/ installed in the year 2015. i discovered this by running:
>
> ebuild /usr/portage/net-libs/webkit-gtk/webkit-gtk-2.
On Mon, Feb 27, 2017 at 8:10 PM, Miroslav Rovis
wrote:
> Apologies for my not being able to reply sooner!
>
> On 170227-18:18+0300, Andrew Savchenko wrote:
>
>> > And via a new private big business, the Github. Giving over all users to
>> > big Github brother.
>>
>> ???
>> Github is entirely optio
On 02/27/2017 03:14 PM, the...@sys-concept.com wrote:
> When will they drop the dev-lang/php-5.6.30 from the portage?
>
> php-7.0 is not working with my application (modification are too
> intensive) besides I'm not a programmer.
>
The php-5.6 series will receive security updates until the end of
On 02/27/2017 06:06 PM, the...@sys-concept.com wrote:
> I have in:
> /etc/revdep-rebuild/99revdep-rebuild
> ...
> SEARCH_DIRS_MASK="/usr/lib64/openoffice"
>
[snip]
The above should be:
SEARCH_DIRS_MASK="/usr/lib/openoffice"
--
Thelma
Apologies for my not being able to reply sooner!
On 170227-18:18+0300, Andrew Savchenko wrote:
> On Sun, 26 Feb 2017 12:00:50 +0100 Miroslav Rovis wrote:
>
> > But, when we talk crypto being broken,
>
> Git is not in the immediate threat due to SHA1 collision being
> practical. See Linux blog a
I have in:
/etc/revdep-rebuild/99revdep-rebuild
...
SEARCH_DIRS_MASK="/usr/lib64/openoffice"
But my openoffice-bin constantly rebuilds.
Is there a way to prevent it besides switching to non bin ver.?
!!! existing preserved libs:
>>> package: dev-libs/libbsd-0.8.3
* - /usr/lib32/libbsd.so.0
*
corbin,
i've finally discovered the problem with this.
it turns out that there were a set of stale .so files in /usr/iocal/bin/
installed in the year 2015. i discovered this by running:
ebuild /usr/portage/net-libs/webkit-gtk/webkit-gtk-2.14.5.ebuild configure
the resulting ninja files showe
On 27/02/2017 22:14, the...@sys-concept.com wrote:
> When will they drop the dev-lang/php-5.6.30 from the portage?
If you copy the ebuild into your local overlay, then never
>
> php-7.0 is not working with my application (modification are too
> intensive) besides I'm not a programmer.
>
--
A
When will they drop the dev-lang/php-5.6.30 from the portage?
php-7.0 is not working with my application (modification are too
intensive) besides I'm not a programmer.
--
Thelma
On 02/27/2017 01:45 AM, Neil Bothwick wrote:
> On Sun, 26 Feb 2017 17:54:32 -0700, the...@sys-concept.com wrote:
>
>> I just tried gscan2pdf.
>> It does not offer auto-feed either; black borders still persist (so it
>> must be an issue with Brother driver.
>
> Sounds like it.
>
>> In addition, I
On Mon, Feb 27, 2017 at 1:02 PM, Alan McKinnon wrote:
>
> I always though git's use of SHA hashes was to identify commits and
> detect random bit flips, not to provide any measure of security.
>
As somebody said in Twitter recently (and Linus to some degree in his
post), it is, except when it isn
On 26/02/2017 22:32, R0b0t1 wrote:
> On Sun, Feb 26, 2017 at 5:00 AM, Miroslav Rovis
> wrote:
>> On 170225-21:34-0600, R0b0t1 wrote:
>>> On Saturday, February 25, 2017, Miroslav Rovis
>>>
>>> wrote:
>>> https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
>> ...
>>>
On Monday 27 Feb 2017 10:09:34 Harry Putnam wrote:
> I guess I'll try this once more... Its still a big log but I cleaned
> up the escapes ... it is a fresh try at building
> xf86-video-virtualbox-5.1.14
>
> Still failing in the same way and still not seeing clues in the
> log... probably my ow
On Monday 27 Feb 2017 10:09:34 Harry Putnam wrote:
> I guess I'll try this once more... Its still a big log but I cleaned
> up the escapes ... it is a fresh try at building
> xf86-video-virtualbox-5.1.14
>
> Still failing in the same way and still not seeing clues in the
> log... probably my ow
On Sun, 26 Feb 2017 12:00:50 +0100 Miroslav Rovis wrote:
> But, when we talk crypto being broken,
Git is not in the immediate threat due to SHA1 collision being
practical. See Linux blog about this:
https://plus.google.com/+LinusTorvalds/posts/7tp2gYWQugL
Note that git devs are working on mo
Stroller writes:
>> On 25 Feb 2017, at 14:19, Harry Putnam wrote:
>>
>> I've attached a hefty log of some 4000 lines and hope someone will be
>> patient enough to try to identify what is causing the problem.
>
> I took a look at this, but the broken colour codes throughout the log make it
>
On Mon, Feb 27, 2017 at 9:46 AM, Andrew Savchenko wrote:
>
> So danger of SHA1 collision is much closer than
> 9,223,372,036,854,775,808 SHA1 computations or 1 110-GPU year.
Indeed in every way it is closer than that than when Google started
their project, and tomorrow it will be closer still.
T
Dale writes:
> Harry Putnam wrote:
>>
>> Just so you know... I did try that. [--color n] The resulting log
>> looked exactly the same. I posted that fact in an earlier request for
>> help a week or so ago in which I remarked how using the no-color
>> emerge option didn't seem to make a bit of di
On Sat, 25 Feb 2017 22:12:10 +0100 Miroslav Rovis wrote:
> https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
>
> ( you know I hate the Schmoog, and didn't take their cookies, and so
> they didn't show me their page in my Palemoon --working great here!, an
> Angel of Hone
On Thu, 23 Feb 2017 20:10:05 + Mick wrote:
> I am trying to understand why an ssh server keeps dropping the connection
> when
> using openssh on Linux straight after a successful authentication, but it
> works fine with Filezilla in MSWindows.
[...]
> I am guessing all this respawning probab
On Thu, 23 Feb 2017 16:21:04 -0600 R0b0t1 wrote:
> Hello,
>
> So apparently I am single-handedly attempting to stabilize arm64 (at
> least, it feels that way). Per the "Gentoo on Alternative
> Architectures" subforum
> (https://forums.gentoo.org/viewforum-f-32.html) two users have gotten
> almost
On Mon, 20 Feb 2017 17:45:28 + (UTC) Grant Edwards wrote:
> I installed weasyprint-0.29, but it won't run:
>
> $ weasyprint
> Traceback (most recent call last):
> File "/usr/lib/python-exec/python2.7/weasyprint", line 6, in
> from pkg_resources import load_entry_point
> [...
On 170226-09:42-0500, Harry Putnam wrote:
> Stroller writes:
...
>
> > Example at the beginning: [32;01m *
> > Example from the end: *
> >
> > Output to the terminal these would show the text in different colours,
> > but the output was redirected to a textfile or mishandled in a
> > copy-pa
On 170226-14:32-0600, R0b0t1 wrote:
> On Sun, Feb 26, 2017 at 5:00 AM, Miroslav Rovis
> wrote:
> > On 170225-21:34-0600, R0b0t1 wrote:
> >> On Saturday, February 25, 2017, Miroslav Rovis
> >>
> >> wrote:
> >> >
> >> https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
> >
On Mon, 27 Feb 2017 07:31:22 +, Thomas Mueller wrote:
> > On Sat, 25 Feb 2017 21:58:05 +0100, Miroslav Rovis wrote:
>
> > > On 170225-09:19-0500, Harry Putnam wrote:
> > > > Setup: VBox vm running gentoo(amd64) guest on a win-10 (64bit)
> > > > host Hardware: HP xw8600 - 2x Xeon CPU X545
On Sun, 26 Feb 2017 17:54:32 -0700, the...@sys-concept.com wrote:
> I just tried gscan2pdf.
> It does not offer auto-feed either; black borders still persist (so it
> must be an issue with Brother driver.
Sounds like it.
> In addition, I've noticed big difference is scan size of an image.
> Smal
29 matches
Mail list logo
