- openSUSE Software Management

[softwaremgmt] suseinfo.xml, is it used?
by Cristian Morales Vega 01 Mar '10

01 Mar '10

Is http://en.opensuse.org/Standards/RPM_metadata#SUSE_repository_info_.28susei… really used? Neither the 11.2 OSS repo nor the OBS repos provide it. So, not sure if the package management tools take it into account. I think it would be really useful that the OBS repos provide that "distro" tag. That would avoid yet another post in the forums from an user that confused http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openS… with http://download.opensuse.org/repositories/KDE:/KDE4:/Factory:/Desktop/openS…. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

3 2

[softwaremgmt] enhancerepo 0.4.1 released
by Duncan Mac-Vicar Prett 26 Feb '10

26 Feb '10

You can find the packages in my [home project][3]. # Changes * Gemified. It is now available as a ruby gem. The rpm package is now therefore rubygem-enhancerepo * Changed command line option parsing: for multiple items in an option, don't use commas anymore: --generate-update pkg1,pkg2 becomes --generate-update pkg1 pkg2 * Support for product metadata generation from release packages. Enhancerepo will scan *-release rpm packages and insert product.xml information in the metadata. * Bugfixes for delta and updates generation * Improved output # Thanks This release was possible thanks to contributions and testing from Michael Calmer and Jordi Massaguer Pla # Next release A 0.4.2 release will follow shortly, because 0.4.1 was queued from some time already. At least 2 features are planned for 0.4.2/0.4.3 * Merge splitting of any metadata patch from Jordi Massaguer Pla * Merge pattern conversion patch from Michael Calmer # About Enhancerepo [Enhancerepo][1] is a tool to edit and index rpm-md (a.k.a yum) software repositories. It is developed in [gitorious][2]. ## Main features: * Reindex metadata * Generate delta rpms from different package versions, and the corresponding metadata * Generate updates (patches) metadata from different package versions * Insert keywords and other properties * Create product descriptions from -release packages [1]: http://en.opensuse.org/Enhancerepo [2]: http://www.gitorious.org/opensuse/enhancerepo [3]: http://download.opensuse.org/repositories/home:/dmacvicar/ -- Duncan Mac-Vicar P. - Novell® Making IT Work As One™ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] JFYI: [Rpm-maint] RPM 4.8.0 released!
by Klaus Kaempf 08 Jan '10

08 Jan '10

JFYI ----- Forwarded message from Panu Matilainen <pmatilai(a)redhat.com> ----- Date: Fri, 8 Jan 2010 11:20:47 +0200 (EET) From: Panu Matilainen <pmatilai(a)redhat.com> To: rpm-announce(a)lists.rpm.org, rpm-maint(a)lists.rpm.org Cc: lwn(a)lwn.net Subject: [Rpm-maint] RPM 4.8.0 released! We're pleased to announce the availability of RPM release 4.8.0. Download instructions and more detailed information are available from: http://rpm.org/wiki/Releases/4.8.0 Here's the executive summary of user-visible changes since RPM 4.7.x: General bugfixes and enhancements: * Fix ftp/http proxy options (RhBug:529214) (regression originating from 4.6.0) * Fix remote package retrieval in rpm2cpio (RhBug:523260) * Fix --tid and --querybynumber query selectors (regression originating from 4.6.0) * Fix extranuous dependency type characters in --filerequires/provides output * Fix package relocatability checking (broken since forever) * Fix --excludepath (RhBug:409637) * Fix verification result depending on verbosity level (RhBug:510213) * Fix filename starting with '-' treated as stdin * Fix --nodirtokens yet again (RhBug:546663) * Query error code fixes (SuseBug:527191) * Report multiple scriptlet dependency bits in deptype format extension * Permit user specified query formats to behave differently on rpm's verbosity level * Dependency information queries now return the dependency type too in verbose mode * New tag extensions: o DBINSTANCE (record number of installed packages) o HEADERCOLOR (multilib "color" of header) o EVR, NVR, NEVR, NEVRA, NVRA (convenience formatting of name, epoch, version, release and arch tags) o EPOCHNUM (epoch of header, returns 0 for no epoch) o VERBOSE (is rpm in verbose mode or not) * New format extensions: o :fstate (human readable file state information) o :vflags (human readable file verifyflags information) * Major speed improvement in file list queries (eg -qal) * Major speed improvements in installation dependency calculations * Error out early when trying to install to readonly filesystem (ticket #99, RhBug:464750) * Disk space problems are only reported for affected packages (RhBug:517418) * Skip %posttrans scriptlets of failed transaction elements * Package erasures are now ordered too (ticket #48) * Improved ordering of packages with dependency loops - loopy sets are now guaranteed to be installed together (ticket #51) * Install ordering now differentiates between "colored" dependencies, giving better order with multilib package sets * Handle Requires(pre,preun) ordering correctly on erasure * %_netsharedpath is evaluated for erasures too (RhBug:494640) * Validate rpmlib() dependencies on src.rpm install (RhBug:490613) * Various minor corner-case memory leaks fixed * Several documentation fixes (ticket #72, #63) * Several translation updates (Spanish, Portugese Brasilian, Polish, German, Japanese, French, Serbian) Package building: * Automatic extraction of OCaml dependencies * Automatic extraction of mime-handler provides from .desktop files * Automatic extraction of font provides * OSGi dependency generator fixes (ticket #101) * Extra options can be now specified and passed to dependency extractor scripts * %files now accepts multiple filelists through -f (ticket #70, RhBug:475359) * Use 444 permissions for all .debug files (RhBug:522194) * Handle .desktop files with spaces in filename (RhBug:520920) * Fix duplicate dependency checking on build (RhBug:490378) * Various commonly used Python macros added (ticket #83) * Support for multiple major python versions in brp-python-bytecompile * Packages can now have a separate bug reporting url by setting BugUrl in spec or through %_bugurl in macro configuration (RhBug:512774) * Fix %sources and %patches containing the same items multiple times (ticket #82) * Add default %clean section unless overridden in spec (ticket #81) * %patch macro supports new -d option (ticket #69) * New %make_install macro which does the right thing wrt modern autotools (ie "make install DESTDIR=...") * Unset CDPATH (and DISPLAY) environment variables on build-scripts * Always run build-scripts in C-locale * Don't set --target in %configure (RhBug:458648) * Fix segfault on %include of empty file * Add XZ and LZMA recompress support to brp-compress (ticket #84) * Correctly inherit default %attr(-,-,-) from %defattr (RhBug:515685) * Support DWARF-3 in debugedit (RhBug:505774) * Much stricter set of allowed characters in various tags like Name, Version etc (ticket #59, RhBug:493157) * PreReq and BuildPreReq are now officially deprecated, with warnings at build-time * PreReq is mapped to Requires(pre,preun) at build-time * Permit %ghost to be used on non-existent files (RhBug:495040) * Configurable changelog trimming in rpm files (ticket #47) * Error out on unsupported payload compressor (RhBug:495429) * Correctly handle "./" in file paths (RhBug:491388) * Various tweaks to the internal file classifier (RhBug:491349) * Handle XZ in %uncompress macro * New built-in %getconfdir macro for getting rpm configuration "home directory" * Support for signing with the ancient PGP has been removed * Backwards compatibility macros %{PACKAGE_VERSION} and %{PACKAGE_RELEASE} are no longer supported in spec. Use %{version} and %{release} instead. Changes since rpm-4.8.0-beta1: - Avoid noise from python bytecompile on non-python packages (RhBug:539635) - Avoid exposing libmagic dependency in public headers - Several refcount-error caused memory leaks in python bindings fixed - Move python transaction element refcounting back to C-level - Permit unexpanded macros in spec tags again (RhBug:547997) - Remove the internal-only disk-space related functions from public API - Hardwire lead major version to 3 (RhBug:546663) On behalf of the rpm-team, - Panu - _______________________________________________ Rpm-maint mailing list Rpm-maint(a)lists.rpm.org http://lists.rpm.org/mailman/listinfo/rpm-maint ----- End forwarded message ----- --- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] [ANNOUNCE] ZYpp source repositories on gitorious.org/opensuse
by Duncan Mac-Vicar Prett 11 Dec '09

11 Dec '09

The ZYpp repositories previously published at git.opensuse.org repositories are now available on http://gitorious.org/opensuse http://gitorious.org/opensuse/sat-solver http://gitorious.org/opensuse/libzypp http://gitorious.org/opensuse/zypper http://gitorious.org/opensuse/zypp-utils (previously zypp/tools) http://gitorious.org/opensuse/libzypp-bindings http://gitorious.org/opensuse/libzypp-testsuite http://gitorious.org/opensuse/zypp-dialogsolver http://gitorious.org/opensuse/cmpi-zypp http://gitorious.org/opensuse/zypp-zmd-backend (previously zypp/backend) There is an initial opensuse-zypp team defined with access to those repositories. To switch you only need to edit your .git/config origin remote If before it was git@git.opensuse.org:projects/zypp/zypper.git Now it would be: git@gitorious.org:opensuse/zypper.git The repositories in git.opensuse.org are still accessible, but you can't push to them anymore. They will stay there until no repositories are left on that machine. Gitorious provides feeds for each repository pushes, and per each branch commits. To make it easier to follow the overall project, I have created this feed which merges various feeds and make the titles more similar to the old mails: http://pipes.yahoo.com/pipes/pipe.info?_id=36dc1dc1c0380cca92df9ddaa5b6e26d In the next days we will look for a solution to mail those feed updates to the commits mailing list. -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] Re: RFC: enhancerepo 0.4.0
by Duncan Mac-Vicar Prett 10 Dec '09

10 Dec '09

On Wednesday 09 December 2009 17:40:50 Jordi Massaguer Pla wrote: > Hi Duncan, > > I am attaching a new patch. Basically it adds the functionality to split > or merge any of the xmls in the repodata. > > We use this functionality in order to filter some rpms and its data > associated, so that we distribute only the updates associated to the > rpms we provide support of. > > See attached patches for version 0.3.2 . Could they be applied to the > 0.4.0? Your split-updates patch was merged long time ago :-) It is just missing from the command line help, I will fix that -- Duncan Mac-Vicar P. - Engineering Manager, YaST SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] RFC: enhancerepo 0.4.0
by Duncan Mac-Vicar Prett 08 Dec '09

08 Dec '09

Hey guys I just uploaded to home:dmacvicar what I would like to be enhancerepo 0.4.0 This release has lot of refactorings, bugfixes and new testcases as a result of the feedback of the Linkat guys (Jordi & Jordi) and also from Michael Calmer who works in our SLE migration process. Before release I want to wait a small time-window to collect some feedback. I do not plan to fix all issues, as I already have a TODO list for 0.4.1, but depending on the feedback I may hold releasing it. Changes: * Various delta and update generation bugfixes: * improved logger support * --split-updates, patch by Jordi Massaguer Pla * primary data generation (EXPERIMENTAL, don't use it yet) * allows to generate metadata to a separate directory * product metadata generation extracted from *-release rpm packages * benchmark feature * speed improvements * lot of testcases to avoid regressions TODO for 0.4.1 - finish switching xml parsing and creation to nokogiri, to speedup - experiment with primary metadata support Things you can do with enhancerepo: * take a rpmmd repository (created by createrepo) and add disk usage information, expiry info, keywords * take a rpmmd repository containing various versions of some package, and generate any level of deltarpms and generate deltainfo.xml automatically * take a rpmmd repository containing various versions of some package, and generate patches grouping the packages per fix/issue, automatically generating the patch description from the changelog, including bug and security references * more... If you want the latest code, it can be run from the source tree: bin/enhancerepo --help Get it from: git clone git://gitorious.org/opensuse/enhancerepo.git -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] setup own repo
by Elmar Stellnberger 16 Sep '09

16 Sep '09

Trying to set up an own repo I have run into the problem of zypper not accepting my private key signature. Following the instructions at http://en.opensuse.org/Secure_Installation_Sources I should have successfully created all necessary files: cd <repository directory> createrepo . gpg -a --detach-sign repodata/repomd.xml gpg -a --export <your key id> > repodata/repomd.xml.key ls repodata/ filelists.xml.gz primary.xml.gz repomd.xml.asc repomd.xml.key other.xml.gz repomd.xml repomd.xml.asc.oss However zypper refuses to use my repo: > zypper refresh --force Xorg-anc Forcing raw metadata refresh Retrieving repository 'Xorg-anc' metadata [error] Repository 'Xorg-anc' is invalid. File /var/tmp/TmpFile.OGmlRL doesn't contain public key data Please check if the URIs defined for this repository are pointing to a valid repository. Skipping repository 'Xorg-anc' because of the above error. Could not refresh the repositories because of errors. Searching for similar errors on the web I have found out that zypper might have a problem with my gpg version. The oss repos repomd.xml.asc.oss starts like the following -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) while my own repomd.xml.asc looks like this: -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.12 (GNU/Linux) ..... Will I have to use an elder gpg version or should I try sth. else? -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 9

[softwaremgmt] rypper - extension for managing multiple repositories via zypper
by Adam Spiers 16 Sep '09

16 Sep '09

Hi all, Such is the value of the openSUSE Build Service from my perspective that I now have over 40 repositories registered on my main SUSE machine! I found that zypper was slightly awkward for managing this number of repositories, so I found a few hours of spare time to knock up the following; hope it's of use to somebody. Patches welcome! http://adamspiers.org/computing/rypper Here is an extract from the documentation for those reading this offline on their Blackberries :-) =head1 NAME rypper - extension for managing multiple repositories via zypper =head1 SYNOPSIS # See complete usage documentation rypper --help # list all disabled repos rypper -d # list all enabled repos with autorefresh off rypper -e -R # list all repos which have anything to do with KDE rypper -x kde # list priority and URIs for all repos whose alias contains 'home:' rypper -a home: l -pu # enable autorefresh on all OpenSUSE Build Service repos rypper -u download.opensuse.org -R mr -r # remove all repos on external USB HDD mounted on /media/disk rypper -u /media/disk rr =head1 DESCRIPTION rypper is a wrapper around zypper for performing repository operations in batch. It allows selection of which repositories to operate on via a number of different repository selection specifiers. The zypper commands which can be wrapped are: removerepo, rr Remove specified repository. modifyrepo, mr Modify specified repository. refresh, ref Refresh all repositories. clean Clean local caches. Additionally, the zypper pseudo-command 'l' can be used to list matching repos. There are a number of options controlling the output format; run C<rypper --help> for details. If no zypper command is provided, it defaults to the 'l' pseudo-command, trying to intelligently choose which fields to display, e.g. omitting any which were included in the repo selection parameters. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 2

[softwaremgmt] Power Outage
by ml-admin＠opensuse.org 11 Sep '09

11 Sep '09

Broadcast message from ml-admin(a)opensuse.org (/dev/pts/0) at 07:30 GMT ... The system is going down for halt NOW! -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

1 0

[softwaremgmt] Software management status update using zypp:Head YaST:Head on 11.1
by Cristian Morales Vega 07 Aug '09

07 Aug '09

Some time ago I wrote about the problems in the software management stack. At that time zypper was a good tool, but the GUI apps did too much by themself without asking libzypp. Now I have added the zypp:Head and YaST:Head repos to my openSUSE 11.1, and that's what I see (looking at the QT version of sw_single, no idea about GTK): The good: 1- The YaST search now is a lot faster than in default 11.1. 2- As explained in http://jniq.blogspot.com/ the zypper interface now it's a lot better. The bad: 1- It's my understanding that sw_single still hasn't an equivalent to "zypper update". Neither Package->All Packages->Update if newer version available/Update unconditionally do the same. No sure if for single package installs the dependency resolution now is equivalent to zypper. 2- The vendor thing... OK, I don't see where the problem is, but it seems users have a problem when YaST ask them if it's ok to do a vendor change. They just see a "dependency conflict" and get scared. I would say that dialog could indeed get an update: 2.1- The classic situation gives three options: "vendor change", "do not install" or "ignore deps". Neither of them selected by default. Since users report that they click "OK" and they don't see any change (normal, they selected to do nothing) I would suggest two alternatives a) Enable the first option by default. Is ZYpp really returning them in an order that makes sense? b) Disable the OK button until the user selects an option. 2.2- The vendor change option could be reported with a better layout I get: Conflic Resolution: <radiobutton> Following actions will be done: install <package> (with vendor change) <previous vendor> --> <new vendor> <number (of lines)> more... <radiobutton> do not install <package> <radiobutton> ignore some dependencies of <package> So 2.2.1- The first radiobutton is in "Following actions will be done" and should be in "install <package> (with vendor change)". That could be a problem because of my mix of 11.1 and Factory packages. But if isn't it is a bug. 2.2.2- "<previous vendor> --> <new vendor>" is easier to read if is in a single line, I don't see space problems. 2.2.3- "<number (of lines)> more..." isn't clear. The "number" is lines of text, packages or what? Only once you click you see it means lines of text, that I would say isn't the best option... number of (more) packages that need a vendor change would make more sense. 2.2.4- "ignore some dependencies" is too dangerous. I would hide it and only show it if the user has activated an "advanced" mode in YaST sw_single. 2.2.5- Since now we have only two option (vendor change or do not install) I would argue that all the dialog should be redone. I would argue that there should be two dialogs, one specific for vendor changes and another for "real" dependency resolution problems that require a decision from the user. The vendor change specific dialog would say something as: "The selected action requires to change some packages for versions provided by different vendors. If you subtitute an official package from openSUSE by one provided by a third party you will lose the support from openSUSE. If you continue these packages will be subtituted by others from different vendors: <packageA>: <old_vendorA> --> <new_vendorB> <packageB>: <old_vendorB> --> <new_vendorB>" An "OK" would be equivalent to the current first option. A "Cancel" would be equivalent to the current second option. If the user clicks on "Cancel" he will return to the main sw_single window and the package that triggered the vendor change will be unselected (now the package continues marked for installation, so the conflict dialog will show again at some point). I mean, if I mark libxine1-codecs for install I get the dialog asking for a vendor change of libxine1... if I click on "cancel" libxine1 isn't marked for installation but libxine1-codecs is keep marked. 2.3- An alternative option is to add another option to the main sw_single module: "Force resolution". It would be the same option available in zypper. If "Force resolution" is enabled YaST will not ask the user when there are multiple possibilities, it will select the options it thinks it's better automatically. zypper forces resolution by default for "install" and asks the user for "update". 3- The updater applet from default 11.1 can only update patches. It seems a problem in PackageKit, that only knows about a single update, not about patches/packages. IIRC it's already reported in bugzilla. No idea if it's already fixed in Factory and I don't see a package backported to 11.1. So... for what should I open a bug? The lack of a "zypper update" equivalent in sw_single is known since a lot ago. Any plans to fix it for 11.2? Since you have been working on the zypper interface, can I suppose you are already also working in the YaST interface to solve problems as the vendor change dialog I just explained? I would summarize the current situation as: "with the new zypper interface I don't need the GUI anymore, but if I would want to use it I couldn't.". Because the lack of "zypper update" for GUI apps is a really big problem if you want to use them. -- To unsubscribe, e-mail: opensuse-softwaremgmt+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-softwaremgmt+help(a)opensuse.org

2 2