On 02/14/2010 08:12 AM, Samuel Baldwin wrote:
Worked like a charm, thanks guys. I guess it's a good thing that
pacman won't touch my data; not what I was expecting, though, but I
much prefer pacman's current behaviour.
Its not a guess. Its the design, a feature!
Its like saying, "If you don't
Worked like a charm, thanks guys. I guess it's a good thing that
pacman won't touch my data; not what I was expecting, though, but I
much prefer pacman's current behaviour.
--
Samuel Baldwin - logik.li
On 02/14/2010 06:17 AM, Samuel Baldwin wrote:
Howdy.
I fucked up an old mysql install and I want to start completely over,
but pacman -R mysql (even with --nosave) doesn't remove everything;
I'm still unable to run '/usr/bin/mysql_secure_installation' after
reinstalling mysql; it fails setting t
Samuel Baldwin escribió:
> Howdy.
>
> I fucked up an old mysql install and I want to start completely over,
> but pacman -R mysql (even with --nosave) doesn't remove everything;
> I'm still unable to run '/usr/bin/mysql_secure_installation' after
> reinstalling mysql; it fails setting the new passw
On Sat, Feb 13, 2010 at 20:50, gt wrote:
> Did you try the --debug switch for pacman. See what information it shows.
>
You want pacman -Rscn to "nuke" it. You'll have to manually remove the
databases, pacman isn't going to touch your data, nor should it.
On Sun, Feb 14, 2010 at 6:17 AM, Samuel Baldwin
wrote:
> Howdy.
>
> I fucked up an old mysql install and I want to start completely over,
> but pacman -R mysql (even with --nosave) doesn't remove everything;
> I'm still unable to run '/usr/bin/mysql_secure_installation' after
> reinstalling mysql;
Howdy.
I fucked up an old mysql install and I want to start completely over,
but pacman -R mysql (even with --nosave) doesn't remove everything;
I'm still unable to run '/usr/bin/mysql_secure_installation' after
reinstalling mysql; it fails setting the new password. Any way to
completely obliterat
On 02/13/2010 10:20 AM, Steve Holmes wrote:
> Yeah for the past 12 hours or more, I have about 6 packages that won't
> update/download. They are all the gstreamer packages and vim from
> extra. Because of those failed downloads, none of my other updates
> would occur automatically. I had to appl
On Sat, 13 Feb 2010 16:10:08 -0600
Muhammed Uluyol wrote:
> On Sat, Feb 13, 2010 at 4:05 PM, Dieter Plaetinck
> wrote:
> >
> > what do you mean context? it only depends on whether the first
> > character after the variablename is a valid character in a
> > variablename or not. if it's valid, us
On Sat, Feb 13, 2010 at 4:05 PM, Dieter Plaetinck wrote:
>
> what do you mean context? it only depends on whether the first
> character after the variablename is a valid character in a variablename
> or not. if it's valid, use braces. if it isn't, no need for braces.
Arrays can't be used with $a
Am 13.02.2010 22:13, schrieb Dieter Plaetinck:
>> If you use braces only when necessary, it will not be consistent - you
>> have braces sometimes and other times you don't. I thought coding
>> style was about consistency.
>>
>
> you can apply "only when needed" consistently.
This is very unintuit
On 13/02/2010 11:11 μμ, Thomas Bächler wrote:
Am 13.02.2010 21:57, schrieb Dieter Plaetinck:
For example, in a PKGBUILD I would write ${pkgname}_$pkgver,
because _ can be part of a variable name, but I'd much rather
prefer to use $pkgname-$pkgver, since hyphens are not allowed in
variable names.
On Sat, 13 Feb 2010 22:11:01 +0100
Thomas Bächler wrote:
> Am 13.02.2010 21:57, schrieb Dieter Plaetinck:
> >>> For example, in a PKGBUILD I would write ${pkgname}_$pkgver,
> >>> because _ can be part of a variable name, but I'd much rather
> >>> prefer to use $pkgname-$pkgver, since hyphens are
Am 13.02.2010 21:57, schrieb Dieter Plaetinck:
>>> For example, in a PKGBUILD I would write ${pkgname}_$pkgver,
>>> because _ can be part of a variable name, but I'd much rather
>>> prefer to use $pkgname-$pkgver, since hyphens are not allowed in
>>> variable names.
>>>
>>> Less typing, less ugline
On Sat, 13 Feb 2010 15:16:01 -0500
Daenyth Blank wrote:
> On Sat, Feb 13, 2010 at 15:12, Evangelos Foutras
> wrote:
> > For example, in a PKGBUILD I would write ${pkgname}_$pkgver,
> > because _ can be part of a variable name, but I'd much rather
> > prefer to use $pkgname-$pkgver, since hyphens
Am 13.02.2010 17:41, schrieb Thomas Bächler:
Am 01.02.2010 18:27, schrieb Daniel Isenmann:
Hi,
this is a small fix for the bug reported here:
http://bbs.archlinux.org/viewtopic.php?pid=699763
Now, you have to set explicit the plugin path to the kernel mode
plugin if you want to use it. So, it'
On Sat, Feb 13, 2010 at 15:12, Evangelos Foutras wrote:
> For example, in a PKGBUILD I would write ${pkgname}_$pkgver, because _ can
> be part of a variable name, but I'd much rather prefer to use
> $pkgname-$pkgver, since hyphens are not allowed in variable names.
>
> Less typing, less ugliness.
On 13/02/2010 08:57 μμ, Thomas Bächler wrote:
Never use `...`, always $(...), always use the braces for variable names
and always quote paths that contain variables.
I do not agree with your view that braces should always be used around
variable names. While I would like to read any justificat
Beautiful, thanks.
--
Samuel Baldwin - logik.li
On Sat, Feb 13, 2010 at 10:51 PM, Samuel Baldwin wrote:
> I'm trying to update my system with 'pacman -Syu', but doing so
> discovers a conflict with phonon; phonon conflicts with qt, but
> kdelibs apparently needs both. What should I do? Trying to install
> phonon by hand requires uninstalling q
I'm trying to update my system with 'pacman -Syu', but doing so
discovers a conflict with phonon; phonon conflicts with qt, but
kdelibs apparently needs both. What should I do? Trying to install
phonon by hand requires uninstalling qt, but other packages depend on
it (including kdelibs).
arrakis^s
On Saturday 13 February 2010 22:11:51 Thomas Bächler wrote:
>
> I rebuilt rp-pppoe against ppp 2.4.5, because apparently the plugins
> break on update. This should be moved quickly, as rp-pppoe is currently
> broken in core. Please sign off.
Sign-off x86_64
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
Yeah for the past 12 hours or more, I have about 6 packages that won't
update/download. They are all the gstreamer packages and vim from
extra. Because of those failed downloads, none of my other updates
would occur automatically. I had to appl
Am 01.02.2010 18:27, schrieb Daniel Isenmann:
> Hi,
>
> this is a small fix for the bug reported here:
> http://bbs.archlinux.org/viewtopic.php?pid=699763
>
> Now, you have to set explicit the plugin path to the kernel mode
> plugin if you want to use it. So, it's up to you if you need it or
> no
2010/2/13 David Rosenstrauch
> On 02/12/2010 09:09 PM, ludovic coues wrote:
>
>> 2010/2/12 David Rosenstrauch
>>
>> So it looks like an annoying "feature" got added to a recent upgrade to
>>> KDE4. (Maybe in the recent 4.4 beta?)
>>>
>>> When using Konqueror as a file manager, apparently there'
On 13 February 2010 12:03, Gerardo Exequiel Pozzi
wrote:
> On 02/13/2010 12:57 AM, Allan McRae wrote:
>>
>>
>> ftp.archlinux.org is just a mirror like any other mirror.
>>
> Oh, Ok, sorry. I thought it was the master.
I think it goes like this:
commit > server (gerolde/sigurd) > mirrors
But acc
26 matches
Mail list logo
