Got this odd behaviour today, and I use GIMP fairly frequently so this
only turned up in the past 3-4 days I think. I can't seem to
left-click in the image itself (left-clicking on menus registers), so
I can't, for example, paint anything.
Is this specific to my machine, or can someone else confir
On Tue, Apr 8, 2014 at 4:43 PM, Oon-Ee Ng wrote:
> Got this odd behaviour today, and I use GIMP fairly frequently so this
> only turned up in the past 3-4 days I think. I can't seem to
> left-click in the image itself (left-clicking on menus registers), so
> I can't, for example, paint anything.
>
On Tuesday, April 08, 2014 17:39:56 Oon-Ee Ng wrote:
> And python-setuptools/python2-setuptools just updated, fixing it for
> me. That was fast.
I don't think your problem was related to setuptools though. The recent two
version bumps are only for patching its tests against python 3.1, which has
Hi, I change for example dns in networkmanager, when restart
NetworkManager , "systemctl restart NetworkManager" the network not
works...
[maykel@maykel-arch ~]$ sudo systemctl status NetworkManager
● NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManage
And python-setuptools/python2-setuptools just updated, fixing it for
me. That was fast.
I don't think your problem was related to setuptools though. The recent two
version bumps are only for patching its tests against python 3.1, which has
nothing to do about us in any way.
What's more, setup
On Tue, Apr 8, 2014 at 7:57 PM, Nowaker wrote:
>>> And python-setuptools/python2-setuptools just updated, fixing it for
>>> me. That was fast.
>
>
>> I don't think your problem was related to setuptools though. The recent
>> two
>> version bumps are only for patching its tests against python 3.1,
Hey guys,
I've started using /tmp for building packages using extra-x86_64-build
(and similar). However, I've a problem with the /tmp/extra-x86_64 not
being cleaned on boot by systemd-tmpclean.
I have the following in /etc/tmpfiles.d/tmp.conf:
# Clear tmp directories separately, to make them
Hi,
there is an Bug(1) in OpenSSL 1.0.1 and as far as I'm informed this has
only been patched in 1.0.1g.
Many other Distributions have build there own patch, what is with us?
Currently we have "1.0.1.f-2" which is effected as far as I can know.
Greetings
Neal
1) (sry, German)
http://www.golem.de
On Tuesday, April 08, 2014 05:29:11 PM Neal Oakey wrote:
> Hi,
>
> there is an Bug(1) in OpenSSL 1.0.1 and as far as I'm informed this has
> only been patched in 1.0.1g.
> Many other Distributions have build there own patch, what is with us?
> Currently we have "1.0.1.f-2" which is effected as far
% pacman -Si openssl
Repository : core
Name : openssl
Version: 1.0.1.g-1
Description: The Open Source toolkit for Secure Sockets Layer and
Transport Layer Security
Architecture : x86_64
URL: https://www.openssl.org
Licenses : custom:BSD
Groups :
Hi
On Tue, Apr 8, 2014 at 8:29 AM, Neal Oakey wrote:
> Hi,
>
> there is an Bug(1) in OpenSSL 1.0.1 and as far as I'm informed this has
> only been patched in 1.0.1g.
> Many other Distributions have build there own patch, what is with us?
It is fixed already. The new version of openssl is in stab
> Currently we have "1.0.1.f-2" which is effected as far as I can know.
pacman -Syu should upgrade it to 1.0.1.g-1?
pacman -Q openssl reports that version anyway, which fixes heartbleed.
[1]
Greetings,
Zeger-Jan van de Weg
[1] https://www.openssl.org/news/secadv_20140407.txt
Hi,
ah ... ok kickt the top mirror - now I'm back up to date
tanks
Neal
Am 08.04.2014 17:32, schrieb y...@marupa.net:
> On Tuesday, April 08, 2014 05:29:11 PM Neal Oakey wrote:
>> Hi,
>>
>> there is an Bug(1) in OpenSSL 1.0.1 and as far as I'm informed this has
>> only been patched in 1.0.1g.
>>
On 08/04/2014 17:29, Neal Oakey wrote:
> Many other Distributions have build there own patch, what is with us?
As a reminder, there is now a Wiki page that tracks all security issues
and their status in Arch Linux [1]. If it's not there, please either add
the issue in the wiki by yourself and file
Am 08.04.2014 17:29, schrieb Neal Oakey:
> Hi,
>
> there is an Bug(1) in OpenSSL 1.0.1 and as far as I'm informed this has
> only been patched in 1.0.1g.
> Many other Distributions have build there own patch, what is with us?
> Currently we have "1.0.1.f-2" which is effected as far as I can know.
Hi
On Tue, Apr 8, 2014 at 9:29 AM, Pierre Schmitz wrote:
> Am 08.04.2014 17:29, schrieb Neal Oakey:
>> Hi,
>>
>> there is an Bug(1) in OpenSSL 1.0.1 and as far as I'm informed this has
>> only been patched in 1.0.1g.
>> Many other Distributions have build there own patch, what is with us?
>> Curr
Slightly OT but for those interested, I added the heartbleed utility
(used by the heartbleed checker site) to the AUR:
https://aur.archlinux.org/packages/heartbleed-git/
% heartbleed mediacru.sh:443
2014/04/08 17:53:57 mediacru.sh:443 - SAFE
J. Leclanche
On Tue, Apr 8, 2014 at 5:35 PM, Anatol Po
Hi
On Tue, Apr 8, 2014 at 8:32 AM, Anatol Pomozov wrote:
> Hi
>
> On Tue, Apr 8, 2014 at 8:29 AM, Neal Oakey wrote:
>> Hi,
>>
>> there is an Bug(1) in OpenSSL 1.0.1 and as far as I'm informed this has
>> only been patched in 1.0.1g.
>> Many other Distributions have build there own patch, what is
> I actually did push an updated package within 3 hours after the public
> announcement. I think that is pretty reasonable especially since we are
> not among the fortunate distros and companies that were notified
> beforehand.
It's very good! Only a few distribution and vendors can do that!
What
On Tue, Apr 8, 2014 at 2:32 PM, Oon-Ee Ng wrote:
> On Tue, Apr 8, 2014 at 7:57 PM, Nowaker wrote:
And python-setuptools/python2-setuptools just updated, fixing it for
me. That was fast.
>>
>>
>>> I don't think your problem was related to setuptools though. The recent
>>> two
>>> version
On 04/08/2014 04:31 AM, Maykel Franco wrote:
> Hi, I change for example dns in networkmanager, when restart
> NetworkManager , "systemctl restart NetworkManager" the network not
> works...
>
> ...
>
> I have reboot my computer for network on again.
>
> Is a bug networkmanager?
>
> The version i
Hello all,
With the arrival of ghc 7.8.1 [0], I would like to address the following
problems with a restructuring of how we treat haskell packages in archlinux:
Problem 1: Updating any haskell package has been delayed until we bump ghc.
Explanation: ghc is unable to produce a library that has a s
22 matches
Mail list logo
