On Thu, Jul 31, 2003 at 09:46:43AM +0200, Matthias Urlichs wrote:
> Hi, Jamin W. Collins wrote:
>
> > The old DB works fine after the upgrade against it. The questions
> > are. Whether removing the configuration files (/etc/moviemate) is a
> > taboo, even though the configuration is migrated (/e
On Thu, Jul 31, 2003 at 11:42:32AM +0200, Santiago Vila wrote:
> If you make the dummy package of extra priority and section: oldlibs,
> the package will be there only until the user runs deborphan to remove
> obsolete libraries.
Well oldlibs is for libraries, no? And debfoster can automatically f
On Wed, 30 Jul 2003, Jamin W. Collins wrote:
> I was thinking about the dummy package approach, but then the dummy
> package would just hang around indefinitely, right?
If you make the dummy package of extra priority and section: oldlibs,
the package will be there only until the user runs deborph
On Wed, Jul 30, 2003 at 08:47:53PM -0600, Jamin W. Collins wrote:
> I was thinking about the dummy package approach, but then the dummy
> package would just hang around indefinitely, right?
If the new package replaces all files in the dummy package, dpkg removes
it automatically. But cf. #202997.
Hi, Jamin W. Collins wrote:
> The old DB works fine after the upgrade against it. The questions are.
> Whether removing the configuration files (/etc/moviemate) is a taboo,
> even though the configuration is migrated (/etc/mediamate).
Leave it there. What if the user wants to downgrade?
--
Mat
This one time, at band camp, Sean 'Shaleh' Perry wrote:
>you should Conflict, Replace, and provide MovieMate. This will ensure a
>smooth transition. You instead (may) want to upload a package called
>moviemate which is a dummy package that depends on MediaMate.
You should do both, with the Con
"Jamin W. Collins" <[EMAIL PROTECTED]> writes:
> I was thinking about the dummy package approach, but then the dummy
> package would just hang around indefinitely, right?
Well, until the user removes it; the description usually hints at
that, and deborphan will also optionally point out dummy pac
Sean 'Shaleh' Perry <[EMAIL PROTECTED]> writes:
> you should Conflict, Replace, and provide MovieMate. This will ensure a
> smooth transition. You instead (may) want to upload a package called
> moviemate which is a dummy package that depends on MediaMate.
I'd say "as well as" rather than "in
On Wed, Jul 30, 2003 at 06:17:17PM -0700, Sean 'Shaleh' Perry wrote:
> you should Conflict, Replace, and provide MovieMate. This will ensure
> a smooth transition. You instead (may) want to upload a package
> called moviemate which is a dummy package that depends on MediaMate.
>
> Remember, if
On Wednesday 30 July 2003 15:56, Jamin W. Collins wrote:
>
> In building the new Media Mate package, I've declared a Conflicts with
> the moviemate package to effect moviemate's uninstall when the mediamate
> package is installed. However, this leaves the question of migrating
> the moviemate's co
What is the preferred method of effecting a package rename and upgrade
between versions?
Movie Mate v0.9.2 is currently in the Debian archive. Due to upstream
changes (added tracking for other media types), the name has been
changed to Media Mate.
Thus, Media Mate is the upgrade to Movie Mate.
11 matches
Mail list logo