Re: Explain to me "any all"

2012-02-26 Thread Dmitry Smirnov 
Fantastic, thanks very much Bernhard, I think that's the explanation we're all 
needed.

Regards,
Dmitry.

On Sunday 26 February 2012 22:02:15 Bernhard R. Link wrote:
> * Paul Elliott  [120226 02:03]:
> > The new standard allows "any all" in the Architecture field.
> > 
> > Please explain this new feature. What does it do and under what
> > circumstances should it be used?
> 
> It's for the Architecture field of the .dsc. As that field is
> automatically generated, you don't "use" it normally.
> 
> As maintainer you usually edit the debian/control field. There every
> binary package has an Architecture list. This Architecture in the .dsc
> is the merged list of all those architectures.
> 
> If one package is e.g. architecture "i386" and one is architecture
> "any", then those are merged to "any" (as there is a package to be
> generated on any architecture, it does not matter that on i386 there
> are even more packages to generate).
> 
> What is changed is what happens if one .deb is architecture "any"
> and one .deb is architecture "all". Former versions of dpkg merged
> that to "any" and policy reflected that.
> 
> The problem with this is that it loses information whether there
> are architecture "all" packages to be built. As architecture "all"
> packages were never built by the buildds, this was no actual
> problem, so only fixed recently.
> 
> Current versions of dpkg merge this to "any all", and policy was
> changed to reflect this.
> 
> Bernhard R. Link


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201202262352.35402.only...@member.fsf.org

Re: Explain to me "any all"

2012-02-26 Thread Bernhard R. Link 
* Paul Elliott  [120226 02:03]:
> The new standard allows "any all" in the Architecture field.
>
> Please explain this new feature. What does it do and under what circumstances
> should it be used?

It's for the Architecture field of the .dsc. As that field is
automatically generated, you don't "use" it normally.

As maintainer you usually edit the debian/control field. There every
binary package has an Architecture list. This Architecture in the .dsc
is the merged list of all those architectures.

If one package is e.g. architecture "i386" and one is architecture
"any", then those are merged to "any" (as there is a package to be
generated on any architecture, it does not matter that on i386 there
are even more packages to generate).

What is changed is what happens if one .deb is architecture "any"
and one .deb is architecture "all". Former versions of dpkg merged
that to "any" and policy reflected that.

The problem with this is that it loses information whether there
are architecture "all" packages to be built. As architecture "all"
packages were never built by the buildds, this was no actual
problem, so only fixed recently.

Current versions of dpkg merge this to "any all", and policy was
changed to reflect this.

Bernhard R. Link


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120226110207.ga2...@client.brlink.eu

Re: Explain to me "any all"

2012-02-25 Thread Nicholas Breen 
On Sat, Feb 25, 2012 at 07:02:41PM -0600, Paul Elliott wrote:
> The new standard allows "any all" in the Architecture field.
> 
> Please explain this new feature. What does it do and under what circumstances 
> should it be used?

Please see .  It is a technical change related
to the *.dsc file of a source package only, which is an autogenerated file;
there are no changes to the architecture specifications in debian/control that
a package maintainer would edit.


-- 
Nicholas Breen
nbr...@debian.org


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120226011721.gf15...@ofb.net

Re: Explain to me "any all"

2012-02-25 Thread Paul Wise 
On Sun, Feb 26, 2012 at 9:02 AM, Paul Elliott wrote:

> The new standard allows "any all" in the Architecture field.
>
> Please explain this new feature. What does it do and under what circumstances
> should it be used?

Please read the policy section that was changed (5.6.8):

http://www.debian.org/doc/debian-policy/

Reading the rest of policy and also the developers-reference would be
a good idea too:

http://www.debian.org/doc/manuals/developers-reference/

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/CAKTje6HgWdNFR=J_=1afendgkywitoqgj2tvhmvkg1ozahl...@mail.gmail.com

Explain to me "any all"

2012-02-25 Thread Paul Elliott 
The new standard allows "any all" in the Architecture field.

Please explain this new feature. What does it do and under what circumstances 
should it be used?

Thank You.


-- 
Paul Elliott   1(512)837-1096
pelli...@blackpatchpanel.com   PMB 181, 11900 Metric Blvd Suite J
http://www.free.blackpatchpanel.com/pme/   Austin TX 78758-3117


signature.asc
Description: This is a digitally signed message part.