Re: [zypp-devel] Changing libzypp default to keep the last 2 kernel installed.
On Mon, Oct 01, 2012 at 10:45:00AM +0200, Michael Andres wrote:
> There are requests to turn on the multiversion install feature for kernel
> packages per default:
>
> > This change is motivated by several reasons seen by the community:
> >
> > a) With grub2 the additionaly installed kernels aren't longer
> >visitble by default.
> > b) Having the multiversion feature provided by libzypp is only
> >the first step. The majority of our users will never see it
> >nor will they know how to modify the default.
> > c) The changed default ensures to keel the currently running
> >kernel installed. If we remove it this might cause trouble
> >as the system might try to load a module which is no longer
> >available on disk.
> >
> > The actual package change log is:
> > Enable multiversion kernel and set multiversion.kernels in
> > /etc/zypp/zypp.conf to keep the latest, latest-1 and the running.
>
> Objections to do this for Factory?
It's ok for openSUSE, but do *not* do this for SLE, as all of those
ksym requires don't work with multiversion turned on.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] Current cases which Zypp doesn't handle well?
On Fri, Dec 14, 2012 at 11:14:01PM -0800, Edward Z. Yang wrote:
> I quite like the fact that Zypp uses a SAT solver to do its
> dependency generation. However, I'm curious if there are any
> situations which you have encountered where Zypp does a poor
> job, from a solving or usability perspective.
Well, I don't know of any, but as I'm the author, I'm a bit biased ;)
> For example,
> are there any cases where your heuristic for dealing with degrees
> of freedom does poorly?
libsolv (the solver library used by zypp) uses a very simply heuristic:
- it tries to keep the currently installed packages (unless the solver
job says otherwise)
- if there are choices, it always goes for the "best" package.
This normally matches what the user expects, if new packages have
to be downloaded and installed, they will be the newest ones, thus
saving extra work later on.
> Any places where the language of boolean
> formulas is not expressive enough (e.g. you want integer ranges
> or comparisons?)
For the package dependencies, we don't really need integer ranges. They
would be useful to minimize some metric the user provides, but libsolv
doesn't do that (see above).
> Some context: I recently happened upon this project:
>
> http://www.cs.wm.edu/~tdillig/mistral/index.html
>
> And it seems like it adds some features to SAT solvers that would be
> really useful for package managers: in particular, it has an "explain"
> module which can take some desired end-result (conclusion) and the
> current state (hypothesis), and find the minimal set of extra hypothesis
> necessary to reach the end-result. This seems to more directly correspond
> to the package solving problem, so I'm interested in comparing the two
> approaches!
Thanks for the link, I didn't know about mistral before. I'm looking
forward to your comparison.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] zypp-bindings
On Mon, Jan 28, 2013 at 10:25:42AM +0100, Stephan Kulow wrote:
> On 28.01.2013 10:19, Klaus Kaempf wrote:
> > * Stephan Kulow [Jan 28. 2013 09:44]:
> >> Hi,
> >>
> >> The zypp bindings fail for quite some time and I have no idea how to fix
> >> it - please someone who talks fluent swig, check the errors:
> >
> > Since when does it fail ?
> > Did a SWIG upgrade trigger the failure ?
> >
> It fails since mid november and Duncan does not seem to be the maintainer:
>
> https://bugzilla.novell.com/show_bug.cgi?id=793554
>
> I can't tell you if it's related to swig updates - from the .changes it
> seems rather unlikely.
I'm not the maintainer, but I tried to fix it. The commited
version should build and run the tests with no error, I don't
know if really everything works, though.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] zypper/libsolv broken @System/solv file
Hi Tony,
On Thu, May 02, 2013 at 04:21:45PM +0200, Tony Wolf wrote:
> So, rpm sees all installed packages; but the @System/solv files seems to
> be broken.
>
> We use the following versions:
> * zypper 1.8.9 (+ bugfix of swig BoolSave)
> * libzypp 13.1.0
> * libsolv latest snapshot from git/origin
> * boost 1.53.0
>
> Do you have a hint, where I may take a look at, to solve the problem?
What version of rpm do you use?
Thanks,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] zypper/libsolv broken @System/solv file
On Fri, May 03, 2013 at 02:42:57PM +0200, Michael Schroeder wrote: > On Thu, May 02, 2013 at 04:21:45PM +0200, Tony Wolf wrote: > > So, rpm sees all installed packages; but the @System/solv files seems to > > be broken. > > > > We use the following versions: > > * zypper 1.8.9 (+ bugfix of swig BoolSave) > > * libzypp 13.1.0 > > * libsolv latest snapshot from git/origin > > * boost 1.53.0 > > > > Do you have a hint, where I may take a look at, to solve the problem? > > What version of rpm do you use? Does the little 'solv' example program that comes with libsolv work correctly? M. -- To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] zypper/libsolv broken @System/solv file
On Fri, May 03, 2013 at 02:54:15PM +0200, Tony Wolf wrote: > I'm currently checking the rpm db. As far as I know, libsolv supports 32Bit > IDs only. That should be okay, because we won't need that much IDs :-) > > But for any reason, our IDs within our rpmdb are much higher... (there is > no small number anywhere, really strange :-)) > > So it does not seem to be a libsolv problem at all, sorry for that! > > The rpm version is 4.11.0.1 with berkeley db 4.8.30. Hmm, you don't happen to have defined RPM5 when configuring libsolv by mistake? RPM5 has switched the index from little to bih endian. Also: what arch is that? Is that some standard little endian Intel/AMD platform? M. -- To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] zypper/libsolv broken @System/solv file
On Fri, May 03, 2013 at 03:28:49PM +0200, Tony Wolf wrote:
> all IDs seems to be a multiple of 16777216 (first one is 16777216, second
> 33554432 and so on). An "rpm -i" already inserted those IDs.
>
> 16777216 is a defined value within berkeleydb/common/db_shash.c
Sounds like an endian issue.
"rpmdb2solv | dumpsolv | grep rpm:dbid" should show little numbers as
ids, if that's not the case, libsolv is somehow misconfigured or has
a bug.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] createrepo misses dependencies
On Tue, Jun 04, 2013 at 06:55:12PM +0200, Olaf Hering wrote:
> I'm trying to create a list of dependencies for a given list of package
> names during package build. The steps are like this:
>
> - put "# needsbinariesforbuild" into libguestfs.spec
> - symlink /.build.binaries/* to a private $tmpdir
> - run "createrepo $tmpdir"
> - create a private repos.d with a single repo pointing to that $tmpdir
> - call 'zypper ... install --dry-run --download-only module-init-tools'
>
> This fails because module-init-tools.spec has "PreReq: /usr/bin/eu-nm",
> which comes from elfutils. Putting elfutils into BuildRequires puts this
> package also into /.build.binaries/. But createrepo still fails to
> create a dependency for /usr/bin/eu-nm.
It shouldn't create a dependency but it should create a
/usr/bin/eu-nm
line in the elfutils section. Isn't that the case?
> After poking around in my 11.4 repo data I found /usr/bin/eu-nm in
> "suse/setup/descr/packages.gz", which is eventually the place where
> libzypp is looking for further dependencies. I see a "Req: /usr/bin/eu-nm"
> in module-init-tools and a "Prv: /usr/bin/eu-nm" in elfutils in that file.
Susetags repos don't have a "file" section, but add files directly
to the package provides list.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] Recommended packages ignored when Installing from osb, works with manual download
On Thu, Jun 06, 2013 at 03:26:11PM +0200, Sebastian Schubert wrote:
> I want to install the package flac2all:
> https://build.opensuse.org/package/show?package=flac2all&project=home%3Asebschub
> which is only available in this very repository (my obs home
> repository). I thus added the home repository to my local list of
> repositories (see below for list of activated repositories).
>
> Installing from the repository does not take into account the
> recommended and suggested packages:
>
> # zypper in flac2all
> [...]
> # zypper in /home/schubert/Downloads/flac2all-3.28-2.1.noarch.rpm
> [...]
> The following package is recommended, but will not be installed because
> it's unwanted (was manually removed before):
>
> vorbis-tools
> [...]
> I would expect the very same behaviour. Is this a bug or a feature?
Looks like a bug to me. As I don't see anything in your flac packages
that recommends vorbis-tools, it looks like the "zypper in flac2all"
run is actually correct. The zypper.log probably contains some hints
about what's going on.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] Recommended packages ignored when Installing from osb, works with manual download
On Thu, Jun 06, 2013 at 04:15:31PM +0200, Sebastian Schubert wrote:
> On 06/06/13 15:46, Michael Schroeder wrote:
> > On Thu, Jun 06, 2013 at 03:26:11PM +0200, Sebastian Schubert wrote:
> >> I want to install the package flac2all:
> >> https://build.opensuse.org/package/show?package=flac2all&project=home%3Asebschub
> >> which is only available in this very repository (my obs home
> >> repository). I thus added the home repository to my local list of
> >> repositories (see below for list of activated repositories).
> >>
> >> Installing from the repository does not take into account the
> >> recommended and suggested packages:
> >>
> >> # zypper in flac2all
> >> [...]
> >> # zypper in /home/schubert/Downloads/flac2all-3.28-2.1.noarch.rpm
> >> [...]
> >> The following package is recommended, but will not be installed because
> >> it's unwanted (was manually removed before):
> >>
> >> vorbis-tools
> >> [...]
> >> I would expect the very same behaviour. Is this a bug or a feature?
> >
> > Looks like a bug to me. As I don't see anything in your flac packages
> > that recommends vorbis-tools, it looks like the "zypper in flac2all"
> > run is actually correct. The zypper.log probably contains some hints
> > about what's going on.
>
> In line 26--28 of the flac2all.spec file, it is written
>
> Recommends: vorbis-tools
> Suggests: lame
> Suggests: nero-aac
>
> so the vorbis-tools are in fact recommended, are they not? So the output of
> zypper in /home/schubert/Downloads/flac2all-3.28-2.1.noarch.rpm
> is what I would expect.
Yeah, bug in createrepo in SLE11-SP2. It's now manually fixed on our
server, so the next time something is changed in the repo the
recommends will be back.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] Patches and handling package addition/removal
On Thu, Jul 25, 2013 at 10:30:15PM +, Nashif, Anas wrote:
> when using patches, how can one add packages to be installed on the system
> (that were not installed before) or remove packages?
> I understand this can be done in packages directly by either adding
> dependencies to other packages or obsoleting package, but is there some other
> way to do it?
Dependency wise, patches are just solvables, so they can contain requires
and conflicts. But patches are generated from the data in updateinfo.xml,
and that therefore can only update installed packages.
(You can somewhat do removals of packages by having packages in updateinfo.xml
that do not exist in the repository. But that is a hack.)
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] Patches and handling package addition/removal
On Fri, Jul 26, 2013 at 06:32:12PM +, Nashif, Anas wrote:
>
>
> On 26/07/2013 07:39, "Michael Schroeder" wrote:
>
> >On Thu, Jul 25, 2013 at 10:30:15PM +, Nashif, Anas wrote:
> >> when using patches, how can one add packages to be installed on the
> >>system (that were not installed before) or remove packages?
> >> I understand this can be done in packages directly by either adding
> >>dependencies to other packages or obsoleting package, but is there some
> >>other way to do it?
> >
> >Dependency wise, patches are just solvables, so they can contain requires
> >and conflicts. But patches are generated from the data in updateinfo.xml,
> >and that therefore can only update installed packages.
>
> aha, so is it a limitation in the updateinfo.xml? Where can you add
> requires and conflicts to a patch otherwise?
Well, you can't. You need to extend the updateinfo.xml parser to
do such things.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] PackageKit backend
On Tue, Aug 20, 2013 at 01:08:48PM +0200, Lukas Appelhans wrote:
> The other thing I wanted to ask about is the availability of Appstream data
> in
> the opensuse repositories. From what I understood, the distributions tools
> should provide this data (the appdata.xml in your case) in /usr/share/app-
> info/, but I can only find the categories.xml file there. Can anyone help me
> with this?
If the data is supposed to be in a repository, how can it appear in
/usr/share/app-info? Or are you talking about the app data for installed
applications?
Anyway, the app data for repos is either in suse/setup/descr/appdata.xml.gz
(for susetags type repos), or in repodata/-appdata.xml.gz
(for rpm-md type repos, data type "appdata" in repomd.xml).
Libzypp already downloads it, but I don't think it has an interface to
access it.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] Package conflicting with itself
On Tue, Nov 26, 2013 at 07:47:25PM +0100, Michal Svec wrote: > > On Tue, 26 Nov 2013, Michael Matz wrote: > >>> Is there an easy solution to this? >>> Problem: solvable libstdc++6-4.8.1_20130909-3.2.1.i586 conflicts with >>> libstdc++6 provided by itself >>> >>> This is a 12.1 system I am trying to upgrade to 13.1 so most likely not >>> something usual, but still- this seems to be a change on the package >>> level, even rpm itself would need force and nodeps so I wonder if >>> there's an easy way out (besides reinstall or possibly upgrade from the >>> media). >> >> You somehow need an upgraded zypp stack, which will ignore the self >> conflict. > > Yeah, but it's kind of tough as the new zypp stack requires new libstdc++ > and a bunch of other things which I don't really want to force install. Can't you just force-install libstdc++6-4.8.1_20130909-3.2.1.i586? M. -- To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] A question about SAT-solution filtering
Hi Mr. Deepsolver ;)
On Tue, Jan 14, 2014 at 08:06:54PM +0700, Michael Pozhidaev wrote:
> I'd like to better understand some zypp (maybe libsolv) implementation
> details. Could anybody help me, please!
>
> The question is as follows: consider we have a couple of packages a and
> b. Dependencies rules imply that a requires b. Reflecting that clause
> should be as (not a or b), right?
>
> But if a is not chosen for installation b gets freedom to have any
> value, either true or false without any consequent breaks of a solution.
>
> What strategy do zypp use to left the b variable unchanged? I mean left
> corresponding package uninstalled if it was uninstalled. Is it possible
> to do that strictly or it always implies some probability?
>
> Thank you a lot for your answer! :))
So this is about the time when the solver is free to choose a literal,
not unit propagation. In that case, we only choose positive literals,
*and only if we must* (meaning if none of the negative literals are
fulfilled). So, in your case, we would never choose b from a "-a|b"
rule as long as "a" is not chosen for installation.
When we no longer find rules that we need to fulfill, we set all
undecided literals to "keep". This makes all rules true.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [yast-devel] Re: [zypp-devel] Request 215269 created by jreidinger (delete openSUSE:Factory/yast2-s390)
On Mon, Jan 27, 2014 at 03:31:12PM +0100, Josef Reidinger wrote:
> On Mon, 27 Jan 2014 15:27:41 +0100
> Michael Schroeder wrote:
>
> > On Mon, Jan 27, 2014 at 01:38:06PM +0100, Josef Reidinger wrote:
> > > Visit https://build.opensuse.org/request/show/215269
> > >
> > > Description:
> > > It is exclusive only for s390, so no reason to have it in factory.
> >
> > Huh? Factory is mirrored into the IBS and builds there for s390.
> >
> > Cheers,
> > Michael.
> >
>
> So it makes sense to have it in Factory:Internal as for other SLE
> specific packages, not? Or why is yast2-s390 so special?
Sure, "SUSE:Factory:Head:Internal" would also work. Just don't drop
the package. ;)
M.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] Request 215269 created by jreidinger (delete openSUSE:Factory/yast2-s390)
On Mon, Jan 27, 2014 at 01:38:06PM +0100, Josef Reidinger wrote:
> Visit https://build.opensuse.org/request/show/215269
>
> Description:
> It is exclusive only for s390, so no reason to have it in factory.
Huh? Factory is mirrored into the IBS and builds there for s390.
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX Products GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
Re: [zypp-devel] "Checking for file conflicts" - slower than it used to be?
On Tue, Mar 01, 2016 at 03:05:18PM +, Adam Spiers wrote:
> Is it just me or does the "Checking for file conflicts" stage of a
> zypper install sometimes take a lot longer than it used to?
>
> My memory is that it always used to be extremely fast, whereas now it
> can take tens of seconds in some cases, or even minutes. It seems
> very strange to me that it would ever need to take more than a
> fraction of a second. Is there a good reason for this?
I've seen this as well, but I didn't figure out the reason yet.
It's on my TODO list ;)
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
[zypp-devel] [Modularity] Module metadata proposal (fwd)
FYI:
- Forwarded message from Petr ??abata -
> Good news, everyone,
>
> the first draft of the module metadata format is now available
> for you to comment on. We've decided to go with YAML so it
> should be fairly readable. You can view the latest version here:
>
> https://pagure.io/fm-metadata/blob/master/f/metadata.yaml
>
> What is is:
> The file defines basic properties of the module such as its
> name, version, description, licenses, references to upstream
> documentation or its content. Currently only RPM content
> is supported but this can be easily extended in the future.
> The metadata file is meant as both input and output of the
> module build process (don't confuse it with package build
> process), with various tools adding various new data to it,
> such as vendor and buildsystem identifiers, timestamp of the
> build, autogenerated lists of licenses or whatever you can
> think of (well, maybe not whatever but close). The output is
> then placed in the generated repository, container image or
> any other module deliverable and can be processed by tools and
> services consuming and delivering modules.
>
> What is isn't:
> It's not a SPEC file. It doesn't say how to build individual
> packages. And it's not a simple comps group either. It can
> and does provide lots more additional data.
>
> It's not perfect and it's constantly evolving. Please, do
> comment, ask questions and suggest improvements.
>
> Thanks,
> P
Cheers,
Michael.
--
Michael Schroeder m...@suse.de
SUSE LINUX GmbH, GF Jeff Hawn, HRB 16746 AG Nuernberg
main(_){while(_=~getchar())putchar(~_-1/(~(_|32)/13*2-11)*13);}
--
To unsubscribe, e-mail: zypp-devel+unsubscr...@opensuse.org
To contact the owner, e-mail: zypp-devel+ow...@opensuse.org
