TW
$SUBJECT can't be right, but trying to zypper rm opensans wants to remove
releasenotes. :-(
--
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata *** http://fm.no-ip.com/
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
What are the options to uninstall a removed package?
With SR#390485 the meta pkg "ffmpeg-devel" was removed. There is no
package which would be a good place for the usual 'Obsoletes/Provides'.
So I wonder how to run the 'zypper rm ffmpeg-devel' during 'zypper dup'.
Olaf
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Current cucumber requires gherkin 3.2, which is tagged on github since a
few months. But on rugygems.org the version is still at 3.1.2. As a
result plain gem2rpm wont pick it up, and current cucumber can not be
installed.
What is the workflow to package an inofficial rubygem?
gem2rpm --help gives no hints.
Olaf
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
> If they are created dynamically the uid/gid will vary.
>
> Is this requirement no more needed in newer ceph ?
Well, first of all the use of "ceph" user and group for the Ceph
daemons is itself very new.
Second, although Fedora and Debian agreed to reserve 167 as the
UID/GID for ceph, we were unable to get this reservation in SUSE.
The way I have the scriptlet set up now, it first tries to create the
ceph user and group with UID and GID 167. If that fails because 167 is
taken on the system, then it falls back to dynamic generation.
HTH,
Nathan
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
We build packages on OpenSuSE Build Service. The successful builds end up
in http://download.opensuse.org/repositories/home:/cmft/
But we want also to be able to selectively install previous versions of
our packages (even if they just differ in the "Release" number, which we
auto-change with "Release: 1%{?dist}" in the spec file), and
unfortunately, the repodata of
http://download.opensuse.org/repositories/home:/cmft/ only contains the
latest release.
So we tried to create our own local mirror of
http://download.opensuse.org/repositories/home:/cmft/ where we do not
remove any file and we recreate the repodata info with "createrepo
--update".
According to https://en.opensuse.org/openSUSE:Mirror_infrastructure , the
OSB home directories can be rsynced publicly from:
rsync.opensuse.org::buildservice-repos/home:/
But if we try it, we find that the home dirs are not there:
~~~
rsync rsync.opensuse.org::buildservice-repos/home:/
(...)
rsync: change_dir "/home:" (in buildservice-repos) failed: No such file or
directory (2)
~~~
Note that the home dirs can be found here:
rsync ftp5.gwdg.de::pub/opensuse/repositories/home:/cmft/
BUT "ftp5.gwdg.de" mirror seems to update only once or a few times a day,
and when it updates, it only fetches the latest build, so we end up
missing builds if we sync against this mirror.
So my question is: is there any server where I can find all the successful
builds of our packages?
Or... is there any other way to get all the successful builds?
Thanks a lot!
Zibi
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
some weeks ago I tried to clean up the duplicate packages of libtar in
Office, Education and Archiving. Back then Ismail told me, I should ask
the maintainers to create a link from Archiving to Office, similar to
what he did in Education. His request 353986 got accepted, but
eventually Education/libtar was removed.
Yesterday I was promoted as the maintainer of Office/libtar to create
the link myself. But I am now confused and ask for advice.
1) Why was Education/libtar removed? It was just a link. Now stopmotion
is broken because it cannot resolve libtar-devel.
2) What should I do with Office/libtar? Remove it, similar to
Education/libtar? Or create a _link to Archiving/libtar? Or an _aggregate?
3) How to fix stopmotion in the long run?
4) Are other packages in Education broken as they require libtar?
Bye and thanks
Christoph
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi!
I found this bug: https://bugzilla.suse.com/show_bug.cgi?id=977058
concerning this package
https://build.opensuse.org/package/show/server:http/polipo
IMHO it's just about calling the %fillup_only script correctly to ensure
the config file is written to /etc/sysconfig/ upon installation.
The problem might be that the sysconfig file does not match the package
name and I cannot figure out how to use %fillup_only in such a case.
Can anyone have a look?
BR
Thomas
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
I would like to disable TSL/SSL checks for osc. My SSL configuration
is broken and I don't care about security at the moment.
I added sslcertck = 0 to ~/.oscrc, but it doesn't help.
> cat /etc/issue.net
Welcome to openSUSE 13.1 "Bottle" - Kernel %r (%t).
> osc --version
0.152
Of course I can update my osс (build git version), but maybe is there
some more simple way to do that?
I use official OBS Applience image
http://download.opensuse.org/repositories/OBS:/Server:/2.6/images/iso/obs-s…
Cheers,
Alex
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
You may have noticed that GCC 6 packages appeared in Factory (but gcc
used for building packages still points to GCC 5). Somewhen in
January I set up openSUSE:Factory:Staging:Gcc6 where GCC 6 is used
to build packages. The status of that is that it depends on the
glibc update pending in Staging:B and it still requires fixing a few
packages, mostly -Werror related. There was a point in time where
openQA was green for x86_64 (and Minimal-X).
Once Staging:B has been accepted I'll formally submit an update
to gcc to make it point to GCC 6 thus obsoleting the above Staging:Gcc6.
That staging can nevertheless be used to look at the current FAILs
which are
build failed
cluster-glue failed
elfutils failed
espeak failed
gdb failed
jack failed
libyui failed
llvm failed
mozilla-nss failed
pesign failed
python3-base failed
xen failed
and can also be caused by the glibc update which I pulled into
Staging:Gcc6.
Any help is appreciated.
Richard.
--
Richard Biener <rguenther(a)suse.de>
SUSE LINUX GmbH, GF: Felix Imendoerffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nuernberg)
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
To CEGUI package mainteiners,
Hi,
This is Yaron Cohen-Tal from the CEGUI team. 0.8.5 introduced a
critical bug, therefore we've just released 0.8.6, shortly after
0.8.5, which fixes that bug and contains a few more minor fixes.
You're advised to update your packages, especially if you use 0.8.5.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org