Debian/Ubuntu Pulseaudio packaging

[Felipe Sateler]

On Sun, Nov 23, 2014 at 6:27 PM, Luke Yelavich
<luke.yelavich at canonical.com> wrote:
> On Sun, Nov 23, 2014 at 12:14:35AM AEDT, Felipe Sateler wrote:
>> Trimming CC list to ubuntu and debian lists only.
>>
>> > On 2014-11-18 00:25, Luke Yelavich wrote:
>> >>
>> >> Hey folks.
>> >> I'm starting to work on merging Ubuntu and Debian packaging for
>> >> pulseaudio.
>>
>> Excellent! If there is anything I can do to help, please let me know.
>> Are you using a clone of the pkg-pulseaudio git repo or are you doing
>> the merging somewhere else?
>
> I used a clone of the pkg-pulse git tree and have a local branch for the Ubuntu packaging.

I see you have the rc ready in ubuntu. Could you push this work
somewhere so we can prepare the package for debian experimental as
well? I'd be ok with you pushing this to a new branch in the pkg-pulse
repository, or somewhere else I can pull from.

If we use a shared repository, I propose that changes for ubuntu go to
ubuntu/master by default. similarly, we could rename the debian branch
to debian/master. Upstream tarballs still go to the upstream branch.
That way he have no collission, and if you there is a need for
already-released fixes there is the possibility of using
debian/(codename) or ubuntu/(codename).

Version tags should be prefixed, upstream/* for upstream versions,
debian/* for debian releases, and ubuntu/* for ubuntu releases. This
can be automated by git-buildpackage via an appropriate
debian/gbp.conf setting debian-tag to ubuntu/$(version)s (the other
two are the default for gbp).

If you prefer another layout, please tell me what would you prefer.

> I am a member of the pkg-pulse team, so I do have commit access, but I am not sure
> everybody else who touches pulseaudio packaging in Ubuntu is a member of that team
> yet, and we still need to discuss where and how we want to manage the Ubuntu
> packaging going forward, but that is for another mail.

If you decide to use the alioth space, then of course adding everyone
to the team will be no problem. But you have to decide if you want to
do that or use another hosting space. I believe we would be ok with
either, but obviously it would be simpler if we used the same.

>
> Thanks for the heads up on the patches and their upstream status.

:)


-- 

Saludos,
Felipe Sateler