Hi,
how would I handle a -doc subpackage with the new singlespec approach?
I guess we want the -doc package only once (it doesn't depend on the
python interpreter version).
I looked at the current specs and eg. python-six has a extra .spec file
for building the doc package. I would prefer to build the -doc as
subpackage while building the main packages.
Best,
Tom
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
What causes this problem ?
The perl works.
Where do I get the needed perl module - url please ?
Thanks
--Glenn
--
build soecfile:
https://build.opensuse.org/package/view_file/devel:languages:perl/perl-Gedc…
urls:
https://build.opensuse.org/package/show/devel:languages:perl/perl-Gedcomhttps://build.opensuse.org/package/binaries/devel:languages:perl/perl-Gedco…
# rpm -ivhU perl-Gedcom-1.20-1.2.noarch.rpm
warning: perl-Gedcom-1.20-1.2.noarch.rpm: Header V3 DSA/SHA1 Signature,
key ID dcef338c: NOKEY
error: Failed dependencies:
perl(:MODULE_COMPAT_5.18.2) is needed by
perl-Gedcom-1.20-1.2.noarch
# zypper in perl-Gedcom-1.20-1.2
Loading repository data...
Reading installed packages...
Resolving package dependencies...
Problem: perl-Gedcom-1.20-1.2.noarch requires perl(:MODULE_COMPAT_5.18.2),
but this requirement cannot be provided
uninstallable providers: perl-5.18.2-5.6.x86_64[leap42-2]
Solution 1: Following actions will be done:
deinstallation of limal-nfs-server-perl-1.6.3-7.1.1.x86_64
downgrade of perl-Config-Crontab-1.33-5.1.1.noarch to
perl-Config-Crontab-1.33-4.2.noarch
deinstallation of limal-perl-1.6.3-10.1.1.x86_64
deinstallation of yast2-dbus-client-2.22.0-4.1.1.x86_64
Solution 2: do not install perl-Gedcom-1.20-1.2.noarch
Solution 3: do not install perl-Gedcom-1.20-1.2.noarch
Solution 4: break perl-Gedcom-1.20-1.2.noarch by ignoring some of its
dependencies
Choose from above solutions by number or cancel [1/2/3/4/c] (c): c
#
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
I have an request for an package from factory to leap.
In WEbui i see for the package a older version since actuall in factory.
In displayed code is 0.10.2 and when i click above on submit package line i
see 0.11.1
Will now 0.11.1 got to leap or 0.10.2 when i aprove?
Request is: https://build.opensuse.org/request/show/458111
--
Gruß
eRiC
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
As most of you will be painfully aware - our process for legal reviews
is at its limits.
This is nothing new, but meanwhile the situation is so bad, that a new
package requires months to pass Factory review and this is just nothing
I could stand watching.
So I'm in the process of redefining the legal process and the tools
used for it - and it will mean some changes for packages. Some for the
better, but some for the worse.
The legal-auto bot so far only checked one thing: does it know the
package name with the same license. If not, it would redirect the review
to legal-team, which was overwhelmed by the stupid bot.
So what we needed was a more clever bot. So this is what we're working
on - but it will not happen in days. The problem deserves too much care
to rush it.
But we will introduce new features step by step - and it will mean for
now that reviews of legal-auto will stay open longer than what you are
used to. And we also check different things as legal-auto actually
checks the licenses itself and no longer redirects blindly.
One of the consequences is that we now check something automatically
that was checked only manually so far: if sub-packages have sub-licenses.
Take ant-antlr.spec - its source rpm has License: Apache-2.0, but it
has a ant-javamail sub-package with CDDL-1.0. So the bot will not accept
this package, because the sub-package has a license not part of the
sources license.
The proper fix is to have
License: Apache-2.0 AND CDDL-1.0
Right now we're not declining requests - but we will shortly. So don't
be surprised!
I hope to have good news too soonish ;)
Greetings, Stephan
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
If I try to build a package with gcc6 on Leap 42.2 I get this error:
conflict for provider of libgcc_s1 >= 6.1.1+r238085-1.12 needed by gcc6,
(provider libgcc_s1-gcc6 is conflicted by installed libgcc_s1)
With this in the spec file:
BuildRequires: SDL-devel
BuildRequires: cmake
BuildRequires: gcc6-c++
BuildRequires: libbz2-devel
BuildRequires: libmikmod-devel
BuildRequires: libmng-devel
BuildRequires: libogg-devel
BuildRequires: libpng-devel
BuildRequires: libtheora-devel
BuildRequires: libvorbis-devel
BuildRequires: lua51-devel
BuildRequires: sqlite3-devel
BuildRequires: zlib-devel
Am I missing something or what am I doing wrong?
Best regards,
Ferdinand
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
What should be done if for some reason a request was accepted to the
package which is a link to another one? Is there any way to undo that or
is it necessary at all? I'm talking about KDE:Qt5/python-sip and
KDE:Qt5/python3-sip packages.
The later one links to the former one and request for update was
accepted for the python3-sip package. What would be the right way to
solve this?
Regards,
Mikhail
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
As quoted by a contributor ...
If nobody cares, why should I?
Did we lost all our maintainers there ?
btw what is the status for merged python stuff ?
--
Bruno Friedmann
Ioda-Net Sàrl www.ioda-net.ch
Bareos Partner, openSUSE Member, fsfe fellowship
GPG KEY : D5C9B751C4653227
irc: tigerfoot
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
This is low priority because I may be the only user of python-plaso,
and I install it from security:forensics, not factory.
Factory got an update of python-construct in the last few months.
My "python-plaso" package now fails in factory. I've branched an
older version of python-construct to the security:forensics repo
(where python-plaso lives) and it is passing self-tests as well as
some basic interactive tests.
But the version of python-plaso in factory is INOP.
Is there anything to be done? Or just wait for upstream to release a
new version that supports the newest version of python-construct.
Thanks
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
All
I'm not a python programmer, but I package several python apps.
I'm trying to run log2timeline.py which I have packaged in
security:forensics as part of the python-plaso package.
The self tests all run.
When I try to run the main app, it immediately fails:
=====
> log2timeline.py
Traceback (most recent call last):
File "/usr/bin/log2timeline.py", line 24, in <module>
from plaso.frontend import log2timeline
ImportError: cannot import name log2timeline
======
It should be giving me a syntax error since it requires arguments, but
its not getting that far in the code.
I've used it in the past, but it may have been a year or more under oS
13.2. This is with LEAP 42.2
It's obviously croaking on line 24. The first 30 lines of log2timeline.py are:
==================================
> head -30 /usr/bin/log2timeline.py
#!/usr/bin/python
# -*- coding: utf-8 -*-
"""The log2timeline command line tool."""
import argparse
import logging
import multiprocessing
import sys
import time
import textwrap
try:
import win32console
except ImportError:
win32console = None
from dfvfs.lib import definitions as dfvfs_definitions
import plaso
from plaso import dependencies
from plaso.cli import extraction_tool
from plaso.cli import tools as cli_tools
from plaso.cli import views as cli_views
from plaso.frontend import log2timeline
from plaso.lib import definitions
from plaso.lib import errors
from plaso.lib import pfilter
=====================================
Thanks for any insight.
Thanks
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
does anyone have the right specfile-syntax to tackle the above issue?
Tried various things but did not get the right one....
Thanks
Axel
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org