Tails

#1 Updated by anonym 2016-06-02 12:35:52

• Assignee changed from anonym to intrigeri
• QA Check set to Info Needed

anonym is trying to learn how to be a nice citizen of bugs.debian.org but needs some guidance.

anonym wrote:
> # vagrant-libvirt: include tools/create_box.sh

This one has not been answered yet. I guess I should ping? With a proposed patch (since the maintainer doesn’t care too much, it seems)?

> # ruby-libvirt: backport rubygems integration fix to Jessie

I assume “p-u” = “proposed-updates”. What is the protocol here? I Cc the release team and ask their opinion?

> # vagrant-libvirt: backport to jessie

Unfortunate answer, but oh well, we were ready to maintain a backport ourselves at one point. Again, in hopes of not having to do that, should I just Cc debian-ruby@l.d.o and ask what they think?

#2 Updated by intrigeri 2016-06-02 13:32:20

• Assignee changed from intrigeri to anonym
• QA Check changed from Info Needed to Dev Needed

> anonym is trying to learn how to be a nice citizen of bugs.debian.org but needs some guidance.

Let’s say this is good training for your future NM process ;)

> anonym wrote:
>> # vagrant-libvirt: include tools/create_box.sh

> This one has not been answered yet. I guess I should ping? With a proposed patch (since the maintainer doesn’t care too much, it seems)?

Yes, a patch would be good (and presumably quite easy).

>> # ruby-libvirt: backport rubygems integration fix to Jessie

> I assume “p-u” = “proposed-updates”. What is the protocol here? I Cc the release team and ask their opinion?

Yes, as Guido suggested. The release team would likely prefer being asked in the form of a bug report, for easier tracking: https://www.debian.org/doc/manuals/developers-reference/pkgs.html#upload-stable. Please X-Debbugs-Cc me :)

>> # vagrant-libvirt: backport to jessie

> Unfortunate answer, but oh well, we were ready to maintain a backport ourselves at one point. Again, in hopes of not having to do that, should I just Cc debian-ruby@l.d.o and ask what they think?

I don’t think that debian-ruby@l.d.o will have much to say if Antonio doesn’t want to do it: he’s the major contributor to that list. So, if we really want this (we do, right?) we need to maintain this set of backports ourselves, and as Antonio offered, if we have any issue along the way we can ask help to the Ruby team. I suggest you do that in the relevant Vcs-Git repositories, which probably requires you to get access to collab-maint and pkg-ruby-extras repositories (via Alioth group membership requests, I believe).

#3 Updated by anonym 2016-06-04 13:59:42

• Target version changed from Tails_2.4 to Tails_2.6

Thanks for the pointers! I truly doubt I’ll have time for any of this in the next few months (=> postponing) but one issue is a blocker and will need a short-term solution, namely:

> 2. ruby-libvirt: backport rubygems integration fix to Jessie

=> Bug #11509.

#4 Updated by anonym 2016-06-04 14:01:26

• Subject changed from Make sure vagrant-libvirt is packaged according to our needs to Make sure vagrant-libvirt and its dependencies are packaged according to our needs

#5 Updated by intrigeri 2016-08-31 04:24:30

• Description updated
• Assignee changed from anonym to intrigeri
• Target version changed from Tails_2.6 to Tails_2.7
• Type of work changed from Wait to Debian

Next steps:

• provide a patch for https://bugs.debian.org/823317
• clarify on the two other Debian bugs that it’s no big deal if they are not fixed, and that we’re not going to work on it any further

#6 Updated by intrigeri 2016-09-25 04:43:36

• Status changed from Confirmed to Resolved
• Assignee deleted (intrigeri)
• % Done changed from 0 to 100
• QA Check deleted (Dev Needed)

intrigeri wrote:
> Next steps:
>
> * provide a patch for https://bugs.debian.org/823317

Done.

> * clarify on the two other Debian bugs that it’s no big deal if they are not fixed, and that we’re not going to work on it any further

Done.