29 Oct
2012
29 Oct
'12
9:35 p.m.
Hi,
Does anyone know whats going on with pulseaudio-module-jackdbus in Debian
Wheezy?
On my system the jackdbus module doesn't exist in the repos and the result
is that pulseaudio doesn't play nice with jack.
I can see that jackd2 was compiled with dbus support so not sure what's
going on with the missing pulse module.
--
Patrick Shirkey
Boost Hardware Ltd
29 Oct
29 Oct
9:45 p.m.
On Tue, October 30, 2012 8:35 am, Patrick Shirkey wrote:
Hi,
Does anyone know whats going on with pulseaudio-module-jackdbus in Debian
Wheezy?
On my system the jackdbus module doesn't exist in the repos and the result
is that pulseaudio doesn't play nice with jack.
I can see that jackd2 was compiled with dbus support so not sure what's
going on with the missing pulse module.
I can see with pacmd list-modules that module-jackdbus-connect is loaded
so the module must be compiled into pulse directly.
So any thoughts on why the module is not kicking in?
--
Patrick Shirkey
Boost Hardware Ltd
11:12 p.m.
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
On Tue, October 30, 2012 8:35 am, Patrick Shirkey
wrote:
On ubuntu (which normally uses debian src packages), The module name is
module-jackdbus-detect. I don't think I have seen a module called
module-jackdbus-connect even on the pulse site.
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
Even if jackd comes with dbus support, it can be started without. so use
ps x or similar to check that the running app is jackdbus and not jackd.
If you are using qjackctl there is a checkbox under misc "Enable D-Bus
interface" that has to be checked.
--
Len Ovens
www.OvenWerks.net
Hi,
Does anyone know whats going on with pulseaudio-module-jackdbus in
Debian
Wheezy?
On my system the jackdbus module doesn't exist in the repos and the
result
is that pulseaudio doesn't play nice with jack.
I can see that jackd2 was compiled with dbus support so not sure what's
going on with the missing pulse module.
I can see with pacmd list-modules that module-jackdbus-connect is loaded
so the module must be compiled into pulse directly.
So any thoughts on why the module is not kicking in?
30 Oct
30 Oct
12:13 a.m.
On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
You got the gist...
On Tue, October 30, 2012 8:35 am, Patrick Shirkey
wrote:
On ubuntu (which normally uses debian src packages), The module name is
module-jackdbus-detect. I don't think I have seen a module called
module-jackdbus-connect even on the pulse site.
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
Hi,
Does anyone know whats going on with pulseaudio-module-jackdbus in
Debian
Wheezy?
On my system the jackdbus module doesn't exist in the repos and the
result
is that pulseaudio doesn't play nice with jack.
I can see that jackd2 was compiled with dbus support so not sure what's
going on with the missing pulse module.
I can see with pacmd list-modules that module-jackdbus-connect is loaded
so the module must be compiled into pulse directly.
So any thoughts on why the module is not kicking in? Even if jackd comes with dbus support, it can be
started without. so use
ps x or similar to check that the running app is jackdbus and not jackd.
There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
If you are using qjackctl there is a checkbox under
misc "Enable D-Bus
interface" that has to be checked.
That helps which means that debian wheezy has support for pulseaudio,
module-jackdbus-detect and jackd2 by default but there is still an error:
====
Failed to acquire device name : Audio0 error : Method "RequestRelease"
with signature "i" on interface "org.freedesktop.ReserveDevice1"
doesn't
exist
Audio device hw:0 cannot be acquired...
====
What I find completely bizarre is that the top 5 hits on google for this
error have people recommending to disable pulseaudio or use an alternate
method to connect. It seems people have known about this issue for a while
and been ignoring it or waiting for someone else to figure it out.
--
Patrick Shirkey
Boost Hardware Ltd
4:42 a.m.
On 10/29/2012 02:12 PM, Patrick Shirkey wrote:
On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
Removing PulseAudio works for me!
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
You got the gist...
On Tue, October 30, 2012 8:35 am, Patrick Shirkey
wrote:
On ubuntu (which normally uses debian src packages), The module name is
module-jackdbus-detect. I don't think I have seen a module called
module-jackdbus-connect even on the pulse site.
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
Hi,
Does anyone know whats going on with pulseaudio-module-jackdbus in
Debian
Wheezy?
On my system the jackdbus module doesn't exist in the repos and the
result
is that pulseaudio doesn't play nice with jack.
I can see that jackd2 was compiled with dbus support so not sure what's
going on with the missing pulse module.
I can see with pacmd list-modules that module-jackdbus-connect is loaded
so the module must be compiled into pulse directly.
So any thoughts on why the module is not kicking in? Even if jackd comes with dbus support, it can be
started without. so use
ps x or similar to check that the running app is jackdbus and not jackd.
There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
If you are using qjackctl there is a checkbox
under misc "Enable D-Bus
interface" that has to be checked.
That helps which means that debian wheezy has support for pulseaudio,
module-jackdbus-detect and jackd2 by default but there is still an error:
====
Failed to acquire device name : Audio0 error : Method "RequestRelease"
with signature "i" on interface "org.freedesktop.ReserveDevice1"
doesn't
exist
Audio device hw:0 cannot be acquired...
====
What I find completely bizarre is that the top 5 hits on google for this
error have people recommending to disable pulseaudio or use an alternate
method to connect. It seems people have known about this issue for a while
and been ignoring it or waiting for someone else to figure it out.
4:51 a.m.
On Tue, October 30, 2012 3:42 pm, david wrote:
On 10/29/2012 02:12 PM, Patrick Shirkey wrote:
It seems like a regression to me and it's not helping people who want to
use both pulseaudio and jack together.
For most professionals it's completely unnecessary to remove pulse as jack
can run on a second "pro" soundcard. This issue is only a headache when
the user has only one sound card to work with and given that is the
majority of n00b or amateur users it makes sense for pulse and jack to
work well together.
--
Patrick Shirkey
Boost Hardware Ltd
On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
Removing PulseAudio works for me!
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
You got the gist...
On Tue, October 30, 2012 8:35 am, Patrick Shirkey
wrote:
> Hi,
>
> Does anyone know whats going on with pulseaudio-module-jackdbus in
> Debian
> Wheezy?
>
> On my system the jackdbus module doesn't exist in the repos and the
> result
> is that pulseaudio doesn't play nice with jack.
>
> I can see that jackd2 was compiled with dbus support so not sure
> what's
> going on with the missing pulse module.
>
I can see with pacmd list-modules that module-jackdbus-connect is
loaded
so the module must be compiled into pulse directly.
So any thoughts on why the module is not kicking in?
On ubuntu (which normally uses debian src packages), The module name is
module-jackdbus-detect. I don't think I have seen a module called
module-jackdbus-connect even on the pulse site.
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
Even if jackd comes with dbus support, it can be
started without. so
use
ps x or similar to check that the running app is jackdbus and not
jackd.
There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
If you are using qjackctl there is a checkbox
under misc "Enable D-Bus
interface" that has to be checked.
That helps which means that debian wheezy has support for pulseaudio,
module-jackdbus-detect and jackd2 by default but there is still an
error:
====
Failed to acquire device name : Audio0 error : Method "RequestRelease"
with signature "i" on interface "org.freedesktop.ReserveDevice1"
doesn't
exist
Audio device hw:0 cannot be acquired...
====
What I find completely bizarre is that the top 5 hits on google for this
error have people recommending to disable pulseaudio or use an alternate
method to connect. It seems people have known about this issue for a
while
and been ignoring it or waiting for someone else to figure it out.
5:22 p.m.
On 10/29/2012 06:51 PM, Patrick Shirkey wrote:
On Tue, October 30, 2012 3:42 pm, david wrote:
Well, I'm one of those weird people who see *no need whatever* for
PulseAudio. Like Linux needs Yet Another Sound Server to confuse people
and dilute developer resources ...
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
On 10/29/2012 02:12 PM, Patrick Shirkey wrote:
It seems like a regression to me and it's not helping people who want to
use both pulseaudio and jack together.
For most professionals it's completely unnecessary to remove pulse as jack
can run on a second "pro" soundcard. This issue is only a headache when
the user has only one sound card to work with and given that is the
majority of n00b or amateur users it makes sense for pulse and jack to
work well together.
On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
Removing PulseAudio works for me!
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
> On Tue, October 30, 2012 8:35 am, Patrick Shirkey wrote:
>> Hi,
>>
>> Does anyone know whats going on with pulseaudio-module-jackdbus in
>> Debian
>> Wheezy?
>>
>> On my system the jackdbus module doesn't exist in the repos and the
>> result
>> is that pulseaudio doesn't play nice with jack.
>>
>> I can see that jackd2 was compiled with dbus support so not sure
>> what's
>> going on with the missing pulse module.
>>
>
> I can see with pacmd list-modules that module-jackdbus-connect is
> loaded
> so the module must be compiled into pulse directly.
>
> So any thoughts on why the module is not kicking in?
On ubuntu (which normally uses debian src packages), The module name is
module-jackdbus-detect. I don't think I have seen a module called
module-jackdbus-connect even on the pulse site.
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
You got the gist...
Even if jackd comes with dbus support, it can be
started without. so
use
ps x or similar to check that the running app is jackdbus and not
jackd.
There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
If you are using qjackctl there is a checkbox
under misc "Enable D-Bus
interface" that has to be checked.
That helps which means that debian wheezy has support for pulseaudio,
module-jackdbus-detect and jackd2 by default but there is still an
error:
====
Failed to acquire device name : Audio0 error : Method "RequestRelease"
with signature "i" on interface "org.freedesktop.ReserveDevice1"
doesn't
exist
Audio device hw:0 cannot be acquired...
====
What I find completely bizarre is that the top 5 hits on google for this
error have people recommending to disable pulseaudio or use an alternate
method to connect. It seems people have known about this issue for a
while
and been ignoring it or waiting for someone else to figure it out. 
5:28 p.m.
On Tue, Oct 30, 2012 at 1:22 PM, david <gnome(a)hawaii.rr.com> wrote:
Well, I'm one of those weird people who see *no need whatever* for
PulseAudio. Like Linux needs Yet Another Sound Server to confuse people and
dilute developer resources ...
pulseaudio plays a very valuable role in providing services that no other
sound server does. it is unfortunate that the server/user-space view of
linux audio has been fractured in this way but that doesn't make PA a bad
thing all by itself.
5:26 a.m.
2012/10/30 Patrick Shirkey <pshirkey(a)boosthardware.com>
On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
You got the gist...
jackdbus is in debian wheezy and it comes with jackd2 package.
http://packages.debian.org/search?suite=wheezy&arch=any&mode=path&a…
-r
--
*L'unica speranza di catarsi, ammesso che ne esista una, resta affidata
all'istinto di ribellione, alla rivolta non isterilita in progetti, alla
protesta violenta e viscerale. (V. Evangelisti)
*
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
On Tue, October 30, 2012 8:35 am, Patrick Shirkey
wrote:
On ubuntu (which normally uses debian src packages), The module name is
module-jackdbus-detect. I don't think I have seen a module called
module-jackdbus-connect even on the pulse site.
Hi,
Does anyone know whats going on with pulseaudio-module-jackdbus in
Debian
Wheezy?
On my system the jackdbus module doesn't exist in the repos and the
result
is that pulseaudio doesn't play nice with jack.
I can see that jackd2 was compiled with dbus support so not sure what's
going on with the missing pulse module.
I can see with pacmd list-modules that module-jackdbus-connect is loaded
so the module must be compiled into pulse directly.
So any thoughts on why the module is not kicking in? Even if jackd comes with dbus support, it can be
started without. so use
ps x or similar to check that the running app is jackdbus and not jackd.
There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
5:51 a.m.
On Tue, October 30, 2012 4:26 pm, Raffaele Morelli wrote:
2012/10/30 Patrick Shirkey
<pshirkey(a)boosthardware.com>
You're correct. When I looked yesterday I had jackd and jackd2. Today I
have jackd and jackdbus instead.
No wonder people get confused about how to get this stuff working.
What possible reason is there to have jackd and jackd2 *or* jackd and
jackdbus ?
The former must be for jack1 package and the later for the jack2 package
but why would there even be a jackd2 option for the jack1 package? It's
completely redundant.
And why isn't a jackd2 option installed with the jack2 package?
--
Patrick Shirkey
Boost Hardware Ltd
On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
is
You got the gist...
jackdbus is in debian wheezy and it comes with jackd2 package.
http://packages.debian.org/search?suite=wheezy&arch=any&mode=path&a…
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
> On Tue, October 30, 2012 8:35 am, Patrick Shirkey wrote:
>> Hi,
>>
>> Does anyone know whats going on with pulseaudio-module-jackdbus in
>> Debian
>> Wheezy?
>>
>> On my system the jackdbus module doesn't exist in the repos and the
>> result
>> is that pulseaudio doesn't play nice with jack.
>>
>> I can see that jackd2 was compiled with dbus support so not sure
what's
>> going on with the missing pulse module.
>>
>
> I can see with pacmd list-modules that module-jackdbus-connect is
loaded
so the
module must be compiled into pulse directly.
So any thoughts on why the module is not kicking in?
On ubuntu (which normally uses debian src packages), The module name module-jackdbus-detect. I don't think I have
seen a module called
module-jackdbus-connect even on the pulse site.
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
Even if jackd comes with dbus support, it can be
started without. so
use
ps x or similar to check that the running app is
jackdbus and not
jackd.
There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
6:17 a.m.
On Tue, October 30, 2012 4:51 pm, Patrick Shirkey wrote:
On Tue, October 30, 2012 4:26 pm, Raffaele Morelli wrote:
So, If I tell jackqtl to use jackdbus I get a message saying:
----
jackdbus should be auto-executed by D-Bus message bus daemon.
If you want to run it manually anyway, specify "auto" as only parameter
----
The obvious question is where do you specify "auto" as the only parameter?
I tried adding it to qjackctl but it doesn't work there.
This process was being worked on at least three years ago. What happened?
Did everyone just get bored of testing stuff or something?
--
Patrick Shirkey
Boost Hardware Ltd
2012/10/30 Patrick Shirkey
<pshirkey(a)boosthardware.com>
You're correct. When I looked yesterday I had jackd and jackd2. Today I
have jackd and jackdbus instead.
No wonder people get confused about how to get this stuff working.
What possible reason is there to have jackd and jackd2 *or* jackd and
jackdbus ?
The former must be for jack1 package and the later for the jack2 package
but why would there even be a jackd2 option for the jack1 package? It's
completely redundant.
And why isn't a jackd2 option installed with the jack2 package?
On Tue, October 30, 2012 10:11 am, Len Ovens wrote:
You got the gist...
jackdbus is in debian wheezy and it comes with jackd2 package.
http://packages.debian.org/search?suite=wheezy&arch=any&mode=path&a…
On Mon, October 29, 2012 2:45 pm, Patrick Shirkey wrote:
> On Tue, October 30, 2012 8:35 am, Patrick Shirkey wrote:
>> Hi,
>>
>> Does anyone know whats going on with pulseaudio-module-jackdbus in
>> Debian
>> Wheezy?
>>
>> On my system the jackdbus module doesn't exist in the repos and the
>> result
>> is that pulseaudio doesn't play nice with jack.
>>
>> I can see that jackd2 was compiled with dbus support so not sure
what's
>> going on with the missing pulse module.
>>
>
> I can see with pacmd list-modules that module-jackdbus-connect is
loaded
> so the module must be compiled into pulse
directly.
>
> So any thoughts on why the module is not kicking in?
On ubuntu (which normally uses debian src packages), The module name
is
module-jackdbus-detect. I don't think I have
seen a module called
module-jackdbus-connect even on the pulse site.
http://www.freedesktop.org/wiki/Software/PulseAudio/Documentation/User/Modu…
Even if jackd comes with dbus support, it can be
started without. so
use
ps x or similar to check that the running app is
jackdbus and not
jackd.
There is no jackdbus on debian wheezy, just "jackd" or "jackd2".
6:23 a.m.
2012/10/30 Patrick Shirkey <pshirkey(a)boosthardware.com>
http://packages.debian.org/search?suite=wheezy&arch=any&mode=path&a…
You're correct. When I looked yesterday I had jackd and jackd2. Today I
have jackd and jackdbus instead.
No wonder people get confused about how to get this stuff working.
What possible reason is there to have jackd and jackd2 *or* jackd and
jackdbus ?
It's been a long time I have both installed from official repos...
There is no jackdbus on debian wheezy, just
"jackd" or "jackd2".
jackdbus is in debian wheezy and it comes with jackd2 package.
The former must be for jack1 package and the later for the jack2 package
but why would there even be a jackd2 option for the jack1 package? It's
completely redundant.
And why isn't a jackd2 option installed with the jack2 package?
I am confused, can't understand what's the matter with jackd and/or jackd2
but remember that ubuntu != debian, they do not share same repos and they
are not supposed to work with each other ones.
Probably the dbus stuff needs some tweaking on his debian system (eg.
feedesktop config in /usr/share/polkit-1/* )
regards
-r
--
*L'unica speranza di catarsi, ammesso che ne esista una, resta affidata
all'istinto di ribellione, alla rivolta non isterilita in progetti, alla
protesta violenta e viscerale. (V. Evangelisti)
*
5:18 p.m.
On 10/29/2012 08:23 PM, Raffaele Morelli wrote:
2012/10/30 Patrick Shirkey <pshirkey(a)boosthardware.com
<mailto:pshirkey@boosthardware.com>>
http://packages.debian.org/search?suite=wheezy&arch=any&mode=path&a…
<http://packages.debian.org/search?suite=wheezy&arch=any&mode=path&searchon=contents&keywords=jackdbus>
You're correct. When I looked yesterday I had jackd and jackd2. Today I
have jackd and jackdbus instead.
No wonder people get confused about how to get this stuff working.
What possible reason is there to have jackd and jackd2 *or* jackd and
jackdbus ?
It's been a long time I have both installed from official repos...
The former must be for jack1 package and the later for the jack2 package
but why would there even be a jackd2 option for the jack1 package? It's
completely redundant.
And why isn't a jackd2 option installed with the jack2 package?
I am confused, can't understand what's the matter with jackd and/or
jackd2 but remember that ubuntu != debian, they do not share same repos
and they are not supposed to work with each other ones.
You can use Ubuntu repositories with Debian.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
There is
no jackdbus on debian wheezy, just "jackd" or "jackd2".
jackdbus is in debian wheezy and it comes with jackd2 package.
5:37 p.m.
On Tue, 30 Oct 2012 07:18:03 -1000, david wrote
On 10/29/2012 08:23 PM, Raffaele Morelli wrote:
No, for anything non-trivial this is a _big_ no-go.
Dependency consistency can only be guaranteed within one
distribution. There's no guarantee that packages with the different
name from two distros don't provide files with identical names.
Equally, package with the same name might provide different files
(or even pack totally unrelated software).
Software/libs written in C++ and compiled with diffent versions of GCC
might not link at all, or, worse, might link but will not work correctly.
Really: DONT'T DO THAT!
HTH Ralf Mattes
I am confused, can't understand what's the matter with jackd and/or
jackd2 but remember that ubuntu != debian, they do not share same repos
and they are not supposed to work with each other ones.
You can use Ubuntu repositories with Debian.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
_______________________________________________
Linux-audio-user mailing list
Linux-audio-user(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-user
--
R. Mattes -
Hochschule fuer Musik Freiburg
rm(a)inm.mh-freiburg.de
31 Oct
31 Oct
5:55 a.m.
2012/10/30 david <gnome(a)hawaii.rr.com>
You can use Ubuntu repositories with Debian.
I wonder what you use to resolve depedencies then...
-r
--
*L'unica speranza di catarsi, ammesso che ne esista una, resta affidata
all'istinto di ribellione, alla rivolta non isterilita in progetti, alla
protesta violenta e viscerale. (V. Evangelisti)
*
8:04 a.m.
On 10/30/2012 07:55 PM, Raffaele Morelli wrote:
2012/10/30 david <gnome(a)hawaii.rr.com
<mailto:gnome@hawaii.rr.com>>
You can use Ubuntu repositories with Debian.
I wonder what you use to resolve depedencies then...
-r
I never used it for anything ambitious. Anything I've really needed,
Debian has had. And I don't need anything unique to Ubuntu, such as the
Unity interface.
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
8:21 a.m.
2012/10/31 david <gnome(a)hawaii.rr.com>
On 10/30/2012 07:55 PM, Raffaele Morelli wrote:
indeed, there's no use in it and it is quite dangerous (euphemism here) and
you should not reccommend it to other users.
it's well known that the majority of ubuntu packages is taken from debian
unstable and, no matter how you try and how simple is your target,
installing unstable packages on testing or stable will result in a neverend
dependencies war - 100%.
regards
-r
--
*L'unica speranza di catarsi, ammesso che ne esista una, resta affidata
all'istinto di ribellione, alla rivolta non isterilita in progetti, alla
protesta violenta e viscerale. (V. Evangelisti)
*
2012/10/30 david <gnome(a)hawaii.rr.com
<mailto:gnome@hawaii.rr.com>>
You can use Ubuntu repositories with Debian.
I wonder what you use to resolve depedencies then...
-r
I never used it for anything ambitious. Anything I've really needed,
Debian has had. And I don't need anything unique to Ubuntu, such as the
Unity interface.
2 Nov
2 Nov
6:43 a.m.
On 10/30/2012 10:21 PM, Raffaele Morelli wrote:
2012/10/31 david <gnome(a)hawaii.rr.com
<mailto:gnome@hawaii.rr.com>>
On 10/30/2012 07:55 PM, Raffaele Morelli wrote:
2012/10/30 david <gnome(a)hawaii.rr.com
<mailto:gnome@hawaii.rr.com> <mailto:gnome@hawaii.rr.com
<mailto:gnome@hawaii.rr.com>>>
You can use Ubuntu repositories with Debian.
I wonder what you use to resolve depedencies then...
-r
I never used it for anything ambitious. Anything I've really needed,
Debian has had. And I don't need anything unique to Ubuntu, such as
the Unity interface.
indeed, there's no use in it and it is quite dangerous (euphemism here)
and you should not reccommend it to other users.
it's well known that the majority of ubuntu packages is taken from
debian unstable and, no matter how you try and how simple is your
target, installing unstable packages on testing or stable will result in
a neverend dependencies war - 100%.
I ran a mix of Sid + Unstable for a while, it was OK if you didn't do
silly things like "apt-get upgrade". Aptosid smooths things out a bit, too.
Didn't know Ubuntu was using unstable. It would kind of surprise me.
I've done dist-upgrades and upgrades on my wife's netbook (running
Ubuntu 12.04) without any of the problems I used to get using unstable ...
But I prefer the Debian philosophy to Ubuntu's, and find Unity useless
(and incompatible with applications that we use everyday).
--
David
gnome(a)hawaii.rr.com
authenticity, honesty, community
http://clanjones.org/david/
http://dancing-treefrog.deviantart.com/
4199
days inactive
4203
days old
linux-audio-user@lists.linuxaudio.org
17 comments
6 participants
participants (6)
-
david -
Len Ovens -
Patrick Shirkey -
Paul Davis -
R. Mattes -
Raffaele Morelli