12:46 a.m.
Hello all,
Upstream contains a crucial D3D fix that I need.
Any idea when it's gonna get built?
(I'd build it myself, but I don't have an i386 machine handy and i386 on
x86_64 build - at least AFAIK, is broken)
- Gilboa
12:58 a.m.
On 18/11/2007, Gilboa Davara <gilboad(a)gmail.com> wrote:
Hello all,
(I'd build it myself, but I don't have an i386 machine handy and i386 on
x86_64 build - at least AFAIK, is broken)
You can try a koji scratch build, if you are a Fedora contributor?
koji build --scratch dist-f8 filename.src.rpm
You might have to 'setarch i386' to create the .src.rpm though, and
perhaps delete /etc/rpm/platform
--
Michel Salim
http://hircus.jaiku.com/
2:47 a.m.
On Sun, 2007-11-18 at 01:58 -0500, Michel Salim wrote:
On 18/11/2007, Gilboa Davara <gilboad(a)gmail.com> wrote:
> Hello all,
>
> (I'd build it myself, but I don't have an i386 machine handy and i386 on
> x86_64 build - at least AFAIK, is broken)
>
You can try a koji scratch build, if you are a Fedora contributor?
koji build --scratch dist-f8 filename.src.rpm
You might have to 'setarch i386' to create the .src.rpm though, and
perhaps delete /etc/rpm/platform
I'm bandwidth limited.
Using koji/mock to build wine will most likely take ~10 hours :(
- Gilboa
6:02 a.m.
I'm bandwidth limited.
Using koji/mock to build wine will most likely take ~10 hours :(
I can understand that with Mock, but why would Koji be a problem? You
only need to upload the src.rpm you want to build. You don't need to
download the dependencies.
Cheers,
Debarshi
--
GPG key ID: 63D4A5A7
Key server: pgp.mit.edu
8:15 a.m.
On Sun, 2007-11-18 at 17:32 +0530, Debarshi 'Rishi' Ray wrote:
> I'm bandwidth limited.
> Using koji/mock to build wine will most likely take ~10 hours :(
I can understand that with Mock, but why would Koji be a problem? You
only need to upload the src.rpm you want to build. You don't need to
download the dependencies.
Cheers,
Debarshi
--
GPG key ID: 63D4A5A7
Key server: pgp.mit.edu
... I assume you mean koji client, right?
I may be wrong... but wouldn't this mean that I'm using fedora servers
as my build-sys? (As I normally do with the packages that I maintain?)
- Gilboa
8:34 a.m.
but wouldn't this mean that I'm using fedora servers
as my build-sys? (As I normally do with the packages that I maintain?)
Yes.
Cheers,
Debarshi
--
GPG key ID: 63D4A5A7
Key server: pgp.mit.edu
9:31 a.m.
On Sun, 2007-11-18 at 20:04 +0530, Debarshi 'Rishi' Ray wrote:
> but wouldn't this mean that I'm using fedora servers
> as my build-sys? (As I normally do with the packages that I maintain?)
Yes.
Doesn't look like an idea solution...
I doubt the Fedora's konji servers were designed to serve as "free"
build servers.
I should really take the time to learn how to set proper caching w/
mock. But thus far, I didn't really have the time to do so.
- Gilboa
9:51 a.m.
Gilboa Davara píše v Ne 18. 11. 2007 v 17:31 +0200:
On Sun, 2007-11-18 at 20:04 +0530, Debarshi 'Rishi' Ray
wrote:
> > but wouldn't this mean that I'm using fedora servers
> > as my build-sys? (As I normally do with the packages that I maintain?)
>
> Yes.
>
Doesn't look like an idea solution...
I doubt the Fedora's konji servers were designed to serve as "free"
build servers.
They are not free, but for package maintainer it is possible to use the
"scratch" build method for testing etc. The created packages are deleted
after some time.
I should really take the time to learn how to set proper caching w/
mock. But thus far, I didn't really have the time to do so.
My internet connection is limited to, so I have used
http://fedoraproject.org/wiki/PackageMaintainers/MockTricks to setup a
squid cache for mock. It really works :-)
Dan
11:10 a.m.
On Sun, Nov 18, 2007 at 04:51:50PM +0100, Dan Horák wrote:
My internet connection is limited to, so I have used
http://fedoraproject.org/wiki/PackageMaintainers/MockTricks to setup a
squid cache for mock. It really works :-)
You might want to take a look at the mock 0.8.x yum caching. With the
yum cache, it is likely that you would not need the squid cache anymore.
The only thing that is re-downloaded is the yum metadata, if it changes.
This is enabled by default, and you can safely set the timeout on it to
be as high as you like.
--
Michael
4:02 p.m.
Michael E Brown wrote:
You might want to take a look at the mock 0.8.x yum caching. With
the yum cache, it is likely that you would not need the squid cache
anymore. The only thing that is re-downloaded is the yum metadata,
if it changes. This is enabled by default, and you can safely set
the timeout on it to be as high as you like.
For those of us with a local mirror on the LAN, is it enough to simply
set config_opts['plugin_conf']['yum_cache_enable'] = False in the mock
defaults.cfg to disable the yum cache?
Also, is there a proper way to clear the cache, or is it fine to just
rm /var/lib/mock/cache/*/yum_cache ?
--
Todd OpenPGP -> KeyID: 0xBEAF0CE3 | URL: www.pobox.com/~tmz/pgp
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
I like this 'God'; he's so deliciously evil.
-- Stewie Griffin
10:03 a.m.
On Sun, Nov 18, 2007 at 05:02:41PM -0500, Todd Zullinger wrote:
Michael E Brown wrote:
> You might want to take a look at the mock 0.8.x yum caching. With
> the yum cache, it is likely that you would not need the squid cache
> anymore. The only thing that is re-downloaded is the yum metadata,
> if it changes. This is enabled by default, and you can safely set
> the timeout on it to be as high as you like.
For those of us with a local mirror on the LAN, is it enough to simply
set config_opts['plugin_conf']['yum_cache_enable'] = False in the mock
defaults.cfg to disable the yum cache?
Correct.
Also, is there a proper way to clear the cache, or is it fine to
just
rm /var/lib/mock/cache/*/yum_cache ?
Yes. You probably have to do that as root.
--
Michael
11:07 a.m.
On Sun, Nov 18, 2007 at 05:31:05PM +0200, Gilboa Davara wrote:
On Sun, 2007-11-18 at 20:04 +0530, Debarshi 'Rishi' Ray
wrote:
> > but wouldn't this mean that I'm using fedora servers
> > as my build-sys? (As I normally do with the packages that I maintain?)
>
> Yes.
>
Doesn't look like an idea solution...
I doubt the Fedora's konji servers were designed to serve as "free"
build servers.
I should really take the time to learn how to set proper caching w/
mock. But thus far, I didn't really have the time to do so.
Mock 0.8.x is set up to cache automatically. It caches the downloaded
RPMs as well as your buildroot. No additional configuration necessary.
For your situation, you probably should set the timeout on the
downloaded yum packages much higher. It defaults to re-download pkgs
after 30 days, you can safely set that to be higher.
--
Michael
3:44 p.m.
On Sun, 18 Nov 2007 08:46:07 +0200
Gilboa Davara <gilboad(a)gmail.com> wrote:
Hello all,
Upstream contains a crucial D3D fix that I need.
Any idea when it's gonna get built?
(I'd build it myself, but I don't have an i386 machine handy and i386 on
x86_64 build - at least AFAIK, is broken)
- Gilboa
I am nearly done with testing here so once I get my mock set up right for f8 (am
I the only one missing the buildsys-build stuff for f8?) I will do a mock test
build and then it should hit testing soon. Sorry for the delay.
- Andreas
--
Andreas Bierfert, B.Sc. | http://awbsworld.de | GPG: C58CF1CB
andreas.bierfert(a)lowlatency.de | http://lowlatency.de | signed/encrypted
phone: +49 2402 102373 | cell: +49 173 5803043 | mail preferred
3:53 p.m.
On So November 18 2007, Andreas Bierfert wrote:
f8 (am I the only one missing the buildsys-build stuff for f8?) I
will do a
Yes, I am happy that it is away finally. The information of buildsys-build is
now in the f8 repo comps file. With
config_opts['chroot_setup_cmd'] = 'groupinstall buildsys-build'
in the mock config file, this information will be used.
Regards,
Till
3:59 p.m.
On Sun, 18 Nov 2007 22:53:15 +0100, Till Maas wrote:
On So November 18 2007, Andreas Bierfert wrote:
> f8 (am I the only one missing the buildsys-build stuff for f8?) I will do a
Yes, I am happy that it is away finally. The information of buildsys-build is
now in the f8 repo comps file. With
config_opts['chroot_setup_cmd'] = 'groupinstall buildsys-build'
in the mock config file, this information will be used.
And if you set up a local F8 mirror, be sure to tell createrepo the
name of comps xml file.
8:16 a.m.
On Sun, 2007-11-18 at 22:44 +0100, Andreas Bierfert wrote:
On Sun, 18 Nov 2007 08:46:07 +0200
Gilboa Davara <gilboad(a)gmail.com> wrote:
> Hello all,
>
> Upstream contains a crucial D3D fix that I need.
> Any idea when it's gonna get built?
> (I'd build it myself, but I don't have an i386 machine handy and i386 on
> x86_64 build - at least AFAIK, is broken)
>
> - Gilboa
>
I am nearly done with testing here so once I get my mock set up right for f8 (am
I the only one missing the buildsys-build stuff for f8?) I will do a mock test
build and then it should hit testing soon. Sorry for the delay.
- Andreas
Looking forward for it.
Thanks,
- Gilboa
11:48 a.m.
On Mon, 19 Nov 2007 16:16:32 +0200
Gilboa Davara <gilboad(a)gmail.com> wrote:
Looking forward for it.
F-{7,8} builds should hit testing with the next push.
Regards,
Andreas
--
Andreas Bierfert, B.Sc. | http://awbsworld.de | GPG: C58CF1CB
andreas.bierfert(a)lowlatency.de | http://lowlatency.de | signed/encrypted
phone: +49 2402 102373 | cell: +49 173 5803043 | mail preferred
6002
days inactive
6004
days old
17 comments
9 participants
participants (9)
-
Andreas Bierfert -
Dan Horák -
Debarshi Ray -
Gilboa Davara -
Michael E Brown -
Michael Schwendt -
Michel Salim -
Till Maas -
Todd Zullinger