[273] in athena10
Re: OpenAFS package and metapackage build script design
daemon@ATHENA.MIT.EDU (Timothy G Abbott)
Wed Jun 25 13:16:05 2008
Date: Wed, 25 Jun 2008 13:15:21 -0400 (EDT)
From: Timothy G Abbott <tabbott@MIT.EDU>
To: ghudson@mit.edu
cc: athena10@mit.edu
In-Reply-To: <200806251631.m5PGVqAP006250@outgoing.mit.edu>
Message-ID: <alpine.DEB.1.10.0806251304160.16779@vinegar-pot.mit.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII
On Wed, 25 Jun 2008, ghudson@MIT.EDU wrote:
> I appear to have everything working except for metapackage creation on
> dapper. "equivs-build --arch=blah foo.equivs" seems to do the wrong
> thing on dapper; although the --arch option is documented in the man
> page, equivs-build creates an "Architecture: all" .deb anyway.
>
> My inclination is to disable metapackage creation on dapper and call
> it a day. I can't think of any other workaround short of synthesizing
> the metapackages the hard way (creating a debian/rules,
> debian/control, etc. and running dpkg-buildpackage). My understanding
> is that there are few or no Dapper users of Debathena, so leaving them
> in the current state (must manually get openafs-modules after
> upgrading kernel) is probably not a big deal.
This is essentially correct; there were about 5 machines using Debathena
on dapper back in November, but we have seen no machines apt-get update on
dapper recently (this is clearly incorrect, because debuild apt-get
updates on dapper -- the monitoring has some problems at the moment. But
for contrast we've seen 93 machines with hardy in their sources.list).
-Tim Abbott
