[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: New release of so-synth-lv2



Thanks! This is the first I heard.  Can I ask, did this happen because of my email,  or because of the automatic monitoring?  Should I do anything next time for the release?

Thanks, 
Jeremy

On Mon, Jan 20, 2020, 12:37 Dennis Braun <d_braun@kabelmail.de> wrote:
Hello Jeremy,

i'm not sure if anybody replied to you so far.
Your new upstream version is uploaded to debian sid and already entered
debian testing :-)

https://tracker.debian.org/pkg/so-synth-lv2

https://salsa.debian.org/multimedia-team/so-synth-lv2

Best regards,
Dennis

Am 06.01.20 um 05:20 schrieb Jeremy Salwen:
> Hello Debian Media Maintainers!
>
> I am the author of so-synth-lv2, and back in 2011, I created the initial
> packaging for Debian, and with the help of Alessio Treglia, got it into
> debian :)
>
> At the time I created the debian packaging in the same repository as the
> upstream source, but the packaging was redone using exported tarballs
> instead: https://salsa.debian.org/multimedia-team/so-synth-lv2.
>
> Now I have a new upstream release, and I am wondering what is the best way
> to proceed forward:
> https://github.com/jeremysalwen/So-synth-LV2/releases/tag/upstream%2F1.5
>
> I would like to keep a copy of the debian packaging in the upstream
> repository, but the debian repository seems to have a separate upstream
> branch based on exporting tarballs and reimporting them.  Is this really
> necessary?  The documentation seems to suggest that you can just have a
> workflow where you directly merge upstream into the debian master branch:
> https://wiki.debian.org/PackagingWithGit#Using_the_upstream_repo
>
> Thanks,
> Jeremy Salwen
>



Reply to: