Merge ocaml-maint and debian-ocaml-maint

Asked by Mehdi

We (some of the Debian OCaml Maintainers) would like to merge the new team ocaml-maint with the unclaimed (yet) team debian-ocaml-maint, so that we can follow bug reports made against our packages in Ubuntu easily.

Question information

Language:
English Edit question
Status:
Answered
For:
Launchpad itself Edit question
Assignee:
[LEGACY] Canonical WebOps Edit question
Last query:
Last reply:
Whiteboard:
Assigned to LOSAs
Revision history for this message
Mehdi (mehdid) said :
#1

BTW, is it also possible to make ocaml-maint administrate https://launchpad.net/ocaml?

Revision history for this message
Tom Haddon (mthaddon) said :
#2

Currently blocked on bug 393664

Revision history for this message
Mehdi (mehdid) said :
#3

A fix has been released for the Bug #156207 (which is a dupe of 393664).
The fix is released in Launchpad sinzui.

When do you think the merge will be done?

Revision history for this message
Steve McInerney (spm) said :
#4

Mehdi,
 just tried again, still fails. Not with a total crash, but no luck.
It appears that the debian-ocaml-maint account is for a person, vs team. Which may be the problem. Educated guessing here.

I've updated the bug report, so hopefully Curtis can give us an update.

Cheers!
- Steve

Revision history for this message
Curtis Hovey (sinzui) said :
#5

Hi. Mehdi.

I think the team cannot be merged until it is activated. Do you or a team member have access to this team's email address. If so, you can claim the team, then we can precede with the merge.

Revision history for this message
Mehdi (mehdid) said :
#6

Curtis Hovey wrote:
> Your question #74409 on Launchpad Registry changed:
> https://answers.edge.launchpad.net/launchpad-registry/+question/74409
>
> Status: Needs information => Answered
>
> Curtis Hovey proposed the following answer:
> Hi. Mehdi.
>
> I think the team cannot be merged until it is activated. Do you or a
> team member have access to this team's email address. If so, you can
> claim the team, then we can precede with the merge.
>

I asked for the activation of debian-ocaml-maint by putting as contact
address <email address hidden> (for now). I'm still waiting
for the confirmation e-mail, but don't know if I will receive it any time
soon (if it got rejected by list masters).

Is there anything else I can do?

Cheers,

--
Mehdi Dogguy مهدي الدڤي
http://www.pps.jussieu.fr/~dogguy
Tel.: (+33).1.44.27.28.38

Revision history for this message
Curtis Hovey (sinzui) said :
#7

No, not regarding this task.

But I think you can accomplish part of your goal by subscribing your team to distribution package bug reports
https://edge.launchpad.net/ubuntu/+source/ocaml

Revision history for this message
Mehdi (mehdid) said :
#8

Curtis Hovey wrote:
>
> But I think you can accomplish part of your goal by subscribing your team to distribution package bug reports
> https://edge.launchpad.net/ubuntu/+source/ocaml
>

Does this mean to subscribe ocaml-maint to all sources packages maintained
by debian-ocaml-maint? (there are approx. 130)

--
Mehdi Dogguy مهدي الدڤي

Revision history for this message
Curtis Hovey (sinzui) said :
#9

yes.

Revision history for this message
Curtis Hovey (sinzui) said :
#10

> No. Seriously, please, can't you force that to happen (the merge)?

No, the admins used the tools and they failed because the data would be corrupted. You or a member of your team need to gain control of debian-ocaml-maint's email address to verify you are the owners.

Since this team is not active in launchpad, it is not subscribed to any packages; it does not get bug mail. Someone must subscribe to the packges regardless of doing a merge.

Merging would change the ~debian-ocaml-maint maitained packages to your team, but that will not give your team any additional power over the distro and series packages...the maintainer information is historical information, not access control.

Can you help with this problem?

Provide an answer of your own, or ask Mehdi for more information if necessary.

To post a message you must log in.