S3 is a convenient option for hosting yum repositories, and using a public S3 bucket works very well.

When trying to enabled authentication hewever, things get hairy. AWS requires either a specific Authorization header or passing a query string with the parameters. The signature that is passed depends on the day when it is generated, so I can't 'presign' the zypper URL with it.

http://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html

It would be great if zypper would have native support for S3 authentication.

According to doc, zypper pa -r # should:

List all packages available in specified repositories.

However, it doesn't respect given repository number (it could be taken from i.e. zypper lr) and it displays packages from few other repositories.

zypper lr

#  | Alias                  | Name                          | Enabled | Refresh
---+------------------------+-------------------------------+---------+--------
 1 | AppFog                 | AppFog                        | Yes     | No     

fisiu@pendrak:~ $ zypper se -r 1 | wc -l
30
fisiu@pendrak:~ $ zypper pa -r 1 | wc -l
2205

I modify machines' /etc/zypp/locks files for a variety of machine-specific reasons.

I'd like to add pertinent comments to the 'locks' file

I note that any added comments are, eventually, removed automatically from the locks file.

Also, I see that changes are automatically made e.g. rewriting a simple solvable version match to a more complex form

complex: AttrMatchData solvable:name cups-* C SolvableRange\ >\ 1.7.0\ ""

Asking on ML,

Q:

Is there a toggle/flag to PREVENT system-automated overwrite of user mods to the
locks file?

A:

No. The locks file just a serialized set of PoolQueries. 
It's parsed+applied, collected+written. There's no coupling 
between parsed and written values.

Preserving comments and user modifications is probably not too hard to 
implement. If you like to open an issue at 
https://github.com/openSUSE/zypper/issues, maybe someone is willing to 
provide a patch.

For some reason, I want to remove all my packages from devel:python and use the openSUSE source instead.
I tried to remove python repo and remove all packages by listing them using zypper packages --orphan, but it will also trigger to remove a lot of necessary packages.

Output of zypper lu can be quite long. I sometimes find myself parsing the version numbers to see whether

a) I should update
b) if I updated in which packages I should expect more than minor changes

This is somewhat cumbersome and error prone so I'm inclined not to do it and thus surely have missed changes I'd have cared about.
It would make a difference if zypper would colorize the first digit where installed and available version differ.

zypper manpage sais the following are avaialble for --type:
package, patch, pattern, product, srcpackage, application

Bash completion for zypper search --type only does package, patch, pattern, product.

I think it could be a workaround for a DNS resolving issue.

Issue details:

I received "Error message: Failed to connect to 2001:67c:2178:8::13: Network is unreachable" frequently when I set Tumbleweed as repository before, "curl --head download.opensuse.org" showed the same error.

I found my router at home has an issue on DNS resolving: ipv6 addresses were returned for both A and AAAA query, result from tcpdump:
22:50:45.925896 IP 192.168.0.2.58627 > 192.168.0.1.domain: 38640+ A? download.opensuse.org. (39)
22:50:45.925907 IP 192.168.0.2.58627 > 192.168.0.1.domain: 21267+ AAAA? download.opensuse.org. (39)
22:50:45.927134 IP 192.168.0.1.domain > 192.168.0.2.58627: 38640 1/0/0 AAAA 2001:67c:2178:8::13 (67)
22:50:46.337089 IP 192.168.0.1.domain > 192.168.0.2.58627: 21267 1/0/0 AAAA 2001:67c:2178:8::13 (67)

"curl -4 --head download.opensuse.org" works, since it tried other nameserver in /etc/resolv.conf when it got wrong ipv4 address, and the second nameserver works.

"-4" option could be a solution, I tried to add "--ipv4" in .curlrc before, but it doesn't apply to zypper; then I modified /etc/resolv.conf to fix it, it works, though.

And I found some other guys want to get this option too, or "-6".

At least one github project (https://github.com/JuliaLang/BinDeps.jl) currently tests for the existence of an apt-get on a system with the command apt-get -v. If zypper-aptitude is installed on an openSUSE system as in Leap 42.1 the result is an unfortunate call to zypper GUI which must be cancelled for the process to continue.
One solution is simply to remove the zypper-aptitude package from the openSUSE system. Then apt-get does not exist and the script takes the necessary steps.
I wonder if the perl script which controls the action of the system on receiving a call to apt-get might more appropriately respond to "apt-get -v" by a simple action not involving a call to zypper? Or perhaps there is an alternate process that can be considered for testing the real role of apt-get on openSUSE?

ref: JuliaPackaging/BinDeps.jl#202

Hi,

I am using SLES12 with rpm 4.4.2 and zypper 1.12.40

My rpm package (built with the gradle rpm nebula plugin) defines the INFO/REQUIRES list

packageZ
packageX
packageY

with needed package dependencies.

My problem: zypper solves and installs the packages in lexicographic order

packageX
packageY
packageZ

Is it possible to guarantee the order of installation of dependencies like it is defined in REQUIRES ?
Thank you very much for help.

As I found now time testing my zypper builds (thanks to mlandres to get them built) I noticed that I can't create a chroot via --root.
The output I get when I want to create a OpenSuSE 12.3 x86_64 chroot is:

~$ sudo zypper --root $CHROOT_DIR ar http://download.opensuse.org/distribution/$VERSION/repo/oss/ repo-oss
No configuration file exists or could be parsed.
*** Augeas exception. No config read, sticking with defaults.
gpg: no valid OpenPGP data found.
Fatal: no entropy gathering module detected

Zypper is built using upstream code, based on the following dependencies:

• libsolv [upstream], using a db fix for -DSUSE - https://code.launchpad.net/~thopiekar/zypper/libsolv-db-fix
• libzypp [upstream]
• augeas [1.0.0-1]
• rpm [4.11.1-2]

While preparing Debian package zypper 1.12.4-1, I found these spelling errors in the human readable texts of this project:

http://anonscm.debian.org/cgit/collab-maint/zypper.git/plain/debian/patches/1003_fix-spelling-errors.patch?id=ea1f71d28aa0e69291088e2740ae5ffb71cee396

I'd like to propose that (either by default or a new option) the detailed output for zypper dup etc highlights the version number components that actually change, using red/green to indicate lower respectively higher version string components.

Consider the following example output:

The following 80 packages are going to be upgraded:
MozillaFirefox 42.0-2.1 -> 42.0-2.2
libsoup-2_4-1 2.52.1-1.1 -> 2.52.2-1.1
openSUSE-release 20151111-1.2 -> 20151113-1.1

The following 8 packages are going to be downgraded:
git 2.6.3-277.1 -> 2.6.3-276.2

(The bold text would be red/green, green/red, respectively. Markdown does not support the colors directly.)

That'd make it immediately obvious from looking at the installation summary whether a package was merely rebuild, checked in, got a major update, etc.

Hi,

Support for exposing /var/lib/zypp/AutoInstalled functionality for marking packages as AutoInstalled or Explicit.

I was thinking of something like:

zypper se --autoinstalled ( list packages that were autoinstalled and present on /var/lib/zypp/AutoInstalled )
zypper se --explicit ( list packages installed on system but no on autoinstalled file )

zypper mark --autoinstalled "packages" ( mark, add packages to autoinstalled file )
zypper mark --explicit "packages" ( mark, remove packages from autoinstalled file )

zypper rm --unneeded ( remove packages not needed on autoinstalled file ).

I have been using these scripts to manage autoinstalled packages: https://github.com/alexjp/zypper_autopackages

zypper_autoinstalled.sh: creates a full autoinstalled file from packages not present in a world file
zypper_autoremove.sh: remove all packages not needed by packages not in autoinstalled
zypper_explicit_installed.sh: creates the world file: all packages installed but no in autoinstalled

With these scripts, I can have a common world file with favorite packages, and manage those across diferent machines.
With zypper_autoremove.sh, I can have the peace of mind that i can install all i want, if later is not in the world file, it can be cleaned and removed from system. ( very helpfull when installing and testing a new desktop environment or group of packages ).

Thanks!

The description reads: "Add a repository to the sytem. […]"
It would cool if the typo could be fixed. Thanks.

I have an ubuntu based docker image running sleep in a loop. That's what zypper ps shows:

PID   | PPID  | UID  | Login | Command  | Service | Files                                                               
------+-------+------+-------+----------+---------+---------------------------------------------------------------------
30953 | 1224  | 1000 | etam  | sh       |         | /lib/x86_64-linux-gnu/ld-2.15.so (stat: No such file or directory)  
      |       |      |       |          |         | /lib/x86_64-linux-gnu/libc-2.15.so (stat: No such file or directory)
30979 | 30953 | 1000 | etam  | sleep    |         | /lib/x86_64-linux-gnu/ld-2.15.so (stat: No such file or directory)  
      |       |      |       |          |         | /lib/x86_64-linux-gnu/libc-2.15.so (stat: No such file or directory)

Obviously such files exist in containers rootfs, not in /.

When running zypper si:

Package 'yast2-qt-branding-openSUSE' has source package 'branding-openSUSE'.

gets translated to

Das Paket 'yast2-qt-branding-openSUSE' enthält das Quellpaket 'branding-openSUSE'.

That is the wrong way around. Better would be:

Das Paket 'yast2-qt-branding-openSUSE' ist im Quellpaket 'branding-openSUSE' enthalten.

Please provide options in zypper to allow listing of unsupported and orphan packages.

When doing updates that require downloading of hundreds of packages, it would be great if Zypper supported downloading more than one package at a time.

This would significantly speed up the update process without having to hack a local repository.

Downsides of this as of right now is that most of the repository servers still serve pages under http 1.X protocols and might have to throttle clients based on the amount of connections initiated.
But the http servers are moving towards http 2 at very fast rates, and this would mitigate this issue completly if Zypper were to support it as well.

Upsides would be that with home connections being at 1Gb/s speeds these days, mobile connections being at ~5-150Mb/s speeds, and 1Gb/s mobile connections (5g) are coming in 3-4 years to the consumer market, the experience would be much better to the user.

Thoughts? Yay's/nay's? Blockers?

Hi,

the Debian lintian tool reported various typos in code and man pages. Also, lintian discovered dozens of hyphen-used-as-minus-sign issues.

This patch solves this:
http://anonscm.debian.org/cgit/collab-maint/zypper.git/tree/debian/patches/1002_fix-spelling-errors.patch

I: zypper: hyphen-used-as-minus-sign usr/share/man/man8/zypper.8.gz
N:
N: This manual page seems to contain a hyphen where a minus sign was
N: intended. By default, "-" chars are interpreted as hyphens (U+2010) by
N: groff, not as minus signs (U+002D). Since options to programs use minus
N: signs (U+002D), this means for example in UTF-8 locales that you cannot
N: cut and paste options, nor search for them easily. The Debian groff
N: package currently forces "-" to be interpreted as a minus sign due to
N: the number of manual pages with this problem, but this is a
N: Debian-specific modification and hopefully eventually can be removed.
N:
N: "-" must be escaped ("-") to be interpreted as minus. If you really
N: intend a hyphen (normally you don't), write it as "(hy" to emphasise
N: that fact. See groff(7) and especially groff_char(7) for details, and
N: also the thread starting with
N: https://lists.debian.org/debian-devel/2003/debian-devel-200303/msg01481.html
N:
N: If you use some tool that converts your documentation to groff format,
N: this tag may indicate a bug in the tool. Some tools convert dashes of
N: any kind to hyphens. The safe way of converting dashes is to convert
N: them to "-".
N:
N: Because this error can occur very often, Lintian shows only the first 10
N: occurrences for each man page and give the number of suppressed
N: occurrences. If you want to see all warnings, run Lintian with the
N: -d/--debug option.
N:
N: Refer to /usr/share/doc/groff-base/README.Debian and the groff_char(7)
N: manual page for details.
N:
N: Severity: wishlist, Certainty: possible
N:
N: Check: manpages, Type: binary
N:

Greets,
Mike

From bnc#492261

I'm managing a number of desktop systems and I use
cron.daily/opensuse.org-online_update to patch them.

Currently, this fails because a minor important repository is not available:

File '/repodata/repomd.xml' not found on medium
'http://download.videolan.org/pub/videolan/vlc/SuSE/13.2'

Abort, retry, ignore? a/r/i/? shows all options:
ABORT request: Aborting requested by user

I would indeed very much appreciate if the major updates from the opensuse
repo would still be installed automatically in such a situation.

So I think some kind of --continue or --ignore-minor-errors would be very
helpful here!

The problem with this is, that zypper does not know whether this is a minor or major important repo to you.

If a repo is disabled/skipped, packages previously installed from this repo are considered as 'orphanded'. Orphanded packages involved in any dependency issue may be silently deleted by the resolver. As zypper can't decide whether this would be OK for you, we don't offer such an option.

For your usecase we had to introduce a new repo property which allows you to tag a repo as 'minor important'. Zypper may then ignore the refresh error and continue using the old (unrefreshed) data.

This way one could wait for a repo to become available again rather than permanently disabling it.

currently, zypper supports locks in a single locksfile.

'The default location of the locks file is /etc/zypp/locks. This can be changed in /etc/zypp/zypp.conf using locksfile.path setting. '

Across multiple machines, it's very useful to deploy a common locksfile.

Machine-specific overrides must be made to the lockfile itself.

Requesting support for /etc/zypp/locks.d/* files.

That directory could be populated @ each machine as required, and still allow for deployment of a cetnrally-managed, common lock file.

Requested 2012-09-14 by Juergen Gehne on [zypp-devel]:

may I add something to the zypper wish list?

We very often install a group of packages via zypper automatically by

zypper --no-refresh --non-interactive --no-gpg-check in pack1 pack2 ... packN

But if only 1 package cannot be found, zypper does not install any package.
I would be very glad if you could implement an option like "--ignore-unknown" so that unknown
packages will be ignored.

Zypper should be able to handle groups in Fedora maybe?

[root@fed22 ~]# zypper install -t pattern core
Loading repository data...
Reading installed packages...
'core' not found in package names. Trying capabilities.
No provider of 'core' found.
Resolving package dependencies...

Nothing to do.

[root@fed22 ~]# zypper install -t pattern @core
Loading repository data...
Reading installed packages...
'@core' not found in package names. Trying capabilities.
No provider of '@core' found.
Resolving package dependencies...

Nothing to do.

[root@fed22 ~]# zypper install @core
Loading repository data...
Reading installed packages...
'@core' not found in package names. Trying capabilities.
No provider of '@core' found.
Resolving package dependencies...

Nothing to do.

[tux@fedora ~]$ dnf group info core
Last metadata expiration check performed 0:05:30 ago on Tue Jul 14 11:09:41 2015.

Group: Core
 Description: Smallest possible installation
 Mandatory Packages:
   audit
   basesystem
   bash
   coreutils
   cronie
   curl
   dhcp-client
   dnf
   dnf-yum
   e2fsprogs
   filesystem
   glibc
   grubby
   hostname
   initscripts
   iproute
   iputils
   kbd
   less
   man-db
   ncurses
   openssh-clients
   openssh-server
   parted
   passwd
   plymouth
   policycoreutils
   procps-ng
   rootfiles
   rpm
   selinux-policy-targeted
   setup
   shadow-utils
   sudo
   systemd
   uboot-tools
   util-linux
   vim-minimal
 Default Packages:
   NetworkManager
   authconfig
   dnf-plugins-core
   dracut-config-rescue
   firewalld
   ppc64-utils

It would be great if we could have a "shorthand" for the option --match-exact for the search command

I suggest using -x

zypper search -x foo.name
instead of doing zypper search --match-exact foo.name

Fedora's 'repomd.xml' files are always unsigned. Yeah, I know: Not so great.
However zypper always asks "unsigned, continue? yes/no".
Could you implement a "Don't ask for this repo again" / "Always yes" answer, please? I guess it's fine when it asks the first time but every time is very tedious.

Not sure if it belongs to libzypp or here.
Just for fun I installed zypper on my Fedora system.
While in general in seems to work, its practical use is limited because in Fedora's repo files the URLs contain the two variables $releasever and $basearch, i.e. http://download.fedoraproject.org/pub/fedora/linux/updates/$releasever/$basearch/ translates into http://download.fedoraproject.org/pub/fedora/linux/updates/21/x86_64/ on a 64bit Fedora 21 installation.

IMO that change would also be beneficial for openSUSE because one thing that regularly annoys me is that after an upgrade I have to tweak all my repos to match the new version number. If I could just add the repo URL http://download.opensuse.org/repositories/home:/KAMiKAZOW/openSUSE_$releasever/ and it'll survive all my oS distro upgrades, it would be great.

Hi,
I tried to install all texlive fonts at once and run into problems with zypper and wild cards. The names of the packages are comparable to "texlive-universalis-fonts".

With zypper install 'texlive-fonts':
Paket 'texlive--fonts' nicht gefunden. (no packages found)

with zypper install 'texlive_fonts' or zypper install 'texlive_-fonts' :

200 packages found

So zypper install does not find any packages, if there's a dash in front of the wild card.

This problem does not occur when I search for packages:
zypper se 'texlive-*-fonts' | wc -l
256

zypper se 'texlive*fonts' | wc -l
271

I'm on Tumbleweed with zypper 1.13.4.
thank you!

It's IMO almost a bug that there is no way to figure out which packages require (or recommend, suggest, obsolete) a specific package (or set of packages or capability).

Hello!

Subj.

A couple of days ago, I tried to refresh in mind what zypper key is responsible for dependencies checking. The first idea was zypper check-deps, similary to --clean-deps option in zypper rm command. But the right way was verify key. So, the idea is to add check-deps key as a synonym to verify key, because check-deps seems to be more intuitive.

Thank you!

Whenever zypper is not able to connect to a repo it asks:

Abort, retry, ignore? a/r/i/?:

I'd propose to add an option to remove that repo from the repo list.

Zypper is not displaying correctly when using CJK locales or anything that uses double width characters, the lines are actually displaying over a line's width that a terminal emulator contains.

It might be confusing in my language, well here is a screenshot of what is happening on my screeen.

If you look to the right of a line, the speed indicator is actually displaying on the next line...

Versions of Zypper runtime:

• zypper version 1.12.27
• libzypp version 15.19.7

This is not openSUSE, it is another distribution with RPM as package manager with Zypper as the default admin utility.

So, I am trying to switch from Arch to openSUSE, and I'm being succesful.
Zypper really is good.
The only thing i miss is the interactive search: the possibility to select the packages i want to install right after i searched for my package.

This is an image taken from yaourt's official website which shows the exact function that i'm suggesting:

gcc --version
gcc (Exherbo gcc-4.6.1-r1) 4.6.1
Copyright (C) 2011 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

complete compile log:

http://paste.pocoo.org/raw/505698/

rpm-md is not a real type and seems to make no sense at all. the type should be rpm, I looked to find discussions on why the chosen name was chosen but was unable to do so.

zypper: Symbol `_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE8_M_eraseEPSt13_Rb_tree_nodeISsE' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE8_M_eraseEPSt13_Rb_tree_nodeISsE' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE8_M_eraseEPSt13_Rb_tree_nodeISsE' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE8_M_eraseEPSt13_Rb_tree_nodeISsE' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE8_M_eraseEPSt13_Rb_tree_nodeISsE' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEED1Ev' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEED1Ev' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEED1Ev' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEED1Ev' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEED1Ev' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEED1Ev' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEED1Ev' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEEaSERKS1_' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEEaSERKS1_' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt6vectorISsSaISsEEaSERKS1_' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE8_M_eraseEPSt13_Rb_tree_nodeISsE' causes overflow in R_X86_64_PC32 relocation
zypper: Symbol `_ZNSt8_Rb_treeISsSsSt9_IdentityISsESt4lessISsESaISsEE8_M_eraseEPSt13_Rb_tree_nodeISsE' causes overflow in R_X86_64_PC32 relocation

I'm try to bootstrap opensuse under another linux distr (exherbo) by runnin example script

!/bin/bash

export LC_ALL=C

ROOT=$1
ARCH=$2
VER=$3

umount -f ${ROOT}/sys ${ROOT}/proc ${ROOT}/dev/hugepages ${ROOT}/dev/mqueue ${ROOT}/dev/pts ${ROOT}/dev/shm ${ROOT}/dev

mount -o bind /dev ${ROOT}/dev/

mount -o bind /sys ${ROOT}/sys/

mount -t proc none ${ROOT}/proc/

REPOS=$(cat <<-EOF
yast2 oss http://download.opensuse.org/distribution/${VER}/repo/oss/ oss
yast2 source-oss http://download.opensuse.org/source/distribution/${VER}/repo/oss/ source-oss
yast2 non-oss http://download.opensuse.org/distribution/${VER}/repo/non-oss/ non-oss
yast2 source-non-oss http://download.opensuse.org/source/distribution/${VER}/repo/non-oss/ source-non-oss
rpm-md update http://download.opensuse.org/update/${VER}/ update
rpm-md contrib http://download.opensuse.org/repositories/openSUSE:/${VER}:/Contrib/standard/ contrib
EOF
)

echo "${REPOS}" | while read type name url alias;do
zypper --non-interactive --no-gpg-checks --gpg-auto-import-keys --root ${ROOT} --disable-system-resolvables addrepo --type $type --no-check --name $name --no-keep-packages --refresh $url $alias
done

zypper --non-interactive --no-gpg-checks --gpg-auto-import-keys --root ${ROOT} --disable-system-resolvables refresh

zypper --non-interactive --no-gpg-checks --gpg-auto-import-keys --root ${ROOT} --disable-system-resolvables install --auto-agree-with-licenses --force-resolution -t pattern base

zypper --non-interactive --no-gpg-checks --gpg-auto-import-keys --root ${ROOT} --disable-system-resolvables install --auto-agree-with-licenses --force-resolution -t package db-utils

for f in ls "${ROOT}"/var/lib/rpm/ | grep -v __db | grep -v new; do
db_dump "${ROOT}"/var/lib/rpm/${f} > ${ROOT}/var/lib/rpm/${f}_new;
done

cat > "${ROOT}"/install <<EOF

!/bin/bash

cd /var/lib/rpm;
FILES=$(ls | grep _new | grep -v alternatives)
for f in $FILES; do
r=$(echo $f | sed 's/_new//g');
rm -f $r;
cat $f | db_load $r;
rm $f;
done

rm -f /var/lib/rpm/__db*
/bin/rpm --quiet --rebuilddb

echo 'nameserver 8.8.8.8' > /etc/resolv.conf

zypper --non-interactive --no-gpg-checks --gpg-auto-import-keys refresh
zypper --non-interactive --no-gpg-checks --gpg-auto-import-keys --disable-system-resolvables install --auto-agree-with-licenses --force-resolution -t pattern base
zypper --non-interactive --no-gpg-checks --gpg-auto-import-keys --disable-system-resolvables install --auto-agree-with-licenses --force-resolution -t package db-utils wget ntp vim lsb-release SuSEfirewall2 iputils man bind-utils
EOF

chmod +x "${ROOT}"/install

chroot "${ROOT}" /install

rm -rf "${ROOT}/root/mkimg" "${ROOT}/install"

Hi,

see: http://lists.opensuse.org/opensuse-factory/2016-03/msg00063.html

translations from SLE contain serious bugs that hotkeys were all translated, which caused CJK users have to input some CJK characters for "yes/no/abort/retry..." stuff when there's no input method for CJK existing in TTY.

and I think it's also a packaging bug because I can see you have two branches of translations, but in Tumbleweed zypper uses translations from SLE, which may not what you want.

"download
Download rpms specified on the commandline to a local directory.
Per default packages are downloaded to the libzypp package cache (/var/cache/zypp/packages; for non-root users $XDG_CACHE_HOME/zypp/packages), but this
can be changed by using the global --pkg-cache-dir option.

          In XML output a <download-result> node is written for each package zypper tried to downlad. Upon  success  the  local  path  is  is  found  in  download-result/localpath@path."

The next to last and last sentence are clearly bad written... excluding the typo.
I did understand that when using "zypper -x download" you will have a ""node per package zypper tried to download upon success or failure in the XML output, but I think this sentence could be more clear. But I still don't understand the last sentence, could someone improved this last sentence please ?.

Thanks,

Problem: gcc6-6.0.0+r234449-1.1.x86_64 requires liblsan0 >= 6.0.0+r234449-1.1, but this requirement cannot be provided

  uninstallable providers: liblsan0-gcc6-6.0.0+r234449-1.1.x86_64[repo-oss]

gets translated to

Problem: gcc6-6.0.0+r234449-1.1.x86_64 benötigt libatomic1 >= 6.0.0+r234449-1.1, kann jedoch nicht zur Verfügung gestellt werden

  Deinstallierbare Anbieter: libatomic1-gcc6-6.0.0+r234449-1.1.i586[repo-oss]
                   libatomic1-gcc6-6.0.0+r234449-1.1.x86_64[repo-oss]"

which is obviously wrong, it should be "Nicht installierbare Anbieter" or similiar.

Why the zypper doesn't just run exec('zypper', argv) or so to finish?

can someone please tell me what's going on here? this is baffling to me...and it's my first experience with OpenSuSE in forever...

hubexchange01:~ # zypper in docker
Retrieving repository 'openSUSE-13.2-Non-Oss' metadata ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------[\]
Download (curl) error for 'http://download.opensuse.org/distribution/13.2/repo/non-oss/media.1/media':
Error code: Connection failed
Error message: Could not resolve host: download.opensuse.org

Abort, retry, ignore? [a/r/i/? shows all options] (a): curl ^Chubexchange01:~ # ^C
hubexchange01:~ # curl http://download.opensuse.org/distribution/13.2/repo/non-oss/media.1/media
curl: (6) Could not resolve host: download.opensuse.org
hubexchange01:~ # vi /etc/hosts

===== Start =====
# This really shouldn't change anything...right?
195.135.221.134 download.opensuse.org
====   End   =====

hubexchange01:~ # 
hubexchange01:~ # curl http://download.opensuse.org/distribution/13.2/repo/non-oss/media.1/media
openSUSE
20141025113158
1
hubexchange01:~ #

what in the world?!

still having issues with this image though...so what is actually going on here?

Here's the image I am using...

[user@openstack images]$ wget http://download.opensuse.org/repositories/Cloud:/Images:/openSUSE_13.2/images/openSUSE-13.2-OpenStack-Guest.x86_64.qcow2

[user@openstack images]$  glance image-create --name='OpenSUSE (13.2)' --is-public=true --container-format=bare --disk-format=qcow2 < /home/virt/openstack/backups/images/openSUSE-13.2-OpenStack-Guest.x86_64.qcow2

am I missing something???

v1k

I want to install packages from samba server using wildcards. Now I'm forced to execute ls and parse results by myself. That's inconvenient.

Desired command:

zypper install 'cifs://login:password@server/path/*.rpm'

This applies to FTP/HTTP/HTTPS/etc.

Hi,

if the cmake config of libzypp (aka "Zypp.cmake") is installed at /usr//cmake/Zypp/, we have to make sure that not only Zypp.cmake gets found by zypper's cmake configuration, but also the ZyppCommon.cmake file needs to be properly located.

This patch handles this:
http://anonscm.debian.org/cgit/collab-maint/zypper.git/tree/debian/patches/1001_make-ZyppCommon-cmake-module-includable.patch

Using "zypper --xmlout ..." doesn't return the same information as "zypper ..." does. Example available in in bnc #793424.

I would like to point out that identifiers like "_T" and "_PL" do not fit to the expected naming convention of the C++ language standard.
Would you like to adjust your selection for unique names?

Hi,

I am trying to use /etc/zypp/systemCheck.d to add files which have packages I always want to have installed.

But zypper seems to not respect files inside /etc/zypp/systemCheck.d. Even moving /etc/zypp/systemCheck to /etc/zypp/systemCheck.d, makes glibc ( default required package ) be unprotected.

Am i missing something ?

Also, can we add more than "requires" ? Can we add "recommends" ?

Thanks.

After a crash of zypper, it only informs (when issueing sudo zypper update in OpenSUSE 12.3 with version 1.8.24) that packages X,Y,Z have not been installed while it could print a command how to do this.

Hi,

I'm currently trying to host an openSuSE repository for a project on Sourceforge:

http://sourceforge.net/projects/wolframe/files/repositories/openSUSE_13.1/

When I try to add the repo with zypper I get:

shell> zypper addrepo http://sourceforge.net/projects/wolframe/files/repositories/openSUSE_13.1/wolframe.repo
Problem parsing the file at the specified URI:
/var/adm/mount/AP_0xALC7ig/projects/wolframe/files/repositories/openSUSE_13.1/wolframe.repo: Line 1 is missing '=' sign
Is it a .repo file? See http://en.opensuse.org/Standards/RepoInfo for details.

This error is a follow-up error. It means I got an HTML page as answer
from SourceForge, but not a repository file, so the parser says it's not
a valid repo file.

Setting ZYPP_MEDIA_CURL_DEBUG=1 I was able to track the problem to this:

MediaCurl.cc(doGetFileCopyFile):1389 URL: http://sourceforge.net//projects/wolframe/files/repositories/openSUSE_13.1/wolframe.repo
MediaMultiCurl.cc(doGetFileCopy):1360 HTTP response: 200

I tested manually with curl -v and indeed a double // in the URL after the host name seems to be the problem.

I was wondering if the repo URL can be normalized in MediaCurl.cc?

I'm aware the bug is for 'libzypp', but there the issue management is not enabled.. :-)

A similar error occurs (unsigned repo) when I add wolframe.repo manually and then try to fetch the 'repomd.xml' file its GPG key..

Hi,

in the course of packaging zypper for Debian, I stumbled over a missing man page for zypp-refresh. Please add one.

Thanks,
Mike