github.com/openSUSE/zypper/issues/13,
so it does not get lost.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+-------
le?
Frankly, I wonder if it actually needs more then a .conf file option. I doubt
that there is much need to turn this on and off on the command line.
> If so, is it ok to put it in the main section?
I'd introduce an [install] or [commit] section for options like this.
--
cu
unpacked)
http://download.opensuse.org/distribution/12.2/repo/oss/suse/x86_64/xteddy-2.2-16.1.2.x86_64.rpm";
percent="-1" rate="-1"/>
http://download.opensuse.org/distribution/12.2/repo/oss/suse/x86_64/xteddy-2.2-16.1.2.x86_64.rpm";
rate=&quo
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 t
(1/1), 270.4 MiB (302.862 TiB unpacked)
I'd need to know the repo it came from. I checked
http://download.opensuse.org/factory/repo/debug/, but it's ok.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73
Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+--+
Michael Andres SUSE LINUX Products GmbH, Development, m...@suse.de
GF:Jeff Hawn
outdated (not
to say useless). We should replace it by something more helpfull.
Most cases are of course covered by 'zypper', but it's a whole application and
not a nice and clean example.
Do you have a particular case in mind? Maybe we can cover parts of it fir
ich scripts were not
executed. They had to be cleaned when the next commit starts.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+--
t a line like
Package 'epages-*' not found.
so it becomes more obvious.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+----------+
Michael Andres SUSE LINUX Products GmbH, Development, m...
hen
those changes were introduced. zypper-1.3.7/libzypp-6.31.4 on your system is
pretty old, even for SLE11. Maybe you can try out the latest versions
zypper-1.3.22/libzypp-6.37.11.
Nevertheless one should also consider to fix the epages-j packages.
--
cu,
Michael Andres
+-
(content or
repomd.xml), so we can trust them.
(If the .rpm file is actually available, you can use RpmHeader::readPackage to
read the rpm header and then retrieve the desired tags value.)
--
cu,
Michael Andres
+--+
Key fingerp
plication.
The installer (libzypp) could be modified to look for a plugin (provided by
e.g. your application) willing to handle a low disk space exception.
[http://en.opensuse.org/Portal:Snapper]
[http://doc.opensuse.org/projects/libzypp/HEAD/zypp-plugins.
em there is
empty and the xml output contains a node which conatins a list
of nodes for all items to be installed:
description
...
--
cu,
Michael Andres
+----------+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+
On Thursday 11 April 2013 15:31:13 Olaf Hering wrote:
>
> Is there an easy way to get the same list of packages with just the rpm
> database?
AFAIK not.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1
ser wants to *completely uninstall* A, then B and C would be removed
...
This is what 'zypper remove --clean-deps' does.
It's available since zypper-1.4.4 (May 2010)
--
cu,
Michael Andres
+--+
Key fingerprint
Hi.
The SuSE-Code-12_3-Branch was created for:
libsolv/
libzypp/
libzypp-bindings/
libzypp-testsuite/
zypp-dialogsolver/
zypper/
Jenkins will be adjusted to submitt tested packages for this branch to
obs://zypp:Code12_3-Branch.
--
cu,
Michael Andres
mp of the rpm database.
If it does not, try `rpm --rebuilddb` to be sure the rpm database is ok.
If the above works, then simply remove the @System solv directory.
`zypper ref` will recreate it.
If the above does not work, we need to ask Michael Schroeder
hat does it do? Is there an observable difference
> from the "ignore" option?
This seems to be a bug.
Please open a bugreport at https://bugzilla.novell.com (Component: libzypp)
and attach the zypper log. Thanks.
--
cu,
Michael Andres
+-
Solutions for problem #1:
do not ask to delete all solvables providing A
--------
do not ask to install a solvable providing pattern:base
==> ignor
to usee
for simple tasks.
ResPool pool( ResPool::instance() );
pool.resolver().addRequire( Capability("pattern:base") );
pool.resolver().addConflict( Capability("A") );
pool.resolver().resolvePool();
--
cu,
Michael Andres
+
needs to be expressed on package level.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------+
Michael Andres SUSE LIN
product metadata must match the products data stored in
the .prod file included in the release package.
Without product metadata or the linking Provides: the resolver does not see
that the product is continued when the -release package is updated.
--
cu,
Michael Andres
+
sr/share/app- info/, but I can only find the categories.xml file there.
> Can anyone help me with this?
Adrian, can you help?
(@Lukas: I forwarded the apper/PK bug to
https://bugzilla.novell.com/show_bug.cgi?id=838000)
--
cu,
ta, so that you do not
> need to implement your own parsers for all metadata formats.
Not yet, but we probably can do. Question is what kind of support do we need.
Just access to the data or do we think about even integrating this into the
solver?
--
cu,
Michael Andres
+-
:Update
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+--+
Michael Andres SUSE LINUX Products GmbH, Development, m
zypp-team account.
Nevertheless YAST packages should not be submitted using this account. AFAIK
there is also a 'YaST Team' account which is probably a better choice for
Jenkins submissions.
--
cu,
Michael Andres
+---
Visit https://build.suse.de/request/show/30733
State of request 30733 was changed by mlandres:
new -> superseded
Comment:
superseded by 31927
Actions:
- submit Devel:zypp:SLE11SP2/libzypp => SUSE:SLE-11-SP2:Update:Test/libzypp
--
Configure notifications at https://build.suse.de/user/noti
Visit https://build.suse.de/request/show/30754
State of request 30754 was changed by mlandres:
new -> superseded
Comment:
superseded by 31928
Actions:
- submit Devel:zypp:SLE11SP2/zypper => SUSE:SLE-11-SP2:Update:Test/zypper
--
Configure notifications at https://build.suse.de/user/notifi
Visit https://build.suse.de/request/show/31927
State of request 31927 was changed by mlandres:
new -> superseded
Comment:
superseded by 35309
Actions:
- submit Devel:zypp:SLE11SP2/libzypp => SUSE:SLE-11-SP2:Update:Test/libzypp
--
Configure notifications at https://build.suse.de/user/noti
download.opensuse.org";
distver="13.1"
disttarget="openSUSE-%{distver}-x86_64"
debugenable="false"
sourceenable="false">
=[/Local/Service/repo/repo
e
openSUSE-13.1-x86_64
entry in /etc/products./baseproduct.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+-----------
l.com
(component: libzypp) and attach your /var/log/zypper.log.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+--------
;t be used
as mirrorlist (file:/localpath/to/mirrorlist.file) and zypper does not switch
non-interactively between the URLs on error. I filed a bugreport to track
this.
[https://bugzilla.suse.com/show_bug.cgi?id=899510]
--
cu,
Michael Andres
+--
| packman|...| Yes | Yes
19 | videolan |...| Yes | Yes
So what's the exact problem?
If you decide to file a bugreport, please don't forget to attach the relevant
log files.
--
cu,
Michael Andres
+
quot; );
RepoManager repoManager(( RepoManagerOptions(root) ));
for_( it, repoManager.repoBegin(), repoManager.repoEnd() )
std::cout << *it << std::endl;
return 0;
}
==
--
cu,
Michael Andres
+--
r 1]
Use the -r switch to look into rotated logfiles.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+----------+
Michae
be someone is willing to
provide a patch.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------+
Michael Andres
r only of the first package in each letter group (first).
##
## Valid values: all/first/no
## Default value: all
##
# pkglistHighlight = all
For details see the [color] section in zypper.conf.
--
cu,
Michael Andres
+-
refresh
If you're lucky and all required repos are available you can upgrade:
$ zypper --releasever 31.2 dup
Once openSUSE 13.2 is installed, the --releasever option is no longer needed.
--
cu,
Michael Andres
+-
On Wednesday 14 January 2015 13:45:02 Patrick Shanahan wrote:
> * Michael Andres [01-14-15 06:50]:
> > Some of you may know about the '$releasever' placeholder which can be
> > used in yum .repo files. On openSUSE the variable is substituted by the
> > current d
On Thursday 15 January 2015 04:47:09 Andrei Borzenkov wrote:
> В Wed, 14 Jan 2015 12:49:46 +0100
>
> Michael Andres пишет:
> > This gap is now closed by the new '--releasever VERSION' global option.
>
> What exactly "now" refers to?
Sorry, I mentioned it
g schema differs from the OpenSUSE
distro, "$releasever" is probably no benefit.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------
peof__
- or maybe
#define typeof __typeof__
#include
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+-----
version= settings. It may verry well be it
simply looks at the installed kernels and makes it's decision based on the
config values.
That's probably why the multiple 'kernel-default' are kept. But I also can't
explain why kernel-xen-3.16.7 is gone.
On Sunday 26 April 2015 19:13:16 lynd...@your-mail.com wrote:
> Since we have both
>
> multiversion
> multiversion.kernels
>
> in zypp.conf, how can you keep different #'s of different kernel flavors?
AFAIK mkinitrd does not support this.
--
says so.
Without /media.1/products the repo must be in /.
So I'd test for '/media.1/products or /content' being present.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27
shell is currently not supported.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+--+
Michael Andres SUSE
https://github.com/openSUSE/libsolv/issues.
(Somehow related to https://github.com/openSUSE/libzypp/issues/46; zypper is
not familiar with Fedoras way of installing multilib RPM package in
parallel.)
> You open to patches? :)
Of course. Preferred
https://github.com/openSUSE/libsolv/issues.
(Somehow related to https://github.com/openSUSE/libzypp/issues/46; zypper is
not familiar with Fedoras way of installing multilib RPM package in
parallel.)
> You open to patches? :)
Of course. Preferred
On Tuesday 07 July 2015 13:53:11 Damian Ivanov wrote:
> PS: I think the issue is more likely to be in libzypp as fedoras new
> package manager uses libhawkeye which uses libsolv as well but doesn't
> have that issue.
libzypp is ok.
--
cu,
k takes up to several minutes. Due to this it's
## possible to disable the automatic check after each commit. Explicit calls
## to 'zypper ps' are not affected by this option.
##
## Valid values: boolean
## Default value: yes
##
# psCheckAccessDeleted = yes
---
At least different output formats is easy :)
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+----------+
Mich
of breaking the rpm database.
If you're lucky only the index files are out of sync. Try:
rpm --rebuilddb
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB
her package.
Hard to tell without knowing all the dependencies involved. In case of doubt
create and send me a solver testcase and I'll have a look at it.
zypper in --debug-solver test-pattern
tar cvjf /tmp/zypper.solverTestCase.tar.bz2 /var/log/zypper.solverTestCase
--
cu,
t; ); // temp (alias)
> >> is the repo loaded into pool for temporary use repo.eraseFromPool();
That's fine.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+
l{.asc,.key} signed with this key. E.g.
zypper -v ref -f
If it does not work for you, please open a bug and attach the zypper.log.
I'll have a look at it.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D7
ed.
>
> Is this a known issue?
No. Thanks for hunting and reporting it.
I opened a bug at https://bugzilla.suse.com/show_bug.cgi?id=1008325
Please be so kind to attach your repomd.xml, .asc and .key file to the bug,
so we can verify a fix.
--
cu,
Michael Andres
+--
h subpackage
> comes from the same vendor:src.rpm.
The information is available, but the decision is made in the resolver.
Forwarding this to Michael, maybe he likes to turn this into a feature
for libsolv.
--
cu,
Michael Andres
+--
#x27;t have 'zypp.ZYppFactory_instance().haveZYpp()'
to test whether the instance is present.)
On older distros you need to run zypp in a separate process,
so libzypp gets unloaded and releases the lock.
--
cu,
Michael Andres
+--+
Key fi
x27;s on my TODO list ;)
> >
> >That's good enough for me :-) Thanks!
>
> I still see this with Leap 42.2. Is there a bugzilla already, or
> should I file one? Thanks!
https://bugzilla.suse.com/show_bug.cgi?id=953130
Bug 953130 - [libsolv] zypper up "checking for
JFYI:
Maintenance for Code12 (libzypp-16.x zypper-1.13.x) has been moved to
SuSE-SLE-12-SP2-Branch.
Master is now open for Code15 (libzypp 17.x zypper 1.14.x)
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1
ed a bug for it at https://bugzilla.suse.com/show_bug.cgi?id=1088037
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+-
language
supporting packages to the system. Omitting all the 'ordinary' recommends.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+------+
Michael Andres SUSE Linux GmbH, Development, m...@suse.com
Maxfeldstr
ult mode for your system, set [/etc/zypp/zypp.conf:solver.focus] to the
desired value.
--
cu,
Michael Andres
+--+
Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4
+---------
[https://bugzilla.suse.com/show_bug.cgi?id=1165476]
Package status computation regarding unneeded, orphaned, recommended and
suggested is broken in libyzpp-17.23.0.
Try to avoid using it and wait for the fix in libzypp-17.23.1.
--
cu,
Michael Andres
Hi.
This switch alone should not have impact on the apps linking against libzypp.
But Future APIs may make use of new stl types like std::string_view or the
filesystem library, . You won't be able to use them if you stay with an
older standard.
--
cu,
Michael A
68 matches
Mail list logo
