June 2007 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] REFACTORING-10_3: Revision 5818: everything compiles....DOES NOT COMPILE!
by Michael Andres 21 Jun '07

21 Jun '07

Please update to gcc-4.2. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] Re: [zypp-commit] r5810 - /branches/REFACTORING-10_3/
by Duncan Mac-Vicar 21 Jun '07

21 Jun '07

On Wednesday 20 June 2007 13:54, mlandres(a)svn.opensuse.org wrote: > Author: mlandres > Date: Wed Jun 20 13:54:56 2007 > New Revision: 5810 > > URL: http://svn.opensuse.org/viewcvs/zypp?rev=5810&view=rev > Log: > Temporary branch to switch to the new zypp API. > > Added: > branches/REFACTORING-10_3/ > - copied from r5809, trunk/ However trunk has already some new changes. Arvin fixed some typos. mvidner has a commit too. That was my point when I said, lets freeze trunk on a tag/branch, and people continue working on trunk. What is the policy for the testsuite? Do we need to branch it? -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 3

[zypp-devel] Please watch gcc warnings..
by Michael Andres 21 Jun '07

21 Jun '07

No, it is not sufficient, that the code compiles. One benefit of cmake are easy to spot gcc warnings. So don't slack off and fix them, if you see them. warning: return type defaults to 'int' warning: no return statement in function returning non-void warning: control reaches end of non-void function warning: dereferencing type-punned pointer will break strict-aliasing rules gcc42 in stable --------------- I just installed the packages from /dist/install/stable-x86/ on my 10.2 without problems. Except for the fact, that zypp does not compile. Going to fix it. As there is some code that passes gcc41 but is rejected by gcc42, all developers should migrate ASAP. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 3

[zypp-devel] repo modification use cases
by Jan Kupec 21 Jun '07

21 Jun '07

- rename repository (alias, i.e. identifier) (if it is the only repo in the .repo file, rename also the repo file) - disable/enable the repo - disable/enable autorefresh for the repo - set long name (description) - disable/enable gpg check, specify signature location - add/remove a baseUrl - add/remove a mirror URL - ...anything else? - since we support more repositories defined within a single .repo file this will need to be considered if we decide to implement the modifications by removing old repo file and replacing it with a new (modified) one. I think an additional API would be handy for this task (covering all of the above) at last. Something like: RepoManager::modifyRepository(const std::string & repo_alias, const RepoInfo & new); Client just creates it's own modified RepoInfo object and leaves all what's needed on zypp. Of course we need to provide methods for modifying the RepoInfo that we currently don't provide (if any). Also RepoManager::getRepoInfo(const std::string & repo_alias) would be nice so that clients don't need to extract the RepoInfo file from knownRepositories() themselves, if they want to create modified RepoInfo out of the original one. This would be a very simple convenience method. So the client code could look like: RepoManager manager; RepoInfo repo = manager.getRepoInfo(alias); repo.setAlias(new_alias); repo.setEnabled(false); repo.removeMirror(url); // whatever manager.modifyRepository(alias, repo); Cheers, Jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 2

[zypp-devel] Some numbers of the ported zypper
by Duncan Mac-Vicar Prett 20 Jun '07

20 Jun '07

dmacvicar@piscola:/space/build/zypp/trunk/zypper> time sudo src/zypper sl # | Enabled | Refresh | Type | Name | URI --+---------+---------+--------+----------------+------------------------------------------------------------------------ 1 | No | No | rpm-md | filesharing | http://software.opensuse.org/download/filesharing/SUSE_Factory/ 1 | Yes | No | rpm-md | home:dmacvicar | http://software.opensuse.org/download/home:/dmacvicar/openSUSE_Factory/ 1 | Yes | No | rpm-md | ruby | http://software.opensuse.org/download/ruby/openSUSE_Factory/ real 0m0.034s user 0m0.028s sys 0m0.008s dmacvicar@piscola:/space/build/zypp/trunk/zypper> time sudo src/zypper -v --non-interactive install kopete-floor Verbosity 1 Entering non-interactive mode. Initializing Target loading repo resolvables... DONE \ RPM database[100%] Establishing status of aggregates Resolving dependencies... Summary: <install> [S0:0][package]kopete-floor-0.1.0-17.2.i586 Continue? [y/n] y committing Downloading: [S0:0][package]kopete-floor-0.1.0-17.2.i586, -1 B(-1 B unpacked) Downloading: http://software.opensuse.org/download/home:/dmacvicar/openSUSE_Factory/i586… - Downloading[100%] Installing: [S0:0][package]kopete-floor-0.1.0-17.2.i586 | Installing [100%] CommitResult 1 (errors 0, remaining 0, srcremaining 0) real 0m8.925s user 0m7.880s sys 0m0.688s Note: from the 8 seconds, mostly is reading the rpm database. -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

6 9

[zypp-devel] ZYPP: TRUNK->BETA REFACTORING-BACKUP-10_3->STABLE
by Michael Andres 20 Jun '07

20 Jun '07

svn copy -r 5789 http://svn.opensuse.org/svn/zypp/trunk/ http://svn.opensuse.org/svn/zypp/branches/REFACTORING-BACKUP-10_3 REFACTORING-BACKUP-10_3 is a snapshot of the latest libzypp revision we comitted to STABLE. TRUNK is now submitted to BETA only, until all the outdated Source* stuff is removed, an all applications switched to the new Repo* classes. How to handle it in YaST? -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 3

[zypp-devel] Solvererror more verbose
by Stefan Schubert 20 Jun '07

20 Jun '07

Hi, I have enlarged the error messages in order to give the user more feedback _why_ there is an error. This information will be added to "Details". The solver shows information about each item which is involved in an error. (Who has selected, who requires, recommends,.... it) In the last few month we have gotten error messages like: "The solver reports a missing requirement foo. But the package foo_package is available which provides foo. Why the solver does not take this package ?" The answer is that foo_package cannot be taken cause it has own dependency problems. This information will be shown to the user now. In order to give an overview there is an example ( lines without ">!>" shows the new details description): >!> Installing product:openSUSE-factory.i686 from channel 1 >!> Installing pattern:kde.i586 from channel 1 >!> Installing pattern:x11.i586 from channel 1 >!> Installing pattern:base.i586 from channel 1 >!> Installing grub.i586 from channel 1 >!> Installing kernel-default.i586 from channel 1 >!> Installing sendmail from channel 1 >!> Installing postfix from channel 1 >!> 8 problems found: >!> Problem: >!> Cannot install sendmail-8.14.1-23.i586[1] because it is conflicting with postfix >!> A conflict over sendmail == 8.14.1-23 (sendmail) requires the removal of to-be-installed sendmail-8.14.1-23.i586[1] sendmail-8.14.1-23.i586[1] ========================== sendmail-8.14.1-23.i586[1] will be installed by the user. sendmail-8.14.1-23.i586[1] conflicts with postfix postfix-2.4.0-14.i586[1] ======================== postfix-2.4.0-14.i586[1] will be installed by the user. postfix-2.4.0-14.i586[1] is needed by (libpostfix-global.so.1) postfix-2.4.0-14.i586[1] conflicts with sendmail >!> Solution: >!> do not install sendmail >!> do not install sendmail-8.14.1-23.i586[1] >!> Solution: >!> do not install postfix >!> do not install postfix-2.4.0-14.i586[1] >!> Solution: >!> Ignore this conflict of sendmail >!> >!> Problem: >!> Cannot install sendmail-8.14.1-23.i586[1] due to dependency problems >!> sendmail-8.14.1-23.i586[1] is scheduled to be installed, but this is not possible because of dependency problems. sendmail-8.14.1-23.i586[1] ========================== sendmail-8.14.1-23.i586[1] will be installed by the user. sendmail-8.14.1-23.i586[1] conflicts with postfix >!> Solution: >!> do not install sendmail >!> do not install sendmail-8.14.1-23.i586[1] >!> Problem: >!> No valid solution found with only resolvables of best architecture. >!> With this run only resolvables with the best architecture has been regarded. Regarding all possible resolvables takes time but can come to a valid result. >!> Solution: >!> Make a solver run with ALL possibilities. >!> Regarding all resolvables with compatible architecture. >!> Problem: >!> OpenOffice_org-2.2-11.i586[1] cannot be installed due to missing dependencies >!> There are no installable providers of libsndfile.so.1 for OpenOffice_org-2.2-11.i586[1] OpenOffice_org-2.2-11.i586[1] ============================= OpenOffice_org-2.2-11.i586[1] is needed by pattern:kde_office-10.3-61.i586[1] (OpenOffice_org) libsndfile-1.0.17-56.i586[1] provides libsndfile.so.1, but it is uninstallable. Try installing it on its own for more details. >!> Solution: >!> do not install OpenOffice_org >!> do not install OpenOffice_org-2.2-11.i586[1] >!> Solution: >!> Ignore this requirement just here >!> >!> Problem: >!> amarok-1.4.5-57.i586[1] cannot be installed due to missing dependencies >!> There are no installable providers of libtunepimp.so.5 for amarok-1.4.5-57.i586[1] amarok-1.4.5-57.i586[1] ======================= amarok-1.4.5-57.i586[1] is needed by pattern:kde_multimedia-10.3-61.i586[1] (amarok) libtunepimp-0.5.2-50.i586[1] provides libtunepimp.so.5, but it is uninstallable. Try installing it on its own for more details. >!> Solution: >!> do not install amarok >!> do not install amarok-1.4.5-57.i586[1] >!> Solution: >!> Ignore this requirement just here >!> >!> Problem: >!> kaffeine-lang-0.8.4-36.i586[1] cannot be installed due to missing dependencies >!> There are no installable providers of kaffeine == 0.8.4 for kaffeine-lang-0.8.4-36.i586[1] kaffeine-lang-0.8.4-36.i586[1] ============================== kaffeine-lang-0.8.4-36.i586[1] is needed by kaffeine-0.8.4-36.i586[1] (kaffeine-lang == 0.8.4) kaffeine-0.8.4-36.i586[1] provides kaffeine == 0.8.4-36, but it is uninstallable. Try installing it on its own for more details. >!> Solution: >!> do not install kaffeine-lang >!> do not install kaffeine-lang-0.8.4-36.i586[1] >!> Solution: >!> Ignore this requirement just here >!> >!> Problem: >!> kdemultimedia3-3.5.7-16.i586[1] cannot be installed due to missing dependencies >!> There are no installable providers of libakode.so.2 for kdemultimedia3-3.5.7-16.i586[1] kdemultimedia3-3.5.7-16.i586[1] =============================== kdemultimedia3-3.5.7-16.i586[1] is needed by pattern:kde_multimedia-10.3-61.i586[1] (kdemultimedia3) libakode-2.0.2-26.i586[1] provides libakode.so.2, but it is uninstallable. Try installing it on its own for more details. >!> Solution: >!> do not install kdemultimedia3 >!> do not install kdemultimedia3-3.5.7-16.i586[1] >!> Solution: >!> Ignore this requirement just here >!> >!> Problem: >!> pattern:enhanced_base-10.3-61.i586[1] cannot be installed due to missing dependencies >!> There are no installable providers of smtp_daemon for pattern:enhanced_base-10.3-61.i586[1] pattern:enhanced_base-10.3-61.i586[1] ===================================== pattern:enhanced_base-10.3-61.i586[1] is needed by pattern:x11-10.3-61.i586[1] (enhanced_base) exim-4.67-20.i586[1] provides smtp_daemon, but it is uninstallable. Try installing it on its own for more details. >!> Solution: >!> do not install enhanced_base >!> do not install pattern:enhanced_base-10.3-61.i586[1] >!> Solution: >!> Ignore this requirement just here >!> -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] [NOTE] -DZYPP_REFACTORING
by Duncan Mac-Vicar Prett 19 Jun '07

19 Jun '07

If you want the download of packages and commit to work, run cmake with that define, because in order to use the new code in commit without break it, we have to ifdef -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] status repository handling
by Duncan Mac-Vicar Prett 19 Jun '07

19 Jun '07

Adding of repositories using data, remote .repo files, removing them is implemented, and the test case is there. Including all the "strange stuff": - you add a repo file from a url, but a file with the same name exists. - you add a repo from a description but a file with the same name of the alias exists - you remove a repo from a file, and in this file there are more repos - etc Editing is not yet there. -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

1 0

[zypp-devel] Branches again, this time SLE 10 SP2
by Jan Kupec 19 Jun '07

19 Jun '07

Hi there! There are some bugs in zypper that can't be fixed the same way in 10.3 and SLE 10 SP2. I intend to create SLE 10 SP2 branch for zypper (SLE-10-SP2-Branch) for them (out of SuSE-Linux-10_2-Branch, which we used for SP1 - this will become maintenance branch). I'm posting this so that we discuss and agree on one approach for libzypp, zypper, and others. YaST is branch that way as well. Will this be OK? Cheers, Jano -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 1