FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Ubuntu > Ubuntu Development

 
 
LinkBack Thread Tools
 
Old 12-25-2008, 03:09 PM
Philipp Kern
 
Default Maintainance of Packages-arch-specific

Hi there,

the maintainance of a file called Packages-arch-specific, which controls
which packages are built for which architecture and which is used by both
Debian and Ubuntu, was recently handed over to other developers. In the
light of this the change process has been modified, as outlined below.

Packages-arch-specific in a nutshell: This file is consulted whenever
there is a missing build for a source package on an architecture. Some
source packages could only be built on some (like programs which still are
not 64bit-safe, or use special header files that are not commonly
available on all Linux arches) and sometimes it is ok if single binary
packages are missing on an architecture. You could see a current checkout
on [0]. The reason why it is necessary is that the build masters are
often unable to determine architecture restrictions due to them only
inspecting Packages and Sources file. Thus if you limit the architectures
in the source stanza of `debian/control', and it is not only a temporary
measure, then you should also submit a change request.

But please aware that an entry in this file is not always necessary. For
example: If you rely on a runtime which is only ported to some
architectures like Mono (although I think it is ported to all Ubuntu
architectures) then a build-dependency on some Mono package will exclude
the build automatically and only Mono itself needs to be listed in this
control file.

So to the changed procedure as announced in [1]: For transparancy we
want further changes to the file submitted as bugs in the Debian Bug
Tracker against the pseudo-package `buildd.debian.org'[2]. Enquiries
might also be sent to the mail address mentioned in the file[0] itself.

In theory it is necessary to branch the file for releases, but in the
past only one file was used for all releases. Ubuntu currently pulls
the sid branch of the repository[3]. This should probably be refined
at some point in the future either by you (as in Ubuntu/Sojuz) or
by the creation of a Ubuntu branch in our repository.

Questions, anyone? I know that some people want to get rid of this
file for Ubuntu altogether, which would be fine with me, of course.
I just hope that for the time it is (still?) used that we (as in
wanna-build admins on the Debian side) can provide a timely changing
service for both Debian and Ubuntu.

Kind regards,
Philipp Kern

[0] http://buildd.debian.org/quinn-diff/Packages-arch-specific
[1] http://lists.debian.org/debian-devel/2008/12/msg00340.html
[2] http://bugs.debian.org/buildd.debian.org
[3] git://git.debian.org/git/mirror/packages-arch-specific.git
This is no Alioth project because we do not want to move this critical
file away from the wanna-build infrastructure used by Debian as this
might mess horribly with our data.
--
.'`. Philipp Kern Debian Developer
: :' : http://philkern.de Ubuntu MOTU
`. `' xmpphil@0x539.de
`- finger pkern/key@db.debian.org
--
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
 

Thread Tools




All times are GMT. The time now is 06:13 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org