On Fri, 2011-09-02 at 15:43 -0700, Adam Williamson wrote:
> On Fri, 2011-09-02 at 18:33 -0400, Matt McCutchen wrote:
>
> > > We clearly
> > > want to bugs to be CLOSED, not open with a quasi-closed keyword or
> > > whiteboard field.
> >
> > I
On Fri, 2011-09-02 at 13:54 -0700, Adam Williamson wrote:
> Hum, I didn't realize our resolutions were so customized, I thought they
> were the upstream ones; this is what I've been told when discussing
> custom resolutions in the past. It's certainly something you could
> propose as an enhancement
On Fri, 2011-09-02 at 12:29 -0700, Adam Williamson wrote:
> On Fri, 2011-09-02 at 14:01 -0400, Matt McCutchen wrote:
>
> > What you're really saying is that most maintainers want to work from a
> > list of unexpired bugs. But there are ways to achieve that other than
>
04 at 16:10 -0400, Matt McCutchen wrote:
> > On Thu, 2010-11-04 at 09:38 -0700, Adam Williamson wrote:
> > > The practical point is that F12
> > > is about to go EOL which means the bug must be closed...
> >
> > Why? Obviously it needs to be clear that not
On Sat, 2011-03-12 at 16:06 -0800, Christopher Aillon wrote:
> On 03/12/2011 04:33 AM, Kalev Lember wrote:
> > I believe it should be fixed with glibc-2.13.90-6, but the update is
> > currently stuck in Bodhi with 7 karma and not getting pushed even to the
> > requested updates-testing repo:
> > ht
On Thu, 2011-01-27 at 21:05 -0500, Jean-Marc Pigeon wrote:
> Let be straight and simple (package name doesn't
> matter here)
>
> 1) Spec file say version: 1.2.3
> 2) sources file say tar file: 1.0.0
> "sources" as included in git and generated
> by fedpkg
On Mon, 2011-01-24 at 14:02 -0500, Bill Nottingham wrote:
> I believe folding any requirements for %posttrans scripts into
> 'Requires(post)' should be sufficient.
I don't think so... IIUC, Requires(post) only applies until installation
is complete, but a %posttrans script also runs following unin
On Mon, 2011-01-17 at 15:54 -0800, Brad Bell wrote:
> I have a case where a package is noarch and it provides pkg-config support.
>
> The problem is that pkg-config expects a noarch file corresponding to
> the package to be stored in
> ${_libdir}/pkgconfig
> and rpmlint complains that
>
On Thu, 2011-01-13 at 10:42 -0800, Jesse Keating wrote:
> There is the case that when
> we switch to the branch, your last used state is behind or ahead the
> local index (that is the cached metadata the repo has about the state of
> each branch upstream).
Please call it the remote-tracking branch
On Wed, 2011-01-05 at 16:37 -0500, Daniel J Walsh wrote:
> [XDG_RUNTIME_DIR] does not exist until after the User has logged in. X
> starts before
> the user logs in. Also multiple users need to be able to talk to same
> xserver.
On Wed, 2011-01-05 at 16:47 -0500, Adam Jackson wrote:
> atropine:
On Wed, 2011-01-05 at 16:13 -0500, Adam Jackson wrote:
> On Wed, 2011-01-05 at 14:10 -0500, Matt McCutchen wrote:
> > On Wed, 2011-01-05 at 11:12 -0500, Adam Jackson wrote:
> > > (And of course what we're doing here is protecting against a malicious
> > > attacker w
On Wed, 2011-01-05 at 15:25 -0500, Adam Jackson wrote:
> On Wed, 2011-01-05 at 13:38 -0500, Matt McCutchen wrote:
> > The
> > more significant DoS condition is another user taking the name you want,
> > which can happen in the abstract namespace but not in a directory o
An aside:
On Wed, 2011-01-05 at 11:12 -0500, Adam Jackson wrote:
> (And of course what we're doing here is protecting against a malicious
> attacker who already has enough privileges to run code on your system,
> which means you're pretty far into having already lost. Meh.)
I've seen this viewpo
On Wed, 2011-01-05 at 11:12 -0500, Adam Jackson wrote:
> The deeper problem is that clients authenticate themselves to the
> server, but then simply trust that the server is the server they were
> hoping for. If you don't have a process tree relationship (like the gdm
> +displayfd case) then you h
On Wed, 2011-01-05 at 16:35 +0100, Lennart Poettering wrote:
> On Wed, 05.01.11 09:39, Matt McCutchen (m...@mattmccutchen.net) wrote:
>
> > > That's precisely what I want to tell people: don't use the abstract
> > > socket namespace, unless you really know what
On Wed, 2011-01-05 at 13:52 +0100, Lennart Poettering wrote:
> On Tue, 04.01.11 21:31, Matt McCutchen (m...@mattmccutchen.net) wrote:
>
> > On Tue, 2011-01-04 at 14:11 +0100, Lennart Poettering wrote:
> > > Of these being used, dbus is correctly implemented, since it random
On Tue, 2011-01-04 at 14:11 +0100, Lennart Poettering wrote:
> Of these being used, dbus is correctly implemented, since it randomizes
> the socket name. Same for gdm.
The relevant point is not randomness or unguessability, but that dbus
chooses an available name and passes the actual name being u
On Thu, 2010-12-23 at 09:11 -0800, Fernando Lopez-Lezcano wrote:
> On 12/22/2010 12:56 PM, Casey Dahlin wrote:
> > On Mon, Dec 20, 2010 at 07:16:21PM -0800, Fernando Lopez-Lezcano wrote:
> >> (a) unix-domain sockets for non-RT communication with the server
> > Perhaps these could become abstra
On Tue, 2010-12-21 at 22:10 -0500, Tom Lane wrote:
> I'm fooling around with trying to update mysql from 5.1.x to 5.5.x.
> One of the things that's happened in that transition is that they've
> dropped the separate "libmysqlclient_r.so" library --- presumably
> everything in regular "libmysqlclient
On Tue, 2010-12-21 at 16:45 +, Adam Williamson wrote:
> On Tue, 2010-12-21 at 11:24 -0500, Matt McCutchen wrote:
> > On Tue, 2010-12-21 at 16:15 +, Adam Williamson wrote:
> > > it would seem to make more sense, to me, to configure bodhi to re-try
> > > the build
On Tue, 2010-12-21 at 16:15 +, Adam Williamson wrote:
> On Mon, 2010-12-20 at 22:57 +0100, Henrik Nordström wrote:
>
> > * implemented by "only" a change in yum dependency resolution to use
> > fallback repositories (i.e. updates-testing).
>
> I don't think that would be a good change, as it'
On Tue, 2010-12-21 at 01:29 +0100, Henrik Nordström wrote:
> mån 2010-12-20 klockan 18:12 -0500 skrev Matt McCutchen:
>
> > That will work, assuming the user has permission to do the tagging; it
> > is essentially a buildroot override in reverse. So the question is just
&
On Mon, 2010-12-20 at 21:55 +0100, Henrik Nordström wrote:
> Suggestion on how to express this in the packaging process:
> BuildRequires with a version requirement pulling in from updates-testing
> if the required version can not be satisfied from the stable repository.
I don't like this. I would
On Fri, 2010-12-17 at 18:38 -0500, Orcan Ogetbil wrote:
> On Fri, Dec 17, 2010 at 1:36 PM, Matt McCutchen wrote:
> > On Fri, 2010-12-17 at 13:20 -0500, Orcan Ogetbil wrote:
> >> On Thu, Dec 16, 2010 at 11:03 AM, Chris Adams wrote:
> >> > That makes the push proce
On Fri, 2010-12-17 at 13:20 -0500, Orcan Ogetbil wrote:
> On Thu, Dec 16, 2010 at 11:03 AM, Chris Adams wrote:
> > That makes the push process much more fragile/difficult. If you use a
> > updates-testing build of package A, and package B (that depends on
> > package A) gets rebuilt, then you may
On Fri, 2010-12-17 at 18:32 +0100, Ralf Corsepius wrote:
> * we are building packages against the known-to-be-broken package
The old package is already in stable. We're not doing additional harm
by building against it unless the "breakage" is a regression that
affects the building of dependent pa
On Fri, 2010-12-17 at 11:08 -0700, Kevin Fenzi wrote:
> Lets step back a bit here as I think this thread is drifting.
>
> What issue(s) is this proposed change trying to solve?
>
> * The OP talked about that we are not 'testing' the update entirely
> because it's not in the buildroot, so we a
On Thu, 2010-12-16 at 12:28 -0800, Jesse Keating wrote:
> On 12/16/10 12:22 PM, Matt McCutchen wrote:
> > An alternative approach would be to mirror the semantics of tag
> > inheritance by having builds use multiple yum repositories, possibly
> > with priorities, instead of
On Thu, 2010-12-16 at 12:14 -0800, Jesse Keating wrote:
> On 12/16/10 10:29 AM, Matt McCutchen wrote:
> > (BTW, it seems that a custom tag would generally be better than a
> > buildroot override for the reasons we are discussing even if there's
> > only one dependent pack
On Thu, 2010-12-16 at 20:16 +0100, Miloslav Trmač wrote:
> Casey Dahlin píše v Čt 16. 12. 2010 v 11:19 -0500:
> > On Thu, Dec 16, 2010 at 12:27:34PM +, Richard W.M. Jones wrote:
> > > What you don't understand is that you are throwing away the experience
> > > and knowledge of thousands of Unix
On Thu, 2010-12-16 at 18:11 +0100, Ralf Corsepius wrote:
> On 12/16/2010 06:00 PM, Matt McCutchen wrote:
> > On Thu, 2010-12-16 at 17:49 +0100, Ralf Corsepius wrote:
> >> On 12/16/2010 05:28 PM, Kevin Fenzi wrote:
> >>> On Thu, 16 Dec 2010 10:03:30 -
On Thu, 2010-12-16 at 18:54 +0100, Ralf Corsepius wrote:
> On 12/16/2010 06:43 PM, Matt McCutchen wrote:
> > On Thu, 2010-12-16 at 18:33 +0100, Ralf Corsepius wrote:
> >> On 12/16/2010 06:26 PM, seth vidal wrote:
> >>> On Thu, 2010-12-16 at 18:13 +0100, Ralf Corsepiu
On Thu, 2010-12-16 at 18:33 +0100, Ralf Corsepius wrote:
> On 12/16/2010 06:26 PM, seth vidal wrote:
> > On Thu, 2010-12-16 at 18:13 +0100, Ralf Corsepius wrote:
> >> Just a thought: How about equipping a repo's metadata with some sort of
> >> "expiration"/"best before" date, which yum etc. could u
On Thu, 2010-12-16 at 17:49 +0100, Ralf Corsepius wrote:
> On 12/16/2010 05:28 PM, Kevin Fenzi wrote:
> > On Thu, 16 Dec 2010 10:03:30 -0600
> > Chris Adams wrote:
> >
> >> Once upon a time, Stanislav Ochotnicky said:
> >>> Note that I am not saying things should go into buildroot as soon as
> >>
On Thu, 2010-12-16 at 09:28 -0700, Kevin Fenzi wrote:
> On Thu, 16 Dec 2010 10:03:30 -0600
> Chris Adams wrote:
>
> > Once upon a time, Stanislav Ochotnicky said:
> > > Note that I am not saying things should go into buildroot as soon as
> > > they are built, but as soon as they are in updates-t
On Wed, 2010-12-15 at 16:15 -0500, Jon Masters wrote:
> On Wed, 2010-12-15 at 22:25 +0200, Ville Skyttä wrote:
>
> > "Files marked as documentation must not cause additional dependencies that
> > aren't satisfied by the package itself or its dependency chain as it would
> > be
> > if none of it
On Tue, 2010-12-14 at 14:07 +, Paul Johnson wrote:
> Hi,
>
> My main box decided to snuff it last week (motherboard and processor
> decided to fry). My erstwhile friend in the computer shop I use has
> said that he has a nice 64 bit processor and motherboard going for a
> small amount of money
On Fri, 2010-12-10 at 15:06 +, Daniel P. Berrange wrote:
> Adding CLONE_NEWPID would be worthwhile to stop the
> mock process seeing any other PIDs on the machine.
It's critical, or mock could ptrace some process running as root on the
host and inject arbitrary code.
--
Matt
--
devel maili
On Mon, 2010-12-06 at 17:57 -0800, Adam Williamson wrote:
> On Mon, 2010-12-06 at 10:54 +0100, Michał Piotrowski wrote:
>
> > There are no stupid questions :)
> >
> > On most desktop systems firewall is not needed. Many users do not even
> > know how to configure it. In fact I disable it in most
On Tue, 2010-12-07 at 01:07 +0100, Michał Piotrowski wrote:
> 2010/12/7 Matt McCutchen :
> > On Tue, 2010-12-07 at 00:38 +0100, Michał Piotrowski wrote:
> >> Cron - but should be activated only when cron files exist
> >>
> >> It seems to me that the list:
On Tue, 2010-12-07 at 00:38 +0100, Michał Piotrowski wrote:
> Cron - but should be activated only when cron files exist
>
> It seems to me that the list:
> - ssh
> - Dbus
> - syslog
> - iptables
> - ip6tables
> - auditd
> - restorecond
> is an absolute minimum to get "working system".
I don't agr
On Mon, 2010-12-06 at 10:54 +0100, Michał Piotrowski wrote:
> On most desktop systems firewall is not needed. Many users do not even
> know how to configure it. In fact I disable it in most of my systems,
> because there is no real use for it. So I asked a simple question
> whether there is a need
On Wed, 2010-12-01 at 20:29 -0600, Dennis Gilmore wrote:
> libgnome-java failed to build
> http://koji.fedoraproject.org/koji/taskinfo?taskID=2638084
I took a look out of curiosity, and this appears to be an intermittent
problem that occurs when two instances of install(1) try to write to the
same
On Wed, 2010-12-01 at 15:59 -0800, Adam Williamson wrote:
> I'm not sure I'd want to go quite that far unless the sign-up process
> can wave the proven testers instructions in your face quite prominently.
> They're short and easy to read and understand, but you can't infer them
> from first princip
On Wed, 2010-12-01 at 14:17 -0800, Adam Williamson wrote:
> [...] I think we need to be
> careful of the mindset that says 'we can't enforce any standards in
> Fedora because it's a volunteer project so we must just accept what
> people are willing to give us'.
>
> Even though packaging in Fedora
On Mon, 2010-11-29 at 16:08 -0800, John Reiser wrote:
> On 11/29/2010 03:44 PM, Matt McCutchen wrote:
> > What is the mass addition of commented curly braces for? It is
> > distracting from the substance of the patch.
> Those comments enable parenthesis matching in some t
On Sun, 2010-11-28 at 15:13 -0800, John Reiser wrote:
> This patch (with .rpms for x86_64 and i686) enables glibc optionally
> to detect, diagnose, and work around overlap in memcpy/mempcpy:
> http://bitwagon.com/glibc-memlap/glibc-memlap.html
What is the mass addition of commented curly brace
On Sat, 2010-11-20 at 23:09 +0100, Jan Kratochvil wrote:
> Oh, I forgot, Fedora no longer delivers the fix in a day but ... even not in
> a week. Because I usually create new build during the updates-testing week so
> the days start to count again.
> https://admin.fedoraproject.org/updates/g
On Wed, 2010-11-17 at 16:32 +, "Jóhann B. Guðmundsson" wrote:
> Dont we have an upstream mantra to uphold...
>
> Forward all Fedora users and otherwize that experience this to Adobe..
>
> If we are going hack around this on our side where are we going to draw
> the line..
>
> Are we plannin
On Sun, 2010-11-14 at 13:07 -0800, John Reiser wrote:
> When I created 14 partitions using a DOS partition label
> (3 primaries, plus extended containing 10 logical partitions)
> and gave 6 of the partitions to an LVM setup,
> then I could not remove one of the partitions from the clutches
> of the
On Sun, 2010-11-14 at 14:07 -0500, Matt McCutchen wrote:
> On Sun, 2010-11-14 at 10:38 -0800, John Reiser wrote:
> > On 11/13/2010 03:41 PM, Richard W.M. Jones wrote:
> >
> > > Anyway, I think LVM is jolly useful:
> > [stated advantages snipped]
> >
> >
On Sun, 2010-11-14 at 10:38 -0800, John Reiser wrote:
> On 11/13/2010 03:41 PM, Richard W.M. Jones wrote:
>
> > Anyway, I think LVM is jolly useful:
> [stated advantages snipped]
>
> One design error is that you cannot "carve out" an ordinary partition
> from an LVM. Once a portion of the drive
On Sat, 2010-11-13 at 14:22 +, Matthew Garrett wrote:
> On Sat, Nov 13, 2010 at 10:21:30AM +0100, Till Maas wrote:
>
> > The documented issues do not seem to be as bad as a system being
> > exploited. It is only about dependency breakage or services not working
> > anymore. There is no major d
On Thu, 2010-11-04 at 09:38 -0700, Adam Williamson wrote:
> The practical point is that F12
> is about to go EOL which means the bug must be closed...
Why? Obviously it needs to be clear that nothing further should be
expected from the maintainer unless/until the version is bumped. But
the proje
On Thu, 2010-11-04 at 19:44 +0100, Nicolas Mailhot wrote:
> From a practical point of view, as a bug reporter, when I get mass
> notifications to update scores of bugs that were opened years ago, and
> that the people owning the component never bothered to respond on (even
> to confirm they were al
On Wed, 2010-10-20 at 08:13 -0400, Daniel J Walsh wrote:
> I have been trying to get system processes to stop using /tmp for years.
>
> http://danwalsh.livejournal.com/11467.html
>
> As some one who lives with polyinstatiated namespace /tmp, The only
> problem I know of now is handing of kerbero
On Sat, 2010-10-30 at 14:03 -0800, Javier Prats wrote:
> Where is this info kept on the install image and how would I go about
> modifying it locally to start playing? I'd like to learn whether some
> one else does this or not.
It's in anaconda. The / and /home specifications are here (line numb
On Sun, 2010-10-17 at 20:36 +0400, Pavel Alexeev (aka Pahan-Hubbitus) wrote:
> I want fill it, but bugzilla even do not contain such component as
> fedpkg. Why?
$ rpm -q --qf '%{SOURCERPM}\n' fedpkg
fedora-packager-0.5.1.4-5.fc13.src.rpm
So the component to file bugs is "fedora-packager".
--
M
On Wed, 2010-10-13 at 23:45 +0200, Kevin Kofler wrote:
> Firefox is NOT an
> essential package, the GNOME spin could just ship Epiphany (GNOME's default
> browser) instead, and other desktop spins ALREADY ship the respective
> desktop's default instead of Firefox!
Epiphany is still not serious
On Thu, 2010-10-14 at 13:11 +0200, Thorsten Leemhuis wrote:
> I tend to disagree, as including both Iceweasel and Icedove in addition
> to Firefox and Thunderbird gives users, admins and especially those that
> maintain a remix the option to easily chose the solution that suites
> their needs best.
On Thu, 2010-10-14 at 01:48 +0200, Kevin Kofler wrote:
> Petr Sabata wrote:
> > I've been thinking about packaging dwm [1] since we already ship dmenu and
> > dzen2. I wonder if anybody would be interested in this fine window manager
> > (except for me).
>
> I think it's completely unreasonable to
On Tue, 2010-10-12 at 19:37 -0400, Gregory Maxwell wrote:
> On Tue, Oct 12, 2010 at 7:28 PM, Chris Adams wrote:
> > I noticed that ethtool is not in the default install anymore [...]
>
> mii-tool.
The mii-tool man page claims it is deprecated in favor of ethtool. In
fact, neither is in any comp
On Mon, 2010-10-04 at 09:59 +0100, Richard Hughes wrote:
> On 27 September 2010 20:31, Richard Hughes wrote:
> > Right, but you could argue it's a regression as the behavior changed.
> > Could somebody please fix docbook-utils, otherwise all the GNOME koji
> > builds are going to fail.
>
> All my
On Mon, 2010-10-04 at 04:30 -0500, Rex Dieter wrote:
> I've tagged docbook-utils-0.6.14-25.fc14 (the update reportedly fixing this)
> for the buildroot. Please try your builds now.
"f14-build" should appear in the "Tags" line here, right?
https://koji.fedoraproject.org/koji/buildinfo?buildID=19
On Fri, 2010-10-01 at 08:13 +0530, A. Mani wrote:
> sigil is not available from yum
>
> http://code.google.com/p/sigil/
>
> It is easy to install from source on F
You can add it here:
https://fedoraproject.org/wiki/PackageMaintainers/WishList
--
Matt
--
devel mailing list
devel@lists.fedora
On Fri, 2010-09-24 at 16:50 -0400, Matt McCutchen wrote:
> On Fri, 2010-09-24 at 14:48 -0430, Guillermo Gómez wrote:
> > Why is this happening?
> >
> > rubygem-state_machine-0.9.4-3.fc12 unsuccessfully untagged from
> > dist-f12-updates-testing-pending by bodhi
&g
On Fri, 2010-09-24 at 14:48 -0430, Guillermo Gómez wrote:
> Why is this happening?
>
> rubygem-state_machine-0.9.4-3.fc12 unsuccessfully untagged from
> dist-f12-updates-testing-pending by bodhi
> Operation failed with the error:
> koji.TagError: build rubygem-state_machine-0.9.4-3.fc12 not
On Thu, 2010-09-16 at 17:19 +0100, Richard W.M. Jones wrote:
> There are times when static linking is a useful. Robert clearly
> describes one in his original post.
Only because we do not (yet) have a good per-user package manager to
make installing the required dynamic libraries, or assembling a
On Wed, 2010-09-15 at 17:06 +0100, Robert Spanton wrote:
> I've recently had to link a fair amount of my work statically so that
> it'll run on a cluster of RHEL machines. Unfortunately, I am just a
> user of these machines, and so I don't have the power to get them to run
> Fedora or even to get
On Sun, 2010-09-05 at 23:57 -0400, Braden McDaniel wrote:
> Thanks. Now, how do I get fedpkg to preserve it? I see (when doing
> "fedpkg mockbuild"):
>
> INFO: Cleaning up build root ('clean_on_failure=True')
>
> So, where do I set clean_on_failure to False?
In /etc/mock/site-defaults.
On Thu, 2010-09-02 at 09:17 -0600, Kevin Fenzi wrote:
> On Thu, 2 Sep 2010 12:18:26 +0300 (EEST)
> Juha Tuomala wrote:
> > Has it been disabled recently?
>
> Short answer: Yes. It has.
>
> Longer answer:
>
> FESCo looked at trying to use voting data to give us an idea on 'hot'
> bugs that we
On Wed, 2010-09-01 at 09:00 -0700, Jesse Keating wrote:
> On 8/31/10 5:36 PM, Roland McGrath wrote:
> > Perhaps local and so forth could be given a --dist=foo switch, and these
> > sorts of errors could say "can't figure out your dist from git, use --dist
> > or fix your repo".
>
> Yeah, I've been
On Wed, 2010-09-01 at 11:01 -0500, Garrett Holmstrom wrote:
> Andreas Schwab wrote:
> > Matt McCutchen writes:
> >> I propose that fedpkg should consider a --dist option, a "branch"
> >> file, and the name of the current git branch in that order.
> &g
On Wed, 2010-09-01 at 13:33 -0400, Tom Lane wrote:
> Matt McCutchen writes:
> > Does it work if the current branch tracks another local branch which
> > tracks an upstream branch? It looks to me that the code does not handle
> > that, but I haven't found a good way to
On Wed, 2010-09-01 at 10:06 -0700, Jesse Keating wrote:
> On 9/1/10 9:01 AM, Garrett Holmstrom wrote:
> > Andreas Schwab wrote:
> >> Matt McCutchen writes:
> >>> I propose that fedpkg should consider a --dist option, a "branch"
> >>> file,
On Wed, 2010-09-01 at 21:41 +0530, Shakthi Kannan wrote:
> I would like to know if something like the following exists or is it
> possible to display the following for each packager:
>
> Package EL-6 EL-5 F-14 F-13
>
> in a web-page (for example) that can be populated from Koji
> (pe
On Wed, 2010-09-01 at 14:20 +0200, Nils Philippsen wrote:
> On Tue, 2010-08-31 at 20:47 -0400, Matt McCutchen wrote:
> > On Tue, 2010-08-31 at 17:36 -0700, Roland McGrath wrote:
> > > Perhaps local and so forth could be given a --dist=foo switch, and these
> > > sorts
On Tue, 2010-08-31 at 22:14 -0400, Steve Dickson wrote:
> When I do a:
> git push --dry-run origin origin/master:refs/heads/f15/user/steved/pnfs-f15
> To ssh://ste...@pkgs.fedoraproject.org/kernel
> * [new branch] origin/master -> f15/user/steved/pnfs-f15
>
> which appears to do what I want
On Tue, 2010-08-31 at 17:36 -0700, Roland McGrath wrote:
> Perhaps local and so forth could be given a --dist=foo switch, and these
> sorts of errors could say "can't figure out your dist from git, use --dist
> or fix your repo".
Or a "branch" file... :D
--
Matt
--
devel mailing list
devel@lis
On Tue, 2010-08-31 at 16:30 -0500, Bruno Wolff III wrote:
> On Tue, Aug 31, 2010 at 17:20:23 -0400,
> Al Dunsmuir wrote:
> >
> > Please do not ignore that the browser is there for the user to use,
> > not for Fedora to stream information in spite of the user's wishes.
>
> Nor for Mozilla to
On Tue, 2010-08-31 at 08:27 -0700, Adam Williamson wrote:
> It doesn't seem to be an unavoidable requirement, it says:
>
> "If you proposed Start/Home Page is not similar to the existing Firefox
> Start Page, please be prepared to provide a rationale for the change,
> and how it would benefit the
On Tue, 2010-08-31 at 08:19 -0400, Matthew Miller wrote:
> Fedora gets to build and ship a slightly-modified version of Firefox while
> retaining the Firefox name due to a distribution partner agreement with
> Mozilla. Mozilla gets their money from Google. I don't think we *can* make
> it something
On Mon, 2010-08-30 at 22:08 -0700, Jesse Keating wrote:
> Developers put new features in rawhide knowing that they will be in the
> next release of Fedora, which would be at the /most/ 6 months from the
> time they drop the feature.
It's more like 9 months. A feature has to wait until the next br
On Mon, 2010-08-30 at 02:46 +0530, Rahul Sundaram wrote:
> On 08/30/2010 01:01 AM, Matt McCutchen wrote:
> >
> > Interesting. I can understand not wanting to promote a proprietary
> > search engine on the Fedora start page, but if the idea is that Fedora
> > users and
On Sun, 2010-08-29 at 15:07 -0500, Manuel Escudero wrote:
> AGAIN AND AGAIN AND AGAIN... http://start.fedoraproject.org/ is using
> a Google Search Box... YOU DON'T HAVE THE CODE TO PLAY WITH IT OR
> ANYTHING... With "Fedora's engine" I'm giving you the chance of having
> something more "opensource
On Sun, 2010-08-29 at 14:13 -0500, Mike McGrath wrote:
> On Sun, 29 Aug 2010, Manuel Escudero wrote:
> > 3) We're already using a GOOGLE SEARCH BOX!! in
> > http://start.fedoraproject.org/ ¿Do you have the code for this one?
> > NO. And Fedora Project is using it. I'm sharing a "Fedora Solution" a
On Thu, 2010-08-26 at 15:56 -0400, Matt McCutchen wrote:
> $ git show-branch remotes/origin/{f12/,f13/,f14/,}master
> $ git diff refs/remotes/origin/{f12,f13}/master
To avoid any possible confusion: the inconsistency in the arguments I
used was just sloppy, it doesn't have a spec
On Thu, 2010-08-26 at 15:16 -0400, Neal Becker wrote:
> But, I hope this doesn't mean f12 is out of sync with f13, f14, master.
> They should all be identical.
It looks like f12, f14, and rawhide are all the same, and f13 has one
extra commit:
$ git show-branch remotes/origin/{f12/,f13/,f14/,}m
On Wed, 2010-08-25 at 09:49 +0200, Kevin Kofler wrote:
> Matt McCutchen wrote:
> > I think that's precisely the concern. In the event that F14 goes back
> > to upstart, the final release will use a configuration that may not have
> > received much testing.
>
> D
On Tue, 2010-08-24 at 23:31 +0200, Lennart Poettering wrote:
> On Tue, 24.08.10 16:38, Bill Nottingham (nott...@redhat.com) wrote:
> > Lennart Poettering (mzerq...@0pointer.de) said:
> > > > - init shall support a mechanism to re-exec itself to not cause dirty
> > > > inodes on shutdown; initscr
On Tue, 2010-08-24 at 22:32 +0200, drago01 wrote:
> [...] In the event that F14 goes back
> > to upstart, the final release will use a configuration that may not have
> > received much testing. If we want to claim that it's safe to switch
> > back to upstart after beta, we need to be testing that
On Tue, 2010-08-24 at 10:23 -0700, Adam Williamson wrote:
> On Tue, 2010-08-24 at 12:14 -0500, Mike McGrath wrote:
>
> > > The intent is not to do so in the final release, AIUI. We're only
> > > keeping it around during pre-release, so that if we decide we need to
> > > fall back to upstart for fi
On Mon, 2010-08-23 at 08:12 +0200, Kevin Kofler wrote:
> Roberto Ragusa wrote:
> > Some more tags for "functionally comparable to" and the name of
> > some well known programs for Windows or Macintosh would let
> > people cope with the original names of Linux apps.
> >
> > Nero -> k3b, xcdroast
>
On Mon, 2010-08-23 at 13:16 -0400, Matthew Miller wrote:
> On Fri, Aug 20, 2010 at 09:24:42PM +0200, Till Maas wrote:
> > > On Thu, Aug 19, 2010 at 06:49:33PM +0100, Matthew Garrett wrote:
> > > > > I think "run X as user Xorg if you're on KMS" would be a fine
> > > > > F15Feature to aim for. Ubun
On Thu, 2010-08-19 at 07:41 +0100, Richard W.M. Jones wrote:
> On Wed, Aug 18, 2010 at 07:29:35PM -0700, Matt McCutchen wrote:
> > On Wed, 2010-08-18 at 22:43 +0100, Richard W.M. Jones wrote:
> > > On Wed, Aug 18, 2010 at 08:02:13AM -0400, seth vidal wrote:
> > > >
On Tue, 2010-08-17 at 21:31 +0200, Kevin Kofler wrote:
> Adam Williamson wrote:
> > Shipping a Firefox with no ability to use Javascript would be more or
> > less equal to not shipping it, frankly. No-one would use the thing.
>
> What I suggest is just to use the same old JavaScript interpreter w
On Wed, 2010-08-18 at 22:43 +0100, Richard W.M. Jones wrote:
> On Wed, Aug 18, 2010 at 08:02:13AM -0400, seth vidal wrote:
> > I am a libguestfs user and I'm complaining. It means I have to schlep
> > down a bunch of extra info on every update of libguestfs and that sucks
> > on my bandwidth.
>
>
On Mon, 2010-08-16 at 01:15 +0200, Kevin Kofler wrote:
> Some web sites are indeed abusing JavaScript.
> A web site is
> not and should not be an application, an application is not and should not
> be a web site.
Just because you said so? Web applications bring enormous practical
benefits to t
On Sun, 2010-08-15 at 22:41 +0200, drago01 wrote:
> On Sun, Aug 15, 2010 at 9:45 PM, Matt McCutchen
> wrote:
> > On Sun, 2010-08-15 at 18:26 +0200, Kevin Kofler wrote:
> >> But the end effect is, we're allowing a web browser to disable memory
> >> protect
On Sun, 2010-08-15 at 18:26 +0200, Kevin Kofler wrote:
> But the end effect is, we're allowing a web browser to disable memory
> protection, exposing all users to a severe security risk from merely
> browsing web sites. IMHO, the performance improvements in JavaScript aren't
> worth that risk.
1 - 100 of 218 matches
Mail list logo
