On 25/09/09 16:52, Jonathan Aquilina wrote:
isnt the internet connection required thought to sync time with an ntp
server at somepoint during the installation.
It tries to sync, but the installation doesn't stop if it can't find an
internet connection. There's nothing in the installer that
Morten Kjeldgaard wrote:
Mono is evil software and is a mere trojan carrying a patent bomb from
Microsoft waiting to explode. Imagine a situation where hundreds of
essential packages based on Mono exists in Ubuntu, Office apps,
Internet apps, etc. and Microsoft decides to pull their
For the record, this affects hardy and below (although not
hardy-backports). Presumably the universe security team will get onto
this relatively soon - especially if they have a bug to track it.
Hobbsee
the.soylent wrote:
hi again,
still not fixed!
/soylent
Stefan Potyra wrote:
Technically, there aren't any powers that motu-release has, that any other
developer doesn't have: motu-release cannot reject a new upstream version
while in FeatureFreeze, nor can we accept an uploaded package while in deep
freeze (that's left to archive-admins).
Just
Caroline Ford wrote:
As someone with a package in REVU which no-one has ever looked why
would I make a new package for jaunty? My package is at least one
release cycle old and there's no guarantee anyone would look at it
this time round.
And I think this is exactly why we need to look at
Daniel J Blueman wrote:
I agree from a use-case point of view, and I personally think that
'easy' package managers should (by default) install all the
'recommended' dependencies, which should be there to allow experts to
de-select soft-dependencies.
This already happens on Ubuntu 8.10 by
Good afternoon developers, on this fine and sunny afternoon!
Recently, my attention was pointed to bug #273015 [1], about a
metapackage being uninstallable. On closer inspection, this turned out
to be a merge request, actioned 9 days ago.
Also on closer inspection, it turns out that at least
OS Project wrote:
Hey,
I am running short survey for a university research project.
Could you please help me understand whether the project syncmail is
sponsored or initiated by:
(1) an individual
(2) University/research institution
(3) Government
(4) Company
(5) Other (which one?)
Scott Kitterman wrote:
On Sun, 24 Aug 2008 18:23:06 -0300 Christian Robottom Reis
[EMAIL PROTECTED] wrote:
On the other hand, the feedback I get,
despite me asking otherwise, doesn't really give me much to work on --
there is too much talking down our process, where what I am looking for
is
Hey there,
Due to a number of factors, I've decided to step away from the MOTU team
in general, and the MOTU Release Team.
I have been looking to cut down my Ubuntu activities for a few months
now, and this is one of the areas that I feel needs the greatest time
commitment to do properly.
I've got more thoughts on all this, but can't document them tonight.
However:
Cesare Tirabassi wrote:
So, I'd propose a +2 in a (insert a reasonable amount of time here, 2 days
since the date a _valid_ request was filed seems reasonable to me) ? The
obvious drawback is that no FFe can be
Cesare Tirabassi wrote:
I do think it's reasonable to consider the source of recommendations and
accept advice from experts.
It is indeed in principle, but on the specifics depends very much on the
grounds against which the advice is given. For instance an advice like yes,
we miss this
Sounds more than fair to me. If anyone has merges outstanding that they
want to keep for themselves at this point, they should file a bug and
set it in progress. These people are likely to be very much in the
minority.
Hobbsee
signature.asc
Description: OpenPGP digital signature
--
Hey all!
I've recently discovered another reason not to use this too - if the
number of tasks in the bug is too high, launchpad will fall over
(timeouts) in attempting to open them. Launchpad has managed to improve
this in the last couple of releases, but this is clearly still a problem.
Hey all,
FYI: https://bugs.edge.launchpad.net/ubuntu/+source/reportbug/+bug/231316
Please read and comment, as it affects this list.
Hobbsee
signature.asc
Description: OpenPGP digital signature
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at:
Emmet Hikory wrote:
2. LP is hard to track to. Regarding, that we don't have special
maintainers for packages, you can't track all the time the status or
new bugs of all packages/bugs filed at LP. Yes, it sometimes sad for
the contributor...but the easiest way is to go online and ping
Stefan Potyra wrote:
So if you want to help, please reply in this thread.
Have done so before, would be happy to do so again.
Hobbsee
signature.asc
Description: OpenPGP digital signature
--
Ubuntu-motu mailing list
Ubuntu-motu@lists.ubuntu.com
Modify settings or unsubscribe at:
Scott Kitterman wrote:
If we go down this road, I'd suggest accepting only binary uploads. That'd
make sure the package at least builds before MOTUs waste time reviewing it.
Scott K
Don't be a fool. :)
Can you imagine just how many checkinstall-built packages we'd get from
doing that?
James Westby wrote:
Isn't the proposal to accept only uploads that also have binary
packages, like the Debian archive does? They can be discarded (perhaps
after a lintian check), but at least you know they built once somewhere.
The source package that comes with it can then be used for the
rest
Curses. I *knew* someone would try an april fools joke on me at some
point today
Hobbsee
Sarah Hobbs wrote:
Please tell me this is some kind of sick joke. Unfortunately, by
looking at the rejected queue, I suspect it is not.
Else I fear that you will lose your upload rights
Hey all,
After i banned Marco (kmos) from #ubuntu-motu, #ubuntu-devel, and
#ubuntu-bugs, there was excessive channel noise, and I received many
emails, including from people high in authority, about how this was not
to be done, that MOTU is not anarchy, and that the channel decisions
should
Emmet Hikory wrote:
The MOTU Council position is that MOTU Council does not have
jurisdiction or control over IRC (although support for MC statements
by members of the IRC team are appreciated). As such, the MOTU
Council will not be taking any action towards or against the bans
described.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Soren Hansen wrote:
On Fri, Feb 22, 2008 at 12:22:43PM +1100, Sarah Hobbs wrote:
This is a bugfix release that fixes a few typos (well, several
instances of the same typo, really), and fixes a call to qemu-img
that breaks because I added more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Soren Hansen wrote:
On Fri, Feb 22, 2008 at 12:35:14AM -, Soren Hansen wrote:
* New release.
Sorry, that was a little.. um.. terse :)
This is a bugfix release that fixes a few typos (well, several instances
of the same typo, really),
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hadmut Danisch wrote:
Scott Kitterman schrieb:
PPA has nothing to do with MOTU - please don't report their bugs here.
Hobbsee
To go a bit further, it's nothing to do with Ubuntu at all. 3rd party
repositories are
completely unsupported
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hadmut Danisch wrote:
Hi,
when installing the vmware-player package 1:2.0.2-1~ppa5 from
deb http://ppa.launchpad.net/cschieli/ubuntu gutsy main
the apt system tries to reinstall the very same package as an update again
and again.
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Holbach wrote:
Sarah Hobbs schrieb:
This worries me. We apparently have various people who don't think
before sending changes, yet have direct upload access to most of the
archive. Is having a note in the wiki really going to suffice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Holbach wrote:
Scott Kitterman schrieb:
Please think before you send bugs to Debian. It's great for inter-distro
relations when we can send them good fixes that make life easier for Debian.
Stuff like this doesn't help and all and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
To persia and nixternal - well done! You deserve it!
Hobbsee
Daniel Holbach wrote:
On Mi, 2008-01-23 at 14:24 +, Daniel Holbach wrote:
in ten hours from now the polls for the MC election will be opened. If
you're an Ubuntu developer, please
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Soren Hansen wrote:
2. Further we'd like to ask Marco Rodrigues to refrain from
contributing to Ubuntu Development from now on. The way this
happened in the past was marked by repetition and lack of
improvement in a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Holbach wrote:
Hello everybody,
with only four weeks to go until Feature Freeze (Feb 14th), now is a
good time to get the UVF team in place.
I'd like to thank Sarah Hobbs, Søren Hansen, Chuck Short, Steve Kowalik
and Scott Kitterman
see attached.
---BeginMessage---
NEW: ubuntustudio-controls_0.1.tar.gz
NEW: ubuntustudio-controls_0.1.dsc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Format: 1.7
Date: Thu, 10 Jan 2008 17:04:04 -0500
Source: ubuntustudio-controls
Binary: python-meminfo-total ubuntustudio-controls
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
It's already there.
[EMAIL PROTECTED]:~% apt-cache madison libguichan2-dev
5:42PM
libguichan2-dev |0.7.1-1 | http://mirror.internode.on.net
hardy/universe Packages
libguichan2-dev |0.7.1-1 | http://archive.ubuntu.com hardy/universe
Packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
PPA's are not done by MOTU. Reporting bugs from packages here, from
ppa's is useless.
This is also already known.
Hobbsee
Saurabh Asthana wrote:
Yo,
While trying to install your package kdebase-runtime-bin-kde4 from
It would be suggested that you use dpkg-buildpackage general switches
-rfakeroot when building. See fakeroot(1) for more information.
Hobbsee
Daniel T. Chen wrote:
[Adding ubuntu-motu@ to CC:]
On Mon, 2007-11-19 at 13:55 -0500, Manuel Amador (Rudd-O) wrote:
debian/rules clean
test -x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey all,
After a long time, i've decided to give up being the admin of the Ubuntu
Universe Sponsorship queue, as has Steve Kowalik.
Consequently, the queue is now looking for some more administrators.
Daniel Holbach has kindly stepped up to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This would be a new revision of an existing package, not a package new
to Ubuntu. The two are very different, and one is much easier than the
other. Also, it doesn't have to be checked by the archive admins again,
which is good - makes it faster.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey all,
After a long time, i've decided to give up being the admin of the Ubuntu
Universe Sponsorship queue, as has Steve Kowalik.
Consequently, the queue is now looking for some more administrators.
Daniel Holbach has kindly stepped up to fill one
been educated
on what they're doing wrong, and then commit more offenses regardless.
Again, apologies for the harsh mail.
Hobbsee
Michael Bienia wrote:
On 2007-10-23 15:20:55 +1000, Sarah Hobbs wrote:
Michael, what in hell were you thinking?
I was contacted by GNUmed upstream about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This thing propably won't need to get fixed for wesnoth because I plan
to introduce the wesnoth-all package in Debian too, suggested by
upstream (never heard anything about it from any MOTU that this patch is
hanging in there, though, which I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Gerfried Fuchs wrote:
Yes. And do you know about that from my part having to go look there
for every single package every once in a while to see if there is
something new is a quite broken approach, when having some amount of
packages, especially
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael, what in hell were you thinking?
This is utterly and totally unacceptable. Gutsy is a stable release,
and so needs a very high level of QA. This is precisely *why* we have
the pain of stable release updates. You throwing untested crap in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey everyone,
This is just a mail to let you know that i've ended up accepting a few
packages (mostly translations, and a bit of universe stuff) silently -
ie. a mail has not been sent to gutsy-changes about them.
Obviously, this is not good as it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fixed, try again. (Thanks ajmitch)
Hobbsee
Viktor Kazakov wrote:
Hi, Stefan!
Made my first upload to REVU (my account should be created thus). Trying
to recover password using my email. Get the following:
To decrypt your password, type the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please make sure that there are logs of this, and that they are made
easily accessible.
Hobbsee
(from the right address this time!)
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Stefan Potyra wrote:
Since we cannot assume, that tiber was in fact not compromised, all the
previously uploaded packages were not imported into the new instance. Also
the database started completely empty.
Excellent! This should help us get
Please see the note about UVF
https://wiki.ubuntu.com/FreezeExceptionProcess#head-9523bc4076ff011324d67cddc97969ec609618d6
---BeginMessage---
Feature Freeze in Place, Tribe 5 Next Week
Feature Freeze and Upstream Version Freeze are now in place. From now
until release we should be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Done in gutsy, thanks for the mail :)
Hobbsee
ORiON wrote:
The current version (1.5.1) of tree package has a very annoying bug
when exporting the tree to HTML, it fixed at the latest version
(1.5.1.1) as detailed at the changelog:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hello,
It's already at the latest, in gutsy.
[EMAIL PROTECTED]:~$ rmadison -u ubuntu krename
krename | 3.0.9-2ubuntu1 | dapper/universe | source, amd64, i386, powerpc
krename | 3.0.12-0ubuntu1 | edgy/universe | source, amd64, i386, powerpc
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel Holbach wrote:
Am Freitag, den 06.07.2007, 16:24 +0200 schrieb Daniel Holbach:
If you want to work in the team, please nominate yourself in the during
the next week and we'll set up a Launchpad poll the week after that.
up until now Chuck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Whether it's me or not, i'd like to see someone from Kubuntu on this team.
Hobbsee
Daniel Holbach wrote:
Hello everybody,
Am Freitag, den 06.07.2007, 16:02 +0200 schrieb Daniel Holbach:
with Upstream Version Freeze approaching at August 16th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi everyone!
There's a MOTU[0] meeting in 4 hours.
The agenda[1] has a tentative list of discussion
topics.
[0] https://wiki.ubuntu.com/MOTU
[1] https://wiki.ubuntu.com/MOTU/Meetings
Hope to see you there!
Hobbsee
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You'd really have to ask the guys who run beryl-project.org, as we don't
Hobbsee
François-Xavier JEAN wrote:
Hi,
Why this package not include beryl-xgl necessary for ati card with xgl,
like the packages
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ubuntu Installer wrote:
NEW: kde4-style-qtcurve_0.50-0ubuntu1.dsc
OK: kde4-style-qtcurve_0.50.orig.tar.gz
OK: kde4-style-qtcurve_0.50-0ubuntu1.diff.gz
Format: 1.7
Date: Wed, 30 May 2007 18:50:41 +0200
Source: kde4-style-qtcurve
Binary:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ubuntu Installer wrote:
NEW: b5i2iso_0.2-0ubuntu1.dsc
OK: b5i2iso_0.2.orig.tar.gz
OK: b5i2iso_0.2-0ubuntu1.diff.gz
Format: 1.7
Date: Wed, 11 Apr 2007 23:58:29 +0200
Source: b5i2iso
Binary: b5i2iso
Architecture: source
Version:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ubuntu Installer wrote:
NEW: cdi2iso_0.1-0ubuntu1.dsc
OK: cdi2iso_0.1.orig.tar.gz
OK: cdi2iso_0.1-0ubuntu1.diff.gz
Format: 1.7
Date: Thu, 12 Apr 2007 07:08:32 +0200
Source: cdi2iso
Binary: cdi2iso
Architecture: source
Version:
Quoting various things here...
As you certainly noticed, the list of packages waiting on REVU is
really, really long. I've reviewed a few and the update to gutsy is
needed for all of them (only a one line change in the changelog, but
needed). It'd be nice if people having packages on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you find a bug in Ubuntu or any of its derivatives, please file a bug
report at: http://bugs.ubuntu.com/
Also, which version of ubuntu?
Please say, when you file the bug report.
Mailing lists make terrible bugtrackers.
Thanks!
C Martello
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm not sure how debian is actually handling this.
According to
http://packages.debian.org/cgi-bin/search_packages.pl?keywords=supertuxsearchon=namesubword=1version=allrelease=all
supertux 0.3 is in experimental, and 0.1.3 is in unstable. This is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Same here, and I suspect that the other users feel the same way.
Crashes will not get fixed, even in 0.3.1, as they're now working on the
newer series, presumably.
Stefan Potyra wrote:
However I must admit that I'm a little bit biased here, since
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
all done :)
Hobbsee
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFF156y7/o1b30rzoURAp6BAKDYENFTmuHXG8fH/JKOcFeSfvJiUgCdEXU+
jEePQB9Hl6tQHEFel2aucpw=
=o+Iv
NEW: tss_0.8.1-0ubuntu1.dsc
OK: tss_0.8.1.orig.tar.gz
OK: tss_0.8.1-0ubuntu1.diff.gz
* *BEGIN ENCRYPTED or SIGNED PART* *
Format: 1.7
Date: Fri, 22 Sep 2006 17:31:00 +0300
Source: tss
Binary: tss
Architecture: source
Version: 0.8.1-0ubuntu1
Distribution: feisty
Urgency: low
62 matches
Mail list logo
