Re: [ubuntu-studio-devel] Ubuntu Studio on Gnome (23.04)

[Ross Gammon]

On 7/12/23 19:49, Ross Gammon wrote:

On 7/12/23 19:46, Ross Gammon wrote:

qpwgraph is a QT GUI interface to wireplumber which is in Lunar.


Correction - qpwgraph depends on pipewire itself and not wireplumber. 
That was a wrong assumption on my part.


Ross



Well I had a play with qpwgraph and pipwire, and the some of the Ubuntu 
Studio audio tools with 23.04 (Lunar) on Gnome - and you can do stuff!


But I see what everyone means about pro-studios. It is all a bit clunky. 
and latency is a problem without an easy way to get in and fiddle with 
the settings. At least - one that I know of.


Apparently you can use some pipewire command line tools. But the manpage 
is light on information. I suppose your Ubuntu Studio Audio Config tool 
will help here - now I understand better what you were saying about the 
PIPEWIRE_QUANTUM variable.


With qpwgraph, I could make all of the connections that I used to make 
with The patch section of Carla. But everytime I clicked on another 
window, and then clicked back to qpwgraph, its window was un-maximised.


Hydrogen works.

I recorded an extra track into a previous Ardour project. Latency!

I recorded my electric guitar into an extra track via Guitarix. Same 
problem - naturally.


I played FluidSynth via the Virtual Keyboard without going into Ardour - 
there wasn't much point recording my virtual keyboard playing skills :-) 
No problems.


I didn't bother with any other effect/EQ plugins.

So. I didn't confirm what sample rate settings were being used. But if 
you can deal with the latency issue, you can do some rough/basic audio 
work on pipewire. For a true amateur like me - it would be OK after the 
latency is fixed.


Cheers,

Ross




--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio on Gnome (23.04)

[Ross Gammon]

On 7/12/23 19:46, Ross Gammon wrote:

qpwgraph is a QT GUI interface to wireplumber which is in Lunar.


Correction - qpwgraph depends on pipewire itself and not wireplumber. 
That was a wrong assumption on my part.


Ross

--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio on Gnome (23.04)

[Ross Gammon]

Hi Erich,

Thanks for that great description of where we are at!

I don't really want to remove ubuntu-desktop because if I forget to 
reinstall it before I upgrade to 23.10 (Gnome) I could end up with some 
sort of Frankenstein installation.


The machine mainly does emails, web browsing and chromecastng these 
days, so I don't need a pro-audio set up on it as such. I will probably 
stick with pipewire on this machine and see where it takes me.


On 7/9/23 20:53, Erich Eickmeyer wrote:

Hi Ross,



<...>


However, as I read the PipeWire release notes, it might be unnecessary 
to use PulseAudio altogether and we might be able to deprecate it as 
well. Ubuntu 23.04 contains PipeWire 0.3.65. PipeWire 0.3.71 was 
released on 17 May and contains the following notable highlight:



  * A new zero-latency jackdbus bridge was added. This works similar
to what PulseAudio has to offer and creates a sink/source when
jackdbus is started. It is however much more efficient and runs
the complete PipeWire graph as a synchronous JACK client with no
added latency.


<...>


Then, a week ago, PipeWire 0.3.72 was released with this notable highlights:


  * A new module-netjack2-driver and module-netjack2-manager were
added that are compatible with NETJACK2. This allows PipeWire to
become a NETJACK2 manager or a driver between JACK2 or PipeWire
servers.
  * Support was added for firewire devices with FFADO. This is
untested for now and MIDI is not implemented yet.


I see pipewire 0.3.73 is now in Mantic!

<...>

The Gnome Settings under the Sound section allow you to choose inputs 
and outputs, and adjust volumes in a similar way that you could in 
pavucontrol - which is good.


qpwgraph is a QT GUI interface to wireplumber which is in Lunar. 
Unfortunately the GTK equivalent (Helvum) is not yet packaged for 
Debian. I will have a go with qpwgraph and see where it gets me.


I need to find some money and time to build a new Ubuntu Studio test 
machine. I have a spare USB audio interface now. Then I could try and 
help out with some more potentially destructive testing on Mantic.


Cheers,

Ross

--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Ubuntu Studio on Gnome (23.04)

[Ross Gammon]

Hi All,

As you may remember, one of my machines runs plain Ubuntu, has a spare 
USB Audio device plugged in, and I have been testing Ubuntu Studio on 
top of Gnome (ubuntustudio-installer did this for me several releases ago).


Last night I upgraded to 23.04 and as expected, saw that Studio Controls 
was removed. Running ubuntustudio-installer to install 
ubuntustudio-pulseaudio-config failed. To try and understand what might 
have gone wrong, I tried to install us-pulse*-config on the command 
line. It (apt) was going to remove ubuntu-desktop which I thought was a 
bad idea and said "no":


~$ sudo apt install ubuntustudio-pulseaudio-config
...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer 
required:

  libwireplumber-0.4-0 qpwgraph
Use 'sudo apt autoremove' to remove them.
The following additional packages will be installed:
  libasound2-plugins libpulsedsp pavucontrol pipewire-media-session 
pulseaudio

  pulseaudio-module-bluetooth pulseaudio-module-jack pulseaudio-utils
  python3-alsaaudio python3-cffi python3-jack-client python3-pycparser
  studio-controls zita-njbridge
Suggested packages:
  pavumeter paprefs
The following packages will be REMOVED:
  pipewire-alsa pipewire-audio pipewire-jack pipewire-pulse ubuntu-desktop
  ubuntu-desktop-minimal ubuntustudio-pipewire-config wireplumber
The following NEW packages will be installed:
  libasound2-plugins libpulsedsp pavucontrol pipewire-media-session 
pulseaudio

  pulseaudio-module-bluetooth pulseaudio-module-jack pulseaudio-utils
  python3-alsaaudio python3-cffi python3-jack-client python3-pycparser
  studio-controls ubuntustudio-pulseaudio-config zita-njbridge
0 upgraded, 15 newly installed, 8 to remove and 0 not upgraded.
Need to get 142 kB/1,906 kB of archives.
After this operation, 8,530 kB of additional disk space will be used.
Do you want to continue? [Y/n]

I have not looked into the dependencies to see if there is a way to 
untangle this. Instead, I was wondering if it was worth playing with the 
pipewire setup. It is a test setup after all! Does anyone know of any 
good guidance on the workflows in this set up? What would I use to help 
all of the routing between pipewire, jack, and how to use 
Ardour/Hydrogen/Carla etc.?


From the packages listed for removal above, I assume that wireplumber 
in the answer?


I did see some discussion on LAD, but I was hoping for some blog with 
easy instructions, screenshots etc. :-)


Cheers,

Ross

--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Backports PPA

[Ross Gammon]

Glad to hear the official Backports have been resurrected. Someone new 
to Ubuntu Studio and not aware of the ppa, is likely to follow the 
standard Ubuntu instructions to enable backports. Installing from a ppa 
is always a last resort for me.


I had to think a little bit about the decision not to backport to 
non-LTS releases. If someone installs a backport on an LTS, then 
upgrades their system to each intermediate release, they will only ever 
be 6 months behind the latest upstream release until they are back on 
the LTS (and re-enable backports).


If someone is more desperate than that, they can probably ask here on 
the list for a special ppa, or we can provide a link to instructions to 
do it for themselves?


Cheers,

Ross

PS: Sorry about the delay. I missed the email amongst all the automated 
build emails! :-)


On 29.03.2023 17.04, Erich Eickmeyer wrote:


Hi All,


As you all know, for the past several years, we've been maintaining a 
backports PPA for our users to add to their systems to get updated 
software. This has worked well for several reasons.



However, the Ubuntu Backporters team has been resurrected and is very 
active. To give it a try, I backported studio-controls from Lunar to 
22.04 LTS and was successful.



With that, I believe this should be the way we should backport 
packages in the future, and perhaps even sunset the backports PPA. One 
thing to keep in mind is that the official backports repository only 
supports LTS releases, which means we would only be backporting only 
to the latest supported LTS and not the regular releases.



Another approach could be backporting via the backports repo for the 
LTS releases but keeping the backports PPA active for the regular 
releases, but I'd rather not do this as it just feels sloppy and a 
work-around to change process.



I'd love to hear your thoughts about this. Thanks!


--

Erich Eickmeyer

Project Leader - Ubuntu Studio

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] MuseScore 4

[Ross Gammon]

Hi Paul,

Just to be clear. It is possible to package Musescore 4 in Ubuntu 
(without waiting for Debian), and maybe put it in a ppa. But that would 
require somebody with the necessary time and skills to volunteer.


Installing stuff from upstream (from the musecore website) can be risky, 
especially if you are running an older Ubuntu release. There could be 
incompatibilities in the version of libraries that Musescore 4 relies 
on. Will upstream support you in this case? Ubuntu certainly cannot 
support you. If you are desperate to use Musescore 4 (you cannot wait 
for Debian), then I would ask around if anyone has had success using the 
upstream version of Musescore 4 on your version of Ubuntu before doing 
it. Otherwise you may have to uninstall it later and clean up any mess 
yourself.


Regards,

Ross

On 14.02.2023 23.02, Erich Eickmeyer wrote:

Hi Paul,

Packages in Ubuntu may not be the latest. Ubuntu aims for stability, 
so "latest" may not be a good idea. Post-release updates are only 
considered if they are fixes for security vulnerabilities, high impact 
bug fixes, or unintrusive bug fixes with substantial benefit.


Furthermore, that package comes unchanged from Debian, which means 
there isn't an Ubuntu developer that touches it. So, this is really up 
to if Debian picks it up, but then it will only land in a later 
release. Additionally, Debian is coming up on their bi-yearly freeze 
in which they begin their release process for their next version, so 
there's probably not a whole lot of activity to be happening until 
later this year once that freeze starts.


All of that to say it's entirely out of our hands at this point on the 
Ubuntu Studio level as we're not the ones dealing with it; we're just 
putting it on the .iso image.


I hope you understand and I hope that helps.

--
Erich Eickmeyer
Project Leader
Ubuntu Studio


On Tue, Feb 14 2023 at 01:05:32 PM -08:00:00, Paul DeShaw 
 wrote:

Greetings,

Are there any plans to put the latest MuseScore version into the 
repository? Or should I just install it directly from musescore.org 
? I'm running last year's LTS--it's gotten so 
slow and glitchy I am reluctant to upgrade--so maybe that's why 
Synaptic isn't showing the latest MuseScore.


~PD
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio: We're out of space

[Ross Gammon]

Hi Erich,

On 25.03.2022 00.22, Erich Eickmeyer wrote:

With that, we've got the two most active people working on Ubuntu Studio
(myself and Len) who are onboard with the USB media idea. USB media is much
cheaper than it used to be, and more readily available than DVD-/+Rs. I'm OK
with increasing the size. We'll edit the ubuntustudio.org website to specify
that they may want to use a USB stick.



As a very inactive team member, I just wanted to add for the record that 
this sounds fine. In order to test the DVD, I was having to plug in a 
USB DVD read/writer to most of my machines anyway. The biggest issue is 
always having to unplug a USB device, to plug in the USB with the test 
ISO :-)


I am slowly starting to get used to having to use kde based tools/apps 
instead of X/gnome based tools. It is a pain many times, but sometimes 
better.


Keep up the good work.

Ross


--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Full ISO and some proposals

[Ross Gammon]

Hi Stewart,

You could try installing the Debian multimedia-musiciantools
metapackage. This pulls in Musescore, Lilypond and other tools.

The list is of packages is here:
https://blends.debian.org/multimedia/tasks/musiciantools

There is a bug which I need to fix though, because it does not pull in
the latest musescore package.

Cheers,

Ross

On 9/30/21 7:55 PM, Dr. Stewart Thompson wrote:
> Hi All,
> 
>  
> 
> I usually keep out of discussions but as a music publisher I felt this
> hits my area of work.
> 
>  
> 
> It sounds odd but I broadly support this, even as someone who has used
> Ubuntu Studio as a publishing tool. First and foremost is that even with
> the availability of MusicXML Sibelius, Finale and Dorico still dominate
> the publishing profession, Encore in the US and Capella in Europe also
> still have users. They then tend to move to Adobe in the publishing
> process. I use a mixture of this or MuseScore/Scribus etc to produce our
> materials but also produce in-house so don’t need to have too much issue
> with needing to interact. If it’s a big job or cross firm we boot up
> Windows and use what we need.
> 
>  
> 
> Realistically I’d rather have the audio set up and out of the box then
> add in publishing materials as I need. It’s generally a fairly small set
> of programmes so if you are pinching for space it makes sense.   
> 
>  
> 
> *Dr. Stewart Thompson BA(Hons) MA(Mus)(Open) D.Ed. CT,FVCM FCV SFFLM
> FGMS FMCM FIGOC FSCO FFSC FCollT FFSC HonFTCSM ACIEA*
> 
> | Qualifications Director | Victoria College Examinations | 71 Queen
> Victoria Street, London, EC4V 4AY | Telephone 020 7405 6483| Freefone
> from UK 08 0800 EXAMS | _www.vcmexams.com _*
> Encouraging performers since 1890 *
> 
>  
> 
> This email and any attachments transmitted with it are confidential and
> intended solely for the use of the individual or entity named. If you
> are not the intended recipient, any disclosure, copying or
> redistribution of this information is not permitted. If you have
> received this in error please notify the sender and delete it (including
> attachments) from your computer. Neither the sender nor Victoria College
> of Music and Drama, London accept any liability whatsoever for any
> defects of any nature in, or loss or damage arising from, this
> transmission. It is the responsibility of the recipient to ensure all
> materials are virus free. Any views or opinions expressed may be
> personal to the sender and not necessarily reflect those of Victoria
> College of Music and Drama, London.
> 
> *ü** */Please print this e-mail only if absolutely necessary - consider
> the environment!/
> 
>  
> 
> *From: *Erich Eickmeyer 
> *Sent: *30 September 2021 18:19
> *To: *ubuntu-studio-devel@lists.ubuntu.com
> 
> *Subject: *[ubuntu-studio-devel] Full ISO and some proposals
> 
>  
> 
> Hi all,
> 
>  
> 
> We hit a limit. Apparently, between Sunday the 26th and Monday the 27th,
> the
> 
> squashfs hit the technical limit of 4.0GB on our ISO image. Per ISO
> 9660, this
> 
> is a hard limit as the file system is incapable of having a single file
> more
> 
> than 4GB in size (the squashfs acts as a single file on the root of the
> ISO).
> 
> Unfortunately, this means we need to take a hard look at what we
> preinstall by
> 
> default and start eliminating some items.
> 
>  
> 
> As an emergency, I went ahead and removed a few duplicate items and one
> fairly
> 
> large item, but it opened my eyes to a bigger picture issue. More on that
> 
> later.
> 
>  
> 
> In terms of deduplicating functionality, I removed jackd (not jackd2) since
> 
> you can only have one anyhow. Also, I removed lmms which, in mine and Len's
> 
> opinion, is an application that is stuck in the past using the older ladpsa
> 
> (LV1) plugins and refuses to get any update. This is in favor of Ardour
> as our
> 
> DAW of choice.
> 
>  
> 
> Other items:
> 
>  
> 
> * Switched from ksysguard to the new plasma-systemmonitor for the desktop
> 
> * Removed raysession in favor of agordejo and new-session-manager combined,
> 
> which provides the same functionality with more backend support.
> 
> * Removed simple-scan in favor of skanlite (a KDE scanner app)
> 
>  
> 
> However, this is just a bandaid.
> 
>  
> 
> My proposal is that we drop publishing as a category of apps that we
> install
> 
> beginning with 22.04. My reasoning is that we're not very well-known for
> being
> 
> a desktop publishing platform, and it blurs the line between "studio" and
> 
> general-purpose. Moreover, people doing desktop publishing aren't exactly
> 
> looking at Ubuntu Studio as we rarely see any questions about it. In fact,
> 
> when people are reviewing Studio, they're a little surprised and
> perplexed to
> 
> see such tools.
> 
>  
> 
> Len pointed out that while we could remove the publishing items, he feared
> 
> that items in the graphics category would 

Re: [ubuntu-studio-devel] Full ISO and some proposals

[Ross Gammon]

Sounds like a good plan to me!

I remember having a hard time getting lmms updated in Debian, mainly due
to the old copy of calf-plugins being split out into a separate package.
But it is really meant to be a complete, integrated audio solution with
no need to install anything else. Which is really what our seeds are
trying to achieve anyway.

Way back, we were trying to get some "workflows" documented in the wiki
for the different seeds. We did not get much input on publishing. This
change will probably mean matching changes in the installer graphics and
project website.

On 9/30/21 7:19 PM, Erich Eickmeyer wrote:
> Hi all,
> 
> We hit a limit. Apparently, between Sunday the 26th and Monday the 27th, the 
> squashfs hit the technical limit of 4.0GB on our ISO image. Per ISO 9660, 
> this 
> is a hard limit as the file system is incapable of having a single file more 
> than 4GB in size (the squashfs acts as a single file on the root of the ISO). 
> Unfortunately, this means we need to take a hard look at what we preinstall 
> by 
> default and start eliminating some items.
> 
> As an emergency, I went ahead and removed a few duplicate items and one 
> fairly 
> large item, but it opened my eyes to a bigger picture issue. More on that 
> later.
> 
> In terms of deduplicating functionality, I removed jackd (not jackd2) since 
> you can only have one anyhow. Also, I removed lmms which, in mine and Len's 
> opinion, is an application that is stuck in the past using the older ladpsa 
> (LV1) plugins and refuses to get any update. This is in favor of Ardour as 
> our 
> DAW of choice.
> 
> Other items:
> 
>  * Switched from ksysguard to the new plasma-systemmonitor for the desktop
>  * Removed raysession in favor of agordejo and new-session-manager combined, 
> which provides the same functionality with more backend support.
>  * Removed simple-scan in favor of skanlite (a KDE scanner app)
> 
> However, this is just a bandaid.
> 
> My proposal is that we drop publishing as a category of apps that we install 
> beginning with 22.04. My reasoning is that we're not very well-known for 
> being 
> a desktop publishing platform, and it blurs the line between "studio" and 
> general-purpose. Moreover, people doing desktop publishing aren't exactly 
> looking at Ubuntu Studio as we rarely see any questions about it. In fact, 
> when people are reviewing Studio, they're a little surprised and perplexed to 
> see such tools.
> 
> Len pointed out that while we could remove the publishing items, he feared 
> that items in the graphics category would get removed. I assured him  that 
> this is not the case; that while there's some overlap, removing the 
> publishing 
> meta would not remove any graphics items since the graphics meta still pullse 
> those items in.
> 
> Removing the publishing meta would remove the following from the ISO:
> 
>  * scribus
>  * calibre
>  * pdfshuffler
>  * plume-creator
> 
> I know this doesn't sound like much, but I think it would be good to save 
> some 
> space and no longer support desktop publishing as a category of items we 
> install by default.
> 
> Let me know what you think.
> Erich
> 
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Big thanks to Dennis Braun and Ross Gammon!

[Ross Gammon]

Hi Erich,

No problems. It is easier when you are not starting from zero and there
is already packaging to work from. :-)

This way we only need to upload something in Ubuntu if Debian gets
behind for some reason.

As a note. Debian is in a soft freeze at the moment, so new upstream
releases will probably go into experimental rather than unstable. This
is so that they won't get in the way of a small targeted bug fix for the
bullseye release. But you can always sync from experimental to Ubuntu if
required.

I would like to get StudioControls, Carla and one of the session
managers into Debian too.

Cheers,

Ross

On 04/03/2021 20:21, Erich Eickmeyer wrote:
> Hi Ross and Dennis,
> 
> I just wanted to thank you both for taking some packages I had downstream in 
> Ubuntu and upstreaming them to Debian. Dennis, you've been doing some great 
> work, and for that I'm thankful!
> 
> I most recently saw dragonfly-reverb making its way into sid, and when the 
> build was complete I did a quick syncpackage. Of course, the very next day 
> (today), dragonfly-reverb 3.2.4 was released (looks like a fairly trivial 
> bugfix), so now the package is a wee bit out of date. :)
> 
> Anyhow, I've also noticed numerous other packages (dpf-plugins, among 
> others). 
> Since I got a job working on the Kubuntu Focus laptop, these packages getting 
> upstreamed reduces my maintenance workload on Ubuntu Studio.  Granted, after 
> Debian Import Freeze the workload is slightly higher, but every little bit 
> that you're doing helps.
> 
> Dennis, I'd love to include you as part of the Ubuntu Studio team since your 
> work is directly affecting Ubuntu Studio. What do you think?
> 
> And big thanks to Ross for being the amazing DD and sponsoring these 
> packages. 
> You do amazing with supporting Ubuntu Studio from the Debian side, and I'm 
> glad you're on the team.
> 
> As you both probably know, there are numerous other packages which could 
> stand 
> to be upstreamed as well. If you see anything that is Ubuntu-only, feel free 
> to take it on.
> 
> Again, thank you both. Also CC'd the ubuntu-studio-devel mailing list so that 
> others could see the work that you're doing. :)
> 
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Future of Jamin

[Ross Gammon]

Hi,

I was taking a look at some of the build failures for our packages
(archive rebuild for GCC-10), and Jamin is one that is failing.

Upstream have not committed anything since 2015 (sourceforge) and I
could not find a valid fork.

Jamin was removed from Debian Testing in 2017 and nobody has stepped
into maintain the package there (Jonas has stepped down). It was kicked
out of testing for the same GCC-10 issue.

It is likely that it will be removed from Debian.

Should we preemptively remove Jamin from our seeds? I assume it's
typical use case of taking over mastering from Ardour is no longer
important?

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Updates from me

[Ross Gammon]

Hi Erich,

On 17/11/2020 18:54, Erich Eickmeyer wrote:
> Also, during the previous cycle, somehow I got the attention of the
> people behind the Kubuntu Focus project, which is the laptop with the
> Kubuntu brand on it. You can check it out at kfocus.org. It is one
> powerhouse of a machine! That said, they have reached-out to me and
> hired me to do their packaging for the machine-specific repositories
> that ship with the laptop for things such as power management and other
> optimizations, and to keep their "curated software" maintained in a
> backports repository of sorts since they stick with the LTS release. For
> now, it is a temporary, part-time position.

Congratulations on the new job. It was on my radar to look into a new
Development laptop. The current one was a "what is the cheapest laptop
you have?" purchase on the way through the airport to FOSDEM in Brussels!
US-based Debian Developers have been offered discounts from Lenovo, but
so far this doesn't apply for European DDs.
Kfocus looks interesting. Do you know if there are plans to ensure a
smooth upgrade to the next LTS? I would hate to be trapped on 20.04
relying on backports forever.
So far all of my Ubuntu Studio machines are desktop units as I have
never had the need to do music on the run (all of my instruments are too
big to carry, and I rarely get a project to the mixing stage that can't
wait a few weeks anyway). :-) But I would probably use the US installer
anyway to overlay Ubuntu Studio so that the possibility was there.

> That said, since it has become my day job, it is now my focus (no pun
> intended). I'm not leaving Ubuntu Studio, but I want to make you aware
> of my time commitment. As part of this, I'm reserving evenings and
> weekends for time with my family. I have no problem answering questions
> via IRC/Matrix, but if I don't respond on the weekends, just know that
> this is why.

Enjoy your weekends!

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Congratulations on Ubuntu Studio being so Groovy

[Ross Gammon]

Hi All,

I apologise for being a little bit absent during the Groovy release
cycle. There were a few personal issues to sort out which I don't want
to go into on a public list.

But I have actually been running Ubuntu Studio Groovy for the last month
on a spare machine in my Study. And I am starting to get used to
KDE/Plasma which I have never used before. The machine will probably be
moved into my little music studio eventually, as it is a much newer and
faster machine.

I just wanted to sing the praises of all the fantastic work that has
been going on while I was on the sidelines! Great stuff.

And also to say that I should be able to spend a bit more time helping
out this coming cycle.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Relocating, packages awaiting review, KFocus

[Ross Gammon]

Hi Erich,

On 17/08/2020 20:53, Erich Eickmeyer wrote:
> Over the course of the next two weeks, we will be relocating. I will
> have relatively limited access to many of the tools I use. I'm prepping
> for giving myself access to what I can, but my main computer will be
> packed-up this week.

I hope the move goes smoothly. I will hopefully have to move house at
the end of the month myself (if the paperwork gets done on time).

I will have my Ubuntu development machine accessible until the last
minute. But my Ubuntu Studio machine and test machine have already been
packed!

Cheers,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Pre-Installed Application Review

[Ross Gammon]

Thanks Len as always for the intelligence on the different plugins. I
think one of the downsides of now having the extra plugin packages, is
that there is so many to choose from!

Just an idea -
The Debian Multimedia Blends has an audio plugins task with all the
known linux plugins packaged (and maybe one day) packaged for Debian:
https://blends.debian.org/multimedia/tasks/audio-plugins

We could add the multimedia-audio-plugins metapackage to our
ubuntustudio-installer for anyone that wants "all the linux plugins",
and then offer a more discerning set in our seed.

On 12/05/2020 21:45, Hank Stanglow wrote:
> On 5/12/20 8:45 AM, Len Ovens wrote:
>> I would rather answer a few more times why studio doesn't include
>> Calf, that see them continuously recomended as first choice. I see
>> Calf as a "well you can of course install them from the repos but we
>> will not give support if you have trouble with them".
>>
> Interesting, I hadn't known about problems in Calf. They were the
> plugins I always used first because they had a good mix of sound,
> simplicity, and style, but now I use LSP and Xhip effects for everything
> because I either need something that is really detailed or really
> simple. However, I do like that Calf Fluidsynth frontend and their
> simple synths so I would definitely install Calf immediately on a new
> setup.
> 

Cheers,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Pre-Installed Application Review (effective for 20.10)

[Ross Gammon]

On 11/05/2020 00:23, Erich Eickmeyer wrote:
> Len and I have discussed removing the Calf plugins from the default
> install since lsp-plugins covers the things that Calf can do (and then
> some), and Calf has a tendency to be prone to crashing when used in Ardour.

I thought we had fixed that Ardour crash problem by removing the old
version of calf-ladsp that was bundled with lmms? Do we still get bug
reports of these crashes?

Anyway, I can't comment if the lsp-plugins offer the same
functionality/quality as the calf ones (as I have not used either of
them enough).

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Jackd2 1.9.14

[Ross Gammon]

Hi Erich,

I am extremely busy with work this month. I will try and take a look
sometime this week.

It uses cdbs, and repacks the source to exclude files, so it is not a
package I would look to start maintaining with my life being as it is! I
will look at doing a Team Upload instead.

On 09/05/2020 18:57, Erich Eickmeyer wrote:
> Hey all,
>
> This is mostly a message for Ross. Ross, would you mind updating Jackd2
> in Debian to the latest version? I already have done much of the legwork
> in https://code.launchpad.net/~ubuntustudio-dev/+git/jackd2. It builds,
> is lintian-clean minus the non-existent manpages, and while I *could*
> upload it, I would rather this be upstreamed to Debian and maintained there.
>
> So, with that, I was wondering if you'd be so kind[1][2] as to upstream
> this? I'll take what I've got and put it in the Backports PPA.
>
> Thanks,
> Erich
> 
> Erich Eickmeyer
> Project Leader
> Ubuntu Studio
>
> ubuntustudio.org
>
> [1]Please?
> [2]Pretty please?
>
>

Cheers,

Ross




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Displaycal

[Ross Gammon]

On 08/04/2020 14:32, Ross Gammon wrote:
> 
> Upstream have not updated to Python 3 in time.
> 

I forgot the link to the upstream discussion for reference:
https://hub.displaycal.net/issue/17813/



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Displaycal

[Ross Gammon]

Hi All,

I have finally been able to start my Easter holiday, and started looking
at the packages with build failures in focal.

It looks like we might loose displaycal from the photography seed.

Upstream have not updated to Python 3 in time.

I suppose we could add it to the backports-ppa if it gets fixed after
release.

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] LiveFS ubuntustudio/focal/amd64 failed to build on 20191119

[Ross Gammon]

Excellent. We just wait.

On 11/20/19 4:14 PM, Erich Eickmeyer wrote:
> Hi Ross,
> 
> On 11/20/2019 6:25 AM, Ross Gammon wrote:
>> This doesn't look like it is going away by itself!
>>
>> The standard seed pulls in ntfs-3g which pulls in fuse. This is probably
>> not something we should fiddle with.
>>
>> Kdenlive is pulling in fuse3 (which conflicts with fuse) via a tortuous
>> dependency path. But there are a couple of "recommends" in the path.
>> Near the bottom of the chain, qml-module-org-kde-purpose only recommends
>> kdeconnect.
>>
>> Should we try temporarily blacklisting kdeconnect?
>>
>> Cheers,
>>
>> Ross
>>
> I've already been talking to the release team about this (specifically
> Adam Conrad). Unfortunately, there's nothing we can do from our side.
> fuse and fuse3 are meant to be co-installable, so basically somebody
> upstream in Debian screwed-up. Adam is already working on some sort of
> fix in Ubuntu which he intends to push upstream.
> 
> Thanks,
> Erich
> 
> 




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Ubuntu Studio - 19.10 Eoan flickering pixels

[Ross Gammon]

Hi All,

I had the chance to have a play with the soon to be released Ubuntu
Studio today. Work has kept me away from the study for the last few
weeks. It was not the beta I tested, as I had already installed a Daily
image. I did do an "apt upgrade" though.

It is looking good!

I did have to report an annoying display bug though. I am getting
flickering blotches (until you move the mouse away) and the occasional
green screen. It doesn't happen on 18.04, 18.10 and 19.04 which I still
have on the same machine.

https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1845874

Any help diagnosing what the problem might be is welcome. On the bug please!

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] On Vacation & Feature Freeze

[Ross Gammon]

On 8/22/19 2:09 PM, eeickme...@ubuntu.com wrote:
> For session handling, we're including raysession which uses much of the Non 
> Session Manager API. We cannot include Non Session Manager itself as the way 
> its source code is arranged conflicts with the method used for Ubuntu and 
> Debian packaging. Really, it's a long story, but the method of packaging that 
> would be used is incompatible.

Jaromir started packaging NTK in preparation for the Non-* stuff. From
memory the packaging was hard, but not impossible. He is not so active
these days. I could try picking up where he left off if it is worth the
effort. Obviously,like everything I do, it would take some time.

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Package Tracker

[Ross Gammon]

Hi All,

I have now fixed the package tracker so we have a page that shows only
the packages in our Ubuntu Studio package set (that I have upload rights
to):
http://people.ubuntu.com/~rosco2/ubuntustudio-packageset.html

I have also fixed it so build and ~dfsg etc. suffixes in the package
version are managed better in the comparisons with upstream.

At the moment there are approx 17% of these packages with new available
versions. I am working on packages in the Debian Multimedia Team where
Debian is behind upstream.

There are also 17% of packages that have no upstream identified. Many of
these are just errors in the Debian watch files. I am slowly going
through these to find out where the packages came from.

I still run the script & upload manually, so if you notice that the
webpage is way out of date, feel free to ping me.

Cheers,

Ross

On 4/25/19 1:14 PM, Ross Gammon wrote:
> Hi All,
> 
> Now that Erich and I have permission to upload some stuff, Erich and I
> discussed with cyphermox on IRC if there were any websites we could
> tweak to get a view of the state of our packages.
> 
> I have forked one of the suggestions and had a bit of a play:
> http://people.ubuntu.com/~rosco2/ubuntustudio.html
> 
> At the moment I am manually uploading to my people.ubuntu.com site. Once
> we have it working, we should look for a less manual solution.
> 
> It shows all of the packages that "germinate" generates from our seed.
> This is a lot of packages (2000 odd). I tried generating an additional
> page that just shows the packages tagged as being in our package-set,
> but this has a bug at the moment where all the same packages are tagged
> as on the main page.
> 
> I added some code to find the upstream version using the Debian "watch"
> service. This slows things down greatly (40 odd minutes to run the
> script), but saved me manually entering all the upstream URLs.
> 
> Despite this, there are still quite a few "untracked" packages that we
> need to find the correct upstream for (and add this to packages.py).
> 
> Regards,
> 
> Ross
> 
> 




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] -controls tweaks

[Ross Gammon]

Hi Len,

You are right. My test machine only has motherboard sound, and a USB
device (Alesis iO2) which is very portable (but only 2 inputs at a time).

Most of the time it "just works", and it is only when I fiddle that I
get myself into unusual states :-)

But I will test and report back.

Incidently, we should probably create a suite of manual tests we could
point testers at between now and 20.04 (LTS):
http://packages.qa.ubuntu.com/
We have not used it for a few releases, but it could be resurrected.

Ross

On 4/27/19 9:06 PM, Len Ovens wrote:
> Rather than mucking up the bug comments... Ross, I think that you were
> the one who has only a USB device. In any case, that should also be
> fixed as a part of correcting defaults. please check for this. Removing
> ~/.config/autojackrc should show if th9is is so. you should not have to
> set up USB as master expicitely it should do that on it's own. The jack
> master box should sho USB and the USB master box should show your device.
> 
> In a new install, jack is disabled at boot and in order to start jack
> the user has to open -controls and select start jack. Start jack will
> save the configuration and use it to start jack. This should default to
> using your USB device without you having to select it.
> 
> I can't test this without taking my machine apart and removing cards and
> later reinstalling them. Doing this repeatedly will cause problems
> sooner rather than later as the PCI slots are not high use plugs.
> 
> -- 
> Len Ovens
> www.ovenwerks.net
> 
> 




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ISO Tests

[Ross Gammon]

Hi Len,

I have uploaded a new ubuntustudio-controls (v1.8) that fixes things so
us-controls starts with the settings from the last saved config file.

Your changes in git (mentioned below) did not seem to have been pushed,
so unless you were working in a branch, you might have trouble rebasing
on my changes. Sorry about that in advance.

Over the weekend, I will start on an SRU for disco.

Cheers,

Ross

On 4/16/19 11:42 PM, Len Ovens wrote:
> On Tue, 16 Apr 2019, Thomas Pfundt wrote:
> 
>> Most of the test cases worked fine, but in my live system and the
>> first boot on
>> the full install, I wasn't able to get any sound with Controls alone.
> 
> I should ask what kind of Which sound card first off. Assuming the
> system uses pulse for something before controls is started, Pulse will
> turn the audio card up... if it knows which controls do this. So my old
> Delta 66 has never come up on a new install with sound coming out unless
> I turn it up using mudita24, alsa mixer or qasmixer. It may be
> reasonable to allow qasmixer to be opened from within controls for this
> reason.
> 
>> I don't know what exactly the issue was, but I had to reboot once for
>> it to work
>> (it was set to load on startup). Is this something to be expected or
>> should I
>> investigate this further? (I still have the test system installed the
>> way it
>> was.)
> 
> On first startup, jackd should not be running but pulse should be. Once
> controls is used start jack, it should be running on the next boot if it
> was running at shutdown.
> 
> While my personal opinion, is that the most stable way to run audio is
> to always run jack as the backend for pulse, there may be those who's
> main focus is graphics, animation or video and would like to have every
> bit of cpu possible available for rendering. These people may want just
> pulse on their system and probably do want hyperthreading and Boost
> enabled, both of which are bad for low latency audio. (USB is bad for
> low latency audio as well, but that is what we are generally left with
> that most of us can afford) So there need to be choices and sane
> defaults. In the case of jcak starting at session start, My feeling is
> that in most cases the user needs to set latency and device the first
> time they run the system anyway (the default device on my system has no
> speakers hooked to it as it is only used for it's MIDI port)
> 
>> Otherwise, great UI. Very clear and easy to understand. I'd suggest
>> though that
>> it could be helpful to see the current Jack status (running or off),
>> else there
>> isn't a clear response from the start/restart button.
> 
> Already been changed in git.
> 
> Controls is under active development (along with installer and soon to
> be menu_wrecker)
> 
> -- 
> Len Ovens
> www.ovenwerks.net
> 
> 




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Package Tracker

[Ross Gammon]

Hi All,

Now that Erich and I have permission to upload some stuff, Erich and I
discussed with cyphermox on IRC if there were any websites we could
tweak to get a view of the state of our packages.

I have forked one of the suggestions and had a bit of a play:
http://people.ubuntu.com/~rosco2/ubuntustudio.html

At the moment I am manually uploading to my people.ubuntu.com site. Once
we have it working, we should look for a less manual solution.

It shows all of the packages that "germinate" generates from our seed.
This is a lot of packages (2000 odd). I tried generating an additional
page that just shows the packages tagged as being in our package-set,
but this has a bug at the moment where all the same packages are tagged
as on the main page.

I added some code to find the upstream version using the Debian "watch"
service. This slows things down greatly (40 odd minutes to run the
script), but saved me manually entering all the upstream URLs.

Despite this, there are still quite a few "untracked" packages that we
need to find the correct upstream for (and add this to packages.py).

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Slowmovideo

[Ross Gammon]

Hi All,

Slowmovideo was a wishlist for Ubuntu Studio for a long time. It has
been packaged for Debian now, and is therefore available in Ubuntu.

Does anyone have any objections to adding it to our Video seeds? Or do
we already have similar functionality in another package?

Comments from those who work with video stuff would be welcome (here or
on the bug):
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/815101

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Ubuntu Studio Installer on Gnome

[Ross Gammon]

Hi All,

Before I was interrupted by another ISO Release Candidate to test, I had
been testing turning the bog-standard Ubuntu install (Ubuntu 18.04,
18.10) into Ubuntu Studio.

This is just an interim report that I had a couple of crashes (actually
freezes/stalls). I need to go back and continue the test. And if
required, properly document the crash and extract logs.

The first freeze happened with Firefox, hexter and qjackctl open on
Bionic. Everything froze (mouse unusable), and the only way out was a
kill with RELSUB. It is possible I should have done a reboot before
starting to play.

The second was on Cosmic, and this time ubuntustudio-installer stalled.
I see there is a bug (with fix released) to give more feedback of what
apt is doing:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-installer/+bug/1309536
But without this, I suppose I should be able to dig out some apt logs.

Wish List
-

Gnome doesn't have a menu. Yes I know - I don't want to start a flame
war and comparison of Desktops :-)
Using standard Ubuntu (Unity and Gnome) for years for non-audio stuff,
this has never been a problem for me. All my favourite apps are pinned
so I can just click on the icon, and I am mostly in the terminal anyway.
It is very rare that I have to remember the name of that (e.g. scanning
app) and type the first letters to execute it (if it isn't sitting in
the "frequently used" category).

But what is the name of that wierd synthesizer or plugin? Plugins can be
partially solved by pinning carla I suppose. But...

Wouldn't it be great if you could start the Ubuntu Studio menu from some
panel in gnome. Or have some other category based app launcher. I did a
search and there are some extensions out there, but nothing conclusive.
Meow looked promising, but didn't seem to have a way of loading a
configuration for users at install time.
Any ideas?

Ross





signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] CALL FOR TESTING: 19.04 Pre-RC Images Are Ready!

[Ross Gammon]

Giving it a spin.

I love that Disco Dog!

On 4/14/19 12:56 AM, Erich Eickmeyer wrote:
> Hi All,
> 
> Images for the pre-RC release are ready for testing at http://
> cdimage.ubuntu.com/ubuntustudio/dvd/20190413.1/
> 
> Please log-in to the ISO tracker to log your results at https://
> iso.qa.ubuntu.com.
> 
> Happy testing!
> Erich
> 
> Erich Eickmeyer
> Council Chair
> Ubuntu Studio
> 
> ubuntustudio.org
> 
> 
> 




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] xfce4-screensaver

[Ross Gammon]

Hi Erich,

On 3/10/19 12:43 AM, Erich Eickmeyer wrote:
> Hi all,
> 
> Sean Davis (bluesabre) did an amazing job and ported mate-screensaver to
> xfce4-screensaver. The motivation, as I understand it, is because
> light-locker is largely unmaintained and causes a race condition when
> resuming from sleep due to the vt change (or something like that, we
> don't need to get too technical on this).
> 
> With that, light-locker and xscreensaver are being largely depricated by
> the Xubuntu team (who can correct me if I'm wrong... well, anybody can
> correct me) in favor of xfce4-screensaver. I think this change, if it
> needs to happen in our seeds, needs to happen.
> 
> If you want to test it first, that's good practice. That said, I can say
> from personal experience that I have experienced the light-locker race
> condition myself, and it's definitely not a good bug to have.
> 
> Anyhow, we don't need to make this change immediately. Our priority
> right now is the Developer Membership Board meeting happening on Monday
> at 1500 UTC (I may have posted that this was at 1200 UTC, that was a
> mistake) for mine and Ross's applications for Per-Package Uploader
> permissions. My application, I expect, will be rejected due to lack of
> experience, so I'm in it mostly for the feedback. However, we're hoping
> for success with Ross's application, which is getting a lot of support
> at present.
> 
> With that, I want to say that this change in the seed, if necessary,
> isn't as high of a priority, but it would bring some good bug fixes to
> our default Xfce desktop.

The last time we discussed screensavers was quite a while ago when Kai
was still in charge and we decided to remove our Ubuntu Studio
screensaver package becasue it was broken and we didn't have it in the
seeds anyway.

There was some discussion about the use of screensavers in general and
it was decided that in the days of flatscreens the original purpose has
disappeared, and the fact that in audio and video we might want to watch
some rendering/mastering chuntering along for quite a while, that
screensavers did not make much sense. I think the power management
settings would need to be fiddled with to get the screensaver to work
instead of blanking.

But I suppose we could test it as a replacement for light-locker and see
how it goes with audio/video work. I have not had a computer with a
screen saver for so many years (at work or at home), I have forgotten
what it is like :-)

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] LiveFS ubuntustudio/disco/amd64 failed to build on 20190309

[Ross Gammon]

Hi Erich,

On 3/10/19 1:55 PM, Ross Gammon wrote:
> Hi Erich,
> 
> It seems there is a problem with the plymouth theme post-install
> maintainer script in ubuntustudio-look.
> 
> On 3/9/19 7:31 PM, CD Image wrote:
>> Setting up plymouth-theme-ubuntustudio (0.57) ...
>> update-alternatives: using 
>> /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth to 
>> provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in 
>> auto mode
>> update-alternatives: using 
>> /usr/share/plymouth/themes/ubuntustudio-text/ubuntustudio-text.plymouth to 
>> provide /usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode
>> update-initramfs: diverted by livecd-rootfs (will be called later)
>> /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
>> dpkg: error processing package plymouth-theme-ubuntustudio (--configure):
>>  installed plymouth-theme-ubuntustudio package post-installation script 
>> subprocess returned error exit status 1
> 
> I haven't tried upgrading my test Disco machine yet, which I will do
> some time today. Any ideas?
> 
> Cheers,
> 
> Ross
> 

Well, the update went fine on an already installed Disco:
Setting up plymouth-theme-ubuntustudio (0.57) ...
update-alternatives: updating alternative
/usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth
because link group default.plymouth has changed slave links
update-initramfs: deferring update (trigger activated)
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.19.0-13-lowlatency
Found initrd image: /boot/initrd.img-4.19.0-13-lowlatency
Found linux image: /boot/vmlinuz-4.19.0-13-lowlatency
Found initrd image: /boot/initrd.img-4.19.0-13-lowlatency
Found Ubuntu 18.10 (18.10) on /dev/sda2
Found Ubuntu 18.04.2 LTS (18.04) on /dev/sdb1
Found Ubuntu 18.10 (18.10) on /dev/sdb2
Found Ubuntu Disco Dingo (development branch) (19.04) on /dev/sdb3
Adding boot menu entry for EFI firmware configuration
done

I am a bit out of my comfort zone here, but it seems that /dev might not
mounted at this stage in the LiveCD installation process.

Do we need to add back in the guard that was taken out recently?:
if [ -e /boot/grub/grub.cfg ] && which update-grub2 >/dev/null 2>&1; then

Using Debian Code Search, I found a few other packages where this is
used and the comments mention being in a build chroot:
https://codesearch.debian.net/search?q=path%3Adebian%2F*.postinst+update-grub

Cheers,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] LiveFS ubuntustudio/disco/amd64 failed to build on 20190309

[Ross Gammon]

Hi Erich,

It seems there is a problem with the plymouth theme post-install
maintainer script in ubuntustudio-look.

On 3/9/19 7:31 PM, CD Image wrote:
> Setting up plymouth-theme-ubuntustudio (0.57) ...
> update-alternatives: using 
> /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth to 
> provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in 
> auto mode
> update-alternatives: using 
> /usr/share/plymouth/themes/ubuntustudio-text/ubuntustudio-text.plymouth to 
> provide /usr/share/plymouth/themes/text.plymouth (text.plymouth) in auto mode
> update-initramfs: diverted by livecd-rootfs (will be called later)
> /usr/sbin/grub-probe: error: cannot find a device for / (is /dev mounted?).
> dpkg: error processing package plymouth-theme-ubuntustudio (--configure):
>  installed plymouth-theme-ubuntustudio package post-installation script 
> subprocess returned error exit status 1

I haven't tried upgrading my test Disco machine yet, which I will do
some time today. Any ideas?

Cheers,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Yay! Seeds?

[Ross Gammon]

Excellent, I am sure you are right! I just hadn't finished checking all
the dependencies etc. It will all become clear soon anyway :-)

I have just added lmms back to the seeds. I have to go out for a bit,
but when I get back I will trigger a Live-CD rebuild and hopefully we
get no failures!

Cheers,

Ross

On 3/7/19 5:15 PM, Erich Eickmeyer wrote:
> Hi Ross. amd sorry for top-posting,
> 
> The themes are as follows:
> 
> GTK: materia-gtk-theme
> Icons: papirus-icon-theme
> 
> Those are both pulled-in by -default-settings, so I can't imagine they
> need to be added to the seed directly.
> 
> Likewise, grub2-themes-ubuntustudio is a dependency in -look for the
> plymouth theme, which is already in the seed, so I can't imagine it
> needs to be added to the seed directly.
> 
> Unless, of course, you know something I don't (which, as we all know, is
> likely!).
> 
> Thanks,
> Erich
> 
> On Thu, Mar 7, 2019 at 8:00 AM, Ross Gammon  wrote:
>> Hi All,
>>
>> Thanks to a huge amount of work by Erich and Len, and a recent push by
>> several sponsors, we have a whole heap of new packages ready for testing
>> and release for Disco (to be 1904). Well done guys!
>>
>> Carla and the new grub theme are still in the NEW queue, but will
>> hopefully be processed soon.
>>
>> There was one little snag with some files moving between packages, which
>> I had spotted - but not had time to fix. But luckily Dmitry spotted it
>> and followed up with a Breaks/Replaces fix.
>>
>> I will start preparing an update to our meta package now that the fixed
>> lmms has made it into the archive.
>>
>> Erich,
>>
>> I am not clear about which seeds all the new themes etc. should be added
>> to. Can you take a look at this, and maybe make a note in the relevant
>> ubuntustudio-meta bug so we are ready to go when the two NEW packages
>> are available?
>>
>> Regards,
>>
>> Ross
>>
>> -- 
>> ubuntu-studio-devel mailing list
>> ubuntu-studio-devel@lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
> 
> 
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Yay! Seeds?

[Ross Gammon]

Hi All,

Thanks to a huge amount of work by Erich and Len, and a recent push by
several sponsors, we have a whole heap of new packages ready for testing
and release for Disco (to be 1904). Well done guys!

Carla and the new grub theme are still in the NEW queue, but will
hopefully be processed soon.

There was one little snag with some files moving between packages, which
I had spotted - but not had time to fix. But luckily Dmitry spotted it
and followed up with a Breaks/Replaces fix.

I will start preparing an update to our meta package now that the fixed
lmms has made it into the archive.

Erich,

I am not clear about which seeds all the new themes etc. should be added
to. Can you take a look at this, and maybe make a note in the relevant
ubuntustudio-meta bug so we are ready to go when the two NEW packages
are available?

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] [Ubuntu Studio] Cry For Help

[Ross Gammon]

OK - good catch. Strange that the |"dh_missing --fail-missing" didn't
pick up that these files were not installed!  |

On 05/03/2019 02:03, Erich Eickmeyer wrote:
> Hi Ross (and good morning by the time you likely read this),
>
> On Mon, Mar 4, 2019 at 8:02 AM, Ross Gammon 
> wrote:
>> On 3/4/19 4:30 PM, Erich Eickmeyer wrote:
>>
>> Hi Ross, On Mon, Mar 4, 2019 at 3:09 AM, Ross Gammon
>> mailto:ro...@ubuntustudio.org>> wrote:
>>
>> [snip] carla-bridge-wine{64|32} are empty packages that just
>> depend on wine etc. Is there any reason why
>> carla-bridge-win{64|32} could not depend on wine etc. instead
>> of depending on an empty package that depends on wine? It
>> would simplify things and get rid of some lintian warningsI'l 
>>
>> I'll check on this with FalkTX and see if he has any answers. Erich 
>>
>> Thanks. I had to go shopping for more pain-killers, and followup on
>> some Debian bugs (including one I reported) about false-positive
>> lintian warnings. That is the last potential change, then I will
>> finalise and ask for sponsorship. Ross
> Excellent. However, I found the missing .install files for the wine
> bridges and reverted the commit to debian/control. Now the packages
> are no longer empty and should contain the requisite files.
> I'll go ahead and make some install logs and screenshots.
>
> Erich
>


signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] [Ubuntu Studio] Cry For Help

[Ross Gammon]

On 3/4/19 4:30 PM, Erich Eickmeyer wrote:
> Hi Ross,
> 
> On Mon, Mar 4, 2019 at 3:09 AM, Ross Gammon  wrote:
>> [snip]
>> carla-bridge-wine{64|32} are empty packages that just depend on wine
>> etc. Is there any reason why carla-bridge-win{64|32} could not depend
>> on wine etc. instead of depending on an empty package that depends on
>> wine? It would simplify things and get rid of some lintian warningsI'l 
> 
> I'll check on this with FalkTX and see if he has any answers.
> 
> 
> Erich
> 

Thanks. I had to go shopping for more pain-killers, and followup on some
Debian bugs (including one I reported) about false-positive lintian
warnings.

That is the last potential change, then I will finalise and ask for
sponsorship.

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] [Ubuntu Studio] Cry For Help

[Ross Gammon]

Hi Erich,

Hopefully I will finish Carla today. I am sitting at home with a numb
mouth after the dentist attacked me ;-)

On 3/3/19 11:31 AM, Ross Gammon wrote:
> One was about a missing dependency on python. The correct way to fix
> this is to build with dh-python (pybuild) and put a ${python3:Depends}
> in debian/control so that python is added automatically as a dependency.
> But this builds a whole heap of cython files that I wasn't too sure
> about, so I dropped it until I had more time to investigate.

I have added python3 manually as a dependency of carla.

> 
> The other was a warning about an empty package which sounded a bit serious.

carla-bridge-wine{64|32} are empty packages that just depend on wine
etc. Is there any reason why carla-bridge-win{64|32} could not depend on
wine etc. instead of depending on an empty package that depends on wine?
It would simplify things and get rid of some lintian warnings.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] [Ubuntu Studio] Cry For Help

[Ross Gammon]

Hi Erich,

I spent loads of time last weekend working on Carla. Trying to add all
the copyright notices for all the embedded software took by far the
longest. There were some strange warnings which I ran out of time to dig
into.

One was about a missing dependency on python. The correct way to fix
this is to build with dh-python (pybuild) and put a ${python3:Depends}
in debian/control so that python is added automatically as a dependency.
But this builds a whole heap of cython files that I wasn't too sure
about, so I dropped it until I had more time to investigate.

The other was a warning about an empty package which sounded a bit serious.

I will keep working on Carla, and then move on to the others.

It looks like there are some serious archive issues at the moment
(including serious bugs that require a new round of testing for the
Xenial ISO, and a glibc tranistion - which is now the new thing holding
up the fixed lmms by the way). These things normally keep potential
sponsors busy, and it is normal for stuff to be uploaded right up to the
release.

You are doing the right thing in keeping the bugs up to date, and
letting the developer mailing lists know we need help.

Regards,

Ross

On 3/3/19 3:50 AM, Erich Eickmeyer wrote:
> 
> Hi all,
> 
> I've done what I can to get lintian output and links to the PPA (in this
> case, the Ubuntu Studio Developer's Autobuilds PPA) in the bug reports,
> along with the tags. If anyone can help me with getting this finished,
> that would be great.
> 
> Erich
> 
> 
> On Sat, Mar 2, 2019 at 2:09 PM, Erich Eickmeyer
>  wrote:
>>
>>
>> On Sat, Mar 2, 2019 at 11:54 AM, Erich Eickmeyer
>>  wrote:
>>> [Sent to: Ubuntu Studio Development, Ubuntu MOTUs, Ubuntu Release
>>> Team] Hello all, Over the course of the past few months, myself, Len
>>> Ovens, and Ross Gammon have been working hard on updating the Ubuntu
>>> Studio tools. In particluar, we have done a number of things to the
>>> tools: * Updated Ubuntu Studio Controls (ubuntustudio-controls) with
>>> a number of bug fixes * Renamed Ubuntu Studio Meta Installer to
>>> Ubuntu Studio Installer (ubuntustudio-installer) and gave it a
>>> secondary purpose of installing Ubuntu Studio's stack on top of a
>>> flavor other than Ubuntu Studio (think of Ubuntu Studio as a ToolKit)
>>> * Updated Ubuntu Studio's default theme and icon theme (part of
>>> ubuntustudio-look and ubuntustudio-default-settings in addition to
>>> ubuntustudio-icon-theme) * Updated Ubuntu Studio's plymouth boot
>>> theme (part of ubuntustudio-look) * Added a GRUB theme
>>> (grub2-themes-ubuntustudio) * Fixed bugs and missing apps in our menu
>>> (ubuntustudio-menu) * Worked upstream with the developer of Carla to
>>> get Carla in Ubuntu's repos. Unfortunately, none of that made it in
>>> before feature freeze, despite my mailing our development list that
>>> it needed to happen, and tagging certain packages with [needs
>>> packaging]. Perhaps I'm just doing it wrong. Basically, it comes down
>>> to this: Nobody on the Ubuntu Studio Team has upload privileges in
>>> any way. As such, these tools are sitting waiting to be uploaded. So
>>> now, unless I'm wrong, each one of the packages now needs a Feature
>>> Freeze Exception to be uploaded into the repo. This is disappointing
>>> because, as of right now, Ubuntu Studio 19.04 is looking identical to
>>> Ubuntu Studio 18.10. My intention was to apply to become a MOTU after
>>> the release of 19.04 in order to prevent situations like this from
>>> happening again. Unfortunately, it looks like that will be too late
>>> unless we can get someone to get in and review these packages: *
>>> https://launchpad.net/grub2-themes-ubuntustudio *
>>> https://launchpad.net/ubuntustudio-controls *
>>> https://launchpad.net/ubuntustudio-installer *
>>> https://launchpad.net/ubuntustudio-icon-theme *
>>> https://launchpad.net/ubuntustudio-look *
>>> https://launchpad.net/ubuntustudio-menugrub2-theme-ubuntustudio-
>>> <https://launchpad.net/ubuntustudio-menu> *
>>> https://launchpad.net/ubuntustudio-default-settings *
>>> https://launchpad.net/carla So, please take this as our cry for help
>>> to get these packages updated and included. I don't know how to do
>>> this, and I've never been shown the process. So, maybe my MOTU
>>> training sarts here. Thank you for your time, and in advance for your
>>> help.  Erich Eickmeyer Council Chair Ubuntu Studio ubuntustudio.org 
>>
>> Bug reports are as follows: 1816673, 1818372, 1818368, 1818369,
>> 1818370, 1818366, 1809024,

Re: [ubuntu-studio-devel] youtube firefox and jack

[Ross Gammon]

On 3/2/19 4:09 AM, Len wrote:
> On 2019-03-01 18:11, 0therm...@protonmail.com wrote:
> 
>> When I try to watch youtube videos on firefox while jack is running,
>> the video wont play. As soon as i stop jack it will play. Does anyone
>> else experience this?
>>
>> I'm using a fresh install of ubuntu studio 18.10 (though i experienced
>> the same issue with 16.04)
> 
> If you are starting jack with a command line like:
> jackd 
> or you start an application that expects to use jack without jack
> already running, then this behavior is expected. If you use
> ubuntustudio-controls or qjackctl (with default settings) to start jack
> right after session start then you will be starting jackdbus and pulse
> will be bridged to jackdbus and the audio should go to whatever jackdbus
> has for  system_1 and system_2. If you are not using system_1 and
> system_2 as your outputs (some audio devices have the monitor outputs
> elsewhere) then you would want to use ubuntustudio-controls where you
> can set your outputs to some other consecutive outputs.
> 
> 

Further to what Len says about the monitor outputs, I quite often find
that using Qjackctl to start jack and then using Youtube (which is
actually what our ISO test cases ask us to test for every release), that
the videos do not play because the system is trying to use the HDMI port
for audio.



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Audio Handbook

[Ross Gammon]

On 2/19/19 5:47 PM, Erich Eickmeyer wrote:
> Yet the problem with LMMS using calf-ladspa as a dependency persists,
> and while Ross was able to fix the Debian package upstream, there have
> been some build issues with the ppc64 build, which Ross is working on
> to correct, before it can land in 19.04. For now, LMMS has been removed
> from Ubuntu Studio, and while we would like to add it back, we have to
> give it lower priority since it uses a depricated plugin format that is
> conflicting with other parts of the system.

I hopefully have a fix, and it is waiting for sponsorship. We will have
to wait and see if it fixes it, because I have no way to test on the
ppc64el architecture.

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Fwd: [ubuntu-studio-users] Updates for February 2019

[Ross Gammon]

OK - if Simon is busy, it is best to go through the process so that
other sponsors might jump in. We can also then ping Simon, pointing him
at the bug (with patch ready for sponsorship).

I will start looking at it.

We also have some other updated packages in the autobuilders (like
wallpapers & default settings etc.).

On 2/18/19 4:37 PM, Erich Eickmeyer wrote:
> On Mon, 2019-02-18 at 14:59 +0100, Ross Gammon wrote:
>> [snip]
>>
>>> Updated Ubuntu Studio Controls
>>> This is really a bit of a bugfix for the version of Ubuntu Studio
>>> Controls that landed in 18.10. Ubuntu Studio Controls dramatically
>>> simplifies Audio setup for the JACK Audio Connection Kit on your
>>> Ubuntu
>>> installation, and is the only GUI tool that enables JACK to
>>> automatically detect hotplugged USB Audio devices along with
>>> allowing
>>> more than one audio device to be connected to JACK simultaneously.
>>
>> I can't see a new package ready for upload, other than the autobuilt
>> one. Can I help with this (try and get an upload sponsored)?
> 
> This is correct, and the backports PPA has it as well. We had tapped
> Simon Quigley to upload & sponsor the new packages, but he might be
> busy. If you want to go for it, have at it.
> 
>>> Addition of Ubuntu Studio Backports PPA
>>
>> [snip)
>> Excellent idea. The official "Ubuntu Backports" are not being
>> processed.
>> Doing our own will be much easier. However, I think it would be a
>> good
>> idea to create a mailing list for people to contact at:
>> https://launchpad.net/~ubuntustudio-ppa
>> This is where users with questions or bugs are referred to on the ppa
>> page.
>> In any case, bugs for the backported packages should probably be
>> tracked
>> on our "upstream" bug task (not the source/archive tracker).
> 
> I aggree. Apport won't even let a bug report be processed for a package
> that is in a PPA, as far as I know.
> 
>>> New Features in Ubuntu Studio Installer
>>
>> [snip]
>> Same as for controls. Can I help try and get an upload of the latest
>> sponsored?
>>
>>> New Tool: Carla
>>
>> [snip]
>> Excellent. I was reading through the Audio Handbook yesterday, and
>> thought of starting to package Carla for Debian (again). But when I
>> saw
>> your recent commits, I thought I would hold off. Again, can I help
>> try
>> and get Carla sponsored for Ubuntu? I could upload it to Debian, but
>> it
>> would probably sit in the NEW queue for a while, as Debian is now in
>> release freeze. We could try an upload to Ubuntu first.
>>
> 
> This is another package I was having Simon sponsor, but he hasn't
> looked at it yet either. The other packages are pretty much bugfixes
> since they're noot new packages, but this one would be brand new. If we
> can get it in before feature freeze, I think when falktx does the final
> release of 2.0, we might be able to get it in as a bugfix. The version
> packaged is 2.0-RC3.
> 
> There is one more new package in the bunch, and that's grub2-themes-
> ubuntustudio. It's a fork of grub2-themes-ubuntu-mate, and some of the
> newer versions of packages in -look depend on it.
> 
> So, if you want to work on that (now that you're back from yet another
> trip you globetrotter!), that would be very much appreciated.
> 
> Thanks!
> Erich
> 
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Audio Handbook

[Ross Gammon]

On 2/18/19 4:23 PM, Erich Eickmeyer wrote:
> Hi Ross,
> 
> On 2/18/2019 6:12 AM, Ross Gammon wrote:
>> Hi,
>>
>> I finally got my Ubuntu Studio test machine up an running two weekends
>> ago (there was a problem with my plugin video card which I haven't
>> solved yet). With a fresh install of US 18.10, I started following the
>> Audio Handbook. Naturally, I jotted down some TODO items.
>>
>> Where is the source stored? I see we have wiki format, and PDF & EPUB
>> versions (and I remember the original was in Writer format).
>> https://help.ubuntu.com/community/UbuntuStudio/AudioHandbook
>>
>> Would it be an idea to package the handbook so it can be put uploaded to
>> our new ppa? Then there could be a version for each release (e.g. we
>> should start explaining -controls & how to install on other flavours for
>> Disco).
>> The dominant form for documentation in packages is html, but I suppose
>> we could package it in any form with an appropriate launcher.
> The only source he ever gave us was in HTML, which was copied verbatim
> to the wiki with a few edits.
> 
> As for the source of the PDF & EPUB, that pretty much is the wiki, which
> is why I recommend copying & pasting from the wiki to any new document.
> The problem with going from any other format to the wiki is the special
> flavor of markdown used, and I haven't found any way to autoformat from
> any other format to that special markdown.
> 
> That special markdown format is very much why I didn't consider
> uploading the original files he gave me since it required hours of
> painstaking manual conversion to the markdown. I figured any edits would
> be done on the wiki and then could be copy/pasted into a writer document
> for conversion to EPUB or PDF. Essentially, the way I see it, the wiki
> is now the source.

OK - thanks. It is probably the best way to get user (flyby) edits to
improve things.

> 
> As far as packaging goes, wouldn't it be better just to make a link to
> the wiki in our menu? That way it's kept up-to-date.

Yes - but things will (could) change markedly between 18.04 and say
19.10 when it happens. Whilst the backports ppa will reduce this, it
would at least be nice to be working on having the handbook covering the
latest (e.g. what is in the autobuilders) whilst the published version
reflects what has previously been released.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Audio Handbook

[Ross Gammon]

Hi,

I finally got my Ubuntu Studio test machine up an running two weekends
ago (there was a problem with my plugin video card which I haven't
solved yet). With a fresh install of US 18.10, I started following the
Audio Handbook. Naturally, I jotted down some TODO items.

Where is the source stored? I see we have wiki format, and PDF & EPUB
versions (and I remember the original was in Writer format).
https://help.ubuntu.com/community/UbuntuStudio/AudioHandbook

Would it be an idea to package the handbook so it can be put uploaded to
our new ppa? Then there could be a version for each release (e.g. we
should start explaining -controls & how to install on other flavours for
Disco).
The dominant form for documentation in packages is html, but I suppose
we could package it in any form with an appropriate launcher.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Fwd: [ubuntu-studio-users] Updates for February 2019

[Ross Gammon]

Great stuff - I am sitting at home with a sniffly nose after travelling
with work last week (I love catching germs in airports/airplanes), so
had time to watch the podcast.

On 2/16/19 9:49 PM, Erich Eickmeyer wrote:

[snip]

> Updated Ubuntu Studio Controls
> This is really a bit of a bugfix for the version of Ubuntu Studio
> Controls that landed in 18.10. Ubuntu Studio Controls dramatically
> simplifies Audio setup for the JACK Audio Connection Kit on your Ubuntu
> installation, and is the only GUI tool that enables JACK to
> automatically detect hotplugged USB Audio devices along with allowing
> more than one audio device to be connected to JACK simultaneously.

I can't see a new package ready for upload, other than the autobuilt
one. Can I help with this (try and get an upload sponsored)?


> Addition of Ubuntu Studio Backports PPA

[snip)
Excellent idea. The official "Ubuntu Backports" are not being processed.
Doing our own will be much easier. However, I think it would be a good
idea to create a mailing list for people to contact at:
https://launchpad.net/~ubuntustudio-ppa
This is where users with questions or bugs are referred to on the ppa page.
In any case, bugs for the backported packages should probably be tracked
on our "upstream" bug task (not the source/archive tracker).

> New Features in Ubuntu Studio Installer

[snip]
Same as for controls. Can I help try and get an upload of the latest
sponsored?

> New Tool: Carla

[snip]
Excellent. I was reading through the Audio Handbook yesterday, and
thought of starting to package Carla for Debian (again). But when I saw
your recent commits, I thought I would hold off. Again, can I help try
and get Carla sponsored for Ubuntu? I could upload it to Debian, but it
would probably sit in the NEW queue for a while, as Debian is now in
release freeze. We could try an upload to Ubuntu first.

Regards,

Ross


 Forwarded Message 
Subject: [ubuntu-studio-users] Updates for February 2019
Date: Sat, 16 Feb 2019 12:49:22 -0800
From: Erich Eickmeyer 
Reply-To: Ubuntu Studio Users 
To: Ubuntu Studio Users 


--=-Ms5zbKLzNbD6JxVMRcaf
Content-Type: multipart/alternative; boundary="=-j+GyGmXjQgjlxlTlC5lP"


--=-j+GyGmXjQgjlxlTlC5lP
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Updates for February 2019
With Ubuntu 19.04=E2=80=99s feature freeze quickly approaching, we would li=
ke
to announce the new updates coming to Ubuntu Studio 19.04.
Updated Ubuntu Studio ControlsThis is really a bit of a bugfix for the
version of Ubuntu Studio Controls that landed in 18.10. Ubuntu Studio
Controls dramatically simplifies Audio setup for the JACK Audio
Connection Kit on your Ubuntu installation, and is the only GUI tool
that enables JACK to automatically detect hotplugged USB Audio devices
along with allowing more than one audio device to be connected to JACK
simultaneously.
Addition of Ubuntu Studio Backports PPABecause Ubuntu Studio Controls
is easy to use, we found it was also easier to support than the stack
available in Ubuntu Studio 18.04. For this reason, among others, we
have created an Ubuntu Studio Backports PPA, and will backport the
newer versions of the Ubuntu Studio tools and select applications to
this PPA. Please do keep in mind that this PPA is not supported by
Ubuntu. Use it at your own
risk. Support is provided by the Ubuntu Studio team only.
If you are on Ubuntu Studio 18.04 or newer, simply add this PPA by
typing the following into your terminal:
sudo add-apt-repository ppa:ubuntustudio-ppa/backportsWhile support for
Ubuntu Studio 18.04 was supposed to end in January due to its non-LTS
status, we have decided to support it until the release of 20.04, and
we felt a Backports PPA was the best way to do this. There will be no
releases of Ubuntu Studio 18.04.x ISO, but updating the already-
available ISO as well as adding the backports PPA will keep you up-to-
date and allow the Ubuntu Studio team to support you better.
New Features in Ubuntu Studio Installer
In the past, Ubuntu Studio Meta Installer had been a tool used to
install metapackages of various creative application categories. Now,
Ubuntu Studio Installer can be used to install not only those
metapackages, but also the under-the-hood tweaks used to enable real-
time audio processing and reduce the default swappiness, which dictates
when the system starts moving unused portions of RAM to the hard drive
swap file. This increases overall performance for most applications,
but is not recommended for systems with less than 4GB of RAM. Also
included is the lowlatency Linux kernel, as well as the option to move
the lowlatency kernel to the top of your GRUB bootloader menu, making
it the default which is especially useful for audio production.
With these changes, Ubuntu Studio Installer allows you to install
Ubuntu Studio as a ToolKit on top of your existing Ubuntu installation,
including official flavors (Kubuntu, Xubuntu, Lubuntu, Ubuntu 

Re: [ubuntu-studio-devel] LMMS & Calf: The Ongoing Saga

[Ross Gammon]

On 2/2/19 11:23 PM, Len Ovens wrote:
> On Sat, 2 Feb 2019, Ross Gammon wrote:
> 
>> Hi All,
>>
>> The problem with the calf plugin is fixed in Debian! lmms now only
>> recommends calf-ladspa or whatever it was called, instead of Depending
>> on it, which was wrong!
> 
> So, does LMMS actually work without the calf LV1 package? As in can the
> user do what they expect to be able to do?
>  If the user has a project that includes the calf plugins, I would
> assume that project will now be broken and to fix it they will want to
> install the calf LV1 package, What packages will have to be removed (or
> will be autoremoved) for that package to install and what other
> Applications will be broken by this?
> 
> 
> -- 
> Len Ovens
> www.ovenwerks.net
> 
> 

As far as I know, you can use lmms without any plugins (not tested).
That would be the normal setup for any application. There was no
argument suggesting otherwise on the Debian bugs.

If they need calf-ladspa, then when they install it they will have to
remove calf-plugins, because the two packages conflict with each other.
We might need to blacklist calf-ladspa in our seeds.

I have not had time to investigate, but I read in one thread that
upstream had already renamed their internal copy of calf to veal. That
would probably make the problem of other tools (e.g. ardour) picking up
the old calf plugin and crashing go away. In any case the long term
solution should be to drop the "public" plugin package and keep it
private to lmms. But we needed a fast fix because Debian is going into a
release freeze.

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] LMMS & Calf: The Ongoing Saga

[Ross Gammon]

Hi All,

The problem with the calf plugin is fixed in Debian! lmms now only
recommends calf-ladspa or whatever it was called, instead of Depending
on it, which was wrong!

The problem now, is that even though the new Debian version of lmms
builds fine on all architectures, it does not build on ppc64el in
Ubuntu. Therefore this latest version is stuck in -proposed.

I have not had time to understand what the difference in build
environment is between Debian and Ubuntu, or whether it is because the
build dependencies are different.

I have not had time to contact upstream about it either. It will not be
a fun discussion anyway, as we are several versions behind upstream, and
they are up to v1.2.0-rc7, so are probably working on getting the final
release ready.

The temporary fix is simple (to stop the LiveCD failure). Revert the
seeds change and exclude lmms.

Another possibility, is to upload an Ubuntu version changing the Depends
to Recommends. But then I am worried we will run into GCCv8 build
failures on amd64 & i386 which is the other fix included in the latest
Debian version.

Hopefully I will have a chance to dig further this weekend, but I can't
guarantee it.

Ross
PS: I will do the temporary fix now though. That is easy.

On 2/1/19 6:59 AM, Erich Eickmeyer wrote:
> Because that’s not how it works. If it’s in upstream Debian, it is in
> Ubuntu. Remember, Ubuntu Studio is not a separate distribution from
> Ubuntu. Therefore, when a package is in Debian, we work with that.
> 
>  
> 
> *From:* ubuntu-studio-devel
>  on behalf of Jonathan
> Aquilina 
> *Sent:* Thursday, January 31, 2019 9:56 PM
> *To:* Ubuntu Studio Development
> *Subject:* Re: [ubuntu-studio-devel] LMMS & Calf: The Ongoing Saga
>  
> 
> What about not pulling the package from Debian due to this and compiling
> it specifically for US?
> 
>  
> 
> *From:*ubuntu-studio-devel
>  *On Behalf Of *Erich
> Eickmeyer
> *Sent:* 01 February 2019 06:56
> *To:* Ubuntu Studio Development 
> *Subject:* Re: [ubuntu-studio-devel] LMMS & Calf: The Ongoing Saga
> 
>  
> 
> Yes. The Calf developers have and were met with the response of a brick
> wall. Ross is working on it.
> 
>  
> 
>  
> 
> 
> 
> *From:*ubuntu-studio-devel  > on behalf of
> Jonathan Aquilina mailto:jaquil...@eagleeyet.net>>
> *Sent:* Thursday, January 31, 2019 9:54 PM
> *To:* Ubuntu Studio Development
> *Subject:* Re: [ubuntu-studio-devel] LMMS & Calf: The Ongoing Saga
> 
>  
> 
> Has anyone tried to speak to the maintainer to try and ascertain the
> reasoning behind it?
> 
>  
> 
> Regards,
> 
> Jonathan
> 
>  
> 
> *From:*ubuntu-studio-devel  > *On Behalf Of
> *Erich Eickmeyer
> *Sent:* 01 February 2019 06:43
> *To:* Ubuntu Studio Development  >
> *Subject:* Re: [ubuntu-studio-devel] LMMS & Calf: The Ongoing Saga
> 
>  
> 
> LMMS isn’t the problem.  The problem was erroneous packaging by the
> Debian packager.
> 
>  
> 
> The ladspa version of the Calf plugins were never meant to be exposed to
> other applications besides LMMS, but the packager of LMMS in Debian
> decided to expose the ladpsa version to the rest of the system against
> the advice of both the Calf and LMMS developers.
> 
>  
> 
>  
> 
> Erich
> 
>  
> 
>  
> 
> 
> 
> *From:*ubuntu-studio-devel  > on behalf of
> Jonathan Aquilina mailto:jaquil...@eagleeyet.net>>
> *Sent:* Thursday, January 31, 2019 9:39 PM
> *To:* Ubuntu Studio Development
> *Subject:* Re: [ubuntu-studio-devel] LMMS & Calf: The Ongoing Saga
> 
>  
> 
> Has anyone even subscribed to the lmms mailing list to discuss this
> there and maybe get it squared away once and for all?
> 
> -Original Message-
> From: ubuntu-studio-devel  > On Behalf Of
> er...@ericheickmeyer.com 
> Sent: 01 February 2019 00:49
> To: Ubuntu Studio Development  >
> Subject: [ubuntu-studio-devel] LMMS & Calf: The Ongoing Saga
> 
> Hi everyone,
> 
> Specifically to Ross: where are we at with this bane-of-our-existence
> conflict (LP: 1810534)? ISO builds are still failing and will probably
> fail until we can get lmms from Debian to build properly.
> 
> So, any more word?
> 
> Thanks,
> Erich
> -- 
> ubuntu-studio-devel mailing list
> ubuntu-studio-devel@lists.ubuntu.com
> 
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
> 
> 




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list

Re: [ubuntu-studio-devel] LiveFS ubuntustudio/disco/amd64 failed to build on 20190127

[Ross Gammon]

Aaargh!

On 1/27/19 8:06 PM, Erich Eickmeyer wrote:
> So, clearly the new lmms package isn't in Disco. I imagine this will
> require a sync request?
> 
> Erich
> 
> 
> On 1/27/2019 10:23 AM, CD Image wrote:
>> https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/disco/ubuntustudio/+build/155601
>> RUN: /usr/share/launchpad-buildd/slavebin/slave-prep Forking
>> launchpad-buildd slave process... Kernel version: Linux
>> lcy01-amd64-030 4.4.0-141-generic #167-Ubuntu SMP Wed Dec 5 10:40:15

[snip]

lmms 1.1.3-8.1 has already been auto-synced, but has failed to build on
ppc64el, and therefore it is stuck in "proposed". It built on all
architectures in Debian (including ppc64el) - strange. I was too confident!

If I can't get to the bottom of the build failure, I will revert the
change to the seeds.

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Checking in, a little vision, Calf & LMMS

[Ross Gammon]

Hi Erich,

On 1/1/19 7:39 PM, Erich Eickmeyer wrote:
> Hi everyone!
> 
> I hope everyone is having a happy new year. I haven't been checking-in
> lately due to a number of things going on in my life. First, it was work
> getting busy, then it was a bit of depression onset by my resigning said
> position (they pretty much promised me that I wouldn't ever have room
> for advancement or promotion, or even being full-time).

Sorry to hear about your troubles. I hope the new year brings a better
work situation for you.


> 
> With that, I thought I'd check-in to see where everyone is with their
> current projects. I, for one, have started-in on ubuntustudio-installer.
> I have moved it from bzr to git, and I'm going to be working on adding a
> few entries that will enable it to be used on other flavors for
> installation of Ubuntu Studio-specific items, namely the swappiness and
> lowlatency kernel default selection in GRUB. I already split-out the
> parts of ubuntustudio-default-settings to become their own sub-packages,
> so it should be relatively trivial. This should complete the goal of
> allowing other flavors to install the benefits of Ubuntu Studio while
> still keeping their chosen Desktop Environment.

I you need a review of any of these packages before chasing a sponsor,
let me know. If we can minimise the work the sponsors have to do, they
are more likely to look at your packages than somebody else's!

> 
> == Vision for a Beautiful Experience ==
> 
> As many of you know, I also forked Ubuntu MATE's GRUB theme to our own.
> I contacted Simon Quigley to get it into Universe (would be my first
> full package! \o/), so hopefully that will happen. He's got his hands
> full with Lubuntu, so we'll see.

Congrats. It would be great to have an extra hand doing this packaging
stuff :-)

> 
> My thought behind theming GRUB is this: Ubuntu Studio is intended for
> artists of all kinds, and as such should provide a beautiful experience.
> I will concede that the notion of beauty is subjective. For this reason,
> I'm going to also look into the LightDM theme and see if there's
> anything we can learn from other flavors. Right now, Ubuntu MATE
> provides a nice LightDM theme, which I will explore forking into our own.
> 
> The other thing, which I believe Thomas was working on, was changing our
> Plymouth boot theme. I'll admit, Plymouth quite over my head. Thomas,
> have you made any progress on this?
> 
> == Calf & LMMS ==
> 
> Specifically, this goes out to Ross (with a little slice of Len on the
> side): We obviously had to remove LMMS for its dependency on
> calf-ladspa. That said, I have found out that calf-ladspa is a
> subpackage of LMMS and should never have been split-out in upstream
> Debian, that the calf-ladspa plugins are included with LMMS but were
> never intended to 1) be split-out, and 2) be enacted as a dependency.
> This seems like something that could be trivial to fix in the
> debian/control file for the lmms package. I'm wondering, Ross, if you
> could look into this? Here's a link to a thread for more context:
> https://github.com/calf-studio-gear/calf/issues/134

I looked at this a while back. Unfortunately, lmms is not maintained in
the Debian Multimedia Team, so getting it updated is not as easy. but I
will give it ago.

> 
> 
> Well, that's what I've got this time. Would love to hear back from everyone!
> 
> Erich
> 
> 

I have not given up on applying for some upload rights in Ubuntu (again)
sometime this year, so I have been doing a few merges from Debian to
keep the statistics up (they needed to see more sustained activity from
me last time).

Recent sponsored uploads:
1. Qjackctl
2. Blends (needed for debian-multimedia)

Waiting sponsorship:
1. debian-multmedia (multimedia-puredata is used in our audio seed to
pick up all the latest puredata stuff).
I will ping a sponsor soon, now that the holiday season is over.

If you notice any other packages out of date compared to Debian (or
upstream), then let me know.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] New version of Calf plugins (and a failed ISO build)

[Ross Gammon]

On 11/24/18 8:32 PM, Len Ovens wrote:
> On Sat, 24 Nov 2018, Erich Eickmeyer wrote:
> 
>> You all might have notice the "fail mail" we just got for our ISO. This
>> is due to the new version of calf deprecating calf-ladspa per the
>> developer. Ross or Len: Would you mind removing the calf-ladspa package
>> from the seed? I would except, uh... I've never done it. XD
>>
>> That said, I'm very happy to see this progress. 0.90.0 dropped a year
>> ago and was a major change for that package, and 0.90.1 dropped in July
>> as a bugfix. Hopefully this will make the Ardour people happy as well
>> since the old version was messing with compatibility.
> 
> The ardour people would be happy if this was released to 16.04 -
> 18.19... don't hold your breath.
> 
> 
> -- 
> Len Ovens
> www.ovenwerks.net
> 
> 

Getting calf backported to Xenial is not likely. I have had backports
waiting for sponsorship for years. Nobody seems interested in backports
anymore.

We could provide it in a ppa, (probably also with a new metapackage),
and advise those interested in using the ppa that lmms will be removed.

Alternatively, we could go for an SRU (Stable Release Update) with the
"Conflicts: calf-ladspa", and the meta package update to drop lmms?
But this is probably harsh for lmms users with calf installed, and might
not get approved by the release team.



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] New version of Calf plugins (and a failed ISO build)

[Ross Gammon]

I was just going to look into that.

Germinate output shows that it is lmms that is pulling calf-ladspa in:
http://people.canonical.com/~ubuntu-archive/germinate-output/ubuntustudio.disco/all

We will have to temporarily drop lmms. Looking at the Debian lmms bugs,
it is possible that a newer lmms doesn't do this
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=870473). Need to confirm.

I will drop lmms temporarily from the seed. It is pretty easy to do for
next time:
https://wiki.ubuntu.com/UbuntuStudio/Seeds
https://code.launchpad.net/~ubuntustudio-dev/ubuntu-seeds/+git/ubuntustudio


On 11/24/18 7:46 PM, Erich Eickmeyer wrote:
> Hey all,
> 
> You all might have notice the "fail mail" we just got for our ISO. This
> is due to the new version of calf deprecating calf-ladspa per the
> developer. Ross or Len: Would you mind removing the calf-ladspa package
> from the seed? I would except, uh... I've never done it. XD
> 
> That said, I'm very happy to see this progress. 0.90.0 dropped a year
> ago and was a major change for that package, and 0.90.1 dropped in July
> as a bugfix. Hopefully this will make the Ardour people happy as well
> since the old version was messing with compatibility.
> 
> Thanks,
> Erich
> 
> 

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Multiboot USB help

[Ross Gammon]

Hi All,

In preparation for building my new test machine, I created a Multiboot
USB with Debian, Ubuntu & Ubuntu Studio on it. I created it from my
normal Ubuntu desktop with grub-install & grub-mkconfig (with i386
target for maximum compatability), and then deleted everything in
grub.cfg except for the first grub.d/00_header.

Grub (with a manually produced grub.cfg) manages to boot Debian Live &
Ubuntu Live as a loopback fine, but I have tried all sorts of things to
get Ubuntu Studio Live booting and failed, and Mr Google has not helped.
I get a kernel panic (kernel panic-not syncing: VFS: unable to mount
root fs on unknown block). Maybe there is a special incantation for the
low-latency kernel when running US Live? Maybe instead of the standard
grub.d/00_header, there is special incantation I need from our livecd
script?

Has anybody tried this and succeeded?

For reference, the grub.cfg (as it currently stands) is below.

Cheers,

Ross

grub.cfg:
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
  set have_grubenv=true
  load_env
fi
if [ "${next_entry}" ] ; then
   set default="${next_entry}"
   set next_entry=
   save_env next_entry
   set boot_once=true
else
   set default="0"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
  menuentry_id_option="--id"
else
  menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
  set saved_entry="${prev_saved_entry}"
  save_env saved_entry
  set prev_saved_entry=
  save_env prev_saved_entry
  set boot_once=true
fi

function savedefault {
  if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
  fi
}
function recordfail {
  set recordfail=1
  # GRUB lacks write support for lvm, so recordfail support is disabled.
}
function load_video {
  if [ x$feature_all_video_module = xy ]; then
insmod all_video
  else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
  fi
}

if [ x$feature_default_font_path = xy ] ; then
   font=unicode
else
insmod part_msdos
insmod part_msdos
insmod lvm
insmod ext2
set
root='lvmid/c3f015-f275-5011-e5a9-1700-016c-703ccc/c3f05a-6c75-5011-e5a9-1700-016c-703ccc'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root
--hint='lvmid/c3f015-f275-5011-e5a9-1700-016c-703ccc/c3f05a-6c75-5011-e5a9-1700-016c-703ccc'
 2c5da318-b612-41c2-ad97-d3fbc22bf206
else
  search --no-floppy --fs-uuid --set=root
2c5da318-b612-41c2-ad97-d3fbc22bf206
fi
font="/usr/share/grub/unicode.pf2"
fi

if loadfont $font ; then
  set gfxmode=auto
  load_video
  insmod gfxterm
  set locale_dir=$prefix/locale
  set lang=en_GB
  insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
  set timeout=30
else
  if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=10
  # Fallback hidden-timeout code in case the timeout_style feature is
  # unavailable.
  elif sleep --interruptible 10 ; then
set timeout=0
  fi
fi
### END /etc/grub.d/00_header ###

submenu "Ubuntu 18.10" {
 set isofile=/Ubuntu/ubuntu-18.10-desktop-amd64.iso
 set gfxpayload=keep
 loopback loop $isofile
 menuentry "Try Ubuntu 18.10 without installing" {
  linux (loop)/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
boot=casper iso-scan/filename=$isofile quiet splash ---
  initrd (loop)/casper/initrd
 }
 menuentry "Install Ubuntu 18.10" {
  linux (loop)/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed
boot=casper iso-scan/filename=$isofile only-ubiquity quiet splash ---
  initrd (loop)/casper/initrd
 }
}

submenu "Ubuntu Studio 18.04" {
 set isofile=/Ubuntu/ubuntustudio-18.04-dvd-amd64.iso
 set gfxpayload=keep
 loopback loop $isofile
 menuentry "Try Ubuntu Studio 18.04 without installing" {
  linux (loop)/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed
boot=casper iso-scan/filename=$isofile quiet splash ---
  initrd=(loop)/casper/initrd.lz
 }
 menuentry "Install Ubuntu Studio 18.04" {
  linux (loop)/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed
boot=casper only-ubiquity quiet spalsh ---
  initrd=(loop)/casper/initrd.lz
 }
}

submenu "Ubuntu Studio 18.10" {
 set isofile=/Ubuntu/ubuntustudio-18.10-dvd-amd64.iso
 loopback loop $isofile
 menuentry "Try Ubuntu Studio 18.10 without installing" {
  linux (loop)/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed
boot=casper iso-scan/filename=$isofile quiet splash ---
  initrd=(loop)/casper/initrd
 }
 menuentry "Install Ubuntu Studio 18.10" {
  linux (loop)/casper/vmlinuz file=/cdrom/preseed/ubuntustudio.seed
boot=casper only-ubiquity quiet spalsh ---
  initrd=(loop)/casper/initrd
 }
}

submenu "Debian 9.5.0" {
 set isofile=/Debian/debian-live-9.5.0-amd64-gnome.iso
 loopback loop $isofile
 menuentry "Debian 9.5.0 Live" {
  linux 

Re: [ubuntu-studio-devel] New GRUB Theme! And, progress reports anyone?

[Ross Gammon]

On 11/6/18 4:20 AM, er...@ericheickmeyer.com wrote:
> Hi all,



> Anyhow, looks like the new GRUB theme, if it works well, would be my
> first major package contribution to Ubuntu! Kinda nice to be able to
> come up with something like that just after being made an official
> Ubuntu member!

Congratulations! I was lurking on IRC for the Membership Board meeting.
But you didn't need any support.

> While we're at it, would anybody be able to tell me what they're
> working on? I know that Len had been working on refining -controls and
> bringing WACOM configuration to it as well. I also know Ross has been
> working on getting our seed converted to GIT. I have no idea what
> anybody else has been working on.
> 
> I, for one, have been working on getting Carla into Ubuntu, and I'm
> working with FalkTX on getting the WINE bridges to compile, which has
> been a pain.

The seeds are waiting for a sponsor. I made a mistake and the sponsor
asked me to fix it - which I have.

My next task will be to continue working on an update to calf-plugins in
Debian.

I am in the process of building a new PC so I can play with more things
(e.g. grub) without worrying about breaking my working machine. Then I
will start looking at your work towards desktop agnostics.

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Git seeds (was - jack-mixer)

[Ross Gammon]

Hi All,

On 10/28/18 5:31 PM, Ross Gammon wrote:
> On 10/28/2018 04:54 PM, Len Ovens wrote:
>> On Sun, 28 Oct 2018, Ross Gammon wrote:
>>
>>> For information, the seeds have been converted to git. The archive and
>>> cd-image have now been switched to use git instead of bzr. I am just
>>> waiting for the the new "D" name for 19.04, and then we can create the
>>> new git branch for "D", and then I will do an ubuntustudio-meta update
>>> which is the final place to switch away from bzr.
>>
>> Thanks Ross. Can you confirm (or not) my guesses below:
>>
>> So all changes go into master first? Then cycle branches are rebased
>> from master till release? The cycle branches can be directly changed
>> after release for bug fix? Rebasing current cycle branches would be
>> manual or auto?
> 
> We have followed the suggestions of all the other flavours and created
> git branches for each series:
> https://code.launchpad.net/~ubuntustudio-dev/ubuntu-seeds/+git/ubuntustudio
> 
> There is no master branch at the moment.
> 
> With bzr, it was the Ubuntu Release team that created each development
> release branch from the last commit of the previous series branch. It is
> probably a semi-automatic process that they run.
> 
> It is probably easier to keep it this way than switch to a more normal
> git workflow (with master having all the development work).
> 
> While we wait, there is no reason that someone couldn't create a git
> branch, do the jack-mixer fix, and push it to their own git repo with a
> commit referencing the bug. Then it would be ready for merging once the
> development series branch is created.
> 
> It is probably a good idea to practise this and document it for "non-dev
> team" new contributors. Our seeds page needs updating anyway:
> https://wiki.ubuntu.com/UbuntuStudio/Seeds
> 
> Ross
> 

I have just updated our seeds management page to cover the change from
bzr to git:
https://wiki.ubuntu.com/UbuntuStudio/Seeds

I have also updated the Ubuntu Studio Meta Packages wiki page for the
same reason:
https://wiki.ubuntu.com/UbuntuStudio/UbuntuStudioPackageMaintenance#Meta_Package_Maintenance

It was all done from memory, so if there are any wrinkles in the
process, please report them.

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Git seeds (was - jack-mixer)

[Ross Gammon]

On 10/28/2018 04:54 PM, Len Ovens wrote:
> On Sun, 28 Oct 2018, Ross Gammon wrote:
> 
>> For information, the seeds have been converted to git. The archive and
>> cd-image have now been switched to use git instead of bzr. I am just
>> waiting for the the new "D" name for 19.04, and then we can create the
>> new git branch for "D", and then I will do an ubuntustudio-meta update
>> which is the final place to switch away from bzr.
> 
> Thanks Ross. Can you confirm (or not) my guesses below:
> 
> So all changes go into master first? Then cycle branches are rebased
> from master till release? The cycle branches can be directly changed
> after release for bug fix? Rebasing current cycle branches would be
> manual or auto?

We have followed the suggestions of all the other flavours and created
git branches for each series:
https://code.launchpad.net/~ubuntustudio-dev/ubuntu-seeds/+git/ubuntustudio

There is no master branch at the moment.

With bzr, it was the Ubuntu Release team that created each development
release branch from the last commit of the previous series branch. It is
probably a semi-automatic process that they run.

It is probably easier to keep it this way than switch to a more normal
git workflow (with master having all the development work).

While we wait, there is no reason that someone couldn't create a git
branch, do the jack-mixer fix, and push it to their own git repo with a
commit referencing the bug. Then it would be ready for merging once the
development series branch is created.

It is probably a good idea to practise this and document it for "non-dev
team" new contributors. Our seeds page needs updating anyway:
https://wiki.ubuntu.com/UbuntuStudio/Seeds

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] jack-mixer

[Ross Gammon]

Created a bug:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-meta/+bug/1800362

For information, the seeds have been converted to git. The archive and
cd-image have now been switched to use git instead of bzr. I am just
waiting for the the new "D" name for 19.04, and then we can create the
new git branch for "D", and then I will do an ubuntustudio-meta update
which is the final place to switch away from bzr.


On 10/23/2018 08:07 PM, Erich Eickmeyer wrote:
> I agree, Len. I’m surprised we don’t already have it there, but that
> just means I didn’t look. Let’s do it.
> 
> Erich
> 
>  
> 
> *From:* ubuntu-studio-devel
>  on behalf of Len Ovens
> 
> *Sent:* Tuesday, October 23, 2018 11:05 AM
> *To:* Ubuntu Studio Development & Technical Discussion
> *Subject:* [ubuntu-studio-devel] jack-mixer
>  
> As we are doing th9is meetingless... I would suggest adding jack-meter to
> the iso for 19.04. We currently do not have anything that does this. It is
> sort of like a simple version of non-mixer (which we also don't have) with
> no plugins. but it allows a user to mix channels of audio together in
> jack with individual level control..
> 
> --
> Len Ovens
> www.ovenwerks.net
> 
> 
> -- 
> ubuntu-studio-devel mailing list
> ubuntu-studio-devel@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
> 
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Cosmic Release Notes

[Ross Gammon]

On 10/18/2018 05:32 AM, Hank Stanglow wrote:
> On 10/17/2018 07:55 PM, Ralf Mardorf wrote:
>>> On Oct 17, 2018, at 4:34 PM, Ross Gammon wrote:
>>>> https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes/UbuntuStudio
>> Hi,
>>
>> just a warning regarding GIMP 2.10.6.
>>
>> Two days ago I used it on Arch Linux. It's more or less unusable.
> Oh wow, thanks for that important first hand account. I've been looking
> forward to GIMP 2.10 for several months. It's a HUGE release for them
> and I hope they get a stable version soon.
> 
> Thanks for all the hard work Ralf.
> 

Thanks all for the suggestions. I have taken them on board (I think).

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Cosmic Release Notes

[Ross Gammon]

Hi All,

I have drafted some release notes for the release tomorrow.

I am trying to produce a diff between the bionic & cosmic seeds to
confirm what has changed, but the updates to our main packages are done.

Please review, especially my hasty words about the latest on Ubuntu
Studio Controls:
https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseNotes/UbuntuStudio

Regards,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] [ubuntu-studio-users] Fwd: Non-final, but very testable (hint, hint) Cosmic RC builds

[Ross Gammon]

On 10/14/2018 06:03 PM, Len Ovens wrote:
> On Sun, 14 Oct 2018, Ross Gammon wrote:
> 

[snip]

> 
> In particular, ubuntustudio-controls has had the most changes. Please
> test it to death.
> 
> -- 
> Len Ovens
> www.ovenwerks.net
> 
> 

Hi Len,

I was a bit limited on the hardware I could test controls with, but
there were no crashes :-)

I noticed that if you click on "Start Jack" or "Stop Jack", the check
box for "Autostart Jack for session" is checked and unchecked without me
clicking there. Is this deliberate, or should I file a bug? It is not
serious.

Maybe it is time for us to re-write the "Post Installation" ISO testcase
to use controls instead of Qjackctl? We would need to use something else
to view the connections for the Jack sink/source.

Cheers,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Ubuntu Studio Seeds to git [Was: Re: Vision for 19.04 and beyond]

[Ross Gammon]

On 10/15/2018 07:23 AM, Ross Gammon wrote:
> On 10/14/2018 06:01 PM, Len Ovens wrote:
>> On Sun, 14 Oct 2018, Ross Gammon wrote:
>>
>>> With all these changes to seeds, I would recommend converting from
>>> bazaar to git before we start. We are the last flavour to do it I
>>> believe. I am happy to take that on if required.
>>
>> That would be wonderful. It seems that for the history to be right a
>> number of seeds would have to be added as branches. Or do we start fresh
>> for d*? That is the main thing keeping me from trying. Most of our
>> packages are just master linearly with tags (though branches will appear
>> for bug fixes). They were easy :) (well maybe we did them wrong too).
>>
>> -- 
>> Len Ovens
>> www.ovenwerks.net
>>
>>
> 
> There is a guide to how to do it here:
> https://wiki.ubuntu.com/Germinate/ConvertingToGit
> 
> The past releases appear as git branches. See example for Lubuntu here:
> https://code.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu/
> 
> But at the bottom of the conversion guide, is an explanation of how you
> could archive the history in another separate repo. But I would prefer
> to keep the history in one place. That is what a VCS is for!
> 
> I would be nervous about doing the switch just before a release.
> Although it would avoid the release team having to create the d* bzr
> branch for us using the old procedure. Maybe we could do it as soon as
> the release is announced?
> 
> Ross
> 

I have followed the guide and created the git repository for the seeds:
https://code.launchpad.net/~ubuntustudio-dev/ubuntu-seeds/+git/ubuntustudio

I have prepared an update for the ubuntustudio-meta package (converted
to git), which is just waiting for when the d* development release opens
for work (and we know the name - diligent dog? :-) ):
https://code.launchpad.net/~ubuntustudio-dev/ubuntustudio-meta/+git/ubuntustudio-meta

I have prepared the changes to the ubuntu-archive-scripts:
https://code.launchpad.net/~rosco2/ubuntu-archive-scripts/trunk

And the changes to the cdimages:
https://code.launchpad.net/~rosco2/ubuntu-cdimage/ubuntustudio-seeds-git

So we should be ready to go sometime after Cosmic is released. Then We
should delete the supported seed branches to avoid accidental updates to
the old repositories.

Cheers,

Ross


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Vision for 19.04 and beyond

[Ross Gammon]

On 10/14/2018 06:01 PM, Len Ovens wrote:
> On Sun, 14 Oct 2018, Ross Gammon wrote:
> 
>> With all these changes to seeds, I would recommend converting from
>> bazaar to git before we start. We are the last flavour to do it I
>> believe. I am happy to take that on if required.
> 
> That would be wonderful. It seems that for the history to be right a
> number of seeds would have to be added as branches. Or do we start fresh
> for d*? That is the main thing keeping me from trying. Most of our
> packages are just master linearly with tags (though branches will appear
> for bug fixes). They were easy :) (well maybe we did them wrong too).
> 
> -- 
> Len Ovens
> www.ovenwerks.net
> 
> 

There is a guide to how to do it here:
https://wiki.ubuntu.com/Germinate/ConvertingToGit

The past releases appear as git branches. See example for Lubuntu here:
https://code.launchpad.net/~lubuntu-dev/ubuntu-seeds/+git/lubuntu/

But at the bottom of the conversion guide, is an explanation of how you
could archive the history in another separate repo. But I would prefer
to keep the history in one place. That is what a VCS is for!

I would be nervous about doing the switch just before a release.
Although it would avoid the release team having to create the d* bzr
branch for us using the old procedure. Maybe we could do it as soon as
the release is announced?

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] availability of alternate DEs

[Ross Gammon]

On 10/05/2018 07:35 PM, Len Ovens wrote:
> On Fri, 5 Oct 2018, Ross Gammon wrote:
> 
>> Is it not possible to install the kubuntu metapackage (or one of them)
>> on a Ubuntu Studio install and then chose the DE when logging in?
>>
>> If that was possible, then we could add a new metapackage to our
>> ubuntustudio seeds that could be optionally installed, and then switch
>> the seeds to that metapackage once we are happy.
> 
> Probably some of us are just hard of thinking :) That would increase the
> ISO size by the size of the plasma meta, though the resulting ISO would
> probably still fit on a DVD (if those are still a thing). DL time would
> go up yet a again. It would, at this point, be a next cycle thing of
> course. We would need at least an optional -plasma-desktop package, but
> more realistically we would need to split -default-settings into
> -default-setting and -xfce-desktop (replace "desktop" with "settings" if
> needed).
> 
> I guess it is possible for the plasma part to be dl and install during
> ISO install rather than included on the ISO. So there might be a default
> DE on the ISO, but at install time a different DE could be selected. I
> do not know how to do that, but the installer already DL and installes
> non-free packages so there must be a way.

I think we could add to our ubuntustudio-live ubiquity plugin to add the
plasma meta as an option at install time. We already use that to
select/deselect which metas & packages to install.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] availability of alternate DEs

[Ross Gammon]

Is it not possible to install the kubuntu metapackage (or one of them)
on a Ubuntu Studio install and then chose the DE when logging in?

If that was possible, then we could add a new metapackage to our
ubuntustudio seeds that could be optionally installed, and then switch
the seeds to that metapackage once we are happy.

I have never understood the need for the extra ISO. Is it so we can
offer an install for both DE's, or is there some setting that can only
be made at install time?

On 10/03/2018 07:07 PM, Erich Eickmeyer wrote:
> To answer the initial question, Plasma will not be installable from an
> ISO, but will be available in the repositories. Unfortunately spinning a
> new iso for Plasma has proven to be time prohibitive, so a direction
> that is being considered is to add a meta package to a Kubuntu install
> to convert it into Ubuntu Studio (and have metapackages available to
> convert other flavors as well). Yes, that adds an extra step, but it’s
> the most logical solution considering our manpower and time allotment.
> 
> Erich
> 
>  
> 
> *From:* 20104043740n behalf of
> *Sent:* Wednesday, October 3, 2018 9:17 AM
> *To:* Ubuntu Studio Development
> *Subject:* Re: [ubuntu-studio-devel] availability of alternate DEs
>  
> It would be interesting to have end users choose which DE they want. as
> it stands everyone one has their own preferene I prefer KDE others on
> this list like gnome.
> 
> Regards,
> Jonathan
> 
> On 2018-10-03 15:31, Charlie wrote:
>> will KDE plasma be available upon release of the final version of
>> 18.10 or will it be offered later? or will it be an option during
>> installation?
>>
>> Charlie Luna
> 
> -- 
> ubuntu-studio-devel mailing list
> ubuntu-studio-devel@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel
> 
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Some thoughts, frustrations, and considerations.

[Ross Gammon]

Hi Erich,

On 09/21/2018 05:55 PM, Erich Eickmeyer wrote:
> Hi everybody,
> 
> As many of you know, Eylul stepped-down from the core leadership of
> Ubuntu Studio on Saturday. With Eylul's departure, we lost one of our
> key developers. She had planned on stepping-down, so this was not
> completely unforseen, and she isn't the only one who wishes to depart.
> He can correct me if I'm wrong, but it's my understanding that Len was
> looking at stepping-down when the timing was right as well.  This has me
> rethinking some of the ideas we've had with the less-than handful of
> people we have working on this project.

Thanks for taking the time to write this. I was not aware of any of
this. Probably because like everyone, I don't have a lot of spare time
these days. If it didn't appear here, it didn't happen ;-)
Anyway, that is a shame. Both will/would be missed.

> 
> When Ubuntu Studio was born, it started as an add-on to the existing
> GNOME-based Ubuntu install. Those that were there can correct me if I'm
> wrong, but as I understand it, the first ISO came about with Xfce as the
> desktop when Ubuntu went to Unity. With Unity no longer a major factor,
> I asked the team to explore other desktops, and, with Len's
> recommendation, Plasma was chosen as a viable alternative to Xfce.
> 
> Unfortunately, getting an ISO spun-up with Plasma as the desktop has
> proven to be more of a pain than previously thought because we'd
> essentially be creating a new "flavor" of Ubuntu which has to go through
> all of the steps necessary to make that happen. With our dwindling
> numbers and lack of time to dedicate to a project that got too tedious,
> I recommend we abandon this project.

Why is it a new flavour? I thought it would just involve updating the
seeds and meta packages to use the kubuntu defaults instead of xubuntu.

> 
> Also, creating Ubuntu Studio Welcome and the boutique to replace
> -installer have proved to be nearly impossible without help that I
> simply don't have.
> 
> Another frustration is that it is nearly impossible to get packages
> updated, and if they're synced from Debian it is even more difficult.
> For example, I worked on and got the new version of Calf (0.90.0 which
> has been out since November with a point release to 0.90.1 in July)
> updated, and since it gets pulled-in from Debian, I had to go to the
> Debian Multimedia Team to get it updated, only to find that there was
> someone already working on it without the point release (0.90.0), but it
> hadn't yet made its way into Debian Testing or Unstable. The upstream
> developers had released it in November and it's STILL not in Debian
> Testing or Unstable. It shouldn't take 10 months to update a major
> release of a project. Fedora doesn't have this problem because they
> don't have an upstream project from which to pull as they ARE the
> upstream, and already have the 0.90.1 package! Updating a project
> shouldn't have so many hoops through which to jump!

I am a member of the Debian Multimedia Team. The activity in the team is
pretty low at the moment. Especially Jaromir who was the last person to
start updating Calf. Everyone is pretty busy. Unfortunately, the
packaging uses CDBS instead of debhelper, which I am not very familiar
with. Have you pinged Jonas if he has time to upload the latest?
Otherwise, I will try and learn CDBS and give it a go over the next few
weeks.

> 
> The biggest roadblock we have is the lack of active MOTUs on the team. I
> would apply, but I don't feel as though I'm qualified since I've had
> nobody to mentor me in package development. Additionally, we've been
> unable to attract any dedicated MOTUs.

Yes - this has been a pain. At least in the past Kai had upload rights
for the ubuntustudio-* packages. I have tried twice to get upload rights
to some limited number of packages (not MOTU), but no developer will
endorse me, because I have not had enough sponsored uploads. My
sponsorship request for ubuntustudio-look has been sitting there since
the 4th August.
http://reqorts.qa.ubuntu.com/reports/sponsoring/index.html

I suppose I should be sitting on IRC pinging people, but I don't have
time for that. Like I don't have the time to prepare lots of other
uploads. :-)

If we have the packages ready, but nobody to upload them, why don't we
put them in a team ppa, and put some instructions on the wiki for users
to install manually? In the meantime, the packages can sit in the
sponsorship queue until they get a sponsor.

> 
> If Ubuntu Studio is to survive, I believe it might be time for another
> approach which would bring Ubuntu Studio closer to its roots. My
> proposal is to keep Ubuntu Studio's ISO as Xfce, but to develop
> metapackages that bolt Ubuntu Studio on to an existing install of
> another flavor. There are a couple of different approaches to this: 1)
> the metapackage pulls-in the required configureation files to simply add
> some essential configuration such as the lowlatency kernel selection in
> 

Re: [ubuntu-studio-devel] Meeting Update for 2018-08-25

[Ross Gammon]

Hi Erik,

I am back home after 3 weeks travelling with work.

On 08/25/2018 07:18 PM, Erich Eickmeyer wrote:
> Hi everyone,
> 
> I haven't seen a lot of activity over the course of the past two weeks,
> so I'm not 100% sure we should even have a meeting today aside from this
> thread. Also, I haven't seen anything about -controls making it into
> Cosmic officially, so I'm guessing there's nothing going on there.
> 

-controls was uploaded by Simon Quigley on 12 August.
https://launchpad.net/ubuntu/+source/ubuntustudio-controls

I just checked the Sponsorship queue and -look is still waiting.
http://reqorts.qa.ubuntu.com/reports/sponsoring/index.html

> === Packaging ===
> 
> At this point, with feature freeze approaching (does anybody know the
> exact date???), we need to make this the focus on our development.

23rd August
https://wiki.ubuntu.com/CosmicCuttlefish/ReleaseSchedule

Regards,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Fwd: Updates

[Ross Gammon]

On 08/05/2018 03:58 AM, Len Ovens wrote:
> 
>> https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-controls/+bug/1785418
>>
>> * There are quite a few old bugs. I suspect some of them can be closed.
>> I could do with Len's opinion on some of them first though.
> 
> https://launchpad.net/ubuntustudio-controls
> shows 5 bugs. ckicking on "All bugs" gives: "There are currently no open
> bugs." and when I checked all were invalid, fixed or won't fix already.
> So I am not sure which bugs these are.

That link is to the upstream bugs (project). You need the bugs for the
ubuntu archive (source):
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-controls
I see 7 bugs there (including my one for sponsorship).

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Fwd: Updates

[Ross Gammon]

On 08/04/2018 06:29 PM, Ross Gammon wrote:

> ubuntustudio-menu
> ubuntustudio-icon-theme

These have already been uploaded by Simon. So there is no more to do
from what I can see.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Fwd: Updates

[Ross Gammon]

On 08/04/2018 06:29 PM, Ross Gammon wrote:
> ubuntustudio-look

Done - waiting sponsor

> ubuntustudio-controls

Also done. Wow - Len has been busy, and Simon did a good job of tidying
up the packaging. No real extra work required, it was ready.
- Removed duplicate section entry in debian/control
- Created a bug to assign the sponsorship team to:
https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-controls/+bug/1785418
* There are quite a few old bugs. I suspect some of them can be closed.
I could do with Len's opinion on some of them first though.

> ubuntustudio-menu
> ubuntustudio-icon-theme

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Fwd: Updates

[Ross Gammon]

Hi All,

I have taken a look at ubuntustudio-look. It's lookin' good (pun intended).

Updates:

  * Changed the Vcs URL's to point at the new git repository instead of bzr.
  * Moved the update-alternatives maintenance script from postrm to
prerm (it was a lintian error).
  * Triaged some bugs, and fixed 2:
  o Wrong filenames, links and missing attributions.
  o Added README.source file for the bundled Numix Blue theme.

I have uploaded a debdiff, and subscribed ubuntu-sponsors:

https://bugs.launchpad.net/ubuntu/+source/ubuntustudio-look/+bug/1572249

Cheers,

Ross



 Forwarded Message 
Subject:Updates
Date:   Fri, 3 Aug 2018 14:30:38 -0700
From:   Erich Eickmeyer 
To: ros...@ubuntu.com



Hi Ross,

You asked me to bug you if we needed anything uploaded. Well, we have a
few things that need to make their way into Cosmic. A bit of a laundry
list, but without these uploaded, we're dead in the water.

ubuntustudio-look
ubuntustudio-controls
ubuntustudio-menu
ubuntustudio-icon-theme

That's what I know has been worked on. It has all been updated to Git
and can be found at https://code.launchpad.net/~ubuntustudio-dev/+git.

Between myself, Len, and Eylul, we've been working hard. Lots of great
things happening.


Erich




0x20FB053CAF9559CF.asc
Description: application/pgp-keys


signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Meeting Notes 2018-06-09

[Ross Gammon]

On 11/06/18 16:46, er...@ericheickmeyer.com wrote:
> === packaging ===
> The discussion about "packaging" started at 19:56.
>
>   * ''LINK:'' https://github.com/falkTX/Carla 
>   * ''LINK:'' http://kxstudio.linuxaudio.org/Applications:Carla  
>   * New packaging volunteer: WMRamadon

I had a working package that just needed some further work to comply
with Debian Policy here:
https://code.launchpad.net/~rosco2/+git/carla

Feel free to start from there, and push updates to somewhere else. A new
version of Carla has been release since then, so step 1 would be to
import the latest version.

Let me know if there are any questions. I can sponsor the upload into
Debian when it is ready.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Meeting Notes 2018-05-05

[Ross Gammon]

On 05/06/2018 05:21 AM, Erich Eickmeyer wrote:
> Drop 32-bit Support
>   - Ubuntu Studio is not targeting "giving new life to old machines" as 
> many of its apps require a certain amount of horsepower to begin with.
>   - Everyone was in favor of dropping support for 32-bit.
>   - Erich to make official request.

We should probably push this news out on all the channels as a warning
to our users. Of course they can still upgrade to the latest releases,
and there will be 32 bit packages there for them. But users of 32 bit
systems going forward should be aware that they are effectively the only
"testers" of the software (apart from some automated package checks).

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Fwd: Migrating all seeds to Git

[Ross Gammon]

>From the Release Team list - a good job to kick off the Cosmic release
cycle. Coverting seeds to git.

We should decide whether we want to do something similar for our other
Ubuntustudio-* packages.


On 05/02/2018 04:40 AM, Simon Quigley wrote:

> Hello,
>
> As some of you know, a project that I took on for Lubuntu in the 18.04
> cycle was to migrate our seeds to Git (and to get the necessary tooling
> bits in place to cope for that). I spoke to Adam Conrad from the Release
> Team this afternoon, and we agreed that all of the Ubuntu and flavor
> seeds should migrate to Git before the Cosmic release cycle progresses
> too far. This would mean that instead of having individual Bazaar
> branches, there would be one Git repository per flavor, which has
> different branches for each release, and the EOL releases would be moved
> to a different (yet similarly-named) Git repository. The old Bazaar
> branches would be deleted.
>
> I wrote a wiki page[1] on how to migrate flavor seeds to Git, feel free
> to edit the page if I missed anything.
>
> Of course, people are encouraged to convert their seeds sooner rather
> than later, but the goal is to convert all non-converted seeds to Git in
> one week's time (the afternoon (US/Canada time) of May 8th). Please
> respond here or let me know if you would not like to proceed with this
> for the team you represent. No work is required for teams, with the
> exception of adjusting local clones and custom workflows should they exist.
>
> Thanks, and let me know if you have any questions.
>
> [1] https://wiki.ubuntu.com/Germinate/ConvertingToGit
>
>
>



 Forwarded Message 
Subject:Migrating all seeds to Git
Date:   Tue, 1 May 2018 21:40:23 -0500
From:   Simon Quigley 
Organization:   Ubuntu
To: Valorie Zimmerman , Rik Mills
, flocculant , Pasi
Lallinaho , Erich Eickmeyer
, handsome_feng ,
Martin Wimpress ,
dus...@bashfulrobot.com, foss.free...@gmail.com, Jeremy Bicha

CC: ubuntu-release 



This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7BYyWvPPuPJYPTJNarQ4rvMqTdQLwBg9F
Content-Type: multipart/mixed; boundary="Um5qm4RQpfplFF8B6eoYqPUoMU7zzRLPT";
 protected-headers="v1"
From: Simon Quigley 
To: Valorie Zimmerman ,
 Rik Mills , flocculant ,
 Pasi Lallinaho ,
 Erich Eickmeyer ,
 handsome_feng ,
 Martin Wimpress , dus...@bashfulrobot.com,
 foss.free...@gmail.com, Jeremy Bicha 
Cc: ubuntu-release 
Message-ID: 
Subject: Migrating all seeds to Git

--Um5qm4RQpfplFF8B6eoYqPUoMU7zzRLPT
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hello,

As some of you know, a project that I took on for Lubuntu in the 18.04
cycle was to migrate our seeds to Git (and to get the necessary tooling
bits in place to cope for that). I spoke to Adam Conrad from the Release
Team this afternoon, and we agreed that all of the Ubuntu and flavor
seeds should migrate to Git before the Cosmic release cycle progresses
too far. This would mean that instead of having individual Bazaar
branches, there would be one Git repository per flavor, which has
different branches for each release, and the EOL releases would be moved
to a different (yet similarly-named) Git repository. The old Bazaar
branches would be deleted.

I wrote a wiki page[1] on how to migrate flavor seeds to Git, feel free
to edit the page if I missed anything.

Of course, people are encouraged to convert their seeds sooner rather
than later, but the goal is to convert all non-converted seeds to Git in
one week's time (the afternoon (US/Canada time) of May 8th). Please
respond here or let me know if you would not like to proceed with this
for the team you represent. No work is required for teams, with the
exception of adjusting local clones and custom workflows should they exis=
t.

Thanks, and let me know if you have any questions.

[1] https://wiki.ubuntu.com/Germinate/ConvertingToGit

--=20
Simon Quigley
tsimo...@ubuntu.com
tsimonq2 on freenode and OFTC
5C7A BEA2 0F86 3045 9CC8
C8B5 E27F 2CF8 458C 2FA4


--Um5qm4RQpfplFF8B6eoYqPUoMU7zzRLPT--

--7BYyWvPPuPJYPTJNarQ4rvMqTdQLwBg9F
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEXHq+og+GMEWcyMi14n8s+EWML6QFAlrpJRcACgkQ4n8s+EWM

Re: [ubuntu-studio-devel] Release notes for Bionic

[Ross Gammon]

For the release, we normally like to list what has changed since the
last release. Also make sure to list any known bugs that show on the iso
tracker (http://iso.qa.ubuntu.com/)


On 21/04/18 04:32, er...@ericheickmeyer.com wrote:
>
> Hi all,
>
>  
>
> I’m trying to compile the release notes for 18.04. If anyone has
> anything that needs to be on the release notes, let me know.
>
>  
>
> Erich
>
>
>



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Packaging

[Ross Gammon]

Hi Erich,

I can see you have been added to the ubuntustudio-release team on
Launchpad. You should then be able to log into http://iso.qa.ubuntu.com/
with the release manager role. Then you will have the power to mark a
release as "ready". You also have the power to trigger a rebuild of the DVD.

It is best to join the ubuntu-release team mailing list, and IRC
channel. You could send them a mail on the list stating that you are the
new Release Manager for US, with your IRC name, so they know who to look
for on IRC, and who to email.

Normally the Ubuntu release team create the Release/Test Candidates. All
you have to do is keep an eye out for the announcements and encourage
everyone to test.

Thanks for stepping up to make sure the release happens.

Ross 


On 21/04/18 01:47, er...@ericheickmeyer.com wrote:
> Ross: Thanks for the update.
>
> Now, I've been (slowly) working on release management-related stuff. What do 
> I need to do to take care of the RC which was due yesterday? I'm assuming 
> there's a similar process for the release as well. Besides that, do we have 
> anything specific for the release notes other than pointing to the general 
> Ubuntu release notes?
>
> Also, Simon told me that I need the community to basically recognize me as 
> the release manager for the purposes of having access to whatever it is I 
> need access to in order to call a release good. It seems that has happened 
> because I've been brought-in on a couple of bug reports and signed-off on one 
> FFe, but is there anything I need to do to make it official?
>
> In summary, we have to release a RC, but I simply don't know how exactly 
> that's done. Can anybody point me in the right direction?
>
> Thanks,
> Erich
>
>
>



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Busy

[Ross Gammon]

Hi All,

I will be tied up with work for the next two weeks. That means I will
miss the release.

I hope to read my mailing lists, but that is probably all I will have
time for.

It is fantastic to see all the activity again, and the new people that
have stepped up to help. If there is someone reading this that would
like a job to do - please sing out.

Regards,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] GIMP vs MyPaint - Dependency conflicts

[Ross Gammon]

In my view it is too late to make such a change. We release in two weeks.

If the current versions of gimp (2.8) and mypaint install fine, I would
leave it that way. I thought is was only if gimp 2.10 was installed that
there was the clash with mypaint?

I think it would be a good idea to create snaps for our priority
packages, and encourage upstream to maintain them. And then if someone
wants the latest and greatest, they can install it. Adding relevant
snaps to our seeds )instead of the Debian package) would be a good
test/goal for 18.10.

On 11/04/18 19:50, Erich Eickmeyer wrote:
> Hi again,
>
> Speaking with Jeremy Bicha (and Ross, apparently you had a previous 
> conversation), GIMP 2.10 is supposed to be out shortly. However, since 
> libmypaint was split and the new version is dependent on a newer version, 
> having GIMP and MyPaint installed together breaks MyPaint until its 1.3 
> release.
>
> So, the question is whether or not we keep 2.8, change GIMP to a snap, or 
> remove MyPaint from the install.
>
> Thoughts?
>
> Erich
>
>



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Release Cycle for 18.04

[Ross Gammon]

+1

No point claiming support if there isn't any.

We have really only relied on the fact that Xubuntu were helping to
support our desktop, and everything in "main" being supported by
Canonical. We have not had the manpower for SRU (Stable Release Updates)
for the other multimedia packages we care about.

On the other hand, it would be good to have an LTS always available.
Many users prefer not to have to constantly update. Our 16.04 LTS will
not be supported after April 2019.

Ross


On 11/04/18 18:55, Erich Eickmeyer wrote:
> Hey all,
>
> I’ve been speaking with Simon Quigley and he suggested that, due to manpower, 
> we drop 18.04 from being LTS and just go with a 9-month release for this 
> cycle. Thoughts?
>
> Erich
>
>



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Introducing the potential new Ubuntu Studio Council

[Ross Gammon]

Hi Jonathan,

Excellent news! We will probably wait a few days and see how many other
offers we receive, and then workout the process (it is new!).

But for now, welcome to the team :-)

Can you let us know your launchpad ID?

Can you let us know a little but about yourself (skills, what you have
done with Ubuntu Studio in the past, and what you might enjoy working on)?

Feel free to give the 16.04.4 Xenial "point release" a test if you have
time (see other post). It will hopefully be released on Thursday if
there are no serious bugs.

Regards,

Ross

On 02/23/2018 02:23 PM, Jonathan Aquilina wrote:
> I’ll join I don’t use Ubuntu studio at the moment but I remember when it was 
> first created.
> 
> I am in the process of changing jobs and hope to have more time to help and 
> experiment on personal projects.
> 
> 
> Sent from my iPhone
> 
>> On 23 Feb 2018, at 14:16, Ross Gammon <ro...@ubuntustudio.org> wrote:
>>
>> Introducing the potential new Ubuntu Studio Council
>> ===
>>
>> Back in 2016, Set Hallström was elected as the  new Team Lead for
>> Ubuntu Studio, just in time for the 16.04 Xenial Long Term Support
>> (LTS) release. It was intended that Ubuntu Studio would be able to
>> utilise Set's leadership skills at least up until the next LTS
>> release in April 2018. Unfortunately, as happens occasionally in the
>> world of volunteer work, Set's personal circumstances changed and he is
>> no longer able to devote as much time to Ubuntu Studio as he would like.
>>
>> Therefore, an IRC meeting was held between interested Ubuntu Studio
>> contributors on 21st May 2017 to agree on how to fill the void. We
>> decided to follow the lead of Xubuntu and create a Council to take care
>> of Ubuntu Studio, rather than continuing to place the burden of
>> leadership on the shoulder of one particular person.
>>
>> Unfortunately, although the result was an agreement to form the first
>> Ubuntu Studio Council from the meeting participants, we all got busy and
>> the council was never set up.
>>
>> Who was willing to be in the Ubuntu Studio Council?
>> ---
>>
>> The attendees of the IRC Meeting that were to form the Ubuntu Studio
>> Council are: - **Set Hallström** (sakrecoer) - **Eylul** (eylul) -
>> **Len Ovens** (len-ovenwerks) - **Ross Gammon** (rosco2)
>>
>> Now times have changed, and Eylul and Ross have also become very busy.
>> We are also aware that some regular contributors to Ubuntu Studio (I can
>> think of Krytarik for example) were not present for the IRC meeting.
>>
>> So, now we are considering expanding the size of that original proposed
>> Council to try and bring in some new blood to Ubuntu Studio, and keep
>> the project going. In particular, we really need someone to step up help
>> with some leadership and direction, and build up the Ubuntu Studio teams.
>>
>> How would the Ubuntu Studio Council Work?
>> 
>>
>> The Ubuntu Studio Council would exist to provide security and stability
>> for the Ubuntu Studio project, and to spread the workload of
>> administering the project. However, the actual work of producing
>> and maintaining each release of Ubuntu Studio would not done by the
>> Council. The actual work and decision making would be carried out,
>> through the various existing teams (e.g. Artwork, Development,
>> Testing, Website etc.). The council will of course help with
>> agreeing the long term direction of Ubuntu Studio and resolving
>> disputes as required.
>>
>> The exact details of the working of the Ubuntu Studio Council need to be
>> documented on our wiki, but the following points were discussed and are
>> the likely way of working:
>>
>> - A Council Chair
>> will be elected from within the Council with a minimum term of one
>> release of Ubuntu Studio.
>> - Elections to the Council will be carried out yearly to encourage
>> participation, and generate fresh ideas. Council membership terms will
>> be set to expire at overlapping intervals for stability, and re-election
>> is allowed.
>> - The size of the council is preferably between 3 and 5 members.
>>
>> What do you think? Want to help out and keep Ubuntu Studio going?
>> -
>>
>> If you have any questions about this, please make contact on the
>> #ubuntustudio-devel IRC channel on irc.freenode.net, or the
>> developer mailing list
>> https://lists.ubuntu.com/ma

[ubuntu-studio-devel] Ubuntu Studio Xenial 16.04.4 Image is ready for testing

[Ross Gammon]

Hi all,

For those that would like to help out with testing Ubuntu Studio, the
latest "point" release for Ubuntu Studio 16.04.4 (Xenial) is ready for
testing.

http://iso.qa.ubuntu.com/qatracker/milestones/386/builds

Click on the link to the 32 or 64 bit test cases, and you will find
download instructions there. There are also links to testing instructions.

Please make sure to record your result on the tracker (good or bad) so
we can see how much testing has been done.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Introducing the potential new Ubuntu Studio Council

[Ross Gammon]

Introducing the potential new Ubuntu Studio Council
===

Back in 2016, Set Hallström was elected as the  new Team Lead for
Ubuntu Studio, just in time for the 16.04 Xenial Long Term Support
(LTS) release. It was intended that Ubuntu Studio would be able to
utilise Set's leadership skills at least up until the next LTS
release in April 2018. Unfortunately, as happens occasionally in the
world of volunteer work, Set's personal circumstances changed and he is
no longer able to devote as much time to Ubuntu Studio as he would like.

Therefore, an IRC meeting was held between interested Ubuntu Studio
contributors on 21st May 2017 to agree on how to fill the void. We
decided to follow the lead of Xubuntu and create a Council to take care
of Ubuntu Studio, rather than continuing to place the burden of
leadership on the shoulder of one particular person.

Unfortunately, although the result was an agreement to form the first
Ubuntu Studio Council from the meeting participants, we all got busy and
the council was never set up.

Who was willing to be in the Ubuntu Studio Council?
---

The attendees of the IRC Meeting that were to form the Ubuntu Studio
Council are: - **Set Hallström** (sakrecoer) - **Eylul** (eylul) -
**Len Ovens** (len-ovenwerks) - **Ross Gammon** (rosco2)

Now times have changed, and Eylul and Ross have also become very busy.
We are also aware that some regular contributors to Ubuntu Studio (I can
think of Krytarik for example) were not present for the IRC meeting.

So, now we are considering expanding the size of that original proposed
Council to try and bring in some new blood to Ubuntu Studio, and keep
the project going. In particular, we really need someone to step up help
with some leadership and direction, and build up the Ubuntu Studio teams.

How would the Ubuntu Studio Council Work?


The Ubuntu Studio Council would exist to provide security and stability
for the Ubuntu Studio project, and to spread the workload of
administering the project. However, the actual work of producing
and maintaining each release of Ubuntu Studio would not done by the
Council. The actual work and decision making would be carried out,
through the various existing teams (e.g. Artwork, Development,
Testing, Website etc.). The council will of course help with
agreeing the long term direction of Ubuntu Studio and resolving
disputes as required.

The exact details of the working of the Ubuntu Studio Council need to be
documented on our wiki, but the following points were discussed and are
the likely way of working:

- A Council Chair
will be elected from within the Council with a minimum term of one
release of Ubuntu Studio.
- Elections to the Council will be carried out yearly to encourage
participation, and generate fresh ideas. Council membership terms will
be set to expire at overlapping intervals for stability, and re-election
is allowed.
- The size of the council is preferably between 3 and 5 members.

What do you think? Want to help out and keep Ubuntu Studio going?
-

If you have any questions about this, please make contact on the
#ubuntustudio-devel IRC channel on irc.freenode.net, or the
developer mailing list
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel.

If this has inspired you to help out, we are always after more
help. Help to write and improve documentation, add new features,
test and fix Ubuntu Studio applications, help users solve problems,
is always welcome. Get in touch!

Please state whether you would like to join one of the teams and help out.

Please state whether you would be willing to join the council and be the
chair/leader for a release cycle (or more).

Regards,

Ross Gammon
Test Team Lead



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Coming Ubuntu Studio Releases

[Ross Gammon]

Hi,

It is not necessary to have packaging experience. But if it interests
you, it can be learnt over time.

There are plenty of roles you could take to help keep Ubuntu Studio
alive. Checkout our wiki, and all the different roles and teams, and
sign up!
https://help.ubuntu.com/community/UbuntuStudio

Let us know what you would like to try working on, and what experience
you have. What do you use US for at the moment?

As a first step to helping with the up and coming releases, you could
test the Artful & Bionic Daily ISO images, and report your results (good
and bad):
http://iso.qa.ubuntu.com/

Of course, I have been focusing on testing, but there is bug triage,
documentation, website, joining in on forums/mailing lists, and trying
to help users as best as you can...

On 02/23/2018 10:55 AM, jaquilina wrote:
> I am very interested in stepping up thing is I have no previous
> experience in such a role. I also do not have any experience with
> packaging or anything of that sort?
> 
> On 2018-02-22 16:38, Ross Gammon wrote:
>> Hi All,
>>
>> We have some coming release dates that require testing of the ISO
>> images.
>>
>> Ubuntu Studio 16.04.4 Xenial point release: The date has been put back
>> to the 1st of March. I should be around for that.
>>
>> Ubuntu Studio First Beta: As far as I know, we have no new features to
>> test, so we should probably opt out of this release.
>>
>> Ubuntu Studio 18.04 Final Beta: April 5th. I should be around for
>> that.
>>  Ubuntu Studio 18.04 Final Release: April 19th - 26th. I will not be
>> available for that (due to work).
>>
>> Who is around to help testing for the first 3?
>>
>> Who is around to do the Release Manager duties for the 18.04 Final
>> Release (testing, confirming when images are releasable, writing
>> release notes, helping with website/social media announcements)?
>>
>> Should we release 18.04 at all?
>>
>> Regards,
>>
>> Ross
>> US Test Team Lead
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Coming Ubuntu Studio Releases

[Ross Gammon]

Hi All,

We have some coming release dates that require testing of the ISO images.

Ubuntu Studio 16.04.4 Xenial point release: The date has been put back
to the 1st of March. I should be around for that.

Ubuntu Studio First Beta: As far as I know, we have no new features to
test, so we should probably opt out of this release.

Ubuntu Studio 18.04 Final Beta: April 5th. I should be around for that.

Ubuntu Studio 18.04 Final Release: April 19th - 26th. I will not be
available for that (due to work).

Who is around to help testing for the first 3?

Who is around to do the Release Manager duties for the 18.04 Final
Release (testing, confirming when images are releasable, writing release
notes, helping with website/social media announcements)?

Should we release 18.04 at all?

Regards,

Ross
US Test Team Lead
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Fwd: Bug#888657: ladish: should this package be removed?

[Ross Gammon]

Hi All,

It is very likely that ladish/gladish will be removed from the Debian
archive soon, as it is not maintained upstream, and needs to be ported
away from GTK2.

Whilst we can probably keep it a little longer in Ubuntu, unless someone
steps up to take over maintenance (and do the porting work), it will be
lost eventually.

Do we have good alternatives?

Regards,

Ross

On 01/28/2018 04:18 PM, James Cowgill wrote:

> Hi,
>
> On 28/01/18 14:16, treb...@tuxfamily.org wrote:
>> Le 2018-01-28 14:38, Simon McVittie a écrit :
>>> Source: flowcanvas
>>> Severity: important
>>> User: debian...@lists.debian.org
>>> Usertags: proposed-removal
>>> Control: clone -1 -2
>>> Control: reassign -2 ladish
>>> Control: retitle -2 ladish: should this package be removed?
>>>
>>> flowcanvas depends on numerous obsolete GNOME 2-era libraries
>>> (e.g. #885095) and hasn't had a maintainer upload since 2009. Its
>>> upstream
>>> website says:
>>>
>>>     **Note**: FlowCanvas is dead, long live Ganv!
>>>
>>> ganv is also in Debian as src:ganv; it's orphaned in Debian, but appears
>>> to have commit activity upstream.
>>>
>>> flowcanvas has one reverse-dependency in Debian, gladish (src:ladish),
>>> whose most recent maintainer upload was in 2014. web.archive.org says
>>> the ladish.org website has been down since mid 2014.
>> ladish looks to be maintained by alessio (last commit 20 Apr 2017) here :
>> https://github.com/alessio/ladish/
>> (the same goes laditools as well)
> You failed to mention that there has only been one non-merge commit to
> that repository since 2014.
>
> The truth is unless someone is willing to do the porting work, these
> packages are not going to survive whether they are "maintained" or not.
>
> James
>
>
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers




 Forwarded Message 
Subject:Bug#888657: ladish: should this package be removed?
Resent-Date:Sun, 28 Jan 2018 15:21:07 +
Resent-From:James Cowgill 
Resent-To:  debian-bugs-d...@lists.debian.org
Resent-CC:  Debian Multimedia Maintainers

Date:   Sun, 28 Jan 2018 15:18:47 +
From:   James Cowgill 
Reply-To:   James Cowgill , 888...@bugs.debian.org
To: treb...@tuxfamily.org, 888...@bugs.debian.org



This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--AA3wuwQJSNwemsa02U8VM82aeUyfz5se2
Content-Type: multipart/mixed; boundary="1YV4OwYIGUSyBHwRCivLLmp4QKWC5OJpX";
 protected-headers="v1"
From: James Cowgill 
To: treb...@tuxfamily.org, 888...@bugs.debian.org
Message-ID: <11a6d485-873f-cc85-95e9-85d0883d2...@debian.org>
Subject: Re: Bug#888657: ladish: should this package be removed?
References: <20180128133835.ga30...@perpetual.pseudorandom.co.uk>
 <3bf1d8b4332cfb002543a077da7ab...@tuxfamily.org>
 <20180128133835.ga30...@perpetual.pseudorandom.co.uk>
 
In-Reply-To: 

--1YV4OwYIGUSyBHwRCivLLmp4QKWC5OJpX
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi,

On 28/01/18 14:16, treb...@tuxfamily.org wrote:
> Le 2018-01-28 14:38, Simon McVittie a =C3=A9crit=C2=A0:
>> Source: flowcanvas
>> Severity: important
>> User: debian...@lists.debian.org
>> Usertags: proposed-removal
>> Control: clone -1 -2
>> Control: reassign -2 ladish
>> Control: retitle -2 ladish: should this package be removed?
>>
>> flowcanvas depends on numerous obsolete GNOME 2-era libraries
>> (e.g. #885095) and hasn't had a maintainer upload since 2009. Its
>> upstream
>> website says:
>>
>> =C2=A0=C2=A0=C2=A0 **Note**: FlowCanvas is dead, long live Ganv!
>>
>> ganv is also in Debian as src:ganv; it's orphaned in Debian, but appea=
rs
>> to have commit activity upstream.
>>
>> flowcanvas has one reverse-dependency in Debian, gladish (src:ladish),=

>> whose most recent maintainer upload was in 2014. web.archive.org says
>> the ladish.org website has been down since mid 2014.
>=20
> ladish looks to be maintained by alessio (last commit 20 Apr 2017) here=
 :
> https://github.com/alessio/ladish/
> (the same goes laditools as well)

You failed to mention that there has only been one non-merge commit to
that repository since 2014.

The truth is unless someone is willing to do the porting work, these
packages are not going to survive whether they are "maintained" or not.

James


--1YV4OwYIGUSyBHwRCivLLmp4QKWC5OJpX--

--AA3wuwQJSNwemsa02U8VM82aeUyfz5se2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-BEGIN PGP SIGNATURE-

[ubuntu-studio-devel] Testing Team Leader Role in Ubuntu Studio

[Ross Gammon]

Hi All,

This is a call for assistance with Testing in Ubuntu Studio.

I am currently finding it very difficult to put the time I would like
into fulfilling the role I took on some time ago, to be the Test Team
Lead for Ubuntu Studio. Therefore, I am looking for volunteers to join
the team (if not members already), and take over as Test Team Leader
after 18.04 (Bionic) LTS is released.

There is some information about the team on the wiki here:
https://wiki.ubuntu.com/UbuntuStudio/TestingTeamPage

There is also a need to be available for release tasks during the times
we are working on the next release, or there is an update to an LTS
release. Some of the things that need to be done for a release are
listed here:
https://wiki.ubuntu.com/UbuntuStudio/DevEvents/Release

As a summary, the role involves:
- Managing the Manual Test Cases at http://packages.qa.ubuntu.com/
- Being the Release Manager at the appropriate points in the test cycle:
http://iso.qa.ubuntu.com/
https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
- Announcing the coming tests and encouraging others to take part in the
tests.
- Triaging bugs found during the test campaigns.
- Writing the Release Notes & helping the documentation team with text
for the announcements.

I still plan to be a member of the team to help out where I can, and to
assist the new Test Lead develop into the role. But would like to spend
what spare time I have, concentrating on getting more evidence of
uploads to Ubuntu for my Developer application.

If you would like to help out, please apply to be a member of the
testing team on Launchpad (https://launchpad.net/~ubuntustudio-testing),
and let us know on the developers list that you would like to volunteer.

Lets all chip in to help make the next (and future) Ubuntu Studio
releases a success.

Regards,

Ross Gammon
US Test Team Lead



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Fwd: Ubuntu 17.04 (Zesty Zapus) End of Life reached on January 13, 2018

[Ross Gammon]

FYI

 Forwarded Message 
Subject:Ubuntu 17.04 (Zesty Zapus) End of Life reached on January 13,
2018
Date:   Thu, 18 Jan 2018 00:13:36 +0200
From:   Steve Langasek 
To: ubuntu-annou...@lists.ubuntu.com


This is a follow-up to the End of Life warning sent earlier this month to
confirm that as of January 13, 2018, Ubuntu 17.04 is no longer supported. 
No more package updates will be accepted to 17.04, and it will be archived
to old-releases.ubuntu.com in the coming weeks.

The original End of Life warning follows, with upgrade instructions:

Ubuntu announced its 17.04 (Zesty Zapus) release almost 9 months ago, on
April 13, 2017.  As a non-LTS release, 17.04 has a 9-month support cycle
and, as such, will reach end of life on Saturday, January 13th.

At that time, Ubuntu Security Notices will no longer include information or
updated packages for Ubuntu 17.04.

The supported upgrade path from Ubuntu 17.04 is via Ubuntu 17.10.
Instructions and caveats for the upgrade may be found at:

https://help.ubuntu.com/community/Upgrades

Ubuntu 17.10 continues to be actively supported with security updates and
select high-impact bug fixes.  Announcements of security updates for Ubuntu
releases are sent to the ubuntu-security-announce mailing list, information
about which may be found at:

https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce

Development of a complete response to the highly-publicized Meltdown and
Spectre vulnerabilities is ongoing, and due to the timing with respect to
this End of Life, we will not be providing updated Linux kernel packages for
Ubuntu 17.04.  We advise users to upgrade to Ubuntu 17.10 and install the
updated kernel packages for that release when they become available.

For more information about Canonical’s response to the Meltdown and
Spectre vulnerabilities, see:

https://insights.ubuntu.com/2018/01/04/ubuntu-updates-for-the-meltdown-spectre-vulnerabilities/

Since its launch in October 2004 Ubuntu has become one of the most highly
regarded Linux distributions with millions of users in homes, schools,
businesses and governments around the world.  Ubuntu is Open Source
software, costs nothing to download, and users are free to customise or
alter their software in order to meet their needs.

On behalf of the Ubuntu Release Team,
-- Steve Langasek


--cvaofkriejaiobku
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

This is a follow-up to the End of Life warning sent earlier this month to
confirm that as of January 13, 2018, Ubuntu 17.04 is no longer supported.=
=20
No more package updates will be accepted to 17.04, and it will be archived
to old-releases.ubuntu.com in the coming weeks.

The original End of Life warning follows, with upgrade instructions:

Ubuntu announced its 17.04 (Zesty Zapus) release almost 9 months ago, on
April 13, 2017.  As a non-LTS release, 17.04 has a 9-month support cycle
and, as such, will reach end of life on Saturday, January 13th.

At that time, Ubuntu Security Notices will no longer include information or
updated packages for Ubuntu 17.04.

The supported upgrade path from Ubuntu 17.04 is via Ubuntu 17.10.
Instructions and caveats for the upgrade may be found at:

https://help.ubuntu.com/community/Upgrades

Ubuntu 17.10 continues to be actively supported with security updates and
select high-impact bug fixes.  Announcements of security updates for Ubuntu
releases are sent to the ubuntu-security-announce mailing list, information
about which may be found at:

https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce

Development of a complete response to the highly-publicized Meltdown and
Spectre vulnerabilities is ongoing, and due to the timing with respect to
this End of Life, we will not be providing updated Linux kernel packages for
Ubuntu 17.04.  We advise users to upgrade to Ubuntu 17.10 and install the
updated kernel packages for that release when they become available.

For more information about Canonical=E2=80=99s response to the Meltdown and
Spectre vulnerabilities, see:

https://insights.ubuntu.com/2018/01/04/ubuntu-updates-for-the-meltdown-spec=
tre-vulnerabilities/

Since its launch in October 2004 Ubuntu has become one of the most highly
regarded Linux distributions with millions of users in homes, schools,
businesses and governments around the world.  Ubuntu is Open Source
software, costs nothing to download, and users are free to customise or
alter their software in order to meet their needs.

On behalf of the Ubuntu Release Team,
--=20
Steve Langasek

--cvaofkriejaiobku
Content-Type: application/pgp-signature; name="signature.asc"

-BEGIN PGP SIGNATURE-

iQIcBAABCgAGBQJaX8qJAAoJEFaNMPMhshM9FZQP/jlCtNsFkHWDKC9s7MLr078X
86N1mXUq1jQJQB2Y2C7cU5kCMfbRiaNmqUtRW4dxVo/eW6McjzEYZsuBDfys9e/J
gaQ8RP70c/c35KPE+VG0MjhV+gGKyOmcrJzzaC2cSZ/5Yvlx3wU0OiG4C1FPeKAd

Re: [ubuntu-studio-devel] ubuntu-studio-devel Digest, Vol 127, Issue 5

[Ross Gammon]

On 11/17/2017 05:49 PM, Len Ovens wrote:
> On Fri, 17 Nov 2017, Ross Gammon wrote:
> 
>>>> If you are interested in understanding the build process for the Live
>>>> CDs/DVDs, you can try building them locally. There is some information
>>>> here (with further links):
>>>> https://wiki.ubuntu.com/UbuntuStudio/SetupLocalIsoBuildServer
>>>
>> Maybe I will ask on Ubuntu Devel for help to get some simple
>> instructions?
> 
> Your link above actually seems pretty simple and straight forward. It
> looks like things have changed since I last tried. I could get chroot
> directory with all the sw on it, but getting it to the ISO stage seemed
> to take a number of steps that didn't work for me. That link shows one
> script. To be honest, I would rather spend my time getting -controls
> ready but have been busy...

You are right. More scripts are needed. And they are a little bit secret
(Canonical only):
https://wiki.ubuntu.com/ReleaseTeam/CDImageSetup

Like you - a bit busy. I will store it up to try another day.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ubuntu-studio-devel Digest, Vol 127, Issue 5

[Ross Gammon]

On 11/16/2017 03:45 PM, Len Ovens wrote:
> On Thu, 16 Nov 2017, Ross Gammon wrote:
> 
>> If you are interested in understanding the build process for the Live
>> CDs/DVDs, you can try building them locally. There is some information
>> here (with further links):
>> https://wiki.ubuntu.com/UbuntuStudio/SetupLocalIsoBuildServer
> 
> I have tried... but I have never gotten an ISO out of the deal. There
> does not seem to be a script that just does it all... well there must be
> because the ISO are built automatically, but the script does not seem to
> be available. Be nice to cd ~/some_directory; make configure --$arc; make
> 
> Or something like that.
> 
> I should try again though, that looks easier than whatever I tried last
> time.

Well the code seems to be here (link points to the README):
http://bazaar.launchpad.net/~ubuntu-cdimage/ubuntu-cdimage/mainline/view/head:/README

As there had been a commit to the repository about the same time as the
failure, I requested a new build - and it built!

According to the buildlog, the build seems to be done in an lxc
container, so it should be possible to do the same locally.

Maybe I will ask on Ubuntu Devel for help to get some simple instructions?

Regards,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Carla

[Ross Gammon]

On 10/02/2017 05:17 PM, Len Ovens wrote:
> On Mon, 2 Oct 2017, Ross Gammon wrote:
> 
>> Over the weekend, I started to look at packaging Carla. It has a LONG
>> way to go to comply with Debian policy, is missing some functionality
>> due to missing dependencies, and it also fails to build on 32bit, but
>> you are welcome to install and test my WIP (Work In Progress) here:
>> https://launchpad.net/~rosco2/+archive/ubuntu/new
> 
> Cool. How does it mess up debian policy? Does it just depend on the
> wrong things or is it deeper than that? It is very acceptable not to
> include Linux Sampler either as a dep or anything else. In fact if all
> we get is the rack that loads plugins and the plugin that loads other
> plugins, it is well worth it. Being able to load win-VSTs while nice, is
> not required for a first go if we can get it into the repos without.

It is mainly the bundled software that is already packaged separately in
Debian (lilv etc.). It is allowed to bundle, if there is a valid reason
(e.g. the bundled software is heavily patched, or there is a large delta
between the Debian version and the one that Carla uses). But it will
take me some time to sort it out & test using the system versions.
There are also quite a few other minor things that will take time to
sort out.

Thanks for the data on the dependencies. It will help to prioritise. An
ntk package (one of the optional dependencies) is nearly ready in the
Debian Multimedia Team. Jaromir could not find a sponsor back when he
packaged it. But now I have the power!

> 
>> I haven't actually tested it myself yet, so don't try it on a machine
>> that you depend on.
> 
> It is only built for Artful and so while I could boot that up, I can't
> test it my normal workflow on 1604. Not that I use Carla or plugins that
> require it on a regular basis...  :)

I will see if I can upload something for Xenial tonight.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Carla

[Ross Gammon]

Hi All,

Over the weekend, I started to look at packaging Carla. It has a LONG
way to go to comply with Debian policy, is missing some functionality
due to missing dependencies, and it also fails to build on 32bit, but
you are welcome to install and test my WIP (Work In Progress) here:
https://launchpad.net/~rosco2/+archive/ubuntu/new

I haven't actually tested it myself yet, so don't try it on a machine
that you depend on.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Artful 17.10 Final Beta Testing underway

[Ross Gammon]

Hi All,

Please help make sure the release of Ubuntu Studio Artful goes smoothly,
and begin testing the Final Beta with us:
http://iso.qa.ubuntu.com/qatracker/milestones/382/builds

We need as many different types of machine and hardware tested as
possible. Please do not use your "only" machine for this, use a spare
one, or a spare hard disk. Accidents can occasionally happen with a Beta
release.

Take a look and see what has changed since the version of Ubuntu Studio
you are using. Tell us what you think.

Instructions and download links are on that page, but if you need help
then sing out here (or on irc).

The Final Beta release is planned for Thursday 28th September.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Artful - Debian & Feature Freeze

[Ross Gammon]

Hi Len,

Success!

On 08/30/2017 08:27 AM, Ross Gammon wrote:
> On 08/29/2017 11:41 PM, Len Ovens wrote:
>> On Tue, 29 Aug 2017, Ross Gammon wrote:
>>
>>> On 08/29/2017 09:30 PM, Ross Gammon wrote:
>>>> In fact, I was playing with it on Sunday, but it looks like I have no
>>>> cpuFreq driver installed, so it didn't work for me (the governor in
>>>> performance bit). But reading a wiki just now, I see that the driver is
>>>> supposed to be loaded by cpufrequtils. So either the init script is not
>>>> working for me, or I need to do a reboot. I will play some more in a
>>>> minute.
>>>
>>> A reboot does not fix it. I may have run into something like this bug:
>>> https://bugs.launchpad.net/ubuntu/+source/cpufrequtils/+bug/1084262
>>>
>>> More investigation required. Unfortunately I have to sleep now.
>>
>> I am not sure, does -controls have a dep for cpufrequtils? It has worked
>> fine for me so far... I guess I need to try it on 17.10 as well. Make
>> sure you have cpufrequtils installed (it is not by default).
>>
>>
>> -- 
>> Len Ovens
>> www.ovenwerks.net
>>
>>
> 
> Yes, I think the dependency is there. When I installed the .deb it
> complained, and apt-get -f install did the job of installing cpufrequtils.
> 
> But none of the kernel modules in my /some/path/kernel/drivers/cpufreq
> directory are called cpufreq* something. They are called amd*something*.mo.
> Apparently this causes some trouble for the init script in cpufrequtils
> to load the module (at least for the people in the bugs - there are at
> least two with similar problems since 2012). I ran out of time to try
> loading one of them manually to see if I could set it to "performance"
> after that.
> 
> Now I have to run to work..
> 

It turned out that I had to turn on "Clean & Quiet" in my BIOS settings.
Doh! Maybe we should add a note about that (and the equivalent Speedstep
for Intel) in the Help dialogue (or at least in the README).

Now I have had a little play & confirmed that I can change the governor
setting on the fly, and it survives a boot.

I did get a little muddled up once I started fiddling with the audio
settings. I lost jack-sink at one point. Which settings take affect when
you click "Apply Settings"? Is it all the interface card choices etc. at
the top, or just the three tick boxes at the bottom (jack sink etc.)?

Another minor thing I noticed is that it took 4 clicks to close down the
"help" dialogue, and it changed size each time.

Anyway, there were no crashes or annoying bugs. Should I try and get a
sponsor for an upload before the final beta?

Or is there anything you would like to tweak first? I will probably at
least add some notes to the README first.

It would have been nice to have it for the first Beta. But as usual, I
am too slow.

Cheers,

Ross

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Artful - Debian & Feature Freeze

[Ross Gammon]

On 08/29/2017 09:30 PM, Ross Gammon wrote:
> In fact, I was playing with it on Sunday, but it looks like I have no
> cpuFreq driver installed, so it didn't work for me (the governor in
> performance bit). But reading a wiki just now, I see that the driver is
> supposed to be loaded by cpufrequtils. So either the init script is not
> working for me, or I need to do a reboot. I will play some more in a minute.

A reboot does not fix it. I may have run into something like this bug:
https://bugs.launchpad.net/ubuntu/+source/cpufrequtils/+bug/1084262

More investigation required. Unfortunately I have to sleep now.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Artful - Debian & Feature Freeze

[Ross Gammon]

On 08/29/2017 11:51 AM, eylul wrote:
> Congrats with being a debian developer!!! :)
> 
> Did we opt-in to beta 1, and do we have a list of what needs testing
> beyond the usual this round?

I will sign up now.

> 
> Qjackctl is one,
> 
> the controls is another one.

We have not had any feedback on the testing version:
https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild/+build/12643119

So I have not been game to try and get it uploaded yet.

In fact, I was playing with it on Sunday, but it looks like I have no
cpuFreq driver installed, so it didn't work for me (the governor in
performance bit). But reading a wiki just now, I see that the driver is
supposed to be loaded by cpufrequtils. So either the init script is not
working for me, or I need to do a reboot. I will play some more in a minute.



> 
> Anything else we need to keep an eye out for when testing?


Not that I am aware of, but lots of our important apps have been updated
(eg. Ardour to 5.11).

> 
> I am unfortunately probably still semi quiet until early September, but
> after that I will be around for testing, release notes etc (and I didn't
> forget the wallpapers).
> 
> 
> Best
> 
> Eylul
> 
> 
> On 08/25/2017 06:57 PM, Ross Gammon wrote:
>> Hi All,
>>
>> Just a quick note that yesterday we passed the Feature Freeze and Debian
>> Import Freeze deadline, and we are fast approaching the 1st Beta (August
>> 31st):
>> https://wiki.ubuntu.com/ArtfulAardvark/ReleaseSchedule
>>
>> This means if we need any updated packages from Debian, or we want to
>> upload any new feature, we need a Freeze exception.
>>
>> Unfortunately, the only Ubuntu work I have managed in the last few days,
>> is to merge the latest Qjackctl from Debian.
>>
>> On other new, I am now a Debian Developer, so I can be more useful
>> helping with our packages there.
>>
>> Regards,
>>
>> Ross
>>
>>
>>
> 
> 
> 


-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Ubuntu Studio Artful - Debian & Feature Freeze

[Ross Gammon]

Hi All,

Just a quick note that yesterday we passed the Feature Freeze and Debian
Import Freeze deadline, and we are fast approaching the 1st Beta (August
31st):
https://wiki.ubuntu.com/ArtfulAardvark/ReleaseSchedule

This means if we need any updated packages from Debian, or we want to
upload any new feature, we need a Freeze exception.

Unfortunately, the only Ubuntu work I have managed in the last few days,
is to merge the latest Qjackctl from Debian.

On other new, I am now a Debian Developer, so I can be more useful
helping with our packages there.

Regards,

Ross



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] Ubuntu Studio Xenial 16.04.3 Release Testing

[Ross Gammon]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi All,

It is great to see a new tester in the ISO Tracker page. Thanks Helios!

Is anyone else planning to run a test of the latest Xenial installation
image? The more tests we have (especially on different hardware etc.),
the better.

Please let me know, as I need to let the Release Team know when we are
finished testing, and they want to release later today.

Regards,

Ross

On 08/01/2017 05:55 PM, Ross Gammon wrote:
> HI All, > > This is a call for help. > > It is time for the 2nd last release
update of Ubuntu Studio Xenial > (16.04.3), and we need help to test the
images before we release them to > the public. > > The images are now
available, and the release is planned for Thursday > 3rd August. > >
Images (download instructions are linked from there): > > 32bit: >
http://iso.qa.ubuntu.com/qatracker/milestones/380/builds/153566/testcases
> > 64bit: >
http://iso.qa.ubuntu.com/qatracker/milestones/380/builds/153565/testcases
> > There are links for how to test and use the testing tracker here: >
> http://iso.qa.ubuntu.com/qatracker > > Get cracking, and sing out for
help here, or on IRC if you need it. > > Regards, > > Ross > > Ubuntu
Studio Test Team Lead > > > >
-BEGIN PGP SIGNATURE-

iQI0BAEBCgAeBQJZgsXcFxxyb3Njb0B1YnVudHVzdHVkaW8ub3JnAAoJEHM+a/k8
6PbZg1gP/imr7QnnMTl0eP7KTByyt2e7RdH3/t+UqaFpQaen3yqYnbTM1+tuQgKx
EN6riUHUcuDqJ64hwp5oi50twH0Hsxo8Iy6zhyVO6IFtvZiytFWd0EzqAA9KX4F/
1hhbZbvsEiD4hiJe6qLaZd46wI8dnOlchePEdgu86amLeHCDzxfDZn08A73Z6jdq
cZyEycnwmzNcoEFBdYHSRPjbo0rQqSRLh3Q9xT03TxJcRzsaHS64vayUmcZqYETV
j8PvzTp7GPy1jS/qz1KE/xRM/ySP8SyFOlwwjPyoa4PJi+BY577FF8Axj+LCIlvE
PIepKeZzlYaNwR0wOd7KBvH1ekwD8PC1dESj0FtcvizdwDTvINPrRAV342JkT6DO
C7Xdh10GxglM7JPHGgtRWtsSCFA7GExjb067Ejh+iEtYpNjY/vz1Ro0j3YIe/5Og
oxx94QqyEuRBsC8/v88aURyfJsR97IgBnX6UZqyIlKuHxSRh6ZihILFWnDnq41UI
BWxvDE5h88ms59hOcZV5fb90d1cGSUGbfF4FnbGaiFbGzIPE/752+yYKtkSen/Zm
ArUW8JPA/HSb9RU4x6zNR8viYU7yUUGsxSZnwb+yTIGHE8vSci377AqhYSqxIt7Y
QV4NU30h0+5Q2NPctdW15NtqElZblxAlFZwrN+19o3ZMeO8QNcNi
=1D40
-END PGP SIGNATURE-

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Ubuntu Studio Xenial 16.04.3 Release Testing

[Ross Gammon]

HI All,

This is a call for help.

It is time for the 2nd last release update of Ubuntu Studio Xenial
(16.04.3), and we need help to test the images before we release them to
the public.

The images are now available, and the release is planned for Thursday
3rd August.

Images (download instructions are linked from there):

32bit:
http://iso.qa.ubuntu.com/qatracker/milestones/380/builds/153566/testcases

64bit:
http://iso.qa.ubuntu.com/qatracker/milestones/380/builds/153565/testcases

There are links for how to test and use the testing tracker here:

http://iso.qa.ubuntu.com/qatracker

Get cracking, and sing out for help here, or on IRC if you need it.

Regards,

Ross

Ubuntu Studio Test Team Lead




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

Re: [ubuntu-studio-devel] ubuntu-studio-devel Digest, Vol 123, Issue 9

[Ross Gammon]

Hi Helios,

I am not sure exactly what you are trying to achieve, but understand it
might be something to do with keeping Ubuntu Studio working with older
hardware (especially older 32 bit PCs).

As Len says, we are still providing 32 bit installation media at the
moment, but there are plans to drop them eventually. This is because,
testing the installation media (ISOs) takes time, and we struggle to
find enough testers. Actually, I am about to announce a test of the
Ubuntu Studio Xenial 16.04.3 ISOs which you are welcome to help out with.

Even if we stop providing 32 bit installation media, it should still be
possible to upgrade your existing Ubuntu Studio 32 bit installation, as
packages will still be built for that architecture (and several others).
See https://launchpad.net/builders/.

If you want to know how to go ahead and create the 32 bit media anyway.
The Live CDs are built here (e.g. the current development release -
https://launchpad.net/~ubuntu-cdimage/+livefs/ubuntu/artful/ubuntustudio).
From there you can find links to the code etc. There is also some other
information here:
https://wiki.ubuntu.com/UbuntuStudio/SetupLocalIsoBuildServer.

Then we would need a place to publish the images (for users), and to
allow people to test them and provide feedback. Currently this is done
here: http://iso.qa.ubuntu.com/qatracker/milestones/380/builds (but the
32 bit pages will one day disappear).

I hope that helps (although I am not sure if it is what you are after).

Regards,

Ross

On 08/01/2017 03:39 PM, Helios Martinez Dominguez wrote:
> Thank you, Ovens. The fact is my knowledge about the process lacks the
> proper sources where to start from, to get to proceed myself. If there
> are any suggestions where i could start investigating about it, it
> would be grateful. Thanks.
>
> I recently started to configure uck (ubuntu customization kit)
> distributions through shell interactivity directly, having some issues
> with configuration stability. As i understand it, the process has to
> do mainly with compiling the sources for the proper processor at
> "installation time" by configuring the compiler and the linker to make
> use of the processor's configuration, specifically. If there is any
> known way i can instruct myself into such matters more profoundly, for
> instance: how to configure the compiling process through an script
> which chooses compiler's configuration at glance over the system's
> configuration before the installation process is done(?). I remember
> we used to compile from source, back in the nineties with Red Hat from
> 4 to 5 adding features at requirement and i am available for the task
> myself, the fact is i am "out of shape" about it and my knowledge
> about the now-a-days process seem to change after each distribution
> version, so i would like to refresh such knowledge to get in the mood
> and do it. I thought there would be graphic ways (GUI) to do the
> configuration through a front end for the task, in the uck or
> something. I just seem to have missed the way at some point.
>
> Sorry if my requirement seemed out of context and outdated.
>
>
> 
>
>
> WORLD CONSTITUTION AND PARLIAMENT ASSOC. (WCPA)  |  UNITED NATIONS
> *
> Helios Martínez Domínguez
> *Consorcio Cooperativo Cinematográfico Artístico Musical (CCCAM)
> --Director General
>
>
> helios.url.ph  
> cccam.esy.es    
> onu.url.ph 
>
>
> AVISO LEGAL
>
> La información que contiene esta cuenta y este correo es privilegiada,
> confidencial, y se encuentra protegida por la Ley.
> Su contenido y archivos adjuntos son para uso exclusivo
> de los destinatarios arriba mencionados y su emisor.
> Cualquier intercepción, acceso, apertura, uso, difusión
> o copia no autorizada están estrictamente prohibidas.
> En caso de haber recibido su contenido por error u otra circunstancia,
> elimínelo
> y notifique inmediatamente a las autoridades pertinentes y al
> propietario del correo.
>
> Gracias.
>
> Ley_especial_contra_los_delitos_informaticos (Venezuela)
> 
>
> Privacidad y secreto de las telecomunicaciones - Incibe (España)
> 
>
> CONVENTION ON THE PRIVILEDGES AND INMUNITIES OF THE UNITED NATIONS
> 
>
>
> On Mon, Jul 31, 2017 at 8:00 AM,
>  > wrote:
>
> Send ubuntu-studio-devel mailing list submissions to
> ubuntu-studio-devel@lists.ubuntu.com
> 
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> 

[ubuntu-studio-devel] Ubuntu Studio Controls

[Ross Gammon]

Hi Len,

I just successfully installed an Artful 1704 VirtualBox VM this
afternoon, and installed the daily build of ubuntustudio-controls
(https://code.launchpad.net/~ubuntustudio-dev/+archive/ubuntu/autobuild/+build/12643119)
to test out the graphical bits.

It is all looking great!

Some comments:

1. In the "help", I am not sure of the "if requested" wording for the
realtime setting.

2. To test out what might be meant by that, I thought I would fiddle
with the realtime setting. But it is no longer there! us-controls tells
me that RealTime is enabled. If I fire up QJackCtl, and untick RT there,
us-controls does not update its status (with any combination of opening
and closing QJackCtl & us-controls). I see from the README that I
probably should have logged out. Should the help dialogue mention this?
Note: all of this is done without Jack actually started (as I was too
lazy to choose higher later latency settings in the VM & to test a reboot).

3. As you can tell, after all this time I am still a bit of a Linux
Audio noob. Which brings me to documentation. I assume the README &
ROADMAP files need updating. You should probably add yourself to the
AUTHORS too! https://help.ubuntu.com/community/UbuntuStudioControls has
needed an update for a long time. There used to be a manpage
(http://manpages.ubuntu.com/manpages/trusty/en/man1/ubuntustudio-controls.1.html)
which references https://wiki.ubuntu.com/UbuntuStudio/SettingsApp which
is wildly out of date. I suppose the manpage is only really needed if
users might try and run the scripts from the terminal. The us-controls
launchpad page has a link to a wiki which doesn't exist
(http://wiki.ubuntu.com/UbuntuStudio/UbuntuStudioControls). There is a
useful links section at the bottom of
https://wiki.ubuntu.com/UbuntuStudio/ControlsRedesign which probably
contains some documentation to assist with producing a new wiki page.
Are there any others?

Next I will upgrade the real hardware machine in the basement, and give
it a proper spin.

I hope others out there reading this might be encouraged to give it a
spin. Comments gratefully received.

Well done Len!

Cheers,

Ross




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Participating in Artful (17.10) Alpha 2?

[Ross Gammon]

All,

Time flies! Alpha 2 is next week.

As we have failed to do anything (again :-) ), unless anyone objects - I
will opt out of Alpha 2.

Len,

I broke my VirtualBox whilst on holiday (trying to fix something else),
so I was not able to test us-controls. But I am back home now, and I
have more machines to play with, so hopefully I will give it a go tomorrow.

Regards,

Ross




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Fwd: Ubuntu 16.10 (Yakkety Yak) End of Life reached on July 20 2017

[Ross Gammon]

Hi All,

I am sure you have all seen the announcement, but just in case - if you
are running Ubuntu Studio Yakkety (16.10), it might be a good time to
upgrade to Zesty (17.04). See a copy of the full announcement below.

Regards,

Ross

 Forwarded Message 
Subject:Ubuntu 16.10 (Yakkety Yak) End of Life reached on July 20 2017
Date:   Thu, 20 Jul 2017 23:23:31 +
From:   Adam Conrad 
To: ubuntu-annou...@lists.ubuntu.com
CC: ubuntu-security-annou...@lists.ubuntu.com



This is a follow-up to the End of Life warning sent earlier this month
to confirm that as of today (July 20, 2017), Ubuntu 16.10 is no longer
supported.  No more package updates will be accepted to 16.10, and
it will be archived to old-releases.ubuntu.com in the coming weeks.

The original End of Life warning follows, with upgrade instructions:

Ubuntu announced its 16.10 (Yakkety Yak) release almost 9 months
ago, on October 13, 2016.  As a non-LTS release, 16.10 has a 9-month
support cycle and, as such, the support period is now nearing its
end and Ubuntu 16.10 will reach end of life on Thursday, July 20th.

At that time, Ubuntu Security Notices will no longer include
information or updated packages for Ubuntu 16.10.

The supported upgrade path from Ubuntu 16.10 is via Ubuntu 17.04.
Instructions and caveats for the upgrade may be found at:

https://help.ubuntu.com/community/ZestyUpgrades

Ubuntu 17.04 continues to be actively supported with security updates
and select high-impact bug fixes.  Announcements of security updates
for Ubuntu releases are sent to the ubuntu-security-announce mailing
list, information about which may be found at:

https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce

Since its launch in October 2004 Ubuntu has become one of the most
highly regarded Linux distributions with millions of users in homes,
schools, businesses and governments around the world. Ubuntu is Open
Source software, costs nothing to download, and users are free to
customise or alter their software in order to meet their needs.

On behalf of the Ubuntu Release Team,

Adam Conrad

-- 
ubuntu-announce mailing list
ubuntu-annou...@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-announce



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel

[ubuntu-studio-devel] Removing zynjacku from seeds

[Ross Gammon]

Hi All,

I was just looking into this recent bug:

https://bugs.launchpad.net/ubuntu/+source/zynjacku/+bug/1698225

Looking through my archives, we discussed a while back that zynjacku
could probably be removed from our seeds. At the time Len thought that
packaging Carla (still on my todo list) would be the best way to ease
the problem, giving a lot more flexibility regarding plugins.

The bug has a link to the Debian reason for removal, and a link to the
upstream announcement that zynjacku would no longer be maintained (for
reference).

If there are no objections, I will remove zynjacku from our seeds and
ask the Ubuntu Archive Team to remove it from Ubuntu as well.

Regards,

Ross




signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel