Bug#64304: marked as done (A question about uploading to "frozen")
Your message dated Sun, 10 Jun 2001 21:51:14 +0100
with message-id <20010610215114.A10670@polya>
and subject line Fixed in policy 3.5.5.0
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Darren Benham
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 17 May 2000 23:45:47 +0000
>From J.D.Gilbey@qmw.ac.uk Wed May 17 18:45:47 2000
Received: from mserv1a.u-net.net [195.102.240.34]
by master.debian.org with esmtp (Exim 3.12 #2 (Debian))
id 12sDVa-0005AI-00; Wed, 17 May 2000 18:45:47 -0500
Received: from [195.102.197.12] (helo=polya)
by mserv1a.u-net.net with esmtp (Exim 2.10 #63)
id 12sDVj-0003pS-00; Thu, 18 May 2000 00:45:55 +0100
Received: from jdg by polya with local (Exim 3.12 #1 (Debian))
id 12sDLV-0005vr-00; Thu, 18 May 2000 00:35:21 +0100
Date: Thu, 18 May 2000 00:35:21 +0100
From: Julian Gilbey <J.D.Gilbey@qmw.ac.uk>
To: Brian Mays <brian@debian.org>
Cc: debian-devel@lists.debian.org, submit@bugs.debian.org
Subject: Re: A question about uploading to "frozen"
Message-ID: <20000518003521.B22771@polya>
References: <20000517161231.9C8DCDFA6@ariel.local.net> <20000517192404.D22253@polya> <J.D.Gilbey@qmw.ac.uk> <20000517205634.9D618DFA6@ariel.local.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Mutt/1.0.1i
In-Reply-To: <20000517205634.9D618DFA6@ariel.local.net>; from brian@debian.org on Wed, May 17, 2000 at 04:56:33PM -0400
Delivered-To: submit@bugs.debian.org
Package: packaging-manual
Version: 3.1.1.1
Big bug! Thanks for spotting it. Will be fixed in an upcoming
version. Distribution should be unstable, frozen, stable or
experimental; Section should refer to main, contrib and non-free,
etc.
Julian
On Wed, May 17, 2000 at 04:56:33PM -0400, Brian Mays wrote:
> > On Wed, May 17, 2000 at 12:12:30PM -0400, Brian Mays wrote:
>
> > > Someone please help me here. How do I upload a new version of a
> > > package to the non-free part of the frozen distribution? If I use
> > > "frozen" in the heading of the changelog entry, it will be stuck in
> > > the main distribution; if I use "non-free", it will be placed in the
> > > non-free section of the unstable distribution. How do I specify
> > > both "frozen" and "non-free" at the same time?
>
> Julian Gilbey <J.D.Gilbey@qmw.ac.uk> replied:
>
> > Read the packaging manual.
>
> I did, and that's the problem. I suggest that the packaging manual
> needs to be changed.
>
> > In the changelog, you state the distribution (unstable, frozen,
> > stable, experimental or some combination of these). In the
> > debian/control file you state the Section: non-free/* and Priority: of
> > the package.
>
> I realize that this is the correct way of doing things, but how in the
> hell do you get this from reading the packaging manual? Here is what
> the packaging manual ACTUALLY says. I am quoting from version 3.1.1.1
> of the packaging manual (dated 1999-11-22), which AFAIK is the latest
> version of this document.
>
> Here is what the packaging manual says about the the debian/changelog
> file:
>
> ---------------------------------------------------------------------------
> 3.2.3. `debian/changelog'
> -------------------------
>
> This file records the changes to the Debian-specific parts of the
> package [1].
>
> [1] Though there is nothing stopping an author who is also the Debian
> maintainer from using it for all their changes, it will have to
> be renamed if the Debian and upstream maintainers become
> different people.
>
> It has a special format which allows the package building tools to
> discover which version of the package is being built and find out
> other release-specific information.
>
> That format is a series of entries like this:
>
> <package> (<version>) <distribution(s)>; urgency=<urgency>
>
> * <change details>
> <more change details>
> * <even more change details>
>
> -- <maintainer name and email address> <date>
>
> <package> and <version> are the source package name and version
> number.
>
> <distribution(s)> lists the distributions where this version should be
> installed when it is uploaded - it is copied to the `Distribution'
> field in the `.changes' file. See Section 4.2.14, ``Distribution''.
> ---------------------------------------------------------------------------
>
> so now I need to skip to Section 4.2.14 to find out what I should use
> for the "distribution". This is what it says:
>
> ---------------------------------------------------------------------------
> 4.2.14. `Distribution'
> ----------------------
>
> In a `.changes' file or parsed changelog output this contains the
> (space-separated) name(s) of the distribution(s) where this version of
> the package should be or was installed. Distribution names follow the
> rules for package names. (See Section 4.2.1, ``Package'').
>
> Current distribution values are:
>
> _stable_
> This is the current `released' version of Debian GNU/Linux. A
> new version is released approximately every 3 months after the
> _development_ code has been _frozen_ for a month of testing.
> Once the distribution is _stable_ only major bug fixes are
> allowed. When changes are made to this distribution, the release
> number is increased (for example: 1.2r1 becomes 1.2r2 then 1.2r3,
> etc).
>
> _unstable_
> This distribution value refers to the _developmental_ part of the
> Debian distribution tree. New packages, new upstream versions of
> packages and bug fixes go into the _unstable_ directory tree.
> Download from this distribution at your own risk.
>
> _contrib_
> The packages with this distribution value do not meet the
> criteria for inclusion in the main Debian distribution as defined
> by the Policy Manual, but meet the criteria for the _contrib_
> Distribution. There is currently no distinction between stable
> and unstable packages in the _contrib_ or _non-free_
> distributions. Use your best judgement in downloading from this
> Distribution.
>
> _non-free_
> Like the packages in the _contrib_ seciton, the packages in
> _non-free_ do not meet the criteria for inclusion in the main
> Debian distribution as defined by the Policy Manual. Again, use
> your best judgement in downloading from this Distribution.
>
> _experimental_
> The packages with this distribution value are deemed by their
> maintainers to be high risk. Oftentimes they represent early
> beta or developmental packages from various sources that the
> maintainers want people to try, but are not ready to be a part of
> the other parts of the Debian distribution tree. Download at
> your own risk.
>
> _frozen_
> From time to time, (currently, every 3 months) the _unstable_
> distribution enters a state of `code-freeze' in anticipation of
> release as a _stable_ version. During this period of testing
> (usually 4 weeks) only fixes for existing or newly-discovered
> bugs will be allowed.
>
> You should list _all_ distributions that the package should be
> installed into. Except in unusual circumstances, installations to
> _stable_ should also go into _frozen_ (if it exists) and _unstable_.
> Likewise, installations into _frozen_ should also go into _unstable_.
> ---------------------------------------------------------------------------
>
> Therefore, according to the packaging manual, I should be using
> "non-free" as the distribution in the changelog. But the correct way to
> do this, as Julian Gilbey has pointed out, is to specify "non-free" in
> the "Section" field of the debian/control file. Let's see what the
> packaging manual says about this field. It is covered in Section 4.2.9:
>
> ---------------------------------------------------------------------------
> 4.2.9. `Section' and `Priority'
> -------------------------------
>
> These two fields classify the package. The `Priority' represents how
> important that it is that the user have it installed; the `Section'
> represents an application area into which the package has been
> classified.
>
> When they appear in the `debian/control' file these fields give values
> for the section and priority subfields of the `Files' field of the
> `.changes' file, and give defaults for the section and priority of the
> binary packages.
>
> The section and priority are represented, though not as separate
> fields, in the information for each file in the `-File'field of a
> `.changes' file. The section value in a `.changes' file is used to
> decide where to install a package in the FTP archive.
>
> These fields are not used by by `dpkg' proper, but by `dselect' when
> it sorts packages and selects defaults. See the Debian policy manual
> for the priorities in use and the criteria for selecting the priority
> for a Debian package, and look at the Debian FTP archive for a list of
> currently in-use priorities.
>
> These fields may appear in binary package control files, in which case
> they provide a default value in case the `Packages' files are missing
> the information. `dpkg' and `dselect' will only use the value from a
> `.deb' file if they have no other information; a value listed in a
> `Packages' file will always take precedence. By default
> `dpkg-genchanges' does not include the section and priority in the
> control file of a binary package - use the `-isp', `-is' or `-ip'
> options to achieve this effect.
> ---------------------------------------------------------------------------
>
> Very interesting. This section does not mention that "contrib" or
> "non-free" should be specified in the "Section" field, in fact, unlike
> Section 4.2.14 on "Distribution", it doesn't even mention these words at
> all. So again I ask: how am I supposed to know the correct way of doing
> things from this document?
>
> Thank you very much for your help.
>
> - Brian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. J.D.Gilbey@qmw.ac.uk
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
---------------------------------------
Received: (at 64304-done) by bugs.debian.org; 10 Jun 2001 21:32:08 +0000
>From J.D.Gilbey@qmw.ac.uk Sun Jun 10 16:32:08 2001
Return-path: <J.D.Gilbey@qmw.ac.uk>
Received: from mserv1e.vianw.co.uk [::ffff:195.102.240.97]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 159CoZ-0005SQ-00; Sun, 10 Jun 2001 16:32:08 -0500
Received: from [195.102.197.228] (helo=polya)
by mserv1e.vianw.co.uk with esmtp (Exim 3.22 #5)
id 159CoX-00008l-00
for 64304-done@bugs.debian.org; Sun, 10 Jun 2001 22:32:05 +0100
Received: from jdg by polya with local (Exim 3.22 #1 (Debian))
id 159CB1-0002mH-00; Sun, 10 Jun 2001 21:51:15 +0100
Date: Sun, 10 Jun 2001 21:51:14 +0100
From: Julian Gilbey <J.D.Gilbey@qmw.ac.uk>
To: 64304-done@bugs.debian.org
Subject: Fixed in policy 3.5.5.0
Message-ID: <20010610215114.A10670@polya>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.18i
Sender: Julian Gilbey <J.D.Gilbey@qmw.ac.uk>
Delivered-To: 64304-done@bugs.debian.org
This bug has been fixed in the latest versions of policy (which has
superseded the packaging manual).
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, Queen Mary, Univ. of London
Debian GNU/Linux Developer, see http://people.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
Reply to: