Bug#824211: swh-plugins: Package new upstream version

[trebmuh]

Hi Jaromír and all,

I finished my review and Steve has tagged a new version on github :
https://github.com/swh/ladspa/releases

Hope that helps,
Olivier

Bug#824211: swh-plugins: Package new upstream version

[Jaromír Mikeš]

Thank you Olivier for clarifying situation.
I will try update package then soonish when release is ready.

regards

mira



2016-05-24 13:52 GMT+02:00  :
> Hi all,
>
> I've been talking to Steve (upstream) on those last days as I'm currently
> reviewing some of the definition to squash the few typos in there.
>
> Steve is happy to tag a new version in the github repo and it'll certainly
> happen after I'm done with the review which should be in a few days
> hopefully.
>
> I'll let you know when it's done.
>
> Cheers,
> Olivier
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers

Bug#824211: swh-plugins: Package new upstream version

[trebmuh]

Hi all,

I've been talking to Steve (upstream) on those last days as I'm 
currently reviewing some of the definition to squash the few typos in 
there.


Steve is happy to tag a new version in the github repo and it'll 
certainly happen after I'm done with the review which should be in a few 
days hopefully.


I'll let you know when it's done.

Cheers,
Olivier

Bug#824211: swh-plugins: Package new upstream version

[Jaromír Mikeš]

2016-05-20 0:51 GMT+02:00 Javier Serrano Polo :
> El dj 19 de 05 de 2016 a les 19:41 +0200, Jaromír Mikeš va escriure:
>> Yes, that would be definitely possible, but I would to to know where
>> next releases will be published to tune watch file accordingly.
>
> Nine years have passed without a release. I think a watch file is
> obsolete. I would rely on "New upstream release" bugs from users.

Hi Javier,

I would rather hear from upstream what is planned than just wild guess
of user ;)
Did you asked upstream author if new releases is planned?
He is active and for lv2 version doing releases ...

https://github.com/swh/lv2/releases

So I would guess there could be also for ladspa version soon ... new
plugin is good reason for it.

Please ask him and let me know.

mira

Bug#824211: swh-plugins: Package new upstream version

[Javier Serrano Polo]

El dj 19 de 05 de 2016 a les 19:41 +0200, Jaromír Mikeš va escriure:
> Yes, that would be definitely possible, but I would to to know where
> next releases will be published to tune watch file accordingly.

Nine years have passed without a release. I think a watch file is
obsolete. I would rely on "New upstream release" bugs from users.


smime.p7s
Description: S/MIME cryptographic signature

Bug#824211: swh-plugins: Package new upstream version

[Jaromír Mikeš]

2016-05-19 16:20 GMT+02:00 Jonas Smedegaard :
> Quoting Jaromír Mikeš (2016-05-19 15:45:28)
>> 2016-05-13 20:40 GMT+02:00 Javier Serrano Polo :
>> > Package: swh-plugins
>> > Version: 0.4.15+1-8
>> > Severity: wishlist
>> >
>> > The upstream project is maintained at https://github.com/swh/ladspa . It
>> > includes a vocoder plug-in that is shipped with the lmms package. To
>> > reuse this plug-in, lmms could put it under /usr/lib/ladspa, but that
>> > would conflict with a new version of swh-plugins. Could you tell if you
>> > will package a new upstream version, which is preferable, or if lmms can
>> > publish this plug-in in the meantime?
>>
>> I don't see any release here yet :(
>> https://github.com/swh/ladspa/releases
>
> Then perhaps consider release a snapshot of upstream development - to me
> that feels more sensible (without having looked closer at the code) than
> us indirectly doing the same via a snapshot created by another upstream
> (the lmms project).

Yes, that would be definitely possible, but I would to to know where
next releases will be published to tune watch file accordingly.

mira

Bug#824211: swh-plugins: Package new upstream version

[Jonas Smedegaard]

Quoting Jaromír Mikeš (2016-05-19 15:45:28)
> 2016-05-13 20:40 GMT+02:00 Javier Serrano Polo :
> > Package: swh-plugins
> > Version: 0.4.15+1-8
> > Severity: wishlist
> >
> > The upstream project is maintained at https://github.com/swh/ladspa . It
> > includes a vocoder plug-in that is shipped with the lmms package. To
> > reuse this plug-in, lmms could put it under /usr/lib/ladspa, but that
> > would conflict with a new version of swh-plugins. Could you tell if you
> > will package a new upstream version, which is preferable, or if lmms can
> > publish this plug-in in the meantime?
> 
> I don't see any release here yet :(
> https://github.com/swh/ladspa/releases

Then perhaps consider release a snapshot of upstream development - to me 
that feels more sensible (without having looked closer at the code) than 
us indirectly doing the same via a snapshot created by another upstream 
(the lmms project).


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private


signature.asc
Description: signature

Bug#824211: swh-plugins: Package new upstream version

[Jaromír Mikeš]

2016-05-13 20:40 GMT+02:00 Javier Serrano Polo :
> Package: swh-plugins
> Version: 0.4.15+1-8
> Severity: wishlist
>
> The upstream project is maintained at https://github.com/swh/ladspa . It
> includes a vocoder plug-in that is shipped with the lmms package. To
> reuse this plug-in, lmms could put it under /usr/lib/ladspa, but that
> would conflict with a new version of swh-plugins. Could you tell if you
> will package a new upstream version, which is preferable, or if lmms can
> publish this plug-in in the meantime?

I don't see any release here yet :(
https://github.com/swh/ladspa/releases

mira

Bug#824211: swh-plugins: Package new upstream version

[Javier Serrano Polo]

Package: swh-plugins
Version: 0.4.15+1-8
Severity: wishlist

The upstream project is maintained at https://github.com/swh/ladspa . It
includes a vocoder plug-in that is shipped with the lmms package. To
reuse this plug-in, lmms could put it under /usr/lib/ladspa, but that
would conflict with a new version of swh-plugins. Could you tell if you
will package a new upstream version, which is preferable, or if lmms can
publish this plug-in in the meantime?


smime.p7s
Description: S/MIME cryptographic signature