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
Is anyone working on (or thinking of working on) making our build
process reproducible?
https://reproducible-builds.org/
It seems Debian and Fedora are already part of the project, and the
advantages are quite compelling, not just from a security perspective,
but also due to the potential savings in storage and network
consumption:
https://hackweek.suse.com/13/projects/131
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
I have stumbled over a small problem regarding versioned directories.
Currently, it is expected a versioned library uses a pattern like /usr/lib/
libfoo-1_2_3/bar.so. Although this allows multiple packages, it is contrary to
what some upstreams use for versioning, e.g. /usr/lib/libfoo/1.2.3/bar.so.
From an RPM perspective, both are ok, as directories can be owned by multiple
packages. rpmlint throws an "W: shlib-policy-nonversioned-dir" warning, which
is IMHO wrong.
Kind regards,
Stefan
--
Stefan Brüns / Bergstraße 21 / 52062 Aachen
home: +49 241 53809034 mobile: +49 151 50412019
work: +49 2405 49936-424
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello.
source and target locations to copy a file query ?
Tried following but failed:
How to reference a source and target location ?
--Thanks Glenn
--spec
https://build.opensuse.org/package/view_file/home:doiggl/reiser4progs/reise…
Attached file to package.
Try to copy file before build.
cp -v /./.build-srcdir/fsckp.c
%{buildroot}/reiser4progs-1.1.0/progs/mkfs/fsck.c
--log
https://build.opensuse.org/package/live_build_log/home:doiggl/reiser4progs/…
[ 58s] + cp -v /./.build-srcdir/fsckp.c
/home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.1.0-57.1.x86_64/reiser4progs-1.1.0/progs/mkfs/fsck.c
[ 58s] '/./.build-srcdir/fsckp.c' ->
'/home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.1.0-57.1.x86_64/reiser4progs-1.1.0/progs/mkfs/fsck.c'
[ 58s] cp: cannot create regular file
'/home/abuild/rpmbuild/BUILDROOT/reiser4progs-1.1.0-57.1.x86_64/reiser4progs-1.1.0/progs/mkfs/fsck.c':
No such file or directory
[ 58s] error: Bad exit status from /var/tmp/rpm-tmp.8FNW3M (%prep)
[ 58s]
[ 58s]
[ 58s] RPM build errors:
[ 58s] Bad exit status from /var/tmp/rpm-tmp.8FNW3M (%prep)
[ 58s]
[ 58s] morla1 failed "build reiser4progs.spec" at Wed Dec 30 05:12:01
UTC 2015.
[ 58s]
[ 58s] ### WATCHDOG MARKER START ###
[ 62s] [ 51.503928] SysRq : Power Off
[ 62s] [ 51.603796] reboot: Power down
[ 63s] ### WATCHDOG MARKER END ###
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi. I noticed quite a few packages with disabled debuginfo in obs
(namely libqt4-x11-debuginfo) Is this something temporal?
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi there,
in the recent issue of the important German computer magazine c't was an
article about "stopmotion".
Unfortunately openSuse's Education repository provides only a package
for version 0.6.2 which is three years old. The current version 0.8.0 is
not yet packed. Could someone be so kind and create an updated openSuse
package?
Thanks
Christoph
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Is there a reason why various projects build for SP3 and SP4 instead of
just a generic "SLE_11" target? I think the service packs are compatible
when used as a build environment. In packman, devel:languages:ocaml and
Virtualization only the generic "SLE_11" and "SLE_12" targets exist for
that reason.
Since SUSE:SLE-12-SP1:Update already exists (not sure if its already
populated) I wonder if it makes sense to adjust just the paths in the
existing "SLE_12" repositories instead of creating a new "SLE_12_SP1"
repositories in the devel projects.
Also I wonder why multimedia:libs builds for SP3 and SP4, instead of
just SLE_11.
Olaf
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Is this on purpose? It exists for 13.1, 13.2 and TW. kdebase3-SuSE requires it.
--
"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
Hi,
I'm trying to build a webfrontend based on nodejs:
https://build.opensuse.org/package/show/Application:ERP:Tryton:3.8/tryton-s…
not sure yet - my first try with nodejs - if it runs and installs correctly,
but at least it builds correct - for opnSUSE 13.2.
For Leap and the rest of the world it fails, as %{nodejs_modulesdir} is not
getting resolved properly.
Anybody an idea what it could be?
TIA!
Axel
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
My question is, where does openSUSE store its "official" RPM groups?
In raw rpm, it's in /usr/share/doc/packages/rpm/GROUPS, which hasn't
been changed since RH 9.
But openSUSE extends it a lot...we have many own groups...
I would like to know where I can find it, and how can I extend them.
eg: There're a lot of new desktop environments coming out during
recent years, like Cinnamon/Mate/LXQt...
They deserve their own RPM groups instead of landing in System/GUI/Other,
which make that tag a total mess in YaST software management.
Same happens to Devel/Lanaguages/Other too, now all of the Go/Nodejs
packages landing under that tag.
I just modified one or two of my packages to use a new group like:
Devel/Languages/Go, and I didn't see any rpmlint errors/warnings.
But I still want to know the official procedure to update RPM Groups
in openSUSE.
Thanks
Marguerite
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org