[bug-notifications] [pkgutil 0004317]: Behavior with noncsw=true packages on local mirror inconsistent with regular behavior

[Mantis Bug Tracker]

The following issue requires your FEEDBACK. 
====================================================================== 
http://www.opencsw.org/mantis/view.php?id=4317 
====================================================================== 
Reported By:                skayser
Assigned To:                bonivart
====================================================================== 
Project:                    pkgutil
Issue ID:                   4317
Category:                   regular use
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             2010-03-02 15:02 CET
Last Modified:              2010-03-02 16:20 CET
====================================================================== 
Summary:                    Behavior with noncsw=true packages on local mirror
inconsistent with regular behavior
Description: 
Within our company we are using pkgutil configured against the current/ CSW
branch as well as an in-house package repository. Just tried to upgrade a
package from the in-house repo, but pkgutil didn't consider it as an update
candidate although there is an updated package available (different
version, same REV).

root @ ray42 ~# pkgutil -c --single fvwm_dtlogin
CONfvwmdtlogin            0.03,REV=2010.03.02       0.04,REV=2010.03.02   
  
root @ ray42 ~# pkgutil -Ni fvwm_dtlogin
Parsing catalog, may take a while...
CURRENT packages: CONfvwmdtlogin-0.03,REV=2010.03.02

Nothing to do.


According to what you said, noncsw seems to be a patched in feature that's
not properly integrated in the overall pkgutil architecture. Would be very
helpful if it was :) Here is the excerpt from our IRC conversation WRT to
that issue

14:35 <@skayser> bonivart: ping. got a funny pkgutil behavior :)
14:35 < bonivart> skayser, shoot
14:37 <@skayser> here goes: http://pastebin.com/kXH0VY8u
14:37 <@skayser> doesn't upgrade a package from 0.03 to 0.04
14:37 <@skayser> bonivart: that's with noncsw=true packages
14:37 <@skayser> in case it matters
14:38 <@skayser> let me know if you need pkgutil -D output
14:39 < bonivart> do you have current plus your own mirror?
14:39 <@skayser> indeed i do
14:40 < bonivart> i guess it's a bug with noncsw, i was always skeptical
of it but 
                  several people wanted it and offered patches for it but
there's 
                  no real concept of it
14:41 < bonivart> there may be situations all over where it makes a
difference :-(
14:41 < bonivart> could you file a bug please?
14:41 <@skayser> will do, thank you
14:42 < bonivart> what happens if you specify
CONfvwmdtlogin-0.04,REV=2010.03.02 as 
                  package to install? will it be ignored?
14:43  * skayser tries
14:44 <@skayser> "Nothing to do"
14:44 < bonivart> yes, but does it say that 0.03 is current or what?
14:45 <@skayser> bonivart: yes it does CURRENT packages: 
                 CONfvwmdtlogin-0.03,REV=2010.03.02

====================================================================== 

---------------------------------------------------------------------- 
 (0007565) bonivart (manager) - 2010-03-02 16:20
 http://www.opencsw.org/mantis/view.php?id=4317#c7565 
---------------------------------------------------------------------- 
I missed that the REV-field is the same for both packages. Note that -c
isn't really "upgradeable" packages, it's more "packages that are different
in one way or another".

To trigger an update the REV-field must be "greater". See
http://pkgutil.wikidot.com/get-install-and-configure#toc8 for the rules
used to compare package versions.

Also note that more than YYYY.MM.DD is allowed so you can force an upgrade
not only with a newer date but also with, e.g., 2010.03.02.1 if you don't
like faking future dates. Or insert HH.MM if you like, 2010.03.02.16.20.