To recap, there was some discussion about whether a versioned
Pre-Depends on dpkg-maintscript-helper [dpkg (= 1.15.7.2)] is a good
idea for packages in wheezy, with no definite conclusion.
The main complication was such Pre-Depends are not needed for
squeezy-to-wheezy upgrades. Still I believe
Raphael Hertzog writes (Re: Pre-Depends: dpkg (= 1.15.7.2) for
dpkg-maintscript-helper okay?):
Of course, the pre-depends become mostly irrelevant when the version in
oldstable supports it but that's not the case yet. And it's not unusual for
people to try an upgrade that skips a release
On Sun, Mar 6, 2011 at 20:55, Steve Langasek vor...@debian.org wrote:
What apt, aptitude do:
I don't know. Do they allow an already satisfied Pre-Depends to
complicate the upgrade path? IIRC dpkg, as an essential package,
always gets upgraded first anyway, but I am not so familiar
[Dropping the bug cc: again, I don't think that has anything to do with this
question]
On Sat, Mar 05, 2011 at 06:26:27PM -0600, Jonathan Nieder wrote:
So in this case the pre-dependency
should *not* be set, as it only serves to complicate the upgrade path.
I think this example might
On Sat, 5 Mar 2011, Steve Langasek wrote:
For packages in wheezy/sid, it's redundant because the versioned dependency
is already satisfied by the version of dpkg in squeeze, i.e., it's met even
before upgrading to wheezy or sid.
I note that it’s potentially still relevant for the future Ubuntu
Hi,
On Mon, 07 Mar 2011, Anders Kaseorg wrote:
So in this case the pre-dependency should *not* be set, as it only
serves to complicate the upgrade path.
If this becomes the consensus of debian-devel, there are two things that
should probably be changed:
• The section of the
Am 07.03.2011 07:53, schrieb Anders Kaseorg:
On Sat, 5 Mar 2011, Steve Langasek wrote:
For packages in wheezy/sid, it's redundant because the versioned dependency
is already satisfied by the version of dpkg in squeeze, i.e., it's met even
before upgrading to wheezy or sid.
I note that it’s
On Mon, Mar 07, 2011 at 01:53:22AM -0500, Anders Kaseorg wrote:
On Sat, 5 Mar 2011, Steve Langasek wrote:
For packages in wheezy/sid, it's redundant because the versioned dependency
is already satisfied by the version of dpkg in squeeze, i.e., it's met even
before upgrading to wheezy or
According to dpkg-maintscript-helper(1), “using it unconditionally
requires a pre-dependency to ensure that the required version of dpkg has
been unpacked before. The required version depends on the command used,
for rm_conffile and mv_conffile it is 1.15.7.2:
Pre-Depends: dpkg (=
Hi there,
On Sat, Mar 05, 2011 at 04:05:07AM -0500, Anders Kaseorg wrote:
According to dpkg-maintscript-helper(1), “using it unconditionally
requires a pre-dependency to ensure that the required version of dpkg has
been unpacked before. The required version depends on the command used,
Anders Kaseorg ande...@mit.edu wrote on 2011-03-05 04:05:
I see 4 packages currently in squeeze that declare ‘Pre-Depends: dpkg (=
1.15.7.2)’ (cron e16-data ntp ntpdate) and 9 in sid (apticron ccal cron
lilo midori mozplugger ntp ntpdate usb-modeswitch), but I can’t find any
discussion
Hi,
Steve Langasek wrote:
So in this case the pre-dependency
should *not* be set, as it only serves to complicate the upgrade path.
I think this example might deserve a closer look. Documentating the
required dpkg version seems useful for backporters and others who
would use the package in
12 matches
Mail list logo
