On Tue, 2010-01-12 at 21:06 -0600, Dan McGee wrote:
> On Tue, Jan 12, 2010 at 8:55 PM, Jim Pryor
> wrote:
> > On Tue, Jan 12, 2010 at 08:41:47PM -0600, Dan McGee wrote:
> >> > Very nice. When did you guys do that?
> >>
> >> Forever? It is in the initial git import from 2005, which is the
> >> begi
On Tue, Jan 12, 2010 at 8:55 PM, Jim Pryor
wrote:
> On Tue, Jan 12, 2010 at 08:41:47PM -0600, Dan McGee wrote:
>> > Very nice. When did you guys do that?
>>
>> Forever? It is in the initial git import from 2005, which is the
>> beginnings of pacman 3.X:
>> http://projects.archlinux.org/pacman.git/
On Tue, Jan 12, 2010 at 08:41:47PM -0600, Dan McGee wrote:
> > Very nice. When did you guys do that?
>
> Forever? It is in the initial git import from 2005, which is the
> beginnings of pacman 3.X:
> http://projects.archlinux.org/pacman.git/tree/src/pacman/package.c?id=d04ba#n85
Just shows: read
On Tue, Jan 12, 2010 at 6:50 PM, Jim Pryor
wrote:
> On Tue, Jan 12, 2010 at 05:50:47PM -0600, Aaron Griffin wrote:
>> On Tue, Jan 12, 2010 at 5:43 PM, Thomas Bächler wrote:
>> > pacman -Qii is your friend.
>>
>> This.
>> pacman -Qii dcron will show you all the backup files that pacman will
>> tak
On Tue, Jan 12, 2010 at 05:50:47PM -0600, Aaron Griffin wrote:
> On Tue, Jan 12, 2010 at 5:43 PM, Thomas Bächler wrote:
> > pacman -Qii is your friend.
>
> This.
> pacman -Qii dcron will show you all the backup files that pacman will
> take care of.
Very nice. When did you guys do that?
On Tue
On Tue, Jan 12, 2010 at 5:47 PM, Jim Pryor
wrote:
> I know, I've been bitten too. I highly recommend setting up a script to
> backup your /etc directory daily, and keep at least a week or so of
> rotated backups. If you've got a good backup system, you can just
> include this in it. If not, you sh
On Tue, Jan 12, 2010 at 5:43 PM, Thomas Bächler wrote:
> Am 13.01.2010 00:34, schrieb Dimitrios Apostolou:
>> Since I've been bitten by this, how can I know if the file I modified is
>> goint to be overwritten or not, *before* it actually happens? And even
>> if it is, a .pacsave wouldn't hurt any
On Wed, Jan 13, 2010 at 01:34:52AM +0200, Dimitrios Apostolou wrote:
>
> Since I've been bitten by this, how can I know if the file I
> modified is goint to be overwritten or not, *before* it actually
> happens?
pacman -Qo $file
will tell you what package installed $file.
find /var/abs
Am 13.01.2010 00:34, schrieb Dimitrios Apostolou:
> Since I've been bitten by this, how can I know if the file I modified is
> goint to be overwritten or not, *before* it actually happens? And even
> if it is, a .pacsave wouldn't hurt anyone, if I remember correctly (it's
> been some time) I had co
On Wed, Jan 13, 2010 at 12:34 AM, Dimitrios Apostolou wrote:
> On Mon, 11 Jan 2010, Aaron Griffin wrote:
>>
>> If you modify it, you should add it to the NoUpgrade line in
>> /etc/pacman.conf. The backup array is for what we INTEND to be
>> modified. Users are more than welcome to do what we don't
On Mon, 11 Jan 2010, Aaron Griffin wrote:
If you modify it, you should add it to the NoUpgrade line in
/etc/pacman.conf. The backup array is for what we INTEND to be
modified. Users are more than welcome to do what we don't intend, but
you need to control whether of not pacman mucks with those f
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
I'm fairly new to the Arch Linux scene so am still learning a lot
about package building and maintenance. Left over from my Slackware
days gone by, Iknow well the importance of the rc.d scripts and how
they work. For local stuff, there's rc.loca
On Mon, Jan 11, 2010 at 4:38 PM, Thomas Bächler wrote:
> Am 11.01.2010 19:38, schrieb Aaron Griffin:
>> If you modify it, you should add it to the NoUpgrade line in
>> /etc/pacman.conf. The backup array is for what we INTEND to be
>> modified. Users are more than welcome to do what we don't intend
Am 11.01.2010 19:38, schrieb Aaron Griffin:
> If you modify it, you should add it to the NoUpgrade line in
> /etc/pacman.conf. The backup array is for what we INTEND to be
> modified. Users are more than welcome to do what we don't intend, but
> you need to control whether of not pacman mucks with
On Mon 11 Jan 2010 13:54 -0500, Daenyth Blank wrote:
> On Mon, Jan 11, 2010 at 13:38, Aaron Griffin wrote:
> > If you modify it, you should add it to the NoUpgrade line in
> > /etc/pacman.conf. The backup array is for what we INTEND to be
> > modified. Users are more than welcome to do what we don
On Mon, Jan 11, 2010 at 13:38, Aaron Griffin wrote:
> If you modify it, you should add it to the NoUpgrade line in
> /etc/pacman.conf. The backup array is for what we INTEND to be
> modified. Users are more than welcome to do what we don't intend, but
> you need to control whether of not pacman mu
On Mon, Jan 11, 2010 at 12:16 PM, Jim Pryor
wrote:
> On Mon, Jan 11, 2010 at 11:36:55AM -0500, Eric Bélanger wrote:
>> On Mon, Jan 11, 2010 at 8:06 AM, Paul Mattal wrote:
>> > On 01/06/2010 01:09 AM, Paul Mattal wrote:
>> > I've just placed dcron 4.2 into [testing]. This is a major update to dcro
On Mon, Jan 11, 2010 at 11:36:55AM -0500, Eric Bélanger wrote:
> On Mon, Jan 11, 2010 at 8:06 AM, Paul Mattal wrote:
> > On 01/06/2010 01:09 AM, Paul Mattal wrote:
> > I've just placed dcron 4.2 into [testing]. This is a major update to dcron,
> > under a new maintainer (who is an Arch user, and v
18 matches
Mail list logo
