August 2007 - livecd - Fedora mailing-lists

F7 general question about livecd-creator and timezones
by Skunk Worx 01 May '09

01 May '09

My ks scripts have the timezone set to PDT (America/Los_Angeles). Installation to a hard drive works as expected. PDT in startup and in shells, etc. Creating a livecd-creator iso with the same tz setting, then booting, shows A/L_A in the /etc/sysconfig/clock file, as expected. However the date is always EDT in the boot messages, shells, etc. During startup I see : (lvm) Press I to enter interactive startup Setting clock (utc) Mon Jun 4 00:12:59 EDT 2007 (udev) I'm not clear on what is happening between lvm and udev in the Linux startup sequence. If someone could give me a hint about what to look for and where to look for it I would appreciate the help. --- John

3 3

Trimming the size of LiveCD's
by Jeroen van Meeuwen 03 Oct '07

03 Oct '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Here's a thought: 1304 random packages will install 724 MB of data in /usr/share/doc I'm sure there is /something/ to gain here. If every package on average installs ~0.5 MB of docs... Would it worth figuring out what docs should be on the LiveCD in the first place? I guess removing everything RPM calls docs is too much, as this will include man-pages as well. Any thoughts? - -- Kind regards, Jeroen van Meeuwen - -kanarip - -- http://www.kanarip.com/ RHCE, LPIC-2, MCP, CCNA C6B0 7FB4 43E6 CDDA D258 F70B 28DE 9FDA 9342 BF08 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (GNU/Linux) iD8DBQFG19BDKN6f2pNCvwgRAhhaAJ9UCH9WetRBu6foxAgztqMvg3h6OwCeLZU5 LxWzG5TBxdQOAE3VGFp400w= =YiuK -----END PGP SIGNATURE-----

11 32

boot failure on VIA Epia M-6000 board
by Thorsten von Eicken 10 Sep '07

10 Sep '07

I've been trying to boot the F7 live-cd on a VIA Epia M-6000 (600Mhz fan-less VIA C3 Eden processor). With the distributed live-cd (Fedora-7-Live-i686.iso) the machine resets as soon as the kernel starts (i.e right after the initrd is unpacked). I built a custom i386 kernel with the VIA drivers and DMA turned off, which got the kernel to boot. The problem I then have is that when init should be executed, the system simply hangs and nothing happens. The last line printed is "Freeing unused kernel memory". I then built an entire livecd-fedora-minimal system from scratch and still no joy (same problem where init doesn't run). I then replaced init by a "hello world" program. If I statically link the hello world program it happily prints "hello world", but if I dynamically link it it doesn't. So it looks like /bin/bash (dynamically linked) doesn't run. At this point I'm at the end of my fedora wisdom. I have previously successfully booted a custom gentoo 2.6 kernel on this box, and the ubuntu 6.06.1 system boots as well. I'd rather use fedora, though, and would appreciate any suggestions either about what to try, or how to get debug information about what fails when running a dyn linked executable. Thanks! Thorsten NB: I was unsuccessful building the livecd-fedora-minimal system using the provided kickstart. I had to add the following packages so that livecd-creator could operate properly in the chrooted environment: nash, cpio, gzip, findutils, and squashfs-tools.

2 11

Revised: [PATCH] turboLiveInst - improves livecd/usb installer speed by 15-20+%
by Douglas McClendon 07 Sep '07

07 Sep '07

Attached is a revised version of my turboLiveInst patch to livecd-tools and anaconda. This version is more polished. I.e. bugs have been fixed, complexity removed, and therefore should be easier to review. I performed some anecdotal performance tests, on a sony vaio vgn-n250e. I used a 30G destination volume for all tests, and when using usbstick media, it was media that reported 8.5MB/s from hdparm -t. I did have selinux disabled, and did not use the prelink option. I'd love to hear performance numbers from differing test rigs. The performance results I got were- install from cdrom without turboLiveInst: copy: 250s postinst: 86s install from cdrom with turboLiveInst: copy: 299s postinst: 84s install from usb without turboLiveInst: copy: 226s postinst: 72s install from usb with turboLiveInst: copy: 175s postinst: 72s Conclusions: On this testrig, installing from cdrom, turboLiveInst yielded a 20% speedup in copy, which resulted in an end to end install speedup of 15%. Installing from usb, turboLiveInst yielded a 29% speedup in copy, which resulted in an end to end install speedup of 20%. I did test copy-to-ram mode, and the resulting benefits were laughably huge. But this is only because this laptop has 1G of ram, and very strange behaviour occurs this near the threshold of having too little ram to use this feature. Though this is still an argument in favor of turboLiveInst, in that somehow it found itself on the better side of the threshold. I would expect that with 2G of ram, the benefit would be on the order of 35-50% speedup, as the main thing masking the benefit in the cdrom case, is the slow access to install media, which hides the benefit of cutting the needed disk writes nearly in half. The secondary benefit of turboLiveInst is that it removes the artificial limitation that the target rootfs must be greater than 4.0G, instead of the 2.1G actual uncompressed size of the contents of the LiveCD. Jeremy has pushed back against this patch because of complexity. Hopefully this round of polishing will make the patch much easier to read and understand. In addition, since the cleanupDeleted patch which this one depends on has already been merged, that should also make this a bit more palatable. Jeremy also brought up the idea of doing a file level copy installation, rather than the current block level mechanism. This _is_ a good idea, in my opinion, in that it will more intelligently support situations such as a separate /usr filesystem. In addition there is no way that turboLiveInst or the existing block level mechanism can be made to support xfs or other non-ext3 destination filesystems chosen by the user (should those options return). But- I would argue that file level installations may suffer badly due to cdrom seeking. I would also argue that there is no reason why turboLiveInst, could not be the first choice for installation technique, with fallbacks to file level copies for the seperate /usr and xfs type scenarios. Ultimately I just hope that turboLiveInst gets serious consideration for F8, via performance comparison with whatever other options may exist. Finally, here are some notes on the architecture, which may help you to understand the code- As I mentioned in the original patch, the basic idea is to simply, at livecd-creator build time, use a device mapper snapshot to generate a delta file between the 4.0G filesystem housing 2.1G of data, and a 2.1G filesystem holding the same data. Then at anaconda/liveinst time, that delta file is used to recreate a virtual image of the 2.1G filesystem, so that it can be copied to the installation target, rather than the 4.0G filesystem which includes 1.9G of zeros that needn't be written to disk. I ended up using /dev/loop118 in the initramfs init (mayflower generated) to expose the delta file. /dev/loop118 was mknod'd already by mayflower, but not actually used for anything. I used it to expose the delta file (osmin.tgz), because /dev/loop121 was being used to expose the 4.0G os.img, and it seemed simplest to use an identical mechanism to expose that data. Because by the time anaconda runs, the original cdrom and squashfs filesystems have been lazy unmounted, a simple cp at that time was not an option(?). I chose to extract the delta file (osmin, a 16MB sparse file containing 1.2M of data, compressed to 25kb on cdrom) into /dev/shm (i.e. ram) so that reads from it would not try to go to the cdrom. This may not have been necessary. I chose to calculate the size of the filesystem at livecd-creator time, and include it with osmin as osmin.size(together forming osmin.tgz). This is less complex than what I did in the first pass, which was to use dumpe2fs to calculate it at ananconda time. As always, questions, comments, criticisms, and especially testers are more than welcome. peace... -dmc

5 17

local caching
by Colin Walters 04 Sep '07

04 Sep '07

Hi, What's the status of the persistent local RPM caching patches?

2 4

[PATCH] overlay/persistence second pass - for developer reference only
by Douglas McClendon 04 Sep '07

04 Sep '07

(I'm getting a sense of deja vu, that I'm learning the same lesson someone else recently learned here. Lets see if the 3rd time is the charm...) Attached is a revision to the persistence implementation that I posted a couple weeks ago. This is mainly for Jeremy, Tim, and anyone else who is interested in working on this, or something similar. I.e. at the very least, it is worth a read to look at the issues I've dealt with, and the several that are in comments as TODO. It may well be that a simpler persistence implementation that involves just extracting tarballs from usbsticks into the normal ram overlay, may be useful instead of (or even in addition to) this kind of implementation. (or perhaps some implementation of unionfs will make it into fedora eventually?) The main points of note, since the first post are- - all sorts of bugs fixed - I moved the overlay storage filesystem to be visible as /mnt/overlayfs always. This solves some aspects of the current problem of not easily being able to see how much writable space you really have available on the rootfs. (the real answer is a combination of the device mapper overlay file AND the filesystem it resides on). - I've included modified /etc/rc.d/init.d/halt and functions, to handle getting things cleanly shutdown (which is VERY important) - ntfs is somewhat present, but not really working. I have tested with vfat and ext3. Note that ext3 is a PITA when not cleanly unmounted- see TODOs. - rudimentary testing of the choice selection when multiple possible overlay images are detected suggests it works. - the patch format merely reflects my educational process with git, and not that I suggest that code this immature is anywhere near ready for merging. (i.e. inclusion of halt&functions and the origs I based them off of. Refer to list archives for documentation on how to use addidir/addsdir if needed) As always, comments/criticisms/suggestions are more than welcome. peace... -dmc

5 17

SRPMS for installed RPMs?
by Matt Domsch 04 Sep '07

04 Sep '07

I want to be sure, for license compliance, that all the binary bits on the final LiveCD have corresponding source code available. One of the "features" I'd like to see something in the stack of livecd-tools produce is a CD/DVD/whatever of the SRPMS that match the RPMs that go into the LiveCD. Smooge and I have both done this ourselves, with varying degrees of ease, essentially querying all the installed RPMs on the LiveCD after-the-fact and generating the list, then grabbing the files etc. All very manual. I expect there's a better way, and I'm even open to helping code it, but am looking for direction from you - those who know the tools best... Maybe it's really an Anaconda feature? Advise please. Thanks, Matt -- Matt Domsch Linux Technology Strategist, Dell Office of the CTO linux.dell.com & www.dell.com/linux

7 24

Revisor: Cannot setup installation target. Aborting.
by Lars Bjørndal 31 Aug '07

31 Aug '07

Hi! With yesterday's GIT version of Revisor, I got the following error message: Downloading Packages: Filesystem label=livecd-20070825 OS type: Linux Block size=4096 (log=2) Fragment size=4096 (log=2) 325120 inodes, 649728 blocks 6497 blocks (1.00%) reserved for the super user First data block=0 Maximum filesystem blocks=666894336 20 block groups 32768 blocks per group, 32768 fragments per group 16256 inodes per group Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912 Writing inode tables: Creating journal (16384 blocks): done Writing superblocks and filesystem accounting information: done This filesystem will be automatically checked every 38 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override. tune2fs 1.40.2 (12-Jul-2007) Setting maximal mount count to -1 Setting interval between checks to 0 seconds Cannot setup installation target. Aborting. Do you want to continue? [Y/n] y What's wrong here, do you think? Lars

3 13

kickstart file for FEL
by Chitlesh GOORAH 30 Aug '07

30 Aug '07

Hello there, Here is some work about the Fedora Electronic Lab live image. http://chitlesh.fedorapeople.org/FEL/livecd-fedora-electronic-lab.ks I would like to have some feedbacks about it and how to improve it. Will it be possible to spin a live image for FEL when F8T2 will be release? PS: I would like to give you a complete list of rpms installed on the livecd image. But however from today's rawhide, my spins are all broken with the following errors during the : file_contexts: invalid context system_u:object_r:games_exec_t:s0 file_contexts: invalid context system_u:object_r:games_exec_t:s0 Installing: filesystem #################### [ 3/723]file_contexts: invalid context system_u:object_r:games_data_t:s0 file_contexts: invalid context system_u:object_r:games_data_t:s0 Installing: ConsoleKit ################# [ 73/723]file_contexts: invalid context system_u:object_r:consolekit_exec_t:s0 Installing: GConf2 # [133/723]file_contexts: invalid context system_u:object_r:gconfd_exec_t:s0 Installing: pam [173/723]file_contexts: invalid context system_u:object_r:userhelper_conf_t:s0 Installing: usermode [183/723]file_contexts: invalid context system_u:object_r:userhelper_conf_t:s0 file_contexts: invalid context system_u:object_r:userhelper_conf_t:s0 file_contexts: invalid context system_u:object_r:userhelper_conf_t:s0 Installing: usermode # [183/723]file_contexts: invalid context system_u:object_r:userhelper_exec_t:s0 [..] Chitlesh -- http://clunixchit.blogspot.com

2 3

Some problems: rootpassword and liveinst
by Sebastian Vahl 28 Aug '07

28 Aug '07

Hi. My actual spin of the kde livecd from today has some problems: 1. It seems that the root password wasn't erased. If I boot the iso in vmware I got the error in the attached screenshot. If I boot the iso with enforcing=0 all is working. Is this a problem on my local machine (if relabeld the whole filesystem before I tested this)? 2. Because of 1. I've bootet with enforcing=0. If I then want to start liveinst I get this traceback: > [root@localhost ~]# liveinst > FATAL: Module md not found. > Traceback (most recent call last): > File "/usr/sbin/anaconda", line 550, in <module> > import signal, traceback, string, isys, iutil, time > File "/usr/lib/anaconda/isys.py", line 33, in <module> > import block > File "/usr/lib/python2.5/site-packages/block/__init__.py", line 20, > in <module> import dm > ImportError: /usr/lib/python2.5/site-packages/block/dmmodule.so: > undefined symbol: dm_task_get_uuid Any suggestions or more info needed? Sebastian

4 4

Traceback with newest yum
by Sebastian Vahl 28 Aug '07

28 Aug '07

Hi. With newest yum and yum-metadata-parser I got the following traceback when starting livecd-creator: > /usr/lib/python2.5/site-packages/pykickstart/parser.py:600: > DeprecationWarning: Script does not end with %end. This syntax has > been deprecated. It may be removed from future releases, which will > result in a fatal error from kickstart. Please modify your kickstart > file to use this updated syntax. warnings.warn(_("%s does not end > with %%end. This syntax has been deprecated. It may be removed from > future releases, which will result in a fatal error from kickstart. > Please modify your kickstart file to use this updated syntax.") % > _("Script"), DeprecationWarning) mke2fs 1.40.2 (12-Jul-2007) > Filesystem label=F8-KDE-17 OS type: Linux Block size=4096 (log=2) > Fragment size=4096 (log=2) 524288 inodes, 1048576 blocks 10485 blocks > (1.00%) reserved for the super user First data block=0 Maximum > filesystem blocks=1073741824 32 block groups 32768 blocks per group, > 32768 fragments per group 16384 inodes per group > Superblock backups stored on blocks: > 32768, 98304, 163840, 229376, 294912, 819200, 884736 > > Writing inode tables: done > Creating journal (32768 blocks): done > Writing superblocks and filesystem accounting information: done > > This filesystem will be automatically checked every 28 mounts or > 180 days, whichever comes first. Use tune2fs -c or -i to override. > tune2fs 1.40.2 (12-Jul-2007) > Setting maximal mount count to -1 > Setting interval between checks to 0 seconds > No Repositories Available to Set Up > No Repositories Available to Set Up > No such package *debuginfo to remove > Traceback (most recent call last): > File "/usr/bin/livecd-creator", line 1383, in <module> > sys.exit(main()) > File "/usr/bin/livecd-creator", line 1361, in main > target.install() > File "/usr/bin/livecd-creator", line 858, in install > self.installPackages() > File "/usr/bin/livecd-creator", line 550, in installPackages > self.ayum.runInstall() > File "/usr/bin/livecd-creator", line 295, in runInstall > (res, resmsg) = self.buildTransaction() > File "/usr/lib/python2.5/site-packages/yum/__init__.py", line 557, > in buildTransaction (rescode, restring) = self.resolveDeps() > File "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 701, > in resolveDeps CheckDeps, checkremoves, checkinstalls, missing = > self._resolveRequires(errors) File > "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 781, in > _resolveRequires (checkdep, missing, errormsgs) = > self._processReq(po, dep) File > "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 250, in > _processReq CheckDeps, missingdep = > self._requiringFromTransaction(po, requirement, errormsgs) File > "/usr/lib/python2.5/site-packages/yum/depsolve.py", line 496, in > _requiringFromTransaction reqpkg = self.rpmdb.searchNevra(name=name, > ver=version, rel=release)[0] IndexError: list index out of range The latest rawhide version I got here locally is yum-3.2.2-3.fc8 and yum-metadata-parser-1.1.0-2.fc7. With them all is working fine. Is this a problem with livecd-tools? If so I will file a bug against it. Sebastian

2 2

livecd-fedora-base-desktop
by Chitlesh GOORAH 28 Aug '07

28 Aug '07

Hello there, #001: from livecd-fedora-base-desktop.ks repo --name=development --mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide&arch=$basearch [..] # make sure debuginfo doesn't end up on the live image -*debuginfo In accordance to /etc/yum.repos.d/fedora-development.repo [development-debuginfo] name=Fedora - Development - Debug #baseurl=http://download.fedora.redhat.com/pub/fedora/linux/development/$basearch/debug/ mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=rawhide-debug&a… enabled=0 gpgcheck=0 eventually -*debuginfo could be omitted. #002: is it @games required on the livecd-fedora-base-desktop ? shouldn't it rather be in the livecd-fedora-kde-desktop.ks or livecd-fedora-desktop.ks ? Chitlesh -- http://clunixchit.blogspot.com

3 3

livecd-tools question - "GTK+ installer!"?
by Douglas McClendon 27 Aug '07

27 Aug '07

Can someone tell me what the final line in the livecd-tools TODO means. Under "Installer" - GTK+ installer! Does this mean de-integrating liveinst with anaconda? -dmc

2 1

/etc/statetab and persistence
by Jon Steer 27 Aug '07

27 Aug '07

I just noticed that there is apparently a /etc/statetab which allows you to specify directory paths to load from other sources upon bootup. So, on a liveCD,mounting /etc or mounting /var on another partition, especially on USB keys would work pretty handily. What am I missing? jon -

3 2

Error with Revisor
by Lars Bjørndal 24 Aug '07

24 Aug '07

Three days ago, I installed the GIT version of Revisor. Today, whil trying it out, I got the following error: Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 0.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 1.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: 2.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 3.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: # 4.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 5.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 6.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ## 7.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 8.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: ### 9.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 10.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 11.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: #### 12.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 13.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ##### 14.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 15.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 16.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ###### 17.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 18.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ####### 19.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 20.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 21.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######## 22.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 23.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ######### 24.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 25.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 26.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########## 27.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 28.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ########### 29.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 30.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 31.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############ 32.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 33.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############# 34.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 35.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 36.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############## 37.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 38.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ############### 39.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 40.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 41.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################ 42.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 43.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################# 44.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 45.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 46.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################## 47.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 48.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: ################### 49.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 50.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 51.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: #################### 52.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 53.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ##################### 54.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 55.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 56.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ###################### 57.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 58.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ####################### 59.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 60.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 61.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################## 62.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 63.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ######################### 64.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 65.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 66.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################## 67.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 68.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ########################### 69.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 70.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 71.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################ 72.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 73.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################# 74.0%Resolving Dependencies: Resolving Dependencies: ############################## 75.0%Resolving Dependencies: Resolving Dependencies: ######################################## 100.0% Populating statistics: Populating statistics: 0.0%Traceback (most recent call last): File "/usr/sbin/revisor", line 288, in <module> revisorBase.run() File "/usr/lib/python2.5/site-packages/revisor/cli.py", line 47, in run self.base.lift_off() File "/usr/lib/python2.5/site-packages/revisor/base.py", line 813, in lift_off self.check_dependencies(style=self.check_dependencies_no_conflicts) File "/usr/lib/python2.5/site-packages/revisor/base.py", line 565, in check_dependencies self.populate_stats() File "/usr/lib/python2.5/site-packages/revisor/base.py", line 844, in populate_stats installsize += pkg.po.installedsize File "/usr/lib/python2.5/site-packages/yum/packages.py", line 725, in __getattr__ return self.hdr[thing] KeyError: 'unknown header tag' What should I do to solve this? Lars

2 2

kernel panic, unable to load selinux policy
by Chitlesh GOORAH 23 Aug '07

23 Aug '07

Hello there, As proposed on the -devel mailing list, I've started to work on a livecd for "Fedora Electronic Lab". Hopefully, Jeremy's support still stands. with livecd-creator, I created a livecd with a kickstart file based on /usr/share/livecd-tools/livedvd-fedora-kde.ks The kickstart file for FEL is http://chitlesh.fedorapeople.org/FEL/livecd-fedora-electronic-lab.ks I had a livecd of 741.6MB which I'll strip later on to less that 700Mb. However, each time I created a livecd with this process: livecd-creator --config=/home/chitlesh/livecd-fedora-electronic-lab.ks \ --repo=fedora7,file:///home/chitlesh/Public/Fedora7 \ --repo=updates7,file:///home/chitlesh/Public/updates7 \ --fslabel=Fedora-Electronic-Lab on booting the livecd it fails on: [..] unmounting Unable to load SELinux Policy. Machines is in enforcing mode. Halting now. kernel panic: see http://chitlesh.fedorapeople.org/FEL/panic.png The diff of /usr/share/livecd-tools/livedvd-fedora-kde.ks and http://chitlesh.fedorapeople.org/FEL/livecd-fedora-electronic-lab.ks is http://chitlesh.fedorapeople.org/FEL/diff I'm booting on vmware server and my mirrors: fedora7 and updates7 are a rsync of the official mirrors, but the repodata was created with : createrepo comps/comps-f8.xml.in to ensure groups are considered. What could be missing or done wrong in this process ? Chitlesh -- http://clunixchit.blogspot.com

2 5

[PATCH] livecd persistence - devicemapper style - v3 - still not robust
by Douglas McClendon 23 Aug '07

23 Aug '07

The 3rd pass at my overlay/persistence patch for livecd-tools, isn't really bigger than the 2nd, but it is fairly big, and definitely not the final version. So if you want it, or any further updates if and as they become available, see http://filteredperception.org/downloads/overlay/ Summary of changes from the last version - - much better remount read-only teardown of overlayfs - findoverlay script debugging cleaned up, and obeys 'quiet' kernel arg - live script will technically work for initialization of an overlay image file, but it is still pretty much a placeholder - more organized, and revised todo/notes in findoverlay script. - very ugly (but maybe a bit less than before) mechanism for patching the halt and functions scripts to support clean shutdown. I'm _very_ open to suggestions for better ways to do it, than the livecd-creator->mayflower->initramfs->/etc/rc.d/init.d/fedora-live path currently. Also note that to get that done I had to put the same ugly temporary hack in 3 different config files. Maybe it is time to take care of the TODO that suggests getting fedora-live out of the kickstart and into a package. Of particular note, is that at this point in time, I'm getting a bit wary as to whether or not, short of 'fixing' problems that are probably beyond my abilities and/or desires, that this entire devicemapper snapshot mechanism, using overlay image files on disk, may be fatally flawed. See notes at end of findoverlay script for exact ext3 corruption error messages, and my random musings on the subject. I think it may well be that a vastly simpler implementation using only raw partitions, such as Ashok's might actually work better. At least for the short term, until I can figure out the problems I'm seeing. Or perhaps even an implementation with unionfs/funionfs. I would _really_ like to see my method work, but there are also other unrelated lower hanging fruit of interest to me that I think I might rather be working on. That said, my code is there, and I'll be more than happy to answer questions or brainstorm about it if anybody inquires. And maybe some idea will hit me or someone else soon, and I'll actually be able to make it work robustly. Or really, I may have just run into one bad failure case that isn't even reproducable, and further testing will show that it works pretty well. -dmc

2 1

liveinst , where does it get it's kickstart file from?
by Jon Steer 23 Aug '07

23 Aug '07

I would like to customize the kickstart file that anaconda uses during a liveinst install of my liveCD. The kickstart file that is used for the install, is not the same kickstart file that was used to create the LiveCD. A cursory inspection of anaconda doesn't yield any clues about how that kickstart is created, or where it comes from. Any pointers? thanks, jon -- "Whereever you go, there you are"

5 7

[PATCH] cleanupDeleted and container_size - saves 5.5% output size on f7livecd-i686
by Douglas McClendon 21 Aug '07

21 Aug '07

Attached is a patch. It could be broken into two patches for clarity. Please review and apply if appropriate. patch#1: add --container-size flag Using this flag, one can cause the os.img that sits in the squashfs.img, to be a larger sparse file than the filesystem contained in it. By default, the old behavior happens. One somewhat unrealistic, but real justification for this, would be booting a livecd on a system with 16G of ram. Without this flag, you would be limited to only writing 2G of data (given the existing f7-livecd-i686 choice of a 4G uncompressed-size, and about 2.1G of data). With this flag and a container of say 1T or 100G, there would be no negative consequences, but the livecd user would be able to online resize2fs their root filesystem upward if they liked. The more realistic usefulness comes if through a persistence implementation, the overlay file is not a 512M file stored in tmpfs, but an 8G file stored on an ipod. Everything mentioned above applies. patch#2: add --cleanup-deleted flag Using this flag, about 25% is added to the build time, but any files that were created and deleted in the install_root during installation, will not result in wasted space on the resulting iso. This happens because of the nature of the filesystem living on a sparse file. Anecdotally, this could be used to respin the fedora7-livecd-i686, from its existing 700MB, to 664MB. Or more likely, add another 100MB or so of uncompressed software onto it. This is of even greater importance as people spin their own livecds, and do intensive things during the installation, that might cause even more wasted space. Also, this somewhat lays the foundation for a 'turboinstaller' that improves current liveinst efficiency by 10-25% (for cdrom vs usbflash respectively), as mentioned in bug 248082 (pending efficiency tests with extra device mapper layers) Please review. Any comments, suggestions, or criticisms are welcome. I still consider myself a relative novice when it comes to python. peace... -dmc

5 15

How to remove groups in second config?
by Sebastian Vahl 21 Aug '07

21 Aug '07

Hi. (This is for the new changes to livecd-creator from git which uses two kickstarts.) Is there a way to remove a group which is defined in the first config (here livecd-config-base-desktop.ks) in the second config (here livecd-fedora-kde.ks)? My problem is that the language groups (e.g. @estonian-support) pulls also the kde language files (kde-i18n-Estonian) and koffice language files (koffice-langpack-et) in the livecd. And I am not able to remove them in the second config (e.g. -kde-18n-* or -kde-i18n-et). Any hint how to fix this? The language files are about 325 megs and that's to big for the cd. Sebastian

2 6

Adding files into the CD root file system
by Alexandre Magaz Graça 20 Aug '07

20 Aug '07

Hi, I'm making a LiveCD that I want to autorun (from Windows and Linux) to open a browser showing some help about how it works. So I added a new option that lets add to the CD root file system. If someone finds it useful, the attached patch adds this option to pilgrim. The patch is for the latest git version. Cheers, Àlex

5 6

installer efficiency - sparse hackery
by Douglas McClendon 20 Aug '07

20 Aug '07

Out of curiosity Jeremy, in your envisioned sparse-feature method alternative to turboLiveInst- How do you envision detecting which 0s in the file are legitimate data that needs to get written to disk, and which are unnecessary unwritten parts of the file? I took a look at the tar --sparse documentation, which suggests that it handles sparseness by doing a complete extra read of the whole file, to detect 0s. As mentioned, because what you are talking about is _not_ an actual sparse copy, there may be legitimate 0s that need to be written in our case. It seems the only way would be to write a tool, which utilizes "intimate knowledge of ext3fs filesystem internals" to detect the appropriate place of holes in the file. Can I just ask you - please - until you have a specific complete plan for an alternate solution, just go ahead and commit turboLiveInst for f8test2. If you come up with a better cleaner solution (even if only in your opinion), I promise not to utter one word of complaint after you remove turboLiveInst. I mean, you've already been down the path of suggesting a file-level copy. That turned out to have a 5X slowdown performance penalty. Now you are going down the path of this sparse copy, which is an incomplete solution, that despite what you've said, is not simply an elegant implementation of sparse support in python's shutil.copy. Rather, it is at least as much of a hack as what I did. And I maintain that turboLiveInst is not a hack, but an elegant use of devicemapper snapshot, which is the same elegant mechanism responsible for the fedora7 livecd in the first place. Getting more exposure to devicemapper shapshot usage in the developer community - is a good thing. It is a wonderful tool, that I'm sure will see many elegant uses in the coming years. Regards, -dmc

1 0

[Fwd: RE : Persistancy in livecd achieved [Patch attached]]
by Rahul Sundaram 20 Aug '07

20 Aug '07

Hi I looked for this in the list archives from the recent discussions. Sending it here again since it might have reached the list before. Rahul

2 1

LiveCD as Xen Guest, existence proof?
by Jon Steer 20 Aug '07

20 Aug '07

Has anyone managed to boot an F7 LiveCD as an F7 Xen Guest? I can boot an F6 LiveCD, but not F7. I can also boot the F7 LiveCD on VirtualBox, but not on F7 thanks, jon -- "Whereever you go, there you are"

2 2

Re: livecd persistence
by Douglas McClendon 20 Aug '07

20 Aug '07

Jeremy Katz wrote: > Had a chance to look at cleaning up the patches any? If not, I'll take > a stab the first of next week as I really want to get the basic bits in > for test2 :) I've been waiting to put turboLiveInst to rest, as my approach may involve devicemapper tricks, which I need to make sure you are comfortable with reviewing before I waste any time implementing them. Also, I need to make sure that this asdas(a)redhat.com person doesn't have useful persistence code, which I would be wasting my time duplicating if not necessary. Lastly, wouldn't test2 require an approved feature? I've been holding off myself due to no feedback regarding the attached mail -dmc ---- On Mon, 13 Aug 2007, Douglas McClendon wrote: > Any progress on this front? The F8 feature freeze is rapidly approaching. > > If I don't hear back about this issue, I'll just solicit people who have signed the CLA to put up a couple placeholder features, just so they are in place before the freeze. > > 1) livecd persistence, as mentioned on fedora livecd wishlist > > 2) improve livecd boot speed dramatically It was Luis Villa's last act before he left to draft changes to the CLA. I'll find out what the status of those changes are -- and it seems that counsel agreed to them. Max, do you know where this stands? --g ---- Greg Dekoenigsberg wrote: > On Thu, 19 Jul 2007, Douglas McClendon wrote: > >> Yeah, I figured out the CLA issue. I still haven't signed it. I hate legaleze. Maybe you can clarify- By signing that, and submitting works via channels under that umbrella, am I giving RH a license to modify my work, distribute those modifications to others, and not be obliged (ala GPL) to submit modifications back to me? Thats sort of what it sounds like, i.e. that they get as many rights as the original copyright holder (which would be those aforementioned rights). >> >> I'm sure this has been talked to death on some mailinglist or FAQ, any pointer to such a thread would be appreciated. > > You know, I'm not sure this particular reading has ever been discussed. I know that we want to make super-sure that (a) you actually *have* the right to share code with us, and (b) you can't take your ball and go home, and the CLA is structured to do that. > > I've never interpreted the CLA as giving us the right to take your work, modify it, and not give the modifications back -- but yeah, on a closer reading, that looks possible. I'll check it out with legal. Any progress on this front? The F8 feature freeze is rapidly approaching. If I don't hear back about this issue, I'll just solicit people who have signed the CLA to put up a couple placeholder features, just so they are in place before the freeze. 1) livecd persistence, as mentioned on fedora livecd wishlist 2) improve livecd boot speed dramatically -dmc > > I can assure you that's not our intent, but contracts don't really care much about intent. :) > > --g >

5 10

Is it possible to use yum setup on build host?
by Lars Bjørndal 20 Aug '07

20 Aug '07

Hello! I wonder if it's possible to use the yum setup on the machine you're using to build the livecd, instead of using the "repo" commands in the .ks file? In case it is, how do you do it? In case I need to use the repo command in the .ks file, I would like to know if it's possible to use "includepkgs=" in any way. Thank you! Lars

3 2

Get an error message with Revisor
by Lars Bjørndal 20 Aug '07

20 Aug '07

The command I ran was: revisor --cli --kickstart=/etc/livecd-console-rev.ks --optical\ --model=lrs After package download, and creating the file image, I got: Setting interval between checks to 0 seconds Traceback (most recent call last): File "/usr/sbin/revisor", line 203, in <module> revisorBase.run() File "/usr/lib/python2.5/site-packages/revisor/cli.py", line 48, in run self.base.lift_off() File "/usr/lib/python2.5/site-packages/revisor/base.py", line 532, in lift_off self.buildLiveMedia() File "/usr/lib/python2.5/site-packages/revisor/base.py", line 904, in buildLiveMedia if not liveImage.setup(livemedia_targetsize, build_dir="/var/tmp/revisor-livecd", yum_installroot=self.cfg.yumobj.conf.installroot, yum_cachedir=self.cfg.yumobj.conf.cachedir): File "/usr/lib/python2.5/site-packages/revisor/pilgrim.py", line 448, in setup os.symlink("../proc/mounts", self.build_dir + "/install_root/etc/mtab") OSError: [Errno 17] File exists What could I do to fix this? Thanks! Lars

2 1

[PATCH] overlay/persistence second pass - for developer reference only
by Douglas McClendon 20 Aug '07

20 Aug '07

Attached (for real this time) is a revision to the persistence implementation that I posted a couple weeks ago. This is mainly for Jeremy, Tim, and anyone else who is interested in working on this, or something similar. I.e. at the very least, it is worth a read to look at the issues I've dealt with, and the several that are in comments as TODO. It may well be that a simpler persistence implementation that involves just extracting tarballs from usbsticks into the normal ram overlay, may be useful instead of (or even in addition to) this kind of implementation. (or perhaps some implementation of unionfs will make it into fedora eventually?) The main points of note, since the first post are- - all sorts of bugs fixed - I moved the overlay storage filesystem to be visible as /mnt/overlayfs always. This solves some aspects of the current problem of not easily being able to see how much writable space you really have available on the rootfs. (the real answer is a combination of the device mapper overlay file AND the filesystem it resides on). - I've included modified /etc/rc.d/init.d/halt and functions, to handle getting things cleanly shutdown (which is VERY important) - ntfs is somewhat present, but not really working. I have tested with vfat and ext3. Note that ext3 is a PITA when not cleanly unmounted- see TODOs. - rudimentary testing of the choice selection when multiple possible overlay images are detected suggests it works. - the patch format merely reflects my educational process with git, and not that I suggest that code this immature is anywhere near ready for merging. (i.e. inclusion of halt&functions and the origs I based them off of. Refer to list archives for documentation on how to use addidir/addsdir if needed) As always, comments/criticisms/suggestions are more than welcome. peace... -dmc

1 0

[PATCH] overlay/persistence second pass - for developer reference only
by Douglas McClendon 20 Aug '07

20 Aug '07

Attached is a revision to the persistence implementation that I posted a couple weeks ago. This is mainly for Jeremy, Tim, and anyone else who is interested in working on this, or something similar. I.e. at the very least, it is worth a read to look at the issues I've dealt with, and the several that are in comments as TODO. It may well be that a simpler persistence implementation that involves just extracting tarballs from usbsticks into the normal ram overlay, may be useful instead of (or even in addition to) this kind of implementation. (or perhaps some implementation of unionfs will make it into fedora eventually?) The main points of note, since the first post are- - all sorts of bugs fixed - I moved the overlay storage filesystem to be visible as /mnt/overlayfs always. This solves some aspects of the current problem of not easily being able to see how much writable space you really have available on the rootfs. (the real answer is a combination of the device mapper overlay file AND the filesystem it resides on). - I've included modified /etc/rc.d/init.d/halt and functions, to handle getting things cleanly shutdown (which is VERY important) - ntfs is somewhat present, but not really working. I have tested with vfat and ext3. Note that ext3 is a PITA when not cleanly unmounted- see TODOs. - rudimentary testing of the choice selection when multiple possible overlay images are detected suggests it works. - the patch format merely reflects my educational process with git, and not that I suggest that code this immature is anywhere near ready for merging. (i.e. inclusion of halt&functions and the origs I based them off of. Refer to list archives for documentation on how to use addidir/addsdir if needed) As always, comments/criticisms/suggestions are more than welcome. peace... -dmc

1 0

How to install one package from a specific repo?
by Lars Bjørndal 17 Aug '07

17 Aug '07

Hello! I need to install clamav from the development repository. I tried to do "yum --enablerepo=development -y install clamav" in the %post section of the .ks file, but it didn't work. BTW: I tried to set keepcache=1 in the yum.conf file on the build system, but the packages are lost after the livecd is built. So next time, they need to be refetched... Is it possible to keep them for future use? Lars

2 3

[PATCH] print out what urls are being downloaded, more verbose yum
by Colin Walters 14 Aug '07

14 Aug '07

This patch was useful for debugging the first one.

4 7

RE: [Fedora-livecd-list] SRPMS for installed RPMs?
by Jeroen van Meeuwen 14 Aug '07

14 Aug '07

Hey, this is done already. Downloading packages includes downloading the corresponding SRPMs, even for Live Media. /me, from his cell -----Oorspronkelijk bericht ----- Van: "Jonathan Steffan" <jonathansteffan(a)gmail.com> Aan: fedora-livecd-list(a)redhat.com Verzonden: 07-08-13 22:25 Onderwerp: Re: [Fedora-livecd-list] SRPMS for installed RPMs? On Mon, 2007-08-13 at 22:11 -0500, Matt Domsch wrote: > I want to be sure, for license compliance, that all the binary bits on > the final LiveCD have corresponding source code available. > > One of the "features" I'd like to see something in the stack of > livecd-tools produce is a CD/DVD/whatever of the SRPMS that match the > RPMs that go into the LiveCD. Smooge and I have both done this > ourselves, with varying degrees of ease, essentially querying all the > installed RPMs on the LiveCD after-the-fact and generating the list, > then grabbing the files etc. All very manual. I expect there's a > better way, and I'm even open to helping code it, but am looking for > direction from you - those who know the tools best... We can just use the same concept that pungi uses. The revisor team is actually working on this and when we have progress we'll let the list know. If anyone wants to just get it done, please do. def getSRPMList(self): """Cycle through the list of package objects and find the sourcerpm for them. Requires yum still configured and a list of package objects""" for po in self.polist: srpm = po.sourcerpm.split('.src.rpm')[0] if not srpm in self.srpmlist: self.srpmlist.append(srpm) Start reading at line 327 of /usr/lib/python2.5/site-packages/pypungi/gather.py: def downloadSRPMs(self): """Cycle through the list of srpms and find the package objects for them, Then download them.""" [...] Jonathan Steffan -- Fedora-livecd-list mailing list Fedora-livecd-list(a)redhat.com https://www.redhat.com/mailman/listinfo/fedora-livecd-list

1 1

Can't boot LiveCD Boot on MS Virtual Server 2005 R2
by Jon Steer 13 Aug '07

13 Aug '07

My LiveCD boot is hanging when booting from MS Virtual Server 2005 R2. F6 based LiveCD's worked fine. It hangs at Uncompressing Linux.. Ok, booting the kernel. Since the box is running on a Dell Dual Core box, I tried all the maxcpu suggestions but no joy. Any ideas? Any ideas on what I can enable to get some tracing? thanks, jon -- "Whereever you go, there you are"

2 1

RFC- mayflower flexibility enhancements
by Douglas McClendon 13 Aug '07

13 Aug '07

I have a few changes I'd like to request to mayflower. I'd like to get some feedback before actually laying down the effort of producing patches. #1 - mayflower.conf - add PROGRAMS and FILES I'd like it if mayflower, in addition to supporting MODULES+= lines, would also support PROGRAMS+= and FILES+= PROGRAMS+= would be used for example, in my prior persistence patch, to add things like ntfsmount. FILES+= would differ from PROGRAMS, in that the auto shared library dependency check would not apply to them. Maybe that doesn't matter, and you could just have FILES. #2 - support user specified mayflower.conf location (i.e. not just /etc/mayflower.conf) #3 - optional program, sort of like existing shell cmdline arg Have a cmdline argument of program= and eprogram= which would cause the specified program to be executed. program= would happen right after the current shell, and eprogram would happen right after the current eshell. You would of course supply your own custom program via #1 above. Now, you are no doubt asking, what would this be used for... Answers: 1) support SELinux enabled livecd creation from an SELinux disabled build system. 2) support building of anaconda rpm as a non root user 3) support livecd-creator as a non root user Now you are no doubt asking, how do #1 #2 & #3 get you 1) 2) and 3)? The answer is by implementing the qmkfs program I alluded to a long time ago on fedora-devel, and it's more general incarnation, qrr (qemu root run) The idea is this- qrr is a script. qrr reads it's input, a config file, describing a program and some data. qrr then invokes mayflower (as a user, not root, with #2) to generate an initramfs, that is basically the same as the livecd initramfs, but with extra programs, specified by the config file, and added with #1. Then, qemu is invoked with #3, somewhat like this- mkdir ./my_input_output_dir cp -av <user supplied input data> ./my_input_output_dir qemu-img create scratch.img 10G qemu -kernel /boot/vmlinuz-$(uname -r) \ -initrd ./my_mayflower_generated_initrd.img \ -append "program=/my_custom_qrr_program" \ -hda ./scratch.img \ -hdb fat:rw:./my_input_output_dir Thus, the mayflower initramfs boots, runs the user supplied my_custom_qrr_program, which mounts the my_input_output_dir, and proceeds to process it with root privs (i.e. it can do loopback mounts, selinux relabeling, etc...), and then leaves its output (e.g. a filesystem image) in my_input_output_dir. I think that the changes involved with #1 #2 and #3 are fairly minor, elegant, and safe. Actually implementing 1) and 2) are a bit tricky. 3) is probably a lot tricky, but arguably worth the effort. Mainly I want this feature (qrr) for my own currently private project, though I would definitely go ahead and implement 1) as part of the patchset to be submitted for merging, which I think is justification enough for #1 #2 and #3. In general, the ability to use mayflower to construct arbitrarily useful custom purpose initramfs-s, seems quite useful. I imagine that when people really start to think about this, and what it allows, they will come up with many uses that I would probably never imagine. Personally I am hoping for a koji/pungi/livecd-creator/revisor that does not require root privileges at all. It seems to me like there should be no reason why a non-root user cannot take the fedora cvs/git trees, and output (customized) F9 media sets. I realize this may sound like a lot of stuff, but please focus on how small and safe the patches to support #1 #2 and #3 really are. Also, I have basically done this somewhat manually. (tweaked mayflower, generated initramfs as user, booted qemu to get arbitrary program to run) questions/comments/criticisms? -dmc

4 14

RFC- improving livecd installer efficiency
by Douglas McClendon 13 Aug '07

13 Aug '07

Question: Does the current livecd installer inefficiently write lots of 0's to the destination drive that it doesn't need to? I think it might. The os.img on the F7 livecd is a 4G sparse file with about 2.3G of data. Anaconda's livecdcopy backend uses python's os.read/write. I would guess that that means that 4G of data is getting written, when theoretically only 2.3G needs to. The solution that comes to mind is this- in livecd-tools, create the os.img as a 7G (or 700G??) sparse file. Basically just way big. Then take care to make the ext3fs be the exact correct size for the data (i.e. 2.3G). Then, in the initramfs, just after mounting it (after snapshotting it), do a resize2fs to 7G (or 700G). Then when anaconda does the copy, only copy the first 2.3G of the sparse file. It is however late in the 'day' for me, so maybe someone can chime in with confirmation or refutation of my logic here. -dmc

4 15

error: Couldn't fork %post: Cannot allocate memory
by Lars Bjørndal 13 Aug '07

13 Aug '07

Hello! A lot of that message appeared after trying to make a livecd with the latest GIT version of livecd-creator. What could I do to get rid of them? Lars

2 2

Commits to the list?
by Jeremy Katz 09 Aug '07

09 Aug '07

Okay, I've finally gotten the git commit mail script to work with the weird git setup on git.fedoraproject.org. Any objections to send the commit mails to the list? Jeremy

5 7

[PATCH 3/6] Setting the yumcache
by Jeroen van Meeuwen 08 Aug '07

08 Aug '07

A patch to change the location of the yum cache directory. This enables existing yum cache to be used, which in our case is especially useful because that cache is populated already. Most importantly, livecd-creator doesn't bind mount the yum cache directory. Kind regards, Jeroen van Meeuwen -kanarip

3 7

[PATCH 1/6] Set the build directory
by Jeroen van Meeuwen 08 Aug '07

08 Aug '07

A patch to enable setting the build directory. This adds more flexibility for those who don't have as much space in /var/tmp. Kind regards, Jeroen van Meeuwen -kanarip

3 10

[patch] Configuring Network after Configuring System
by Jeroen van Meeuwen 08 Aug '07

08 Aug '07

Hi All, livecd-creator's InstallationTarget.install() seems to run self.configureSystem(), then run self.configureNetwork(), possible overriding some configuration files generated with %post. Attached is a patch to prevent this from happening. Thanks to Mads Kiilerich <killerix a gmail.com> for pointing this out in https://hosted.fedoraproject.org/projects/revisor/ticket/257 Kind regards, Jeroen van Meeuwen -kanarip

3 10

[PATCH] pick a better fs label by default
by Colin Walters 08 Aug '07

08 Aug '07

This makes it so things aren't all named livecd-.

4 5

[PATCH] default to using a global livecd yum cache, not a private one
by Colin Walters 07 Aug '07

07 Aug '07

Hi, This patch moves the yum cache into /var/cache/livecd so that out of the box, the tool doesn't repeatedly download stuff from the internet.

3 3

[PATCH 6/6] Several Kernels
by Jeroen van Meeuwen 07 Aug '07

07 Aug '07

A patch which allows multiple kernels to be installed on the live media, giving boot options in the syslinux menu for all of them. In addition, this patch adds an optional timeout parameter for the boot menu. It also adds a cli parameter for appending boot options. Kind regards, Jeroen van Meeuwen -kanarip

4 13

[PATCH 5/6] Optionally prevent killing application
by Jeroen van Meeuwen 07 Aug '07

07 Aug '07

A patch to prevent livecd-creator from also killing the application that is build on top of livecd-tools, while not changing the default behaviour. Kind regards, Jeroen van Meeuwen -kanarip

2 4

[PATCH 2/6] Setting the install_root
by Jeroen van Meeuwen 06 Aug '07

06 Aug '07

A patch to enable changing the install_root from default. This enables other applications using livecd-creator as a backend application, while already having initialized a yum object configured with a certain installroot (which once the yum object is initialized, cannot be changed). Matching the build environment to what livecd-creator expects results in trouble with other builds running (eg., symlinking the actual yum installroot to "%s/install_root" % self.build_dir). We have not found loop-mounting the ext3 filesystem to be a problem. Kind regards, Jeroen van Meeuwen -kanarip

3 5

[PATCH 4/6] Translation
by Jeroen van Meeuwen 06 Aug '07

06 Aug '07

A patch which is enabling translation in the python code, but is not including that what builds livecd-tools or it's RPMs. If you have a clue about what else I would need to patch to fully enable translation, please let me know because I don't have the slightest idea at this moment. Kind regards, Jeroen van Meeuwen -kanarip

2 3

Re: LiveCD wiping root partition?
by Douglas McClendon 06 Aug '07

06 Aug '07

Michel Salim wrote: > On 01/08/07, Douglas McClendon <dmc.fedora(a)filteredperception.org> wrote: >> Rahul Sundaram wrote: >>> Michel Salim wrote: >>> >>>> Anyway, hard lesson learned. I wonder how Ubuntu does their live CD >>>> install. openSUSE is introducing one too, hopefully for their users >>>> the same bug does not occur. >>> Pretty much every live cd does a dd afaik. >> ubuntu 7.04 keeps their rootfs natively on squashfs (versus fedora which >> keeps >> it natively on an ext3 image which lives on a squashfs). >> >> Therefore they can't be doing a dd for the install. > > > Any reason why dd is preferred over, say, tar? The latter would be much > safer. And files would not have to be moved to their final partitions after > 'dd' too. seeking (cdrom and disk). Lots slower (5X?). I suspect that file level copy (tar) will be the long term answer for the flexible general case. Though I also suspect the much faster dd will be part of the long term answer as well for the typical case (i.e. formatting / as ext3, and no separate /usr). For example, on my system, using the existing 4.0G dd, the copy takes 299s. Using my turboLiveInst patch, I can shave that down to 250s. Using tar however to copy the 85896 files, took 1247s. And you also need to throw in another 30s or so for the format that isn't required in the dd case. Maybe(??) there is some more efficient way to copy those 85K files than the ( tar cpsf - | tar xpsf - ) that I used for that trial. Lastly safety has nothing to do with the tar vs dd issue. The safety issue had to do with the bug of the user interface not accurately reflecting what was happening. fyi, I did go ahead and file the bug, and even submit a patch which might fix it. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=250301 That doesn't mean of course that you don't have every right and justification to be cursing the bits of the F7 livecd while watching it spark in a microwave. -dmc

2 1

RFE- kickstart and package selection support for livecd installs
by Douglas McClendon 06 Aug '07

06 Aug '07

After having fully grokked the livecd-creator code, it occurs to me that it may not be such a completely crazy idea to bring full package selection and even kickstart support to the livecd installer. The main constraint of course is having access to the 'core' or full repo, either via network or existing disk filesystem. The key aspect of feasibility I see, is how similar the task would be to the existing livecd-creator base-on-iso code path. I.e. that code path already takes as input, a livecd type installation, and then effectively applies a kickstart configuration to it. If similar code were in anaconda, it could act on the on-disk installed system after the normal liveinst/anaconda-livecd-backend installation. Just a thought... Probably more for F9 timeframe... -dmc

1 0

LiveUSB to LiveUSB with F7?
by C S 06 Aug '07

06 Aug '07

All references I can find for spinning have a running host(with rpm, yum, etc) as a requirement to build live's upon. But is it possible to have livecd-creator spin a new CD off of F7's Live itself? I assume Revisor would only build upon this. Being a newbie I didn't know if it's in the design, plan or not possible at all... cs ____________________________________________________________________________________ Be a better Heartthrob. Get better relationship answers from someone who knows. Yahoo! Answers - Check it out. http://answers.yahoo.com/dir/?link=list&sid=396545433

4 7

[PATCH] Run post after having configured the network
by Jeroen van Meeuwen 05 Aug '07

05 Aug '07

As proposed earlier, a patch to run %post only after configureNetwork() has run because %post network configuration may override configureNetwork() configuration, but vice-versa just seems wrong as you cannot do everything with kickstart network configuration directives. Thanks to Mads Kiilerich for pointing this out. Kind regards, Jeroen van Meeuwen -kanarip

1 1

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

livecd August 2007