On Sun, Dec 08, 2013 at 09:43:33AM +1100, Craig Small wrote: > Hi, > procps 3.3.9 which contains the new pidof has been released upstream. > This will mean that it will shortly disappear from sysvinit I guess. > > I can see that 2.88dsf-43 is the current version. Is this the one > I should be targeting for the Breaks: line? > > I suspect that it will go something like > procps-base 3.3.9-1 releases with Breaks: sysvinit-utils <= 2.88dsf-43 > It will also be Essential: Yes > sysvinit-utils 2.88dsf-44 comes out with no pidof > > Does that make sense? I'd like to get this done the next few days.
That sounds fine, I think. So on the sysvinit-utils side, we simply drop pidof? Will procps-base be guaranteed to be installed via upgrade? I imagine we'll have to also have a depends on procps-base >= 3.3.9-1 to ensure pidof is available at all times during the upgrade? To ensure proper upgrade ordering, should the procps-base Breaks also be a Conflicts? (I mean, we want to avoid a window where any other packages/maintainer scripts need to use pidof but sysvinit-utils is upgraded but the new procps-base is not yet unpacked) Just to double-check: the new pidof is completely compatible with the old? Thanks, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linux http://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `- GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 _______________________________________________ Pkg-sysvinit-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-sysvinit-devel
