February 2008 - openSUSE Software Management

[softwaremgmt] XML output for zypper
by Jan Kupec 29 Feb '08

29 Feb '08

Hi there! zypper -x (--xmlout) is almost done. The main features (currently in svn, to be in zypper-0.10.2) include: * all output in XML: info, warning, error messages, progress/download progress, prompts, * uniquely identified user dialogs (prompts) * enumerated possible dialog answers (comming soon: prompt help) * query command results as xml data - list-updates (obsoletes the xu command) uses the established update info xml structure from zypp-check-patches/zypper xu - repos - search (TODO) - patches (TODO) - info (TODO) * other special information as xml data - install summary * common types of output (messages, progress) are written using classes derived from Out class (OutNormal, OutXML) so this type of output can easily be changed/extended, new class can be added (e.g. OutColored). Output examples attached. I have left the <update-status> subtree compatible with zypp-check-patches, but i've changed the rest of the xml written by 'zypper --terse xu' [2] (used by the updater applets) a bit as i believe it is only used by the applets so far, which we can adapt. There is an RNC scheme at [0], which will get installed to /usr/share/zypper/$somewhere/xmlout.rnc. I will also update [2] http://en.opensuse.org/Standards/Zypper_Xml after the code freeze. Also there is prompt.h header file at [1] with an enum of the prompt IDs and their description (TODO) which i plan to get installed into /usr/include/zypper/prompt.h. As for zypper commands and options: - I would like to drop the xu command in favor of 'zypper -x lu -t package -t patch'. - Also, i'd like to use the --terse option for other type of machine-readable output (like zypper repos printing the table without header and decoration). For 11.0 it should be just ignored (provided only for rug-compatibility). IMO we can afford dropping these, as they were only used by the updater applets so far (probably :O). XML input is not implemented yet, but eventually will be. So go ahead and play with it, feedback is welcome! Cheers, jano [0] http://svn.opensuse.org/svn/zypp/trunk/zypper/src/output/xmlout.rnc [1] http://svn.opensuse.org/svn/zypp/trunk/zypper/src/output/prompt.h [2] http://en.opensuse.org/Standards/Zypper_Xml

1 0

[softwaremgmt] Invalid SHA during Smart update (SuSE10.2)
by Nail El-Sourani 26 Feb '08

26 Feb '08

Hi, the following Problem occurs during a "smart update" since yesterday (well actually the last changes made to ...update/10.2 on the servers/mirrors: error: Failed acquiring information for 'Suse 10.2 UpdateMirror': error: ftp://ftp.hosteurope.de/mirror/ftp.suse.com/pub/suse/update/10.2/repodata/p…: Invalid SHA (expected f02669b9fce8a9bc9a1300cb54932459495a9d84, got f98cedc19121f46b42d5bbd8b174dd3d4fe8f29e) tried different Servers, primary.xml.gz has the same size and date modified on all of them, error happens with all of them. what can i do? is this a security issue? kind regards, *nail el-Sourani -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 2

[softwaremgmt] Obsoletes and zypp vs. rpm
by Michal Svec 18 Feb '08

18 Feb '08

Hello, I wonder what should be the correct handling of Obsoletes, apparently rpm and zypp differ on its handling which confuses users. You can see it on an example of java-1_6_0-sun-plugin.rpm, which obsoletes java-1.5.0-plugin and thus java-1_5_0-sun-plugin.rpm. So when you try to install both packages, zypper bails on conflicts (*), while rpm allows you to install without any problem (might be due to the fact the obsoleted name is not a package). That of course brings quite some confusion, so I wonder whether this is a desired behavior or if it could be improved in any way. Thanks, Michal (*) You need zypper from factory to find out, on 10.3 the message is quite horrible :) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

4 11

[softwaremgmt] Need Help: sync with repositories, such as http://www2.ati.com/suse/10.3/
by Artyom Loenko 18 Feb '08

18 Feb '08

hi, all! I placed the server with partial openSUSE repositories for the residents of Tomsk Region, Russian Federation (unlimited traffic on the area of 100 Mb speed). By major repositories problems are solved there is no set of lines like: rsync -vaz --partial --stats --no-p --compress-level=9 --exclude-from=/etc/repo/exclude --delay-updates --timeout=1800 --delete --delete-after "rsync://ftp5.gwdg.de::/pub/opensuse/update/10.3/" /srv/ftp/pub/opensuse/update/10.3/ but there is a problem with the addition of "not browseable" mirrors, such as http://www2.ati.com/suse/10.3/ Now, it is way below, but there can be any more correct method? Main did not pull the entire repository again, and check whether the files. In fact, in xml all the information is there, but his hands parser write these fields in xml not managed. #!/bin/bash TMP_DIR=/srv/mirror/tmp LOG_DIR=/srv/mirror-scripts/log REPO_CURRENT_DIR=/srv/mirror/opensuse/misc/ati/10.3 function update_ati { echo " ====================================================== ATI " REPO_DIR=$REPO_CURRENT_DIR REPO_URL='http://www2.ati.com/suse/10.3/' REPO_URL2='http:\/\/www2.ati.com\/suse\/10.3\/' REPO_URL_CUT=2 REPO_TMP=$TMP_DIR/ati mkdir -p $REPO_TMP/repodata/ cd $REPO_TMP wget -nH -x --cut-dirs=$REPO_URL_CUT $REPO_URL/repodata/repomd.xml wget -nH -x --cut-dirs=$REPO_URL_CUT $REPO_URL/repodata/repomd.xml.asc wget -nH -x --cut-dirs=$REPO_URL_CUT $REPO_URL/repodata/repomd.xml.key cat $REPO_TMP/repodata/repomd.xml |sed -e 's/ /\n/g' -e 's/</\n/g'| grep -E -o 'href=".+"' | sed -e "s/^href=\"//g" -e 's/^/'$REPO_URL2'/' -e 's/"//g' |xargs wget -nH -x --cut-dirs=$REPO_URL_CUT gzip -d -c $REPO_TMP/repodata/primary.xml.gz | sed -e 's/ /\n/g' -e 's/</\n/g'| grep -E -o 'href=".+"' | sed -e "s/^href=\"//g" -e 's/^/'$REPO_URL2'/' -e 's/"//g' |xargs wget -nH -x --cut-dirs=$REPO_URL_CUT rm -fr $REPO_DIR/* mkdir -p $REPO_DIR cp -R $REPO_TMP/* $REPO_DIR rm -fr $REPO_TMP } >$LOG_DIR/ati.log 2>&1 update_ati; how to organize the work in such repository version and management tool? -- with respect, Artyom Loenko Jabber: divenvrsk(a)jabber.ru Mail: divenvrsk(a)gmail.com Phone: +7 (906) 2583135 -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0