Re: Debian Policy 4.6.0.0 released

[Jochen Sprickerhof]

* Sean Whitton  [2021-08-18 13:21]:

On Wed 18 Aug 2021 at 11:10AM +02, Aurelien Jarno wrote:


9.1.1
No package is allowed to install files in ``/usr/lib64/``. Previously,
this prohibition only applied to packages for 64-bit architectures.


This path is used by the multilib 64-bit toolchain on 32-bit
architectures, for instance libc6-amd64:i386, or a few essential
libraries like ncurses.

What kind of fix do you expect on the packages? Is it finally the time
to get rid of multilib and use pure multiarch instead?


We did not intend to make any packages buggy with this change.  It was
thought to be just a clarification.


Also with usrmerge libc6:amd64 will put a link in /usr/lib64/. Arguably 
this is covered in 3. but maybe should be considered.


Cheers Jochen


signature.asc
Description: PGP signature

Re: Debian Policy 4.6.0.0 released

[Russ Allbery]

Sean Whitton  writes:
> On Wed 18 Aug 2021 at 11:10AM +02, Aurelien Jarno wrote:

>> This path is used by the multilib 64-bit toolchain on 32-bit
>> architectures, for instance libc6-amd64:i386, or a few essential
>> libraries like ncurses.
>>
>> What kind of fix do you expect on the packages? Is it finally the time
>> to get rid of multilib and use pure multiarch instead?

> We did not intend to make any packages buggy with this change.  It was
> thought to be just a clarification.

> Russ, perhaps we should revert this?

Yes, that was a subtlety that I had completely failed to grasp and didn't
realize this was way the rule was worded the way it was.  Sorry for that
mistake; we should revert it.

If we separately want to drop this in favor of pure multiarch, that's
great and we can always reflect that later, but we shouldn't make that
change based on my mistake in Policy.

-- 
Russ Allbery (r...@debian.org)  

Re: Debian Policy 4.6.0.0 released

[Johannes Schauer Marin Rodrigues]

Quoting Sean Whitton (2021-08-18 22:21:15)
> On Wed 18 Aug 2021 at 11:10AM +02, Aurelien Jarno wrote:
> 
> >> 9.1.1
> >> No package is allowed to install files in ``/usr/lib64/``. Previously,
> >> this prohibition only applied to packages for 64-bit architectures.
> >
> > This path is used by the multilib 64-bit toolchain on 32-bit
> > architectures, for instance libc6-amd64:i386, or a few essential
> > libraries like ncurses.
> >
> > What kind of fix do you expect on the packages? Is it finally the time
> > to get rid of multilib and use pure multiarch instead?
> 
> We did not intend to make any packages buggy with this change.  It was
> thought to be just a clarification.
> 
> Russ, perhaps we should revert this?

Or maybe it is finally the time to get rid of multilib and use pure multiarch
instead?

signature.asc
Description: signature

Re: Debian Policy 4.6.0.0 released

[Sean Whitton]

Hello,

On Wed 18 Aug 2021 at 11:10AM +02, Aurelien Jarno wrote:

>> 9.1.1
>> No package is allowed to install files in ``/usr/lib64/``. Previously,
>> this prohibition only applied to packages for 64-bit architectures.
>
> This path is used by the multilib 64-bit toolchain on 32-bit
> architectures, for instance libc6-amd64:i386, or a few essential
> libraries like ncurses.
>
> What kind of fix do you expect on the packages? Is it finally the time
> to get rid of multilib and use pure multiarch instead?

We did not intend to make any packages buggy with this change.  It was
thought to be just a clarification.

Russ, perhaps we should revert this?

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: Debian Policy 4.6.0.0 released

[Sean Whitton]

Hello,

On Wed 18 Aug 2021 at 10:57AM -04, Scott Talbert wrote:

> The upgrading checklist on [1] is for version 4.5.2.  I could be wrong,
> but doesn't this usually match first parts of the policy version
> (4.6.0.0)?
>
> [1] 
> https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4-5-2

Fixed, thanks.  Will reach web mirrors later today.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: Debian Policy 4.6.0.0 released

[Scott Talbert]

On Tue, 17 Aug 2021, Sean Whitton wrote:


Hello everyone,

I just pushed version 4.6.0.0 of the Debian Policy Manual and related
documents to sid.  Below you will find the significant normative changes
from the previously announced release of Policy (4.5.1).

The formal upgrading checklist is short, but also included in this
release is important work by Russ Allbery to improve how we use Policy's
explicitly normative terms -- 'must', 'should', 'recommended', etc.
These keywords are now used more consistently.  We have also introduced
a new category of statements which we are calling "Policy advice".  The
addition of this category should make it easier to incorporate
descriptions of more of our best practices into Policy.  Please see 1.1.

There are also a number of miscellaneous corrections.  Thank you to
those who submitted bug reports and patches.

=*=*=*=

9.1.1
   No package is allowed to install files in ``/usr/lib64/``. Previously,
   this prohibition only applied to packages for 64-bit architectures.

12.1
   Manual pages may be included in dependencies, not only in the packages
   containing the things they document.


Hi,

The upgrading checklist on [1] is for version 4.5.2.  I could be wrong, 
but doesn't this usually match first parts of the policy version 
(4.6.0.0)?


[1] 
https://www.debian.org/doc/debian-policy/upgrading-checklist.html#version-4-5-2

Thanks,
Scott

Re: Debian Policy 4.6.0.0 released

[Aurelien Jarno]

Hi,

On 2021-08-17 20:35, Sean Whitton wrote:
> Hello everyone,
> 
> I just pushed version 4.6.0.0 of the Debian Policy Manual and related
> documents to sid.  Below you will find the significant normative changes
> from the previously announced release of Policy (4.5.1).

[snip]

> 9.1.1
> No package is allowed to install files in ``/usr/lib64/``. Previously,
> this prohibition only applied to packages for 64-bit architectures.

This path is used by the multilib 64-bit toolchain on 32-bit
architectures, for instance libc6-amd64:i386, or a few essential
libraries like ncurses.

What kind of fix do you expect on the packages? Is it finally the time
to get rid of multilib and use pure multiarch instead?

Regards,
Aurelien

-- 
Aurelien Jarno  GPG: 4096R/1DDD8C9B
aurel...@aurel32.net http://www.aurel32.net


signature.asc
Description: PGP signature