Re: How to produce the file Packages
eck@sc10.dseg.ti.com (Terry Eck) writes:
> What I'd like to know is how is the file Packages constructed.
dpkg-scanpackages(8)
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
>From miss
Received: from mongo.pixar.com (138.72.50.60)
by master.debian.org with SMTP; 10 Jan 1997 22:44:53 -0000
Received: (qmail 23817 invoked from network); 10 Jan 1997 19:13:13 -0000
Received: from primer.i-connect.net (HELO master.debian.org) (bruce@206.190.143.13)
by mongo.pixar.com with SMTP; 10 Jan 1997 19:13:13 -0000
Message-Id: <97Jan10.140410est.19592@sctorfw001.sprint-canada.com>
Date:Fri, 10 Jan 1997 14:14:39 -0500
From: Ami Ganguli <ami@ganguli.com>
Reply-To: ami@ganguli.com
Organization: Ganguli Consulting Inc.
X-Sender: Ami Ganguli <ami@ganguli.com>
X-Mailer: Mozilla 4.0b1 (Win95; I)
MIME-Version: 1.0
To: debian-user@lists.debian.org
Subject: Re: Problems with 1.2.1
X-Priority: Normal
References: <[🔎] Pine.LNX.3.95.970110091930.3569B-100000@dwarf.polaris.net>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
Resent-Message-ID: <"ocmFl2.0.uB7.CKfro"@master.debian.org>
Resent-From: debian-user@lists.debian.org
Resent-Reply-To: debian-user@lists.debian.org
X-Mailing-List: <debian-user@lists.debian.org> archive/latest/3136
X-Loop: debian-user@lists.debian.org
Precedence: list
Priority: non-urgent
Importance: low
Resent-Sender: debian-user-request@lists.debian.org
Dale Scheetz wrote:
> The first rule of publishing: Don't let the writer proof his/her own work.
> Yet, we as maintainers, are the first to test our packages, and in some
> cases, no other test occurs untill the general user gets to try it out.
> We do have several folks who do "new installs" to test things out, but
> many of the problems users have are due to their particular hardware
> configuration.
>
> As a result of these factors, we must depend upon our user base to "find"
> the other problems.
Understandable, but maybe fixable. I remember Bruce asking people on the
list to test 1.2 before it went out. If that testing process were a little
more structured, we might have found more of the problems ahead of time. I
understand that there's a bug tracking system. Is there a release tracking/
testing system to complement it? I'll volunteer for this if needed, although
there are probably people closer to the project who'd be better suited to it.
My approach would be to treat the distribution as a whole in the same way
you treat a large application program. After a new package is integrated
into the release the entire release passes a series of tests (performed by
various people on various platforms) before the package is accepted.
The process would probably delay the release of "stable" distributions by a
couple of weeks, but I think it would be worth it.
Comments?
... Ami.
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-user-REQUEST@lists.debian.org . Trouble? e-mail to Bruce@Pixar.com
Reply to: