Hi,
mtr fails for 113 days
jpilot fails for 99 days
python-hacking fails for 98 days
I'm also sending another round of reminder mails.
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 folks,
recently, a lot of PHP packages have been either converted from PEAR
format to composer or offered in both format. Some new software has been
composer-only right from the start.
As far as I know, we only have tools for automatically dealing with PEAR
format packages.
This is going to get worse as the most widely used 3rd party pear server
software, pirum, has been deprecated in favor of composer.
This renders more and more pear based installations useless.
http://pirum.sensiolabs.org/https://twitter.com/fabpot/status/434256189258735616
Do you know how other distributions handle this?
Is there any effort for (semi)automatic composer->rpm conversion tools?
--
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang(a)b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
FYI,
It could apply to kde-mplayer-thumbnailer for openSUSE:Factory
--Glenn
MPlayer 1.1.1 update MPlayer-1.1.1.tar.xz
http://www.mplayerhq.hu/MPlayer/releases/MPlayer-1.1.1.tar.xzhttp://www.mplayerhq.hu/design7/news.html
>From the website:
2013-05-05, Sunday :: MPlayer 1.1.1 update
For those of you sticking to the release version, we recommend to update
to 1.1.1 to avoid security issues. The tar file in the download section
also contains the latest version of the FFmpeg 0.11 release with many fixes
of its own.
If you need a diff of only the fix itself, for example for old versions
you still want or need to maintain please use
svn di -c36242 svn://svn.mplayerhq.hu/mplayer/branches/1.1
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi:
I am trying to build a KMP package for SLES 11 SP3 using IBS.
I am modeling my package after ocfs2, if that helps answer my question.
My package patches the rbd device driver, patching rbd.c, then builds
the rbd.ko kernel module.
I can get this to work on my local system using rpmbuild. My local
system is SLES 11 SP3, and the kernel on it is 3.0.101-0.35-default.
But when I specify SLES 11 SP3 as a build target in IBS, it seems to get
kernel-syms-3.0.76-0.11.1.
This causes patch errors because the 3.0.76 kernel had an older version
of rbd.c.
In my spec file, I have:
BuildRequires: kernel-syms
I have also tried:
BuildRequires: kernel-syms = 3.0.101
and
BuildRequires: kernel-syms >= 3.0.101
I have several questions:
- Why does my system have a newer 3.0.101 kernel and the build
service have an older one?
- Can I specify 3.0.101, or should I just patch against
3.0.76?
- How do I know what kernel a particular OS flavor will use
in general?
--
Lee Duncan
SUSE Labs
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi,
Several people touched build-compare lately and I'm afraid it's right
now completely broken.
I reviewed several build logs and they are all changed with this log:
[ 119s] ... comparing built packages with the former built
[ 119s] /usr/lib/build/rpm-check.sh
[ 119s] compare /.build.oldpackages/xteddy-2.2-22.1.src.rpm /home/abuild/rpmbuild/SRPMS/xteddy-2.2-22.2.src.rpm
[ 119s] compare /.build.oldpackages/xteddy-2.2-22.1.i586.rpm /home/abuild/rpmbuild/RPMS/i586/xteddy-2.2-22.2.i586.rpm
[ 120s] WARNING: no idea about /usr/bin/xteddy
[ 120s] compare /.build.oldpackages/xteddy-debuginfo-2.2-22.1.i586.rpm /home/abuild/rpmbuild/RPMS/i586/xteddy-debuginfo-2.2-22.2.i586.rpm
[ 120s] skipping -debuginfo package
[ 120s] compare /.build.oldpackages/xteddy-debugsource-2.2-22.1.i586.rpm /home/abuild/rpmbuild/RPMS/i586/xteddy-debugsource-2.2-22.2.i586.rpm
[ 121s] comparing /.build.oldpackages/rpmlint.log and /home/abuild/rpmbuild/OTHER/rpmlint.log
After the "no idea about" is a return 1, so this is considered different without an idea.
Greetings, Stephan
--
Ma muaß weiterkämpfen, kämpfen bis zum Umfalln, a wenn die
ganze Welt an Arsch offen hat, oder grad deswegn.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
I try to upgrade Base:System/coreutils to the brand-new 8.23.
Porting the oS-specific patches was easy pie, but I don't know
what the local build error is about:
---------------------------
osc build --clean
Run source service: /usr/lib/obs/service/format_spec_file --outdir /tmp/tmp44yFgX
Run source service: /usr/lib/obs/service/source_validator --outdir /tmp/tmpxUW7Fi
- package has baselibs.conf: (unchanged)
Run source service: /usr/lib/obs/service/format_spec_file --outdir /tmp/tmpIHn9Hq
Run source service: /usr/lib/obs/service/source_validator --outdir /tmp/tmp9de0QK
- package has baselibs.conf: (unchanged)
Building coreutils.spec for openSUSE_Factory/x86_64
Getting buildinfo from server and store to
/media/sdb5/berny/osc/Base:System/coreutils/.osc/_buildinfo-openSUSE_Factory-x86_64.xml
Getting buildconfig from server and store to
/media/sdb5/berny/osc/Base:System/coreutils/.osc/_buildconfig-openSUSE_Factory-x86_64
buildinfo is broken... it says:
unresolvable: nothing provides perl(:MODULE_COMPAT_5.18.2) needed by vim, nothing provides perl = 5.18.2 needed by vim
---------------------------
There's definitely no BuildRequires:vim in the spec, so why
is it trying to install vim in the local build environment?
Any hint?
Thanks & have a nice day,
Berny
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi *,
I remember some time ago someone mentioning here that
projects are encouraged to use git underneath osc.
Is there a tutorial in the wiki - I can't find it.
Thanks & have a nice day,
Berny
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi all,
FYI, I have successfully compiled an AVR cross-compiler using the
generic template in devel:gcc (well, after fixing it slightly). I even
submitted it back to devel:gcc, and the request got accepted. So, at
least the compiler could be maintained in devel:gcc, rather than making
a private copy in CrossToolchain:avr.
However, to make this actually work, some more packages in
CrossToolchain:avr would have to be adjusted. Before I start doing
that, is there a reason to keep a separate gcc in CrossToolchain:avr?
Petr Tesarik
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi List,
I have been using an amazing plugin called YouCompleteMe for [G]VIM
for the past few months and it has been really helpful.
However, setting it up is not so straight-forward. It needs inclusion
of new llvm etc. The instructions are all documented at the project
page though https://github.com/Valloric/YouCompleteMe
I set it up once and was using it for the last few months. Bu sadly
for some reason, I had to re-format my machine and lost the setup. I
tried setting the plugin again and got lost somewhere. The plugin is
not loading for some reason.
I have seen some plugins are maintained for openSUSE as rpms (such as
nerdtree etc.). So, I come with a request to the very helpful
packagers to consider shipping the YouCompleteMe as a rpm for
openSUSE.
Also, I wonder if it will be possible to use docker and package vim
with a set of extensions, as a single docker app too. I have not
experimented on it though. I just thought it will be a good idea and
if someone has experimented it.
Thanks.
--
Sankar P
http://psankar.blogspot.com
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hello,
Can this be fixed in Kernel:HEAD > kernel-vanilla [1]
https://build.opensuse.org/package/show/Kernel:HEAD/kernel-vanilla
--Glenn
[1] from the logs:
[13253s] Installed (but unpackaged) file(s) found:
[13253s]
/lib/modules/3.16.0-rc3-3.g56ffa43-vanilla/vdso/.build-id/cd/13830f6725593601cdee3f0d295bc581b5a37c.debug
[13253s]
/lib/modules/3.16.0-rc3-3.g56ffa43-vanilla/vdso/.build-id/e8/258ac9117d258e3c1eca59605b6447eddb72a9.debug
[13257s] [13192.875644] SysRq : Power Off
[13257s] [13193.048200] reboot: Power down
[ 6544s] Installed (but unpackaged) file(s) found:
[ 6544s]
/lib/modules/3.16.0-rc3-3.g56ffa43-vanilla/vdso/.build-id/28/a15788db55e6c4a0c3613097bf4131db7c49db.debug
[ 6544s]
/lib/modules/3.16.0-rc3-3.g56ffa43-vanilla/vdso/.build-id/34/fd941315b74714a22cd6ccebd57d26913b0e75.debug
[ 6544s]
/lib/modules/3.16.0-rc3-3.g56ffa43-vanilla/vdso/.build-id/52/ac7e7499d67c48d50f96f3ed9c00c9aa990160.debug
[ 6544s]
/lib/modules/3.16.0-rc3-3.g56ffa43-vanilla/vdso/.build-id/d0/8983a32980f8a5b9c442de9878b782a4007aee.debug
[ 6544s]
/lib/modules/3.16.0-rc3-3.g56ffa43-vanilla/vdso/.build-id/f4/92f5e0b90d47240a5b98cf5b1baf2f743ca529.debug
[ 6548s] [ 6503.940652] SysRq : Power Off
[ 6548s] [ 6503.943426] reboot: Power down
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org