Bug#379150: Documentation for Breaks in dpkg

[Russ Allbery]

Russ Allbery <[EMAIL PROTECTED]> writes:

> Here is an updated patch.  The changes from Ian's original patch are:
>
>  * Add a statement saying that Breaks should not be used until support is
>present in Debian stable, which I think was the consensus of recent
>discussion on the policy list, and also note this near the mention of
>Breaks in the Conflicts section.
>
>  * Just remove the entire paragraph about suidmanager from the
>dpkg-statoverride section rather than changing it to use Breaks.
>suidmanager predates oldstable at this point; I don't think there's any
>reason to mention it ever existed at this point.

I have applied this version of the patch to my Policy arch repository.

-- 
Russ Allbery ([EMAIL PROTECTED])   



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#379150: Documentation for Breaks in dpkg

[Guillem Jover]

Hi,

On Tue, 2008-01-01 at 13:46:58 -0800, Russ Allbery wrote:
> Ian Jackson <[EMAIL PROTECTED]> writes:
> > Package: debian-policy
> > Version: 3.7.2.1
> > Severity: wishlist
> > Tags: patch
> >
> > As I report in #379140 (against dpkg), I have implemented Breaks in
> > dpkg.  The attached patch is the corresponding change to the manual.
> >
> > It would probably not be wise to apply this patch until we have
> > settled on a deployment plan for Breaks in Debian; as I say in
> > #379140, I hope to get around to that this weekend.
> 
> Here is an updated patch.  The changes from Ian's original patch are:
> 
>  * Add a statement saying that Breaks should not be used until support is
>present in Debian stable, which I think was the consensus of recent
>discussion on the policy list, and also note this near the mention of
>Breaks in the Conflicts section.
> 
>  * Just remove the entire paragraph about suidmanager from the
>dpkg-statoverride section rather than changing it to use Breaks.
>suidmanager predates oldstable at this point; I don't think there's any
>reason to mention it ever existed at this point.
> 
> dpkg folks, could you please review this patch as a final double-check
> that it matches the dpkg implementation as was committed and released?  I
> want to be sure that nothing changed from the original patch so that we
> don't document the wrong thing in Policy.

The patch seems fine.

regards,
guillem



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#379150: Documentation for Breaks in dpkg

[Russ Allbery]

Ian Jackson <[EMAIL PROTECTED]> writes:

> Package: debian-policy
> Version: 3.7.2.1
> Severity: wishlist
> Tags: patch
>
> As I report in #379140 (against dpkg), I have implemented Breaks in
> dpkg.  The attached patch is the corresponding change to the manual.
>
> It would probably not be wise to apply this patch until we have
> settled on a deployment plan for Breaks in Debian; as I say in
> #379140, I hope to get around to that this weekend.

Here is an updated patch.  The changes from Ian's original patch are:

 * Add a statement saying that Breaks should not be used until support is
   present in Debian stable, which I think was the consensus of recent
   discussion on the policy list, and also note this near the mention of
   Breaks in the Conflicts section.

 * Just remove the entire paragraph about suidmanager from the
   dpkg-statoverride section rather than changing it to use Breaks.
   suidmanager predates oldstable at this point; I don't think there's any
   reason to mention it ever existed at this point.

dpkg folks, could you please review this patch as a final double-check
that it matches the dpkg implementation as was committed and released?  I
want to be sure that nothing changed from the original patch so that we
don't document the wrong thing in Policy.

Other policy readers, comments or seconds?

--- orig/policy.sgml
+++ mod/policy.sgml
@@ -2545,7 +2545,8 @@

  Package interrelationship fields:
Depends, Pre-Depends,
-   Recommends, Suggests, Conflicts,
+   Recommends, Suggests,
+   Breaks, Conflicts,
Provides, Replaces, Enhances
  
 
@@ -3336,8 +3337,8 @@
deconfigured's-postinst
abort-deconfigure in-favour
failed-install-package version
-   removing conflicting-package
-   version
+   [removing conflicting-package
+   version]

  
 
@@ -3362,9 +3363,9 @@

deconfigured's-prerm deconfigure
in-favour package-being-installed
-   version removing
+   version [removing
conflicting-package
-   version
+   version]

  
 
@@ -3445,11 +3446,30 @@

 

-   If a "conflicting" package is being removed at the same time:
+   If a "conflicting" package is being removed at the same time,
+   or if any package will be broken (due to Breaks):

  
- If any packages depended on that conflicting
- package and --auto-deconfigure is
+ If --auto-deconfigure is
+ specified, call, for each package to be deconfigured
+ due to Breaks:
+ 
+deconfigured's-prerm deconfigure \
+  in-favour package-being-installed version
+ 
+ Error unwind:
+ 
+deconfigured's-postinst abort-deconfigure \
+  in-favour package-being-installed-but-failed version
+ 
+ The deconfigured packages are marked as
+ requiring configuration, so that if
+ --install is used they will be
+ configured again if possible.
+ 
+ 
+ If any packages depended on a conflicting
+ package being removed and --auto-deconfigure is
  specified, call, for each such package:
  
 deconfigured's-prerm deconfigure \
@@ -3468,7 +3488,7 @@
  configured again if possible.
  
  
- To prepare for removal of the conflicting package, call:
+ To prepare for removal of each conflicting package, call:
  
 conflictor's-prerm remove \
   in-favour package new-version
@@ -3962,16 +3982,19 @@
 
 
   This is done using the Depends, Pre-Depends,
-  Recommends, Suggests, Enhances and
-  Conflicts control file fields.
+  Recommends, Suggests, Enhances,
+  Breaks and Conflicts control file fields.
 
 

- These six fields are used to declare a dependency
+ These seven fields are used to declare a dependency
  relationship by one package on another.  Except for
- Enhances, they appear in the depending (binary)
- package's control file.  (Enhances appears in the
- recommending package's control file.)
+ Enhances and Breaks, they appear in the
+ depending (binary) package's control file.
+ (Enhances appears in the recommending package's
+ control file, and Breaks appears in the version of
+ depended-on package which causes the named package to
+

Bug#379150: Documentation for Breaks in dpkg

[Ian Jackson]

Package: debian-policy
Version: 3.7.2.1
Severity: wishlist
Tags: patch

As I report in #379140 (against dpkg), I have implemented Breaks in
dpkg.  The attached patch is the corresponding change to the manual.

It would probably not be wise to apply this patch until we have
settled on a deployment plan for Breaks in Debian; as I say in
#379140, I hope to get around to that this weekend.

Regards,
Ian.

diff -ru orig/debian-policy-3.7.2.1/debian/changelog 
debian-policy-3.7.2.1/debian/changelog
--- orig/debian-policy-3.7.2.1/debian/changelog 2006-06-20 06:20:13.0 
+0100
+++ debian-policy-3.7.2.1/debian/changelog  2006-07-21 18:58:36.0 
+0100
@@ -1,3 +1,9 @@
+debian-policy (3.7.2.1-0iwj1) unstable; urgency=low
+
+  * Document new `Breaks' dependency field.
+
+ -- Ian Jackson <[EMAIL PROTECTED]>  Fri, 21 Jul 2006 18:58:32 +0100
+
 debian-policy (3.7.2.1) unstable; urgency=low
 
   * Bug fix: "debian-policy: s/control are/&a/; s/stats/status/;
Only in debian-policy-3.7.2.1/debian: changelog~
diff -ru orig/debian-policy-3.7.2.1/policy.sgml 
debian-policy-3.7.2.1/policy.sgml
--- orig/debian-policy-3.7.2.1/policy.sgml  2006-06-20 06:20:13.0 
+0100
+++ debian-policy-3.7.2.1/policy.sgml   2006-07-21 18:56:52.0 +0100
@@ -2546,7 +2546,8 @@

  Package interrelationship fields:
Depends, Pre-Depends,
-   Recommends, Suggests, Conflicts,
+   Recommends, Suggests,
+Breaks, Conflicts,
Provides, Replaces, Enhances
  
 
@@ -3319,8 +3320,8 @@
deconfigured's-postinst
abort-deconfigure in-favour
failed-install-package version
-   removing conflicting-package
-   version
+   [removing conflicting-package
+   version]

  
 
@@ -3345,9 +3346,9 @@

deconfigured's-prerm deconfigure
in-favour package-being-installed
-   version removing
+   version [removing
conflicting-package
-   version
+   version]

  
 
@@ -3428,11 +3429,30 @@

 

-   If a "conflicting" package is being removed at the same time:
+   If a "conflicting" package is being removed at the same time,
+or if any package will be broken (due to Breaks):

  
- If any packages depended on that conflicting
- package and --auto-deconfigure is
+ If --auto-deconfigure is
+ specified, call, for each package to be deconfigured
+  due to Breaks:
+ 
+deconfigured's-prerm deconfigure \
+  in-favour package-being-installed version
+ 
+ Error unwind:
+ 
+deconfigured's-postinst abort-deconfigure \
+  in-favour package-being-installed-but-failed version
+ 
+ The deconfigured packages are marked as
+ requiring configuration, so that if
+ --install is used they will be
+ configured again if possible.
+ 
+ 
+ If any packages depended on a conflicting
+ package being removed and --auto-deconfigure is
  specified, call, for each such package:
  
 deconfigured's-prerm deconfigure \
@@ -3451,7 +3471,7 @@
  configured again if possible.
  
  
- To prepare for removal of the conflicting package, call:
+ To prepare for removal of each conflicting package, call:
  
 conflictor's-prerm remove \
   in-favour package new-version
@@ -3945,16 +3965,19 @@
 
 
   This is done using the Depends, Pre-Depends,
-  Recommends, Suggests, Enhances and
-  Conflicts control file fields.
+  Recommends, Suggests, Enhances,
+  Breaks and Conflicts control file fields.
 
 

- These six fields are used to declare a dependency
+ These seven fields are used to declare a dependency
  relationship by one package on another.  Except for
- Enhances, they appear in the depending (binary)
- package's control file.  (Enhances appears in the
- recommending package's control file.)
+ Enhances and Breaks, they appear in the
+ depending (binary) package's control file.
+ (Enhances appears in the recommending package's
+ control file, and Breaks appears in the version of
+ depended-on package which causes the named package to
+ break).

 

@@ -3991,7 +4014,7 @@
   point, and some packages may not be able to re