Overview page is not up to date

Bug #190806 reported by Morten Kjeldgaard
4
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Medium
Celso Providelo

Bug Description

When I go to my Overview page, and choose "List assigned packages" on the Action menu, the lists there, both of maintained packages, and of packages in my ppa, is out of date.

Tags: lp-soyuz ui
Celso Providelo (cprov)
Changed in soyuz:
milestone: none → 1.2.3
status: New → Triaged
Revision history for this message
Celso Providelo (cprov) wrote :

Morten, could you provide more information about this problem. How 'out of date' ? Can you point us what you were expecting to see ?

Changed in soyuz:
milestone: 1.2.3 → none
status: Triaged → Incomplete
Revision history for this message
Morten Kjeldgaard (mok0) wrote :

Well, for example, check my PPA, and then check the overview. You can see that a bunch of packages are not listed.

Revision history for this message
Morten Kjeldgaard (mok0) wrote :

I was a bit too quick there. Here's some more detail:

My overview -> "List assigned packages" in the actions menu. The list of packages in my ppa has not been updated in 2008. Compare with the list you get from "Personal Package Archive".

I have also contributed several packages to hardy that are not listed in the "Uploaded packages" section: gpp4, ssm, mmdb, torque, xtide-wvs1-data, clipper.

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

Morten, the root cause of the problem was that you've changed the email address you used to upload files in 2008-01-21 from "<email address hidden>" to "<email address hidden>" which wasn't validated to your original account.

Since the GPG signature was fine and inside the keyring, LP created a new account for it https://edge.launchpad.net/~mok-bioxray, which contains all the packages you are looking for.

This is actually very odd from the code point of view because we can't easily reassign the packages for you original account without updating our DB manually. IIRC, it has never happened before.

I hope that you understood the problem now, let me think about a feasible solution for a bit.

Thanks for reporting this bug.

Changed in soyuz:
importance: Undecided → Medium
status: Incomplete → Confirmed
Celso Providelo (cprov)
Changed in soyuz:
assignee: nobody → cprov
milestone: none → 1.2.4
status: Confirmed → Triaged
Revision history for this message
Christian Reis (kiko) wrote : Re: [Bug 190806] Re: Overview page is not up to date

On Wed, Feb 20, 2008 at 08:19:45PM -0000, Celso Providelo wrote:
> This is actually very odd from the code point of view because we can't
> easily reassign the packages for you original account without updating
> our DB manually. IIRC, it has never happened before.

Can't we just merge the accounts?

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

On Wed, Feb 20, 2008 at 7:05 PM, Christian Reis <email address hidden> wrote:
> On Wed, Feb 20, 2008 at 08:19:45PM -0000, Celso Providelo wrote:
> > This is actually very odd from the code point of view because we can't
> > easily reassign the packages for you original account without updating
> > our DB manually. IIRC, it has never happened before.
>
> Can't we just merge the accounts?

Yes, but the packages will remain attached to the old account, which
in practical terms means /lost/ because we can't access merged
accounts.

We should fix the package lookup to follow merged accounts references,
AFAICS, but I don't know if it's easy to do.

I will investigate.

[]
--
Celso Providelo <email address hidden>

Revision history for this message
Morten Kjeldgaard (mok0) wrote :

>> This is actually very odd from the code point of view because we
>> can't
>> easily reassign the packages for you original account without
>> updating
>> our DB manually. IIRC, it has never happened before.
>
> Can't we just merge the accounts?

As far as I am aware, I only have one LP account? Very strange.

Cheers,
Morten

Revision history for this message
Morten Kjeldgaard (mok0) wrote :

On 20/02/2008, at 21.19, Celso Providelo wrote:

> Morten, the root cause of the problem was that you've changed the
> email
> address you used to upload files in 2008-01-21 from
> "<email address hidden>" to
> "<email address hidden>" which wasn't validated to your original account.
>
> Since the GPG signature was fine and inside the keyring, LP created a
> new account for it https://edge.launchpad.net/~mok-bioxray, which
> contains all the packages you are looking for.
>
> This is actually very odd from the code point of view because we can't
> easily reassign the packages for you original account without updating
> our DB manually. IIRC, it has never happened before.
>
> I hope that you understood the problem now, let me think about a
> feasible solution for a bit.
>
> Thanks for reporting this bug.
>
>
> ** Changed in: soyuz
> Importance: Undecided => Medium
> Status: Incomplete => Confirmed
>
> --
> Overview page is not up to date
> https://bugs.launchpad.net/bugs/190806
> You received this bug notification because you are a direct subscriber
> of the bug.
>

Revision history for this message
Morten Kjeldgaard (mok0) wrote :

I now understand what happened: I added my new email address to my gpg key, and started to use the new address in debian/changelog. I uploaded to LP, but behind my back, LP started another account which now "own" those packages. I continued my bug work etc. in the "old" account never knowing about this.

My opinion is that this behavior of LP is wrong. It should not by itself initiate a new account, but rather fail if the email address it finds as the signer in the gpg key is not authorized. If I had authorized the new email account in LP before starting to upload, I assume this problem would not have arisen.

I now realize that I cannot authorize my new email address in my LP overview page without being asked to merge mok-bioxray.

Revision history for this message
Christian Reis (kiko) wrote :

On Wed, Feb 20, 2008 at 11:39:44PM -0000, Celso Providelo wrote:
> > Can't we just merge the accounts?
>
> Yes, but the packages will remain attached to the old account, which
> in practical terms means /lost/ because we can't access merged
> accounts.

So is this a dupe of the bug in which merged accounts don't copy
packages over?

Revision history for this message
Morten Kjeldgaard (mok0) wrote :

I went ahead and merged the two accounts. As far as I can see things now look normal, and everything I expect to see in Overview- > List assigned packages is there.

I am satisfied that the problem is solved and close this bug.

Revision history for this message
Morten Kjeldgaard (mok0) wrote :

Problem solved by merging accounts.

Changed in soyuz:
status: Triaged → Invalid
Celso Providelo (cprov)
Changed in soyuz:
status: Invalid → Confirmed
milestone: 1.2.4 → none
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.