Hi,

thanks, that's fine :)

But on my Fedora 14 system I am unable to install the mic package.
I installed the meego-tools.repo-file and tried yum update and yum
install mic2, but I get some dependencies errors:

Resolving Dependencies
--> Running transaction check
---> Package mic2.noarch 0:0.24.5-2.1 set to be installed
--> Processing Dependency: python-zypp >= 0.5.7 for package:
mic2-0.24.5-2.1.noarch
--> Running transaction check
---> Package python-zypp.i386 0:0.5.8-1.3 set to be installed
--> Processing Dependency: libzypp.so.807 for package:
python-zypp-0.5.8-1.3.i386
--> Finished Dependency Resolution
Error: Package: python-zypp-0.5.8-1.3.i386 (meego-tools)
           Requires: libzypp.so.807

Any idea how to fix this?
My system is Fedora 14 with all updates.

Best regards,
Klaus




On Mon, 21 Mar 2011 15:30:36 +0800, Yi Yang <[email protected]>
wrote:
> Hi, all
> 
> mic2 0.24.5 is available in http://repo.meego.com/MeeGo/tools/repos/, this
> release used a new package manager 'zypp' but yum is still available for
> transition. The last mic2 version you saw in tools repo is 0.22.13, but
> we have had many transitional versions, 0.23.0, 0.24.0, 0.24.1, 0.24.2
> , 0.24.3, 0.24.4, 0.24.5 for supporting zypp, from 0.23.0, we had basic
> zypp support, so if you're using 0.23.0 and later versions, you must
> have a file /etc/sysconfig/proxy on your system if you need to use proxy
> to access internet, the sample file for it is at the end, just for reference,
> you need to replace proxy link with your real proxy. Moreover, proxy
> environment variables are still necessary for mic2, the reason is zypp
> used /etc/sysconfig/proxy to get proxy info, but other components in mic2
> are still use urlgrabber to get packages and repo metadata.
> 
> Here are detailed steps to make it work normally for you:
> 
> #1. Touch/Change /etc/sysconfig/proxy on your system
> 
> If you don't need proxy to access internet, you can ignore this step.
> 
> #2. Remove the old bootstrap
> 
> mic2 provided a command mic-rm-chroot-dir, it can help you remove
> your bootstap
> very safely.
> 
>     $ sudo mic-rm-chroot-dir <your-bootstrap-dir>
> 
> The default bootstrap dir is /var/cache/meego-bootstrap
> 
> #3. Ensure you have configured proxy in /etc/mic2/mic2.conf or environment
> variables.
> 
> Generally, you can get proxy environment variables in terminal if you have
> configured system proxy in your system UI, but you also need to add 
> 
>    Defaults env_keep += " no_proxy http_proxy https_proxy"
> 
> to /etc/sudoers in order that proxy environment variables can be delivered to
> sudo command.
> 
> Or you can set proxy in /etc/mic2/mic2.conf, in section [main], add
> the below two
> lines:
> 
> proxy=http://proxy.yourcompany.com:8888/
> no_proxy=localhost,127.0.0.0/8,.yourcompany.com
> 
> you need to change proxy.yourcompany.com:8888 and .yourcompany.com
> according to
> your network.
> 
> #4. Set use_comps to 0 in /etc/mic2/mic2.conf
> 
> This mic2 will use patterns by default, but in the old mic2.conf, it
> was set to
> 1, that means it will use comps by default, so you need to edit your
> /etc/mic2/mic2.conf manually and ensure use_comps is 0.
> 
> This official public release used zypp as a new package manager for the first
> time, so if you find any issue, please file a bug on MeeGo bugzilla without
> hesitation, you also can fall back to the old package manager using
> --pkgmgr=yum
> option to work around zypp-specific issues.
> 
> Main features:
>     * Added zypp package manager
>     * Support package manager switch using --pkgmgr=yum or pkgmgr=zypp
>     * Support chroot raw image with btrfs
>     * Added armv7hl and armv7nhl architectures
>     * Enable active flag for partition in kickstart
>     * Added raw image chroot support
>     * Allow to read all the options from config file
>     * Read options from kickstart magic line
>     * Order bind mount points
>     * Enable bootstrap mode for ARM image
>     * Bind mount local packages path to bootstrap
>     * Clean up yum garbage info
>     * Use patterns by default
>     * Add a new vertical 'tv'
>     * Comply with ignoremissing option in kickstart
>     * Exit when run mode is set to 0 on non-fedora and non-mmego systems
>     * Cache source packages
>     * Preload the required kernel modules before entering bootstrap
> 
> Bug fixes:
>     Bug 10313 - mic-image-creator (> 0.22.2)
>     Bug 4808 - mic2 doesn't accept --includepkgs or --excludepkgs for
> multiple packages (x,y) in repo lines
>     Bug 11405 - mic-chroot(0.23.0)could not create image file
>     Bug 11866 - MIC2 0.24.0 cann't create arm image on Fedora 13
>     Bug 11867 - Get a error output "Failed to unmap partitions for
> '/dev/loop2'"
>     Bug 12125 - TypeError: 'Url' object is unsubscriptable
>     Bug 12127 - 0.22.9 blocked after create core-armv7l image on
> bootstrap mode
>     Bug 12773 - Pointer printed to architecture field while using
> zypp as package manager
>     Bug 12774 - Pointers printed while using zypp as package manager
>     Bug 11051 - genisoimage support
>     Bug 13391 - mic2 will print inacceptable error info on running
> 'mic' or 'mic --version' on openSUSE
>     Bug 7277 - Support overwrite volume id in iso file
>     Bug 10115 - --include-source option failed with -t and -o options
>     Bug 12872 - Rename zypper packagemanager to zypp
>     Bug 13659 - mic2 will not run, errors out after version output
>     Bug 13643 - during an ARM build mic spills out a lot of messages
>     Bug 13644 - Mic2 prints out error even when build is finished fine
> 
> 
> FYI
> ===
> MeeGo Compliance Tool:
> http://meego.gitorious.org/meego-developer-tools/meego-compliance-tools
> MeeGo Compliance Tool Document: http://wiki.meego.com/Quality/ComplianceTools
> 
> Released by mic2 team
> =====================
> Documentation: http://wiki.meego.com/Image_Creation
> Project home:  http://meego.gitorious.org/meego-developer-tools/image-creator
> Git tree:      git://gitorious.org/meego-developer-tools/image-creator.git
> Bugzilla:     
> http://bugs.meego.com/enter_bug.cgi?product=Development%20Tools&component=MIC%20(Image%20Creator)
> Development & Release Processes:
> http://wiki.meego.com/MIC2_Development_Release_Processes
> Maillist:      http://lists.meego.com/listinfo/meego-distribution-tools
> 
> #### /etc/sysconfig/proxy sample ####
> ## Path:      Network/Proxy
> ## Description:
> ## Type:      yesno
> ## Default:   no
> ## Config:      kde,profiles
> #
> # Enable a generation of the proxy settings to the profile.
> # This setting allows to turn the proxy on and off while
> # preserving the particular proxy setup.
> # 
> PROXY_ENABLED="yes"
> 
> ## Type:      string
> ## Default:   ""
> #
> # Some programs (e.g. lynx, arena and wget) support proxies, if set in
> # the environment.  SuSEconfig can add these environment variables to
> # /etc/SuSEconfig/* (sourced by /etc/profile etc.) -
> # See http://portal.suse.com/sdb/en/1998/01/lynx_proxy.html for more details.
> # Example: HTTP_PROXY="http://proxy.provider.de:3128/";
> HTTP_PROXY="http://proxy.yourcompany.com:8888/";
> 
> ## Type:      string
> ## Default:   ""
> #
> # Some programs (e.g. lynx, arena and wget) support proxies, if set in
> # the environment.  SuSEconfig can add these environment variables to
> # /etc/SuSEconfig/* (sourced by /etc/profile etc.) -
> # this setting is for https connections
> HTTPS_PROXY="http://proxy.yourcompany.com:8888/";
> 
> ## Type:      string
> ## Default:   ""
> #
> # Example: FTP_PROXY="http://proxy.provider.de:3128/";
> #
> FTP_PROXY="http://proxy.yourcompany.com:8888/";
> 
> ## Type:      string
> ## Default:   ""
> #
> # Example: GOPHER_PROXY="http://proxy.provider.de:3128/";
> #
> GOPHER_PROXY=""
> 
> ## Type:      string(localhost)
> ## Default:   localhost
> #
> # Example: NO_PROXY="www.me.de, do.main, localhost"
> #
> NO_PROXY="localhost, 127.0.0.1, .yourcompany.com"
> 
> #### /etc/sysconfig/proxy sample ####
> _______________________________________________
> MeeGo-dev mailing list
> [email protected]
> http://lists.meego.com/listinfo/meego-dev
> http://wiki.meego.com/Mailing_list_guidelines

_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
http://wiki.meego.com/Mailing_list_guidelines

Reply via email to