On Sat, Jun 2, 2012 at 11:56 AM, Myra Nelson wrote:
> While working on some AUR packages, I took a look at the PKGBUILD
> prototypes that come with pacman. The one difference that I had a
> question about has to do with this snippet:
>
> _author=AUTHOR_NAME
>
> _perlmod=MODNAME
>
> pkgname=perl-$_
Guys,
Before I cause myself headaches -- is there anyone that has updated to systemd
running a hylafax server with traditional serial modems? I see that systemd has
the faxq.service and hafaxd.service:
usr/lib/systemd/system/faxq.service
usr/lib/systemd/system/hfaxd.service
But what about th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/12 18:06, Allan McRae wrote:
>
> Wrong.
The error had been appearing for quite long enough for my mirror to
update. The correct solution seems to have been:
pacman -S db perl-berkeleydb
- --
David Benfell
benf...@parts-unknown.org
-BE
On 03/06/12 10:55, David Benfell wrote:
> On 06/02/12 16:38, Florian Pritz wrote:
>> On 06/02/2012 11:53 PM, David Benfell wrote:
>>> I think this says it all (output from pacman -Syu):
>
>> No, it doesn't explain what you believe to be a typo and why.
>
>>>
>
>
>
>>> warning: cannot resolve "
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 06/02/12 16:38, Florian Pritz wrote:
> On 06/02/2012 11:53 PM, David Benfell wrote:
>> I think this says it all (output from pacman -Syu):
>
> No, it doesn't explain what you believe to be a typo and why.
>
>>
>> warning: cannot resolve "db=5.
On 03/06/12 05:32, Jude DaShiell wrote:
> Last perl build broke my instance of perl and made it necessary to
> reinstall archlinux or try to. Maybe I'll get that done tomorrow. On Sat,
I don't know what "it" is in this particular case... but you are doing
it wrong.
On 06/02/2012 11:53 PM, David Benfell wrote:
> I think this says it all (output from pacman -Syu):
No, it doesn't explain what you believe to be a typo and why.
>
> :: Synchronizing package databases...
> core is up to date
> extra is up to date
> community is up to date
> multilib is up to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I think this says it all (output from pacman -Syu):
:: Synchronizing package databases...
core is up to date
extra is up to date
community is up to date
multilib is up to date
:: Starting full system upgrade...
resolving dependencies...
warning: c
Last perl build broke my instance of perl and made it necessary to
reinstall archlinux or try to. Maybe I'll get that done tomorrow. On Sat,
2 Jun 2012, Myra Nelson wrote:
> While working on some AUR packages, I took a look at the PKGBUILD
> prototypes that come with pacman. The one difference
On 06/02/2012 01:09 AM, Allan McRae wrote:
> Because krb5 no longer provides it. Whoever is maintaining the kdemod3
> packages had a very long time to replace heimdal with krb5...
Thank you Allan ;-)
Were it not for a few 'subtle' runtime issues introduced by gcc 4.7, this would
be an issue that
While working on some AUR packages, I took a look at the PKGBUILD
prototypes that come with pacman. The one difference that I had a
question about has to do with this snippet:
_author=AUTHOR_NAME
_perlmod=MODNAME
pkgname=perl-$_perlmod
pkgver=VERSION
Since the MODNAME package being downloaded
On 2 June 2012 14:01, Lukáš Jirkovský wrote:
> I'm going to fill a bug report, because this
> is pretty serious issue as it makes KDE completely unusable.
Bug report filled:
https://bugs.archlinux.org/task/30106
For now I'm going to rebuild kdelibs locally.
On 2 June 2012 13:52, Lukáš Jirkovský wrote:
> On 2 June 2012 12:40, Lukáš Jirkovský wrote:
>> Actually I think wher the problem is (but I don't know what the
>> problem is yet) – it seems to be in the Herqq library.
>
> Soo, the rebuild of the herqq library didn't help.
>
> Anyway, here are a fe
On 2 June 2012 12:40, Lukáš Jirkovský wrote:
> Actually I think wher the problem is (but I don't know what the
> problem is yet) – it seems to be in the Herqq library.
Soo, the rebuild of the herqq library didn't help.
Anyway, here are a few backtraces I got few minutes earlier. All of
them cont
On 2 June 2012 11:55, Lukáš Jirkovský wrote:
> On 2 June 2012 11:44, GSC wrote:
>> After upgrading yesterday(including udev system-tools and x), I
>> experienced quite a lot Knotify crashes today. Though I'm using gnome-shell
>> and only use some KDE apps.
>
> I guess you are having the same pro
On 2 June 2012 11:44, GSC wrote:
> After upgrading yesterday(including udev system-tools and x), I
> experienced quite a lot Knotify crashes today. Though I'm using gnome-shell
> and only use some KDE apps.
I guess you are having the same problem as I do.
> video-drivers ?
I don't think it's video driver related, because the crashes seems to
always occur somewhere in Qt, but not a single crash contains anything
graphics-related, it just crashes in random places – sometimes it's in
Qtcore, sometimes in QtNetwork (I remember this one contained
someth
After upgrading yesterday(including udev system-tools and x), I
experienced quite a lot Knotify crashes today. Though I'm using gnome-shell
and only use some KDE apps.
On Sat, Jun 2, 2012 at 5:23 PM, Ike Devolder wrote:
> Op zaterdag 2 juni 2012 11:05:58 schreef Lukáš Jirkovský:
> > Is anyone e
Le samedi 02 juin 2012 à 01:06 +0200, Tom Gundersen a écrit :
[...]
Thanks Tom for the good advices/response.
I'll try to improve the wiki page once I'll understand/master systemd
too.
Op zaterdag 2 juni 2012 11:05:58 schreef Lukáš Jirkovský:
> Is anyone experiencing lots weird crashes of KDE applications
> recently? I'm getting tons of crashes very often, sometimes less then
> ten minutes between a bunch of crashes (Aaargh, KNotify, KMix,
> Krunner, Plasma, Kded and KMix crashed
Is anyone experiencing lots weird crashes of KDE applications
recently? I'm getting tons of crashes very often, sometimes less then
ten minutes between a bunch of crashes (Aaargh, KNotify, KMix,
Krunner, Plasma, Kded and KMix crashed within a second while writing
this email).
It started here after
21 matches
Mail list logo
