Le 01/11/2016 à 20:25, Peter Nabbefeld a écrit :
> /usr/bin/pyrogenesis is contained in 0ad a20-9
> 0ad-dataa20-1
> boost 1.62.0-2
>
> Should be latest versions, as updated this morning.
>
> Regards,
> Peter
File a bug report against 0ad in ArchLinux bug tracker. It somehow
escaped the
/usr/bin/pyrogenesis is contained in 0ad a20-9
0ad-dataa20-1
boost 1.62.0-2
Should be latest versions, as updated this morning.
Regards,
Peter
Am 01.11.2016 um 16:09 schrieb Jelle van der Waa:
On 11/01/16 at 04:05pm, Peter Nabbefeld wrote:
Hello,
when I want to start "0ad", I'm
On 11/01/16 at 04:05pm, Peter Nabbefeld wrote:
>
> Hello,
>
> when I want to start "0ad", I'm getting the following error message:
>
> /usr/bin/pyrogenesis: error while loading shared libraries:
pacman -Qo /usr/bin/pyrogenesis
Also please report the 0ad and boost version..
> libboost_filesyst
Thank You :)
I wanted to do sth. similar as the Gnome tool in Java, so I tried the
RSS variant, but it doesn't seem to be reliable.
I'm using XFCE, so I wanted to have some tool in a language I'm using
for software development, but it seems not possible, yet.
So, of course, I'll have to do
Hello,
when I want to start "0ad", I'm getting the following error message:
/usr/bin/pyrogenesis: error while loading shared libraries:
libboost_filesystem.so.1.61.0: cannot open shared object file: No such
file or directory
I've already tried to re-install boost and boost-libs.
Kind regar
When I updated that package here yesterday, I had file conflicts and
resolved them by removing from /etc/fonts/conf.d and then reinstalled
the package. Fortunately I don't use fonts since I've been totally
blind from birth and there aren't too many other authorized sighted
people looking at my
Thank You, subscribed it now :)
Regards,
Peter
Am 01.11.2016 um 13:34 schrieb Chris Warrick via arch-general:
On 1 November 2016 at 13:28, Peter Nabbefeld wrote:
Thank You. At some time I've subscribed to the arch linux update feed, but
it doesn't seem very useful, so I'll remove it:
1. It
> Morning. Try this, sudo pacman -Syu --force.
Please do not run that command unless the Arch site specifically recommends
it. Forcing a full system upgrade is extremely dangerous.
The safe solution is to force only ttf-dejavu.
I subscribed to the Arch Announcement feed at https://lists.archlinux.o
rg/listinfo/arch-announce
You almost never get any mail (which I love). It's actually a copy of
everything which will be shown on the arch website frontpage. Since I
never had any trouble with updates besides those mentioned o
On 1 November 2016 at 13:28, Peter Nabbefeld wrote:
> Thank You. At some time I've subscribed to the arch linux update feed, but
> it doesn't seem very useful, so I'll remove it:
>
> 1. It seems not all updates are reported
> 2. It doesn't show any hints - just like this
>
> Do You probably know o
Thank You!
Regards,
Peter
Am 01.11.2016 um 12:23 schrieb matthew dyer via arch-general:
Morning. Try this, sudo pacman -Syu --force. Worked for me thismorning
after this was sugested to me by someone on the sonar support list and
worked with my machine. HTH.
Matthew
On 11/01/2016 04:4
Thank You. At some time I've subscribed to the arch linux update feed,
but it doesn't seem very useful, so I'll remove it:
1. It seems not all updates are reported
2. It doesn't show any hints - just like this
Do You probably know of any other more useful feed(s)?
Kind regards
Peter
Am 01.11
On 11/01/2016 12:40 AM, Allan McRae wrote:
> I would like some bourbon.
>
> Allan
I like your sense of humor :)
>
> * It might appear unrelated, but I can spend time on pacman/makepkg if I
> don't have to work for bourbon. Then again, bourbon reduces the quality
> of my coding after a point...
> Any PKGBUILD kept in git can already optionally have this feature. See
> git-commit(1), specifically, its --gpg-sign option.
I know that, I have
[commit]
gpgsign = true
in my ~/.gitconfig.
It would be nice if more people did that and if makepkg checked that,
though.
It would probabl
Morning. Try this, sudo pacman -Syu --force. Worked for me thismorning
after this was sugested to me by someone on the sonar support list and
worked with my machine. HTH.
Matthew
On 11/01/2016 04:47 AM, Peter Nabbefeld wrote:
Hello,
cannot update packages, as ttf-dejavu has conflicts
See the website for tips on how to update: https://www.archlinux.org/ne
ws/ttf-dejavu-237-will-require-forced-upgrade/
pacman -S --force ttf-deja
ente
On Tue, 2016-11-01 at 09:47 +0100, Peter Nabbefeld wrote:
> Hello,
>
> cannot update packages, as ttf-dejavu has conflicts.
>
>
> ---
Hello,
cannot update packages, as ttf-dejavu has conflicts.
---
Output
---
Fehler: Konnte den Vorgang nicht durchführen (In Konflikt stehende Dateien)
ttf-dejavu: /etc/fonts/conf.d/20-unhint-small-dejavu-sans-mono.conf
existiert im Dateisystem
ttf-dejavu: /etc/fonts/conf.d/20-
Hi
The fontconfig for the package should go in /etc/fonts/conf.avail since I
was advised to create symbolic links to /etc/fonts/conf.d/ to enable
specific features. If this is not the case, the wiki needs to be updated.
Thanks guys!
Regards
Jagan
18 matches
Mail list logo
