Hello!
I know I'm subscribed to the digest for this mailing list so I don't
know if it's been addressed yet, but it's not just the amd64 cd
images. I've noticed that they're all too big since. At least since
the 12th September. For people wanted to test actual hardware I think
it may be a problem
Hello all,
I wanted to ask about the widescreen boot up splash/logo. My concerns
have been raised at:
https://bugs.edge.launchpad.net/ubuntu/+source/usplash/+bug/64147
In specific, from the bug report:
"There are only 4:3 and 16:9 themes. It picks the closest."
I can understand if you don't want
On Mon, 2007-09-17 at 07:37 +0300, Murat Gunes wrote:
> Not many daily images end up oversized. If it were a substantial
> percentage of all images, you'd have a point. With the current state of
> things, people can wait a day, or two at worst, or use the image from a
> day or two before (I think
On 12/09/2007, Onno Benschop <[EMAIL PROTECTED]> wrote:
>2. While Dapper isn't the bleeding edge of Ubuntu, code that exists
> in Dapper exists in Feisty and Gutsy today. That implies that bugs
> that exist in Dapper are also likely to exist. Disk space is
> cheap. A computer
Jordan Mantha wrote:
> Secondly, I think we would increase collaboration and development
> tools if the community developers were allowed to have access to
> people.ubuntu.com. The Canonical devs already use that space quite
> extensively (making moving it definitely non-ideal). The MOTU have
> los
On Mon, 17 Sep 2007 10:27:49 +0100, "Fergal Daly" <[EMAIL PROTECTED]>
said:
> On 12/09/2007, Onno Benschop <[EMAIL PROTECTED]> wrote:
> >2. While Dapper isn't the bleeding edge of Ubuntu, code that exists
> > in Dapper exists in Feisty and Gutsy today. That implies that bugs
> > tha
On Mon, 2007-09-17 at 08:03 +0200, Martin Pitt wrote:
> Milan [2007-09-15 16:54 +0200]:
> > We can also think (and this is my opinion ;-) ) that the locate
> command
> > is only used by advanced users that now how to install slocate in
> two
> > minutes, and thus that we don't need to install it b
Hi,
Why is the amd64 release/tribe always late?
My favorite example is about the Xen support:
http://packages.ubuntu.com/gutsy/base/linux-image-2.6.22-11-xen
It is i386 only at the moment...
As far as I know, Ubuntu tries to be up to date and tries to support the
maximum of hardware as possible. An
On Mon, Sep 17, 2007 at 01:09:44PM +0200, Mihamina (R12y) Rakotomandimby wrote:
> Why is the amd64 release/tribe always late?
It isn't. amd64 releases happen at the exact same time as i386.
> My favorite example is about the Xen support:
> http://packages.ubuntu.com/gutsy/base/linux-image-2.6.22-
On Mon, Sep 17, 2007 at 08:29:10AM +0100, Tim Kersten wrote:
> I know I'm subscribed to the digest for this mailing list so I don't
> know if it's been addressed yet, but it's not just the amd64 cd
> images. I've noticed that they're all too big since. At least since
> the 12th September. For peopl
On Mon, Sep 17, 2007 at 08:03:49AM +0200, Martin Pitt wrote:
> Milan [2007-09-15 16:54 +0200]:
> > We can also think (and this is my opinion ;-) ) that the locate command
> > is only used by advanced users that now how to install slocate in two
> > minutes, and thus that we don't need to install it
Le lundi 17 septembre 2007 à 08:03 +0200, Martin Pitt a écrit :
> I fully agree. Installing *two* search tools by default is too much.
> We probably should not uninstall locate on upgrades, but we should not
> put it into new installations.
That will break gnome-search-tools (the panel item to
Colin Watson wrote:
> On Mon, Sep 17, 2007 at 01:09:44PM +0200, Mihamina (R12y) Rakotomandimby
> wrote:
>> Why is the amd64 release/tribe always late?
> It isn't. amd64 releases happen at the exact same time as i386.
>> My favorite example is about the Xen support:
>> http://packages.ubuntu.com/gu
On 17/09/2007 Mark Schouten wrote:
> > > Can we not come up with a way to generate the locate database from
> > > tracker instead?
>
> I prefer this too. I also think it is good to think about newbies, but
> is it really necessary to ignore more advanced users just because they
> know what they're
"Fergal Daly" <[EMAIL PROTECTED]> writes:
> On 12/09/2007, Onno Benschop <[EMAIL PROTECTED]> wrote:
>>2. While Dapper isn't the bleeding edge of Ubuntu, code that exists
>> in Dapper exists in Feisty and Gutsy today. That implies that bugs
>> that exist in Dapper are also likely to
Bryce <[EMAIL PROTECTED]> writes:
> That really does not make any sense if thats the case. What is the
> point in making daily images available for testing if know one is
> going to be able to use them?
You can always burn them on a DVD, or use it in a VM like qemu or
vmware.
--
Gruesse/greeti
On Mon, 2007-09-17 at 12:27 +0100, Colin Watson wrote:
> > I fully agree. Installing *two* search tools by default is too much.
> > We probably should not uninstall locate on upgrades, but we should not
> > put it into new installations. One is painful enough (although they do
> > not server the s
> I don´t know if that already happens, but the same way updatedb could be
> instructed to do a 'delta' only and leave unchanged files alone (instead of
> update the whole db each time).
# time /etc/cron.weekly/slocate
real1m6.354s
user0m0.247s
sys 0m0.581s
# time /etc/cron.weekly/s
On 9/17/07, Colin Watson <[EMAIL PROTECTED]> wrote:
> On Mon, Sep 17, 2007 at 08:29:10AM +0100, Tim Kersten wrote:
> > I know I'm subscribed to the digest for this mailing list so I don't
> > know if it's been addressed yet, but it's not just the amd64 cd
> > images. I've noticed that they're all t
On Mon, Sep 17, 2007 at 08:29:10AM +0100, Tim Kersten wrote:
> For people wanted to test actual hardware I think
> it may be a problem if the cd images remain so big as they won't be
> able to burn them.
As a temporary measure, they work fine if you burn them to a DVD RW
(which is what I do)
Also,
Mark Schouten said:
> I prefer this too. I also think it is good to think about newbies, but
> is it really necessary to ignore more advanced users just because they
> know what they're looking for? I know I would be annoyed if locate was
> missing on my server.
>
We're not talking about servers
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Another missing package in Gutsy is the emboss suite, even though it
is in Sid:
http://packages.debian.org/sid/emboss
- -- Morten
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFG7s0hB4zzG0BIJecRAhWOAJ0Q0nkoYOS+r3igcIP4FlWyTq
On 9/17/07, Scott Kitterman <[EMAIL PROTECTED]> wrote:
> It wasn't in Sid when the auto-sync was turned off. It'll be automatically
> sync'ed for Hardy.
>
> Scott K
For Hardy, could there be made a distinction between autosyncing new
versions and autosyncing new packages? Autosyncing new package
Hello,
I would like to discuss the recent inclusion of apturl in the Gutsy
default installation. The idea of apturl is great but the current
implementation has a lot of issues, some of which I will list here:
1. It's possible to run arbitrary scripts in the preinst/postrm phase
of dpkg installati
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As one of those who triages various KDE bugs...in the area of KDEBase,
in particular, there are around 450 open bugs, we *have* to close
invalid bugs. There are around 750, with the INVALID and WONTFIX bugs
included.
There is simply no way to deal wi
On Monday 17 September 2007 14:53, Kjeldgaard Morten wrote:
> Another missing package in Gutsy is the emboss suite, even though it
> is in Sid:
>
> http://packages.debian.org/sid/emboss
It wasn't in Sid when the auto-sync was turned off. It'll be automatically
sync'ed for Hardy.
Scott K
--
Ub
26 matches
Mail list logo
