Scott Moser be30dcfdbb mk-sbuild: better support apt http proxy (LP: #881654)
This improves the support for apt http proxy.
It determines the value for 'http_proxy' by, in increasing importance:
  * setting in apt.conf (per apt-config)
  * environment variable 'http_proxy'
  * command line flag '--debootstrap-proxy'

Then, if that is set, it makes use of it in
  * initial call to debootstrap (environment variable passed through sudo)
  * 'finish.sh' and subsequent invocation by writing config to
    /etc/apt/config.d/

Thus, the value here is 'sticky' after the debootstrap invocation.
2011-10-25 16:33:28 -04:00
2010-12-20 21:33:48 +02:00
2011-05-23 23:41:30 +02:00
2011-05-23 23:44:45 +02:00
2010-12-03 00:06:43 +01:00
2010-12-27 21:54:31 +01:00
2011-09-10 16:40:19 +02:00
2011-09-10 21:28:28 +02:00
2011-09-09 23:54:36 +02:00
2011-10-22 23:10:27 +02:00
2010-12-27 22:33:01 +01:00
2011-05-24 20:22:37 +02:00

Updating the ubuntu-dev-tools package
-------------------------------------

Here are the steps that are recommended to take when updating the
ubuntu-dev-tools package in Ubuntu.

1)  Make sure that there are no new revisions to the package's trunk in Bazaar:

    bzr pull lp:ubuntu-dev-tools

2)  Check to make sure that all approved merges have been merged:

    https://code.launchpad.net/ubuntu-dev-tools/+activereviews

3)  Make sure that there is no low lying fruit that can be fixed at:

    https://bugs.launchpad.net/ubuntu/+source/ubuntu-dev-tools

4)  Check that the test suite passes

    setup.py test

5)  Before uploading the package change the UNRELEASED field in the
    debian/changelog file to unstable. (ubuntu-dev-tools is maintained in Debian
    and synced to Ubuntu)

    If there is no UNRELEASED entry, make sure that the version for the current
    one has not been uploaded by someone else already:

    http://packages.qa.debian.org/u/ubuntu-dev-tools.html
    https://launchpad.net/ubuntu/+source/ubuntu-dev-tools/+publishinghistory

6)  Once the target release has been changed, commit it to Bazaar (where X.YY is
    the new package version):

    bzr commit -m "Uploaded X.YY to RELEASE."

7)  Tag the new release in Bazaar:

    bzr tag

    For a full list of tags, please see: 'bzr tags'. This is so we can track
    which Bazaar revision is in which release and makes bug triaging easier.

8)  Create the new source package:

    bzr bd -S

9)  Upload the package to Debian with dput as normal:

    dput ftp-master ubuntu-dev-tools_X.YY_$arch.changes

10) Create a new blank entry with dch -i and mark it as UNRELEASED.

11) After it's been dinstalled in Debian, sync to Ubuntu:

    syncpackage ubuntu-dev-tools
Description
No description provided
Readme 15 MiB
Languages
Python 89%
Shell 9.9%
Perl 1.1%