BZR will never work with submodules.
also whats the status of the fixed 1.0 as I have an MOTU thats willing to
sponsor the package before release otherwise we will need to do an SRU
On Tue, Apr 15, 2014 at 1:59 PM, Israel wrote:
> On 04/15/2014 03:13 AM, Timo Jyrinki wrote:
> > 2014-04-14 10:3
On 04/15/2014 03:13 AM, Timo Jyrinki wrote:
> 2014-04-14 10:32 GMT+03:00 Jonathan Aquilina :
>> @Timo if we file an SRU is it safe to say that we have you to back such a
>> request?
> Sure. I can probably help best by reviewing any branch that's
> suggested to be merged against
> https://code.launc
Timo im going to email you later as we have a bigger issue with our master
branch and bzr
On 15 Apr 2014 10:14, "Timo Jyrinki" wrote:
> 2014-04-14 10:32 GMT+03:00 Jonathan Aquilina :
> > @Timo if we file an SRU is it safe to say that we have you to back such a
> > request?
>
> Sure. I can probabl
2014-04-14 10:32 GMT+03:00 Jonathan Aquilina :
> @Timo if we file an SRU is it safe to say that we have you to back such a
> request?
Sure. I can probably help best by reviewing any branch that's
suggested to be merged against
https://code.launchpad.net/~ubuntu-branches/ubuntu/trusty/lmms/trusty
a
I think we need to find out if KXStudio has the right version. If not
Israel or DNS (on irc) can do it as DNS seems to be maintaining the PPA,
but I spoke to him on IRC and he isnt maintaining his PPA. I will try and
speak to him again on irc.
On Mon, Apr 14, 2014 at 9:40 AM, Vesa wrote:
> On 0
On 04/14/2014 10:25 AM, Jonathan Aquilina wrote:
> @Vesa What Timo explained in a previous email is that if we package
> the correct version we can file an SRU (stable release update) for 1.0
> and that will ensure we will have the right version in the repos.
>
Well, Israel is the one who has been
@Israel
Is it possible to get a new package built so we can file an SRU (stable
release update) request
@Timo if we file an SRU is it safe to say that we have you to back such a
request?
On Mon, Apr 14, 2014 at 8:32 AM, Timo Jyrinki wrote:
> I'm sorry but I can't currently find more time for L
On 04/14/2014 09:10 AM, Timo Jyrinki wrote:
> Sure, although I believe fixing of the Ubuntu issue should probably
> happen within the Ubuntu Studio mailing lists
> (https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel) and
> Launchpad, in case some developers are not terribly interested in
@Vesa What Timo explained in a previous email is that if we package the
correct version we can file an SRU (stable release update) for 1.0 and that
will ensure we will have the right version in the repos.
On Mon, Apr 14, 2014 at 9:23 AM, Vesa wrote:
> On 04/14/2014 08:32 AM, Timo Jyrinki wrote:
On 04/14/2014 08:32 AM, Timo Jyrinki wrote:
> To fix the most severe issues, I'd ask to check whether eg. a single
> plugin should be disabled and file bugs accordingly. It is also
> possible to upload a '1.0.0+bzr2569.really.is.1.0.0' type of version,
> but in case there is only 1 or 2 really prob
1.0 is a major improvement over the previous version but we are wanting to
try and only put features out there that are tried and tested. I appreciate
your help with the help that you provided to get lmms packaged.
@Israel See what Timo said below.
On Mon, Apr 14, 2014 at 8:32 AM, Timo Jyrinki w
I'm sorry but I can't currently find more time for LMMS packaging and
it's not as simple as "revert and fire away". I'm not in Ubuntu Studio
development team either (even though interested!), but I was reacting
to the packaging help request.
If someone from eg. the Studio team or any volunteer can
Timo, couldnt you just diff the package vs the current stable branch to see
what needs to be removed?
On Mon, Apr 14, 2014 at 8:10 AM, Timo Jyrinki wrote:
> Sure, although I believe fixing of the Ubuntu issue should probably
> happen within the Ubuntu Studio mailing lists
> (https://lists.ubuntu
Sure, although I believe fixing of the Ubuntu issue should probably
happen within the Ubuntu Studio mailing lists
(https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel) and
Launchpad, in case some developers are not terribly interested in a
single distribution's problems.
So just to give
Would it be possible to get a proper 1.0 built and an SRU request filed for
14.04
On Mon, Apr 14, 2014 at 7:46 AM, Timo Jyrinki wrote:
> 2014-04-14 8:32 GMT+03:00 Timo Jyrinki :
> > to get the fixes needed. His branch was not '1.0.0' but a snapshot
> > release instead from a Launchpad bzr branch
Thanks for your quick reply Timo, but it has been mentioned though that
there are some features which are in our master branch and are not even
ready for prime time yet as they are incomplete implementations of certain
things. One such example is the FX mixer changges Vesa was working on. He
can gi
2014-04-14 8:32 GMT+03:00 Timo Jyrinki :
> to get the fixes needed. His branch was not '1.0.0' but a snapshot
> release instead from a Launchpad bzr branch that mirrored git master.
To elaborate where the problem probably happened (Israel can correct
me if I'm wrong): Israel probably did bzr merge
> I understand that you are upset, but no one here has strictly
> communicated with Ubuntu, (or myself for that matter) what commit is the
> final commit to use.
Hi LMMS folks. I'm here to give a background why how the git master
snapshot from March 26 (+ 2 other patches) was uploaded instead of t
On 04/13/2014 11:14 PM, Israel wrote:
> I understand that you guys are upset about this issue, but please keep
> all the feedback on a more positive tone towards others.
> The people who took the package and updated it obviously are not on
> this list, nor are they LMMS developers.
> I am also simp
I understand that you guys are upset about this issue, but please keep
all the feedback on a more positive tone towards others.
The people who took the package and updated it obviously are not on this
list, nor are they LMMS developers.
I am also simply a Ubuntu user who wanted to be able to use
On 04/13/2014 09:43 PM, Jonathan Aquilina wrote:
>
> Would you like me to work on this and see what we need to do to get
> this pulled
>
Yes, that'd be nice... do what you can...
--
Put Bad Developers to Shame
Dominate De
Would you like me to work on this and see what we need to do to get this
pulled
--
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a
22 matches
Mail list logo
