Enable uploads to post-release pockets in PPA

Bug #151528 reported by Bertrand G
2
Affects Status Importance Assigned to Milestone
Launchpad itself
Won't Fix
Medium
Celso Providelo

Bug Description

Please enable uploads to post-release pockets in PPA. They would use the respective (and maintained) ubuntu chroots and get build-deps according the target pocket.

This would enable packages to be build against feisty-backports packages, for instance.

Revision history for this message
Bertrand G (berteh) wrote :

snippet from the launchpad-users mailing list: https://lists.ubuntu.com/archives/launchpad-users/2007-October/002471.html where alternatives have been exposed by Celso Providelo.

> > 2) a support for other distributions than Release (actually I'm mostly interested in backports, especially dapper-backports, as it is bit too out-dated to my needs)
>
(...)
> Can you explain exactly what it is you are trying to do that you can't
> do?

He means that PPA packages are built with dependencies coming only
from 'release' pocket.

We can solve this problem in two different ways:

 1. Enable uploads to post-release pockets in PPA. They would use the
respective (and maintained) ubuntu chroots and get build-deps
according the target pocket.

 2. Wait for 'archive_purpose-specific-chroots' implementation, when
we will be able to customize the 'release' chroot for PPA to grab
build-deps from post-release pockets.

The former would represent more complexity to the PPA-owners, in the
sense they will have to coordinate uploads across pockets, and no
extra work for ubuntu-admins.

The latter solution is exactly the opposite, PPA-owners won't notice
any drawback in their workflow and would get post-release build-deps
for free, but ubuntu-admins will have to maintain a parallel chroot
for PPAs.

Another major side-effect of the second solution is that PPA users
(clients) will have to enable all post-release pockets in their
systems in other to install possible binary-dependencies required in
PPA packages.

It's a complicated decision.

[]
--
Celso Providelo

Revision history for this message
Celso Providelo (cprov) wrote :

As I mentioned in the lp-user@ message, it's a tough decision and we have to consult the involve parts to see what they prefer (ubuntu-team, buildd-admins, etc).

Changed in soyuz:
assignee: nobody → cprov
importance: Undecided → Medium
milestone: none → 1.1.11
status: New → Incomplete
Revision history for this message
Bertrand G (berteh) wrote :

Is there any way I can help submitting the topic for discussion to other stakeholders? ... just to be sure it gets addressed someday...

Revision history for this message
Celso Providelo (cprov) wrote :

Sure, you can point ubuntu-motu and other PPA users to this bug and collect suggestion, ideas, impacts of the proposed solution ... if you have time.

From my side, I can only say that we won't have time to address it before LP 1.1.11 (5 ~ 6 weeks), sorry :(.

Christian Reis (kiko)
Changed in soyuz:
milestone: 1.1.11 → 1.1.12
Revision history for this message
Julian Edwards (julian-edwards) wrote :

PPA builds already use the Ubuntu chroots and will also use the same pocket dependencies as builds in the Ubuntu archive. In addition, PPA builds do not use the ogre model for components and can build against dependencies in any component in the primary archve. Therefore, I don't see any problems here and am marking this bug accordingly.

Changed in soyuz:
status: Incomplete → Won't Fix
Revision history for this message
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/151528

tags: added: iso-testing
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.