Hi,
I am facing some problems with alsa. During booting it shows some
errors. But I don't know how to copy those and paste them here. Can
someone please tell me where can I find the log file?
Thanks.
On Tue, 2011-03-15 at 15:32 -0500, David C. Rankin wrote:
> Problem with depends=('xorg') is NOT limited to this one box. I have
> added the
> info to bug:
Sorry, but depending on a group is plain stupid. I didn't even know
pacman could handle that.
[2011-03-15 21:42:03 +0100] Tobias Powalowski:
> - bump to latest version
Another signoff for x86_64.
--
Gaetan
pgpHf5LIUzATw.pgp
Description: PGP signature
udev contains rules to generate persistent symlinks, if they do not work
as intendend this should be reported upstream.
Furthermore, upstream discourages using /dev/.udev as its format might
change at any time. As of upstream commit 5f59fa0900a5 the location has
changed to /dev/.run/udev, so we wo
Hi all,
As of the next udev release, /dev/.udev has moved to /dev/.run/udev. So, since
we have to update this anyway, I thought this was a good opportunity to review
our persistent net/cd rules functionality.
If I understand correctly, udev allready has support for creating persistent
net/cd s
Latest LTS kernel is in testing,
- added numa support on x86_64 config
please signoff for both arches
greetings
tpowa
--
Tobias Powalowski
Archlinux Developer & Package Maintainer (tpowa)
http://www.archlinux.org
tp...@archlinux.org
signature.asc
Description: This is a digitally signed message
Hi guys,
- bump to latest version
greetings
tpowa
--
Tobias Powalowski
Archlinux Developer & Package Maintainer (tpowa)
http://www.archlinux.org
tp...@archlinux.org
signature.asc
Description: This is a digitally signed message part.
[2011-03-15 14:24:10 -0500] David C. Rankin:
> After the latest xorg updates, PKGBUILD scripts that include
> depends=('xorg') are triggering complete reinstalls of all xorg
> packages. This didn't happen before.
You should probably read arch-dev-public.
See:
http://mailman.archlinux.org/piperma
On 03/15/2011 02:45 PM, David C. Rankin wrote:
On 03/15/2011 02:24 PM, David C. Rankin wrote:
After the latest xorg updates, PKGBUILD scripts that include depends=('xorg')
are triggering complete reinstalls of all xorg packages.
I have started a build on another box to see if this problem is l
On 03/15/2011 02:51 PM, Lukas Fleischer wrote:
Well, this is probably related to FS#23271, isn't it? [1]
[1]https://bugs.archlinux.org/task/23271
Right you are - my bad. This looks like what I saw, except I had a few more
packages. I'll add that info.
--
David C. Rankin, J.D.,P.E.
On Tue, Mar 15, 2011 at 02:44:25PM -0500, David C. Rankin wrote:
> On 03/15/2011 02:25 PM, David C. Rankin wrote:
> >On 03/15/2011 01:42 PM, Cédric Girard wrote:
> >>The useful thing to do in that case is to run a "pkgfile -s" (provided by
> >>pkgtools) on those files to see which package own them.
On 03/15/2011 02:24 PM, David C. Rankin wrote:
After the latest xorg updates, PKGBUILD scripts that include depends=('xorg')
are triggering complete reinstalls of all xorg packages.
I have started a build on another box to see if this problem is limited to the
same box that had the xorg upd
On 03/15/2011 02:25 PM, David C. Rankin wrote:
On 03/15/2011 01:42 PM, Cédric Girard wrote:
The useful thing to do in that case is to run a "pkgfile -s" (provided by
pkgtools) on those files to see which package own them.
Regards,
(smacks self)
Thanks Cédric,
I have a bunch more boxes to up
On 03/15/2011 01:42 PM, Cédric Girard wrote:
The useful thing to do in that case is to run a "pkgfile -s" (provided by
pkgtools) on those files to see which package own them.
Regards,
(smacks self)
Thanks Cédric,
I have a bunch more boxes to update, so I'll get the information and report
Guys,
After the latest xorg updates, PKGBUILD scripts that include depends=('xorg')
are triggering complete reinstalls of all xorg packages. This didn't happen
before. When trying to build trinity with the following depends= line:
depends=('python2-sip'
'libical'
'libxslt'
On Tue, Mar 15, 2011 at 8:19 PM, Heiko Baums wrote:
> Am Tue, 15 Mar 2011 19:42:37 +0100
> schrieb Cédric Girard :
>
> > The useful thing to do in that case is to run a "pkgfile
> > -s" (provided by pkgtools) on those files to see which package own
> > them.
>
> Or a "pacman -Qo". ;-)
>
> Heiko
>
Am Tue, 15 Mar 2011 19:42:37 +0100
schrieb Cédric Girard :
> The useful thing to do in that case is to run a "pkgfile
> -s" (provided by pkgtools) on those files to see which package own
> them.
Or a "pacman -Qo". ;-)
Heiko
Hi,
On Tue, Mar 15, 2011 at 7:37 PM, David C. Rankin <
drankina...@suddenlinkmail.com> wrote:
> Guys,
>
> Updating xorg resulted in pacman finding the following conflicts:
>
> [SKIP]
>
The useful thing to do in that case is to run a "pkgfile -s" (provided by
pkgtools) on those files to see whic
Guys,
Updating xorg resulted in pacman finding the following conflicts:
(87/87) checking for file conflicts
[###] 100%
error: failed to commit transaction (conflicting files)
xorg-bdftopcf: /usr/bin/bdftopcf exists in filesystem
xorg-bdftopcf: /usr/share/m
19 matches
Mail list logo
