måndagen den 21 april 2008 skrev Alec Hussey:
> I obviously want to keep that package and I even entered it in
> pacman.conf under HoldPkg and seems to have no affect. I dont know what
> I should do.
>
> Thanks!
> Alec Hussey
If cairo-lcd is a variation of cairo, it should provide cairo, and conf
On Mon, 2008-04-21 at 17:13 -0400, Alec Hussey wrote:
> Hey everyone,
>
> Ive been kind of frustrated lately because I haven't been able to update
> any of my pacakges because of a conflict between cairo and cairo-lcd.
> Here is the output from pacman.
>
> [EMAIL PROTECTED] ~]$ sudo pacma
just remove cairo then
On Mon, Apr 21, 2008 at 4:13 PM, Alec Hussey <[EMAIL PROTECTED]>
wrote:
> Hey everyone,
>
> Ive been kind of frustrated lately because I haven't been able to update
> any of my pacakges because of a conflict between cairo and cairo-lcd.
> Here is the output from pacman.
>
>
Hey everyone,
Ive been kind of frustrated lately because I haven't been able to update
any of my pacakges because of a conflict between cairo and cairo-lcd.
Here is the output from pacman.
[EMAIL PROTECTED] ~]$ sudo pacman -Syu
:: Synchronizing package databases...
core i
Guys this discussion is about to, if it has not already, become circular.
That's o.k. too, but you guys are not comprehending the information in
some of these emails.
Um, the answer to this is the same for ANY two or more packages that may
be used to do the same thing. And that has already been an
Thomas Bächler a écrit :
Thomas Bächler schrieb:
2) move tetex and all packages depending on it from extra to community
(that's only: kile, latex2html, lyx, texmacs)
(the trouble is that these makedep on tetex: evince, kdegraphics,
yodl; but maybe just keep tetex on the build machine fo
On Sonntag, 20. April 2008 13:42 Attila wrote:
Sorry for commenting myself and see this please only as an information.
> Okay, now i can say that nvidia 173.08 works and it seems that if you
> run /etc/start_udev the /dev/nvdia* devices get killed.
I step back to a patched 169.12 because i have
On Montag, 21. April 2008 11:45 Thomas Bächler wrote:
> Ha! texlive-core already provides tetex. Therefore, you can use all
> applications that depend on tetex with texlive instead. This situation
> is good enough for me.
But there is still the problem that if you do "pacman -S kile" (or auctex,
Excerpts from Thomas Bächler's message of Mon Apr 21 04:45:06 -0500 2008:
> Thomas Bächler schrieb:
> > We could make sure that either these packages depend on a virtual "tex"
> > package that is provided by texlive or make texlive provide tetex.
>
> Ha! texlive-core already provides tetex. There
On Mon, Apr 21, 2008 at 3:20 AM, Neil Darlow <[EMAIL PROTECTED]> wrote:
> Hi,
>
>
> Xavier wrote:
>
> > That's what provisions are for.
> >
>
>
> Wouln't that require that e.g. tetex and texlive have something like?
>
> provides=( "tex" )
>
> In practice, how many packages include such a generi
Thomas Bächler schrieb:
2) move tetex and all packages depending on it from extra to community
(that's only: kile, latex2html, lyx, texmacs)
(the trouble is that these makedep on tetex: evince, kdegraphics,
yodl; but maybe just keep tetex on the build machine for a time
being?)
We c
On Mon, Apr 21, 2008 at 10:20 AM, Neil Darlow <[EMAIL PROTECTED]> wrote:
> Wouln't that require that e.g. tetex and texlive have something like?
>
> provides=( "tex" )
>
> In practice, how many packages include such a generic provides entry? From
> what I've seen most packages' depends rely sole
Hi,
Xavier wrote:
That's what provisions are for.
Wouln't that require that e.g. tetex and texlive have something like?
provides=( "tex" )
In practice, how many packages include such a generic provides entry?
From what I've seen most packages' depends rely solely on the package name.
I t
Jan Spakula schrieb:
Proposal: Switch to texlive eventually officially (for now keeping
tex-related pkgs in community).
Switch? Isn't that your job?
How it can be done:
- from the dev side:
1) "officially" announce that the switch *is* going to happen.
There is no such thing as a "switch".
14 matches
Mail list logo
