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
Why was devel:languages:python/openSUSE_13.1 removed?
I think openSUSE_13.1 is Evergreen.
Regards
Eric
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
Unfortunately, java is a gap in my education. :)
Maybe somebody will point me how to fix the following issue (or even
prepare submit request):
https://build.opensuse.org/build/openSUSE:Leap:42.2:Ports/ports/armv7l/xml-…
This package is required to provide fop (which blocks many packages now).
The error message is the following:
[ 76s] BUILD FAILED
[ 76s]
/home/abuild/rpmbuild/BUILD/xml-commons-1.3.04/xml-commons-1_0_b2/build.xml:49:
The following error occurred while executing this line:
[ 76s]
/home/abuild/rpmbuild/BUILD/xml-commons-1.3.04/xml-commons-1_0_b2/java/external/build.xml:120:
java.lang.IllegalArgumentException: 16877=40755 will not fit in octal
number buffer of length -1292065064
I would say that integer overflow has happened somewhere.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
How is SOURCE_DATE_EPOCH supposed to be used? Is it required to patch
each pkg, or should rather the thing which tweaks Release: during build
also inject a "export SOURCE_DATE_EPOCH=∞" right after the
%build/%install lines?
Olaf
On 06/23/2016 11:58 PM, Greg Freemyer wrote:
> On Thu, Jun 23, 2016 at 11:46 PM, Uzair Shamim <ushamim(a)linux.com> wrote:
>
>> Hi,
>>
>> I'm curious about if it is legal/within rules to distribute Metasploit on
>> OBS? I have been able to get the package to build and so on but I am not
>> sure if this breaks some rule for distribution.
>> Part of my concern is that Metasploit does come bundled with exploits so
>> it could possibly cause issues with the law.
>>
>> Any feedback/answers would be appreciated!
>
>
> Uzair,
>
> It is definitely legal in the US, the concern is German law. OBS restricts
> itself to hosting packages that are legal from both the US and German law
> perspective.
>
> There are some "auditing" tools in OBS that a user can use to attempt to
> hack/crack their website / passwords.
>
> Metasploit is conceptually similar in my mind so it is conceivable.
>
> Do you want it in a home project? devel project? factory?
>
Hi,
For now I would like it in my home repo but it would be nice to get it into at least a devel repo. Besides the legal questions, part of the problem for now is getting some of the ruby libs I need for Metasploit built in my repo and then I would like to submit to devel.
--
Regards,
Uzair Shamim
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi to all!
I'd like to resolve some invalid desktop file warnings about arcade game
level editor and I wonder what category should I set. Upstream provides
single Utility but it is insufficient. Should I set Game;ArcadeGame; or
Categories=Graphics;2DGraphics; or Development;GUIDesigner; or another one?
Any tips are welcomed.
--
Best regards,
Dmitriy Perlow
R&D chemical engineer
Lekpharm JLLC
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
When I am using the suse_update_desktop_file it quotes the parameter in
a wrong way.
E.g. I am using this command:
%suse_update_desktop_file -c "%{name}" "%{name}" "Game with flying
alpaca" "%{name}" jetpaca Game ArcadeGame
Then the resulting command is:
suse_update_desktop_file.sh '-c Jetpaca Jetpaca Game with flying alpaca'
Jetpaca jetpaca Game ArcadeGame
As you can the see the parameter are quoted wrong, so it will fail.
Do I use the macro the wrong way? Thank you for your help!
Regards,
Ferdinand
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
I just want to inform you that I have created a new macro named
go_nostrip at https://github.com/openSUSE/golang-packaging/pull/3.
This macro should be used within the packages which use golang-packaging
to disable the stripping of golang binaries to avoid issues related to
that. Beside that it disables also useless debug sub-packages.
So if you create a package for some golang related tool please use this
macro. Under the hood it just calls one undefine and one define:
%undefine _build_create_debug
%define __arch_install_post export NO_BRP_STRIP_DEBUG=true
If you want to know more about those options read
https://en.opensuse.org/openSUSE:Packaging_guidelines#Debuginfo and
https://github.com/golang/go/issues/1242.
Best,
Thomas Boerger
--
Thomas Boerger <tboerger(a)suse.de>
Docker Developer
SUSE Linux GmbH, Maxfeldstr. 5, D-90409 Nürnberg
Tel: +49-911-74053-0; Fax: +49-911-7417755; https://www.suse.com/
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton,
HRB 21284 (AG Nürnberg)
Hi,
What are the guidelines for packaging udev rules?
1) So far I've found that files should be placed in %{_udevrulesdir}.
2) Should the package call "udevadm control --reload" in %post and
%postun? I've found that there's a macro for this %udev_rules_update
[1]. But I couldn't find any package doing that.
[1]
https://build.opensuse.org/package/view_file/openSUSE:Factory/systemd/macro…
--
Adam Mizerski
Hi,
I'm curious about if it is legal/within rules to distribute Metasploit on OBS? I have been able to get the package to build and so on but I am not sure if this breaks some rule for distribution.
Part of my concern is that Metasploit does come bundled with exploits so it could possibly cause issues with the law.
Any feedback/answers would be appreciated!
--
Thanks,
Uzair Shamim
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org