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
On Wed, Jan 13, 2010 at 12:34 AM, Dimitrios Apostolou ji...@gmx.net 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
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
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
On Tue, Jan 12, 2010 at 5:43 PM, Thomas Bächler tho...@archlinux.org 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
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 tho...@archlinux.org 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
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 a
On Tue, Jan 12, 2010 at 8:55 PM, Jim Pryor
lists+arch-gene...@jimpryor.net 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:
On Tue, 2010-01-12 at 21:06 -0600, Dan McGee wrote:
On Tue, Jan 12, 2010 at 8:55 PM, Jim Pryor
lists+arch-gene...@jimpryor.net 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,
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 p...@mattal.com 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
On Mon, Jan 11, 2010 at 12:16 PM, Jim Pryor
lists+arch-gene...@jimpryor.net 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 p...@mattal.com wrote:
On 01/06/2010 01:09 AM, Paul Mattal wrote:
I've just placed dcron 4.2 into
On Mon, Jan 11, 2010 at 13:38, Aaron Griffin aaronmgrif...@gmail.com 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
On Mon 11 Jan 2010 13:54 -0500, Daenyth Blank wrote:
On Mon, Jan 11, 2010 at 13:38, Aaron Griffin aaronmgrif...@gmail.com 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
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, Jan 11, 2010 at 4:38 PM, Thomas Bächler tho...@archlinux.org 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
15 matches
Mail list logo
