December 2008 - Zypp Development - openSUSE Mailing Lists

[zypp-devel] New solver call : resolveQueue
by Stefan Schubert 11 Mar '09

11 Mar '09

Hi, apart from the solver call "resolvePool" ( collect all transactions from the pool, solving this transactions and writing the result back to pool) the solver can work off a given request queue too: /** * Resolve package dependencies: * * The solver works off the given queue and writes back the solution * to pool. * * Returns "true" on success (i.e., if there were no problems that * need user interaction) and "false" if there were problems. In * the latter case, use problems() and later applySolutions() * below. **/ bool resolveQueue (solver::detail::SolverQueueItemList & queue); The queue can have elements which are described in the following classes: base class: SolverQueueItem.h SolverQueueItemDelete.h SolverQueueItemInstall.h SolverQueueItemLock.h SolverQueueItemInstallOneOf.h SolverQueueItemUpdate.h Known problems: - The update and InstallOneOf request does not work correctly. - The error messages are too abstract now for the user. (Jano, you can start implementation now :-) ) Greetings Stefan -- ******************************************************************************* 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

6 12

[zypp-devel] switching to git during christmas?
by Duncan Mac-Vicar Prett 13 Jan '09

13 Jan '09

We ZYpp developer's OK, and Michael Schröder gave ok for the sat-solver. I will be around during Christmas, and as we will branch Code11 during the next days anyway, it may be good time to do this step during Christmas as there will be no activity in the repos. Duncan -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 6

[zypp-devel] dq.count <= 1
by Matt Barringer 22 Dec '08

22 Dec '08

Hi, I am running into a problem where the satsolver is triggering an abort call in assert(dq.count > 1) in run_solver(). The comment above the call doesn't explain it: /* dq.count < 2 cannot happen as this means that * the rule is unit */ What does a dq.count <= 1 mean, and what does that comment mean? Thanks, Matt -- Matt Barringer, Software Engineer SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) http://susestudio.com http://www.novell.com/linux

2 3

Re: [zypp-devel] OSI: openSUSE Installer Presentation
by Dominique Leuenberger 20 Dec '08

20 Dec '08

>From: Duncan Mac-Vicar Prett <dmacvicar(a)suse.de> >>Dominique Leuenberger wrote: >> That would basically require building against an LSB base project. I think that's the only way this CAN be achieved. >> >Why? Don't loose the context Duncan. The message I replied to was talking about distribution indipendent. You'll not achieve this without creating a LSB compliant build. You simply can't guarantee any library being existant on any random system (which is what distribution indipendent means). Dominique -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

4 6

[zypp-devel] OSI: openSUSE Installer Presentation
by Raul Romero 19 Dec '08

19 Dec '08

Hello everyone, My name is Raúl Romero, and I'm a openSUSE Member. I have an idea that I want to share with you: Off-Line one click install (MSI for Linux) Same concept as MSI packages for Windows but exploiting the One Click Install concept of openSUSE (and therefore inheriting the simplicity, code and security). Basically a compressed file which includes a repository inside, plus one click install information, and a script to trigger the oneclickinstall handler with the data as payload in the script. Therefore is a collection of rpms that can be installed. Detailed description is here http://en.opensuse.org/OSI There is a feature open at https://features.opensuse.org/?rm=feature_show&id=305582 Thanks for your time, and best regards. -- Raúl Romero [^BgTA^] - http://www.bgta.net -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

8 16

[zypp-devel] Automatic removal of orphan depencencies
by Paolo Tuninetto 17 Dec '08

17 Dec '08

Hi all, I'm new to this mailing list and also I don know anything about zypp development. I'm also new to openSUSE, so you may think "what the xxxx are you doing here?". I try to explain... IMHO one of the most annoying missing feature in the openSUSE package management (afaik, YaST and zypper) is that once a user installs a package (i.e. in order to test it), the package management automagically checks for missing dependencies and find all libraries that are required but not yet installed and install them. This is cool, The missing feature is that when the user uninstalls the package all the installed dependencies are left there... there is no help in finding where are such orphan packages. First of all... is it true? Is there no way to "cleanup" such dependencies? Something that is doing the work "apt-get autoremove" is doing in Ubuntu Systems. If it is not currently possible... why not make it so? Looking on the net I found the following links: * https://bugzilla.novell.com/show_bug.cgi?id=425890 looks like there is a feature request related to this stuff. I wrote down some ideas on how this feature can be implemented. * http://opensuse.awardspace.com/ where John Thomas started putting down some YaST mockups with some other ideas. Is there someone working on this? May I help in some way? Where can I find documentation on how openSUSE package management works? Ciao, Paolo -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

9 17

[zypp-devel] Re: [Research] FOSDEM 2009: CFP & more information ...
by Jan Kupec 17 Dec '08

17 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Martin and all! Martin Lasarsch wrote: > * CFP > So lets start with the call for papers. We always have quite a big crowd of > SUSE/Novell staff at FOSDEM, but we want more community talks. So if you have > an idea for a presentation, please send it to the list. Yes, i said idea, not > if you want to make it. If you want to make it: perfect. If not: we might > find someone who can. In the end it's about interesting presentations the > community want to hear. I'd like to give a presentation about zypper if there's still room for it (i hope somebody would be interested :O). Here are some ideas about the contents: * a few words about history of the project, tools using zypper * features, usage examples, hints * ideas for future & how to contribute - -- cheers, jano Ján Kupec YaST team - ---------------------------------------------------------(PGP)--- Key ID: 637EE901 Fingerprint: 93B9 C79B 2D20 51C3 800B E09B 8048 46A6 637E E901 - ---------------------------------------------------------(IRC)--- Server: irc.freenode.net Nick: jniq Channels: #zypp #yast #suse #susecz - ---------------------------------------------------------(EOF)--- -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAklI7KcACgkQgEhGpmN+6QE1YQCeMydZHXsE2RZuSL+2yJi3F6e7 2+QAn105DVCuah75YAkQ1G5y8t9vsDnB =BJQ9 -----END PGP SIGNATURE----- -- 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] New method: zypp::Exception::asUserHistory()
by Michael Andres 12 Dec '08

12 Dec '08

JFYI: zypp rev 11292 /** A single (multiline) string composed of \ref asUserString * and \ref historyAsString. */ std::string Exception::asUserHistory() const; You can use this whenever you have to convert an exception into a (multiline) string includiong the history. E.g. as error string reported in callbacks. -- 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] [bnc 450001] Disable signed repos if the user does not trust the key?
by Michael Andres 04 Dec '08

04 Dec '08

Hi. Disable signed repos if the user does not trust the key? It's IMO a valid request as the user actively prevents the repo from being used. Or shall we continue to nag the user about trusting the key on every refresh? The question is whether this default should be implemented in libzypp, or if it is something the application should explicitly ask for: Trust key? [ ] Once [ ] Always (import) [X] No [X] not now (ask again on next refresh) [ ] maybe later (disable the repository) [ ] never (delete the repository) Or shall we introduce some zconf option RepoWithUntrustedKey = [nag|disable|delete] -- 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

5 8

[zypp-devel] compilation of libsatsolver
by Jan-Simon Möller 03 Dec '08

03 Dec '08

Hi ! I see this error now: [ 94%] Building C object bindings/python/CMakeFiles/satsolver_python.dir/satsolver_python.o cd /usr/src/packages/BUILD/sat-solver/bindings/python && /usr/bin/gcc -D_FILE_OFFSET_BITS=64 -Dsatsolver_python_EXPORTS -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -O2 -g -Werror -Wall -fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -O2 -g -Werror -Wall -g -O3 -fPIC -I/usr/src/packages/BUILD/sat-solver -I/usr/src/packages/BUILD/sat-solver/src -I/usr/include/python2.5 -I/usr/src/packages/BUILD/sat-solver/applayer -I/usr/src/packages/BUILD/sat-solver/tools -DVERSION=\"0.13.0\" -o CMakeFiles/satsolver_python.dir/satsolver_python.o -c /usr/src/packages/BUILD/sat-solver/bindings/python/satsolver_python.c cc1: warnings being treated as errors /usr/src/packages/BUILD/sat-solver/bindings/python/satsolver_python.c: In function 'dataiterator_value': /usr/src/packages/BUILD/sat-solver/bindings/python/satsolver_python.c:2692: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/packages/BUILD/sat-solver/bindings/python/satsolver_python.c: In function 'XSolvable_attr_exists': /usr/src/packages/BUILD/sat-solver/bindings/python/satsolver_python.c:3448: warning: dereferencing type-punned pointer will break strict-aliasing rules /usr/src/packages/BUILD/sat-solver/bindings/python/satsolver_python.c:3473: warning: dereferencing type-punned pointer will break strict-aliasing rules make[2]: *** [bindings/python/CMakeFiles/satsolver_python.dir/satsolver_python.o] Error 1 make[2]: Leaving directory `/usr/src/packages/BUILD/sat-solver' make[1]: *** [bindings/python/CMakeFiles/satsolver_python.dir/all] Error 2 make[1]: Leaving directory `/usr/src/packages/BUILD/sat-solver' make: *** [all] Error 2 error: Bad exit status from /var/tmp/rpm-tmp.73929 (%build) Best regards, Jan-Simon -- To unsubscribe, e-mail: zypp-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: zypp-devel+help(a)opensuse.org

2 3