On Wed, Dec 30, 2009 at 8:05 AM, Ralf Corsepius rc040...@freenet.de wrote:
Well, I disagree: If they want to use their auditied version, they haven't
understood how open source works. They qualify as jerks who prefer to use
proprietary forks instead of paying back to upstream and the wider
On Mon, Dec 14, 2009 at 11:31 PM, Todd Zullinger t...@pobox.com wrote:
Jeff Garzik wrote:
If done right, the move to git can still service CVS requests in
some capacity... that may make the transition a little less abrupt
and painful.
Perhaps. But git-cvsserver is a rather limited crutch
On Tue, Dec 15, 2009 at 9:00 AM, Martin Langhoff
martin.langh...@gmail.com wrote:
branches AFAIK. (It's not that awkward, but for developers resisting
change... ah, every changed comma is a slight :-) ... ).
To be clear, I mean developers with better things to do with their
time than dealing
On Thu, Sep 17, 2009 at 1:47 PM, Daniel Drake d...@laptop.org wrote:
Thanks! Got it working as follows:
1. extract ISO
2. copy in new ks file
3. add more RPMs to Packages/ (using creative use of yumdownloader to
make sure that deps come with the new RPMs)
4. createrepo --database
On Tue, Sep 15, 2009 at 12:02 PM, Daniel Drake d...@laptop.org wrote:
I then tried to create a F9 chroot using mock, with the intention of
running revisor or pungi inside. This doesn't work, because mock
creates a v9 berkeley DB inside the chroot, but the libraries/apps
inside the chroot only
On Sat, Sep 12, 2009 at 10:13 AM, Michael Schwendt mschwe...@gmail.com wrote:
The non-responsive packager procedure could
have been started _several_ months earlier. Perhaps one year ago already.
There have been dead silent bugzilla tickets that ought to have raised an
alarm-bell.
Is this
On Wed, Jul 22, 2009 at 6:50 PM, Richard Hugheshughsi...@gmail.com wrote:
2009/7/22 Matthias Clasen mcla...@redhat.com:
Amazingly, Richard fixed quite a few of the incoming bugs already, while
the test day was still ongoing, and people were able to confirm that the
fixes are working. Well
On Mon, Jun 29, 2009 at 9:27 PM, Matthias Clasenmcla...@redhat.com wrote:
To achieve this, we will hold regular test days, each of which will
focus on use cases in a certain area. A few ideas for test day topics
Overall, an excellent idea and plan. We had some very good results
with an OLPC
On Thu, Jun 25, 2009 at 12:18 AM, Matthew
Woehlkemw_tr...@users.sourceforge.net wrote:
So... 60% smooth sailing rate isn't terrible, especially since I /was/
able to reassemble all the pieces I got to keep without too much trouble.
...
The problem with preupgrade is that it needs user
On Thu, Jun 18, 2009 at 4:48 PM, Bill Nottinghamnott...@redhat.com wrote:
Peter Robinson (pbrobin...@gmail.com) said:
I know of *no one* in the community who tests on i586 to ensure that it
works. (If this drags them out of silence, so be it!) It is certainly not
part of the QA matrix for
On Thu, Jun 18, 2009 at 5:22 PM, Bill Nottinghamnott...@redhat.com wrote:
+arch_compat: geode: i686
...
That should do the trick. :)
Cool. Didn't know we had that compat mechanism available.
Back to my humid cave then...
m
--
martin.langh...@gmail.com
mar...@laptop.org -- School Server
On Sun, Jun 14, 2009 at 8:08 PM, Lennart Poetteringmzerq...@0pointer.de wrote:
Gah. Allowing packages to pierce the firewall just makes the firewall
redundant.
True
A firewall is an extra layer of security that
simply hides the actual problem.
Um!? Layered security is a _good thing_. *All*
In my neverending quest for the School Server, I am looking for a
'unix socket superserver', something akin to xinetd listening on
oldstyle unix sockets. Connecting to the right socket triggers the
superserver to spawn a (potentially memory-heavy, privileged) process
to handle the connection, with
Useful to diagnose problems with %post scripts during the build. This patch
adds the method to the ImageCreator class, and the corresponding options to
image-creator and livecd-creator
--
Actually, quite a handy trick when my dodgy %post scripts mess up
during initial/anaconda installs.
On Thu, Feb 26, 2009 at 9:46 PM, Jeroen van Meeuwen kana...@kanarip.com wrote:
If I gave you some 2.1.4 revisor packages to test on Fedora 9 (I'm not sure
they work but there have been no major changes), are you able to test them?
Yes. My only 'compat' concern is with anaconda. If they expect
On Tue, Feb 24, 2009 at 3:12 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
Are you planning on updating the F-9 or F-11 packages with it?
Hi Jeroen,
- is there a revision coming on the F-9 or F10 branches?
- can you check whether the F-9 package (2.1.1-7) matches what's in
git? From
On Tue, Feb 17, 2009 at 3:17 AM, Jeroen van Meeuwen kana...@kanarip.com wrote:
Can you maybe send me a log file with both Revisor as well as YUM set to
debuglevel 9?
Hi Jeroen,
last week you mentioned the logs made sense... any news on this track?
Did this evolve into a different thread
Hi Jeroen,
we have revisor on F-9 ignoring the requested arch and building the
spin based on the host arch only - is this a known issue? The
revisor-made spin we have doesn't work on i586 :-/
more details below...
On Sun, Feb 15, 2009 at 10:58 AM, Martin Langhoff
martin.langh...@gmail.com wrote
On Mon, Feb 16, 2009 at 2:52 PM, Jeroen van Meeuwen kana...@kanarip.com wrote:
Since your first mail, I've tried to reproduce this. I have no problems
producing installation media with both openssl.i386 and openssl.i686 in the
RPM payload (Packages/ directory) - with either respin mode or
[ resend - now to the appropriate Fedora list - apologies ]
Hi everyone,
the olpc XS spin is hitting a problem installing on i586s (and that
includes our own XO). The problem seems to be well known -- anaconda
composes based on the arch of the build host rather than on the arch
requested, as
On Wed, Oct 15, 2008 at 12:52 AM, seth vidal [EMAIL PROTECTED] wrote:
You can obsolete and conflict
Obsoletes: pkgname=ver.rel
Conflicts: pkgname=ver.rel
Great -- thanks! I'll do exactly this.
m
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] -- School Server Architect
- ask interesting
On Tue, Oct 14, 2008 at 4:23 AM, seth vidal [EMAIL PROTECTED] wrote:
The error is
Missing Dependency: glibc-common = 2.8-3 is needed by package
glibc-2.8-3.i386
Is there any other debug information available?
_something_ is pulling in glibc-2.8-3 instead of 2.8-8. That's what's
horking
On Tue, Oct 14, 2008 at 11:45 AM, Connie Sieh [EMAIL PROTECTED] wrote:
Add
excludes=glibc*
to /etc/revisor/conf.d/revisor-f9-i386.conf in the [fedora] section.
(substitute x86_64 as needed)
thanks - I found the excludes in the manpage as well - that definitely
fixed it.
cheers,
m
--
OLPC's XS ships a number of patched packages. The packages are
normally built with a different stream or flavour (they don't say
f9 but xs05) and sit in a special repository.
Is there a good way to ensure revisor/yum prefers the packages from
the xs stream or repo over the standard F9 release or
On Tue, Oct 14, 2008 at 3:27 PM, seth vidal [EMAIL PROTECTED] wrote:
you can use yum's priorities plugin to achieve similar results.
It's a bit simpler than apt but I can sure work with this. Thanks!
Just as in the apt-world configuring priorities/pinning for
longterm/widespread use is a
On Tue, Oct 14, 2008 at 4:24 PM, James Antill [EMAIL PROTECTED] wrote:
But if you are going to ship a repo to end users which requires/uses
the yum-priority plugin (or excludes, or whatever),
I am shipping a heavily preconfigured spin, the OLPC School Server.
It points to the standard F9
Thanks a lot for your notes. *Extremely* useful. A few comments below,
On Tue, Oct 14, 2008 at 5:39 PM, James Antill [EMAIL PROTECTED] wrote:
On Tue, 2008-10-14 at 16:48 +1300, Martin Langhoff wrote:
I am shipping a heavily preconfigured spin, the OLPC School Server.
It points to the standard
On Tue, Oct 14, 2008 at 6:16 PM, Mike McLean [EMAIL PROTECTED] wrote:
If you go this route, I think what you want is obsoletes. Obsoletes says
this packages replaces this one. Conflicts says this package cannot be
installed at the same time as this other one.
Does 'obsoletes' also mean this
Right now, revisor can build a pristine F9 installer CD but cannot
build a F9 + updates installer CD.
The problem appears by merely enabling the additional repo in the
stock F9 config files that ship with Revisor. It has also been
reported elsewhere: https://fedorahosted.org/genome/ticket/28
The
On Fri, Sep 19, 2008 at 10:23 PM, Jeroen van Meeuwen
[EMAIL PROTECTED] wrote:
Hence the log-file is of interest to me ;-)
Sent it in a private email :-)
Yes, anaconda-runtime needs to exist in the repositories you use.
Sorry - I should have clarified - anaconda-runtime *is* in the repos
On Fri, Sep 19, 2008 at 3:16 AM, Jerry Vonau [EMAIL PROTECTED] wrote:
Yea, revisor needs anaconda-runtime,
cat /usr/lib/revisor/scripts/F9-buildinstall | grep anaconda
Yes, but from what Jeroen has said, revisor will pull it in to satisfy
the need at CD build time, without it being listed in
On Wed, Aug 6, 2008 at 8:37 PM, Nigel Jones [EMAIL PROTECTED] wrote:
http://article.gmane.org/gmane.comp.gcc.devel/94613
That's actually a very useful article and the methods/reasons behind it
sound quite sane and it could be a useful approach for us.
Agreed. git gc on all repos on an
On Fri, Sep 12, 2008 at 3:11 AM, Jeroen van Meeuwen [EMAIL PROTECTED] wrote:
Seth Vidal wrote:
isn't fedora-logos being pulled in in @core in comps?
that's why kickstart is pulling it in, I think.
Very true, notting has just closed #456882, having removed fedora-logos from
@core, but that is
Hoping to provide a custom isolinux menu for the XS spin - and looking
at the src in git, I see the --isolinux-cfg option. If it works, it'll
be just the ticket.
Is it reasonable to expect it to run with F-9 and with F-9 anaconda?
cheers,
m
--
[EMAIL PROTECTED]
[EMAIL PROTECTED] -- School
On Tue, Sep 9, 2008 at 8:48 PM, Jeroen van Meeuwen [EMAIL PROTECTED] wrote:
So what you're saying is that anaconda picks up the kickstart file and runs
away with it, even when it has not been told it should do so?
I am fairly sure that it does, though today I've tested ~20 different
combination
On Tue, Sep 9, 2008 at 10:55 PM, Jeroen van Meeuwen [EMAIL PROTECTED] wrote:
I know it wasn't doing this before, and I'm not sure it's supposed to now.
I've not seen any changes related to kickstart loading other then for the
kickstart located on an NFS share... but then again I may have
By naming the kickstart file as ks.cfg, anaconda would _always_ take
it, regardless of kernel boot options. This is not what was expected -
it is safer to give it a different name, and then use the boot menu
item to select it.
The patch is on top if F-9 .
cheers,
m
--
[EMAIL PROTECTED]
Hi Jeroen,
I am trying to build a revisor-based School Server installer, and I am
finding some oddities
- As I mentioned before, it complains about a missing dependency for
a package that is right there, in the same repo as other packages it
is picking up.
- If I pass --kickstart-include
On Fri, Sep 5, 2008 at 12:01 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
- As I mentioned before, it complains about a missing dependency for
a package that is right there, in the same repo as other packages it
is picking up.
This is still misterious...
- If I pass --kickstart-include
On Fri, Sep 5, 2008 at 12:28 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
On Fri, Sep 5, 2008 at 12:01 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
- As I mentioned before, it complains about a missing dependency for
a package that is right there, in the same repo as other packages
The installer cd I'm trying to build (for the School Server) is driven
by 2 custom packages - a metapackage that pulls in all the
dependenciess, and a configuration package that whacks /etc .
Feeding those to Pungi via a kickstart file gets them on the installer
CD, but does not get them
On Wed, Sep 3, 2008 at 7:03 PM, Seth Vidal [EMAIL PROTECTED] wrote:
why not a kickstart with 'interactive' in the file:
http://www.redhat.com/docs/manuals/enterprise/RHEL-5-manual/Installation_Guide-en-US/s1-kickstart2-options.html
Bah, too easy to be true -- ;-) Thanks a lot for the hint -
On Wed, Sep 3, 2008 at 6:46 PM, Martin Langhoff 1.1 - The
interactive install should have a custom 'default' layout
for the autopartitioning. Can I seed that somehow?
2 - Support a fully automated kickstart install (non-default option
in grub menu). This is also an example for local teams
On Wed, Sep 3, 2008 at 9:42 PM, Jeroen van Meeuwen [EMAIL PROTECTED] wrote:
In any case, Revisor can already do what you're looking for on Fedora 9
genuine.
Cool. I've spent a good part of today playing with your good Revisor.
I have a few questions, hopefully not too OT for fedora-buildsys
Perhaps this is by design: the build tools dependencies
(anaconda-runtime an friends) which end up in stage2 AFAICS need to be
listed (and their dependencies met) in the main packages listing in
the kickstart file.
Is there a way to control those package listings separately? As a
(trivial)
On Wed, Jul 30, 2008 at 5:31 PM, Martin Langhoff
[EMAIL PROTECTED] wrote:
Welcome surprise - the livecd-iso-to-disk utility included in
livecd-tools works well with pungi-created CDs, booting normally into
anaconda.
Time to qualify this. I can get anaconda to start, and with a trivial
patch
On Thu, Jul 31, 2008 at 1:26 AM, Jeremy Katz [EMAIL PROTECTED] wrote:
On Wed, 2008-07-30 at 17:31 +1200, Martin Langhoff wrote:
Welcome surprise - the livecd-iso-to-disk utility included in
livecd-tools works well with pungi-created CDs, booting normally into
anaconda.
The script
Jesse has mentioned (in an earlier thread on fedora-devel) that the
Pungi in F7 has some caveats. At the moment I am considering a
migration from livecd-tools to pungi on F7 _before_ I migrate to F9
(this is all for the OLPC School Server, btw).
So my questions are roughly:
- What known
Getting my feet wet with pungi, I am tring to build a minimal F9
installer, and it is erroring out, as follows.
The ks file is adapted from one from the livecd packages:
$ cat livecd-fedora-9-minimal.ks
repo --name=release
On Wed, Jul 30, 2008 at 1:39 PM, Jesse Keating [EMAIL PROTECTED] wrote:
Please check the arch.log file in your output/logs/ directory, so that
you can get the actual output from buildinstall.
Good hint, thanks. Missing anaconda-runtime it seems.
Pungi.Pungi.DEBUG: Running buildinstall...
Getting closer :-) With the following ks I get a 208MB iso that boots
into anaconda. Anaconda, however, says The Fedora disk was not found
in any of your CDROM drives. Please insert the Fedora disk and press
OK to retry.
What does anaconda look for?
$ cat kickstarts/pungi-f9-minimal.ks
repo
Welcome surprise - the livecd-iso-to-disk utility included in
livecd-tools works well with pungi-created CDs, booting normally into
anaconda.
Now, I only have to figure out how to get anaconda to accept the repo
that's in the CD/USB disk to complete a base install.
cheers,
m
--
[EMAIL
52 matches
Mail list logo
