I have the yarrow's iso files on my HD in a RH9 system. Let's say I want
to upgrade selected packages using an "apt-get install" pointing to my
iso-mounted files, how do I do it?
i.e I mount the iso into some /mnt/yarrow1, /mnt/yarrow 2 etc..
Then what is the complete procedure to make my apt look into my own HD to
upgrade packages. Can anybody redirect me to the correct
resource or some literature hanging on the web? Thanks.
Assume also that I do not wish to burn CDs! I do not want to use
With kind regards,
Singapore Synchrotron Light Source (SSLS)
5 Research Link,
Email: slsbdfc at nus dot edu dot sg \or\
didierbe at sps dot nus dot edu dot sg
we use mock for local package build, but it's very slow. now we install
a new host just for mock with 8core, ram disks etc. it seems it still
slow. first of all most of the time mock use only one 1 core of the cpu.
is there any way to speed up different part of the mock build process?
thanks in advance.
ps. anyway is there any better place to discuss it?
Levente "Si vis pacem para bellum!"
Nowadays the jack project has two branches - old jack (1) branch with
version 0.116.2 and new one called jack2 version 1.9.3.
I'd like to gather opinions and suggestions about applying new version for F13.
Please, share your thoughts!
With Best Regards,
early in the F13 cycle, we enabled the bytecode interpreter in our
freetype package, since the patents on that have expired last fall.
Unfortunately, it turned out that many free fonts don't actually benefit
from this, and actually look worse with the bci. The reason for that is
that without the bci, freetype uses its autohinter on all fonts, but
with the bci turned on, it only applies hints to fonts which have them,
and leaves other fonts alone.
Behdad investigated the situation, and we have a plan to fix this, but
doing it properly requires enhancements in multiple places (freetype,
fontconfig, pango), and will not be ready in time for F13.
Therefore, we decided to turn the bci off again until the necessary
changes are in place to use it only on fonts which benefit from it. This
change went into freetype-2.3.11-3.fc13.
If your fonts look subtly different tomorrow, this is why...
I won't, at least for now, maintain the packages I maintain in EPEL-5 in
EPEL-6. I have added a nobranch file in all of them. If you want to take up
the package, you can. It is still unclear to me how to practically ensure
that you become the EPEL-6 branch owner, instead of me, though. Hopefully
this will be sorted out.
If you want to maintain the EL-5 (or even EL-4) branch too, don't
hesitate, the less package I maintain the better I am.
I think that wdm should not be maintained in EL-6 anyway, since upstream
is dead and there is no ConsoleKit integration.
For the dap-* packages it maybe worth waiting for a stabilisation of
the ABI, and maybe integration with bes and packaging of olfs to have a
working hyrax server before branching. My guess is that there are no
users of these packages anyway. Also maybe the opendap implementantion
in netcdf itself could be used instead of libdap/libnc-dap.
The list is:
Peter Gordon seems to be unreachable and while bumping up to
rb_libtorrent to fix E-V-R, I noticed that deluge has a separate flags
sub package. I remember this was proposed as a guideline and then
dropped. Do we need a flags sub package anymore? Seems rather pointless.