[pacman-dev] RC 2007.02.16

Dan McGee dpmcgee at gmail.com
Fri Feb 16 16:41:04 EST 2007

On 2/16/07, Aaron Griffin <aaronmgriffin at gmail.com> wrote:
> On 2/16/07, Dan McGee <dpmcgee at gmail.com> wrote:
> > I think lines 632-696 could use a careful look over in
> > lib/libalpm/add.c. Aaron, your change in revision 1.98 to line 656 ( }
> > else if(md5_orig || sha1_pkg) { ) seems a bit contradictory- shouldn't
> > they either both be orig, or both be pkg?
> You're probably right, it may have been a "lets see if this works,
> can't test sha1 right now, so I'll only change md5"... I'll peek at
> it.

I'll throw some of my test results out here for this whole possible
bug. I manually edited one of the backup md5sums in the pacman DB and
updated a package, and was able to get a pacnew notice. You only get
this notice if the file has changed between package versions, so I
simulated this manually by modifying the md5sum. This doesn't get me
any closer to determining why my pacman3.conf was overwritten,
however. I have a suspicion it might have to do with uninstalling a
package completely and then reinstalling, but I'm not sure.


More information about the pacman-dev mailing list