requestsync: guess whether sponsor is requested automatically

Bug #130648 reported by Martin-Éric Racine
4
Affects Status Importance Assigned to Milestone
ubuntu-dev-tools (Ubuntu)
Fix Released
Wishlist
Jonathan Davies

Bug Description

Currently, the user must know about whether or not they need sponsorship for a package and whether it applies to main or universe.

Ideally, requestsync should guess this automatically based on environment variables such as DEBEMAIL or EMAIL:

* if someone's address ends with @ubuntu.com or @canonical.com, they most probably don't need sponsorship, so don't play with the switches at all.

* If their address ends with anything BUT these, they most probably DO need sponsorship, so the -s switch will be auto-enabled.

Likewise, if someone needs sponsorship, it implies that the bug should NOT be marked as Confirmed automatically in the syn request message's body.

The above would be very useful if a helpful Debian developer or frequent bug reporter spotted a new Debian version that might fix some Ubuntu bugs and wanted to inform Ubuntu developers of this fact by suggesting a sync.

Changed in devscripts:
status: New → Confirmed
Revision history for this message
Martin-Éric Racine (q-funk) wrote :

PS: it is already understood that Ubuntu members also include non-developers. However, one would assume that all Ubuntu members already know about the Ubuntu procedures a lot better than any random well-meaning user or Debian contributor who simply wants to report a newer version of a package by using a tool that gathers all the relevant supporting info for them.

Daniel Hahler (blueyed)
Changed in ubuntu-dev-tools:
importance: Undecided → Wishlist
Revision history for this message
Jonathan Davies (jpds) wrote :

Fix commited in Bazaar as of revision 146 and shall be in the next upload.

Changed in ubuntu-dev-tools:
assignee: nobody → jpds
status: Confirmed → Fix Committed
Revision history for this message
Martin-Éric Racine (q-funk) wrote :

Many thanks for implementing this! Cheers!

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package ubuntu-dev-tools - 0.37ubuntu1

---------------
ubuntu-dev-tools (0.37ubuntu1) intrepid; urgency=low

  [ Jonathan Patrick Davies ]
  * get-branches:
    - Open the teams code page before making a new directory.
    - Now check team option before anything else.
    - Check that the team has branches before downloading.
  * doc/get-branches.1: Created.
  * hugdaylist: Improved argument and error handling.
  * pull-lp-source:
    - Use optparse for option handling.
    - Check that the 'release' and 'package' actually exist on Launchpad.
    - Use subprocess for dget calls.
  * buildd: Imported from Martin Pitt's scripts.
  * common.py: Python module to be used to enable the use of cookies
    to authenticate with Launchpad.
  * debian/ubuntu-dev-tools.install: Added line to install common.py above to
    the correct location.
  * requestsync:
    - Use the functions in the common.py file above to authenticate with
      Launchpad.
    - Using the Launchpad cookie file, validate that the user is a member of
      the ubuntu-dev team on Launchpad. Thus, checking if the user needs
      sponsership or not (LP: #130648).
  * doc/requestsync.1: Removed mention of -s flag. Obsoleted by the above.
  * massfile:
    - Use the functions in the common.py file above to authenticate with
      Launchpad.
  * debian/control: Changed XS-Python-Version to >= 2.5.

  [ Siegfried-Angel Gevatter Pujals ]
  * Add the GNU General Public License header to all scripts.
  * Remove files AUTHORS (it duplicated content from debian/copyright) and
    README (superseded by the manpages).

 -- Jonathan Patrick Davies <email address hidden> Tue, 12 Aug 2008 14:48:35 +0100

Changed in ubuntu-dev-tools:
status: Fix Committed → Fix Released
Revision history for this message
Jonathan Davies (jpds) wrote :

Uploaded as you can see. Please test when you have the chance to see if it works as it should.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.