Details in source package portlet don't change without new upload
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | Launchpad itself |
Low
|
Julian Edwards | ||
Bug Description
Looking at https:/
| Celso Providelo (cprov) wrote : | #1 |
| Changed in soyuz: | |
| assignee: | nobody → cprov |
| status: | Unconfirmed → Needs Info |
| William Grant (wgrant) wrote : | #2 |
I think it makes little sense to show the 'maintainer defaults', because they're controlled only by overrides anyway. It's completely useless to show the component when this sourcepackagere
| Celso Providelo (cprov) wrote : | #3 |
Hi Willian,
Let me check if I can summarize your points:
Both information set are important (currently published attributes and maintainer default attributes), necessary and are in the right place. However you miss a new Portlet with the 'currently published information across distroreleases', something like:
{{{
Currently Published:
Gutsy (1.30ubuntu1): universe/
Feisty (1.30ubuntu1): universe/
Edgy (1.30ubuntu1): universe/
Dapper(
Breezy(
...
}}}
How does it sound ?
| William Grant (wgrant) wrote : Re: [Bug 93293] Re: Details in source package portlet don't change without new upload | #4 |
On Wed, June 6, 2007 11:51 am, Celso Providelo wrote:
> Hi Willian,
>
> Let me check if I can summarize your points:
>
> Both information set are important (currently published attributes and
> maintainer default attributes), necessary and are in the right place.
> However you miss a new Portlet with the 'currently published information
> across distroreleases', something like:
What are these 'maintainer defaults'? They aren't defined by the
maintainer; they're controlled solely by the overrides (ie. archive
admins).
> {{{
> Currently Published:
>
> Gutsy (1.30ubuntu1): universe/
> Feisty (1.30ubuntu1): universe/
> Edgy (1.30ubuntu1): universe/
> Dapper(
> Breezy(
> ...
> }}}
>
> How does it sound ?
That would be really good! Being able to easily see the versions etc.
across releases on bug pages would be very useful.
> --
> Details in source package portlet don't change without new upload
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
>
| Celso Providelo (cprov) wrote : Re: [Bug 93293] Re: Details in source package portlet don't change without new upload | #5 |
On 6/5/07, William Grant <email address hidden> wrote:
...
> What are these 'maintainer defaults'? They aren't defined by the
> maintainer; they're controlled solely by the overrides (ie. archive
> admins).
>
No, the uploader can control them, they just do not bother much with
this because we implement auto-overrides on the upload processor side.
This information is in the control file (materialized in the DSC) as:
{{{
Section: [component/
Priority: extra|optional|
}}}
> > {{{
> > Currently Published:
> >
> > Gutsy (1.30ubuntu1): universe/
> > Feisty (1.30ubuntu1): universe/
> > Edgy (1.30ubuntu1): universe/
> > Dapper(
> > Breezy(
> > ...
> > }}}
> >
> > How does it sound ?
>
> That would be really good! Being able to easily see the versions etc.
> across releases on bug pages would be very useful.
>
Ok let's do it then.
Thanks for the feedback.
--
Celso Providelo <email address hidden>
| William Grant (wgrant) wrote : Re: [Bug 93293] Re: Details in source package portlet don't change without new upload | #6 |
On Wed, June 6, 2007 1:02 pm, Celso Providelo wrote:
> On 6/5/07, William Grant <email address hidden> wrote:
> ...
>> What are these 'maintainer defaults'? They aren't defined by the
>> maintainer; they're controlled solely by the overrides (ie. archive
>> admins).
>>
>
> No, the uploader can control them, they just do not bother much with
> this because we implement auto-overrides on the upload processor side.
Well, yes, but my point was that it's never done because most stuff is
synced from Debian, and they're overridden anyway. The portlet can't show
the information from debian/control, or we'd have a whole lot of stuff
listed as being in contrib and non-free, but none in restricted, universe
or multiverse.
>> > {{{
>> > Currently Published:
>> >
>> > Gutsy (1.30ubuntu1): universe/
>> > Feisty (1.30ubuntu1): universe/
>> > Edgy (1.30ubuntu1): universe/
>> > Dapper(
>> > Breezy(
>> > ...
>> > }}}
>> >
>> > How does it sound ?
>>
>> That would be really good! Being able to easily see the versions etc.
>> across releases on bug pages would be very useful.
>>
>
> Ok let's do it then.
Great :D
> Thanks for the feedback.
Thanks for listening to your users!
- William
| Celso Providelo (cprov) wrote : | #7 |
Well the fact that debian-synced sources pages would start to present [1] 'non-free' and 'contrib' as their original component is a feature, we do want to preserve this information.
Thats the essence of Soyuz Derivation Model, we should preserve the ability to see what was changed in the SourcePackageRe
I don't understand why you want us to hide it.
[1] I said 'would', because currently we do overrides that corrupt the *original* source metadata
| Celso Providelo (cprov) wrote : | #8 |
It should be trivial to add the suggested new Portlet.
| Changed in soyuz: | |
| importance: | Undecided → Low |
| status: | Needs Info → Confirmed |
| LaserJock (laserjock) wrote : | #9 |
The problem with preserving them is we then lose the Ubuntu information. If a package is taken straight from Debian we need to know what component it ends up in in Ubuntu. So while the Debian component is nice to have, we need to know the Ubuntu component more. It'd be interesting if you could find a way to show both " Ubuntu universe/<sec> from Debian main/<sec>" or something.
| Changed in soyuz: | |
| assignee: | nobody → julian-edwards |
| Changed in soyuz: | |
| milestone: | 1.1.10 → 1.1.11 |
| Changed in soyuz: | |
| milestone: | 1.1.11 → 1.2.1 |
| Julian Edwards (julian-edwards) wrote : | #12 |
Given that the page in the original report no longer has the portlet, but we now have
https:/
does that fulfill your needs?
| Changed in soyuz: | |
| status: | Confirmed → Incomplete |
| William Grant (wgrant) wrote : | #13 |
The portlet is still present on SPR bug pages. That's a bug, albeit a very useful one.
| Julian Edwards (julian-edwards) wrote : | #14 |
Ok, so we need a new portlet on the SPR page.
Thanks for the feedback.
| Changed in soyuz: | |
| status: | Incomplete → Confirmed |
| Julian Edwards (julian-edwards) wrote : | #15 |
That should have read a new portlet on the SPR *bug* page.
| Changed in soyuz: | |
| status: | Confirmed → In Progress |
| Julian Edwards (julian-edwards) wrote : | #16 |
RF 5485
There is a new portlet on the bugs DSP page that shows the info as per Celso's post. Check it out on edge when edge is updated.
| Changed in soyuz: | |
| status: | In Progress → Fix Committed |
| Changed in soyuz: | |
| status: | Fix Committed → Fix Released |

Hi Willian,
You are right, the portlet details are taken from the "Maintainers Defaults Values" and there is a clear note about that assumption. section/ urgency, may vary because we do post-publication overrides and that was the case for kbd-chooser. Current status is found by checking the Publication History in the main content of the mentioned page.
Publication details, as we call component/
Let me know if you have a better suggestion to make this situation more obvious.