On 09/25/12 at 08:16pm, Karol Blazewicz wrote:

On Tue, Sep 25, 2012 at 8:09 PM, Manolo Martínez wrote:

...

Would it be possible/make sense to have pacman inform us whenever it is going to substitute a package that has been ABS'd?

Why not put your tweaked packages in 'IgnorePkg' in pacman.conf?

Many times these tweaks are temporary and, indeed, newer versions make them unnecessary. It can definitely be done as you suggest, but I think it'd be in the spirit of the help provided by, e.g., .pacsave and .pacnew files, to have pacman issue a warning. --

On Wed, Sep 26, 2012 at 3:48 AM, Zeke Sulastin wrote:

...

Many times these tweaks are temporary and, indeed, newer versions make them unnecessary. It can definitely be done as you suggest, but I think it'd be in the spirit of the help provided by, e.g., .pacsave and .pacnew files, to have pacman issue a warning. --

Pacman doesn't really have a way of looking at an installed package and knowing that it's been modified from the default repo package (as far as I know ...). Absent a new patch to add such functionality, Karol's suggestion of IgnorePkg is the best idea and also provides the warning you seek when performing a full update, in the form of

Well, anything that's been locally built should have you set as the package maintainer, so the first sentence is not really true. Not that this fact by itself is particularly useful, lacking the necessary changes to pacman.

On Tue, Sep 25, 2012 at 02:34:37PM -0400, Manolo Martínez wrote:

On 09/25/12 at 08:16pm, Karol Blazewicz wrote:

...

On Tue, Sep 25, 2012 at 8:09 PM, Manolo Martínez wrote:

...

Would it be possible/make sense to have pacman inform us whenever it is going to substitute a package that has been ABS'd?

Why not put your tweaked packages in 'IgnorePkg' in pacman.conf?

Many times these tweaks are temporary and, indeed, newer versions make them unnecessary. It can definitely be done as you suggest, but I think it'd be in the spirit of the help provided by, e.g., .pacsave and .pacnew files, to have pacman issue a warning. --

Patches to pacman are always welcome -- Daniel Wallace Archlinux Trusted User (gtmanfred) Georgia Institute of Technology

Thanks everyone for the illuminating responses. IgnorePackage and IgnoreGroup seem to be what I need, after all. Cheers, Manolo On 09/26/12 at 09:10am, gt wrote:

On Tue, Sep 25, 2012 at 02:09:59PM -0400, Manolo Martínez wrote:

...

Hello,

I've just had a minor hiccup, because one of the packages updated in my pacman -Syu this morning substituted a version I had tweaked the ABS way.

Nothing serious, as I say, and wholly my fault, but yet I was wondering: Would it be possible/make sense to have pacman inform us whenever it is going to substitute a package that has been ABS'd?

I put my local packages under a group "custom_packages" and add IgnoreGroup = custom_packages in pacman.conf

Whenever there's an update available, pacman notifies me as others have mentioned.

Then I go to the arch git repo for the package, see the changes and decide if i need to add those changes to my package.

For example yesterday mutt was updated due to a bug, but since that bug doesn't affect me, i didn't upgrade my custom mutt package.

--