Hi all,
The drive towards stabilising Nouveau for a rocking Lucid LTS release
has resulted in large changes to the packaging stack. Nouveau's kernel
module is now in the main kernel package, which fixes most of the
problems people have previously reported. If you have previously tested
nouveau a
I noticed on the lucid-changes mailing list that libass was recently
updated. https://lists.ubuntu.com/archives/lucid-changes/2010-March/007954.html
At one point mplayer used libass for subtitle rendering. I have not
looked at mplayer or its packaging in quite some time, but I'm
guessing this is s
Op woensdag 10-03-2010 om 02:50 uur [tijdzone +0800], schreef John
McCabe-Dansted:
> Is is what is unsupported. I understand that deb say how to upgrade
> you configuration etc. to the new versions, but don't know how to
> downgrade.
>
> I understand that supporting downgrade could double the work
Having abandoned Karmic, I've been installing Lucid Alpha 3 on a number
of different systems, mostly for testing, and am finding lots of bugs.
For example, on an old Acer Aspire 3000 laptop, after a completely
generic Alpha 3 install + or - up to March 8 daily updates:
1. The console driver is
On Tue, Mar 9, 2010 at 11:36 AM, Scott James Remnant wrote:
> On Tue, 2010-03-09 at 10:36 -0500, Evan wrote:
>
> > In a normal scenario, for a library X, we would have the package libX.
> > When a new version of the lib is released upstream, the new version
> > gets packaged,
> > and the version f
On Tue, Mar 9, 2010 at 10:28, Patrick Goetz wrote:
>> Subject: Re: Evolution & Ubuntu 10.04 LTS
>> From: Sebastien Bacher
>> Date: Mon, 08 Mar 2010 23:02:32 +0100
>> To: ubuntu-devel-disc...@lists.ubuntu.com
>>
>
>> Ubuntu has been bitten by upgrading to new versions which were rewrit
On Wed, Mar 10, 2010 at 2:28 AM, Patrick Goetz wrote:
> Journal, lwn.net, and breathless reviews across the blogosphere. Users
> start clamoring for the features of gumptacular 2.0, not knowing how
> they ever lived without them. So,
>
> apt-get install gumptacular/ubuntu-experimental
Apt-ge
> Subject: Re: Evolution & Ubuntu 10.04 LTS
> From:Sebastien Bacher
> Date:Mon, 08 Mar 2010 23:02:32 +0100
> To: ubuntu-devel-discuss@lists.ubuntu.com
>
> Ubuntu has been bitten by upgrading to new versions which were rewritten
> in the past and we have learnt, the decision has bee
>> I assume that the samba job has been split into two because there was
>> a problem with nmbd not starting when smbd and nmbd were launched
>> through samba.
>> If you look at the respective conf files, you will see that nmbd
>> requires a nic other than lo to be up before starting.
> So, althou
On Tue, 2010-03-09 at 10:36 -0500, Evan wrote:
> In a normal scenario, for a library X, we would have the package libX.
> When a new version of the lib is released upstream, the new version
> gets packaged,
> and the version field of the package gets bumped appropriately.
>
No, not true at all.
This question has been floating in the back of my mind for a while,
and a bug I ran across recently brought it forward.
What is the official policy for including version numbers in the package
name?
This is the way I understand it:
In a normal scenario, for a library X, we would have the package
>> 1. Why does /lib/init/upstart-job direct us to use service rather than
>> initctl?
> Because /usr/sbin/service can handle the start/stop/restart/status
> actions of both traditional System V init scripts in /etc/init.d as
> well as Upstart scripts in /etc/init.
> It's intended to be one-stop-
>>> 999. Could initctl be made to recognize, for example, both
>>> avahi-daemon and avahi-daemon.conf? (If I am in /etc/init - it is rare
>>> but it happens - and type "stop av//tab//", I end up with "stop
>>> avahi-daemon.conf" which, after pressing //enter// results in an
>>> "unknown job" messag
13 matches
Mail list logo
