Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-09 Thread Christiaan Welvaart

On Mon, 8 Apr 2013, Juergen Harms wrote:


On 04/06/2013 06:35 AM, andre999 wrote:

did a little research to hopefully help a bit, on packages still in the
list.
( used http://rpmfind.net/linux/ )



cross-avr-gcc


See bugzilla: https://bugs.mageia.org/show_bug.cgi?id=7825

Looks like an incompatibilty between the object gcc (which is now 4.7.2) and 
the target gcc (the specfile still pulls in 4.6.2).


To make cross-avr-gcc build
- cross-avr-binutils (which is used as a dependency) must be rebuilt
 to use binutils-2.23 (the present cross-avr-binutils uses 2.20),

2.23.2 I guess?


- cross-avr-gcc must be re-built to use gcc-4.7.2 (and some tweeks - see
 bugzilla 7825)

We don't really have a choice here (:


I have locally made such a build and successfully use it in production
for building the software for my AVR cpus (attached my specfile = attachment 
3044).


The reasons why I did not submit my local build are that there are some 
serious rpmlint warnings (serious at least for cross-avr-binutils: complaints 
about the use of hardlinks) which I did not manage to get rid of - but also 
that I did not want to interfere with the work of the maintainer.


The current package has the same rpmlint warnings so you don't need to fix 
this right now INHO. The hardlinks are only a problem when /usr/bin is on 
a different filesystem than /usr. I don't actually maintain these 
packages so you will likely end up being the maintainer.


avr-libc doesn't need to be updated?


Christiaan


Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-09 Thread Juergen Harms

On 04/09/2013 11:03 AM, Christiaan Welvaart wrote:
 The current package has the same rpmlint warnings so you don't need
 to fix this right now INHO. The hardlinks are only a problem when
 /usr/bin is on a different filesystem than /usr. I don't actually
 maintain these packages so you will likely end up being the
 maintainer.
 ... We don't really have a choice

Yes, then replicating my local bricolage into cauldron looks like an 
adequate solution. I just verified: the packages still build without 
throwing errors (but now additionally need lib64mpfr-devel and 
lib64mpc-devel as BuildRequires). But: don't we have release-freeze 
since April 7? An alternative would be to pick this up as a bugfix for 
bugzilla 7825 once Mageia 3 is out (I guess that policy allows to bring 
in new upstream releases in such a case) - a pity we did not discuss 
this earlier.


And no, I don't think that I am a good candidate for the maintainer: I 
am not a compiler virtuoso, and 76 is too close to system freeze, better 
find somebody younger (but I do what I can to help out).


 avr-libc doesn't need to be updated?

avr-libc-1.7.1-3.mga still works ok. I just saw that 1.8.0 has been 
released in January and would certainly be of interest since it adds 
support for new processors. Given release freeze that probably would 
mean a backport after the release.


Juergen


Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-09 Thread Juergen Harms

On 04/09/2013 11:03 AM, Christiaan Welvaart wrote:

... cross-avr-gcc ...

The current package has the same rpmlint warnings so you don't need to
fix this right now INHO. The hardlinks are only a problem when /usr/bin
is on a different filesystem than /usr.


I see there are still packages being pushed - if I manage tomorrow to 
submit a new cross-avr-gcc, would that still have a chance to get pushed 
before the freeze? would be nice if Mageia-3 contains a properly working 
avr cross compiler - and would reduce the count of packages that dont build.


(no need to upgrade the avr-binutils package from 2.20 to 2.23 to 
satisfy that dependency: cross-avr-gcc seems to build and work correctly 
with cross-avr-binutils-2.20 which is presently in cauldron).


Juergen



Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-09 Thread Pierre-Malo Deniélou

On Tue 09 Apr 2013 23:07:38 CEST, Juergen Harms wrote:

On 04/09/2013 11:03 AM, Christiaan Welvaart wrote:

... cross-avr-gcc ...

The current package has the same rpmlint warnings so you don't need to
fix this right now INHO. The hardlinks are only a problem when /usr/bin
is on a different filesystem than /usr.


I see there are still packages being pushed - if I manage tomorrow to
submit a new cross-avr-gcc, would that still have a chance to get
pushed before the freeze? would be nice if Mageia-3 contains a
properly working avr cross compiler - and would reduce the count of
packages that dont build.

(no need to upgrade the avr-binutils package from 2.20 to 2.23 to
satisfy that dependency: cross-avr-gcc seems to build and work
correctly with cross-avr-binutils-2.20 which is presently in cauldron).


If you test that your updated package works ok, and argue it well, it 
will be pushed.

--
Malo




Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-09 Thread Pascal Terjan
On Tue, Apr 9, 2013 at 11:07 PM, Juergen Harms juergen.ha...@unige.chwrote:

 On 04/09/2013 11:03 AM, Christiaan Welvaart wrote:

 ... cross-avr-gcc ...


 The current package has the same rpmlint warnings so you don't need to
 fix this right now INHO. The hardlinks are only a problem when /usr/bin
 is on a different filesystem than /usr.


 I see there are still packages being pushed - if I manage tomorrow to
 submit a new cross-avr-gcc, would that still have a chance to get pushed
 before the freeze? would be nice if Mageia-3 contains a properly working
 avr cross compiler - and would reduce the count of packages that dont build.


Well, given that current version can not even be installed, I don't think
anyone will argue against getting the package pushed, it can't be worse.

(no need to upgrade the avr-binutils package from 2.20 to 2.23 to satisfy
 that dependency: cross-avr-gcc seems to build and work correctly with
 cross-avr-binutils-2.20 which is presently in cauldron).

 Juergen




Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-09 Thread Thomas Backlund

Pascal Terjan skrev 10.4.2013 00:23:



On Tue, Apr 9, 2013 at 11:07 PM, Juergen Harms juergen.ha...@unige.ch
mailto:juergen.ha...@unige.ch wrote:

On 04/09/2013 11:03 AM, Christiaan Welvaart wrote:

... cross-avr-gcc ...


The current package has the same rpmlint warnings so you don't
need to
fix this right now INHO. The hardlinks are only a problem when
/usr/bin
is on a different filesystem than /usr.


I see there are still packages being pushed - if I manage tomorrow
to submit a new cross-avr-gcc, would that still have a chance to get
pushed before the freeze? would be nice if Mageia-3 contains a
properly working avr cross compiler - and would reduce the count of
packages that dont build.


Well, given that current version can not even be installed, I don't
think anyone will argue against getting the package pushed, it can't be
worse.



And since avr stuff is also pretty selfcontained its ok.

--
Thomas




Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-08 Thread Juergen Harms

On 04/06/2013 06:35 AM, andre999 wrote:

did a little research to hopefully help a bit, on packages still in the
list.
( used http://rpmfind.net/linux/ )



cross-avr-gcc


See bugzilla: https://bugs.mageia.org/show_bug.cgi?id=7825

Looks like an incompatibilty between the object gcc (which is now 4.7.2) 
and the target gcc (the specfile still pulls in 4.6.2).


To make cross-avr-gcc build
- cross-avr-binutils (which is used as a dependency) must be rebuilt
  to use binutils-2.23 (the present cross-avr-binutils uses 2.20),
- cross-avr-gcc must be re-built to use gcc-4.7.2 (and some tweeks - see
  bugzilla 7825)

I have locally made such a build and successfully use it in production
for building the software for my AVR cpus (attached my specfile = 
attachment 3044).


The reasons why I did not submit my local build are that there are some 
serious rpmlint warnings (serious at least for cross-avr-binutils: 
complaints about the use of hardlinks) which I did not manage to get rid 
of - but also that I did not want to interfere with the work of the 
maintainer.


Juergen


Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-06 Thread Bruno Cornec
Johnny A. Solbu said on Fri, Apr 05, 2013 at 10:10:33AM +0200:
 project-builder
 rpmbootstrap

Ok, retried tonight and it seems that the required dep
perl-ProjectBuilder has been submitted, so these 2 should disappear.

Bruno.
-- 
Open Source  Linux Profession Lead EMEA http://opensource.hp.com
EMEA Open Source HPISC Chief Technologisthttp://hpintelco.net
FLOSS projects: http://mondorescue.org http://project-builder.org 
Musique ancienne? http://www.musique-ancienne.org http://www.medieval.org


pgpd9ZcPsjCLQ.pgp
Description: PGP signature


Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-05 Thread Sandro CAZZANIGA
Le 05/04/2013 10:10, Johnny A. Solbu a écrit :
 http://check.mageia.org/cauldron/dependencies.html
 
 According to the link above, there are 14 packages that needs to be fixed, or 
 removed.
 I have looked at most of them, and I can't figure out how to fix them, the 
 maintainers doesn't seem to be working on them and apparently doesn't respond 
 to email. Or they are to busy to work on the packages.
 All of these packages have broken dependencies, that I am unable to figure 
 out. (E.g some have versioned dependencies not listed in spec,)
 
 Here is the list of packages with missing dependencies that need fixing:
 (If they are not fixed by sunday, which is the scheduled releaase freeze, 
 what should be done with them?)
 
 openstack-glance
 openstack-keystone

I'm the maintainer of those two, I'll take care.

Thanks.


-- 
Sandro Cazzaniga
Jabber: kha...@jabber.fr
Twitter: @Kharec



signature.asc
Description: OpenPGP digital signature


Re: [Mageia-dev] Upcoming release freeze: 14 packages needs fixing, by Sunday

2013-04-05 Thread andre999

Johnny A. Solbu a écrit :

http://check.mageia.org/cauldron/dependencies.html

According to the link above, there are 14 packages that needs to be fixed, or 
removed.
I have looked at most of them, and I can't figure out how to fix them, the 
maintainers doesn't seem to be working on them and apparently doesn't respond 
to email. Or they are to busy to work on the packages.
All of these packages have broken dependencies, that I am unable to figure out. 
(E.g some have versioned dependencies not listed in spec,)

Here is the list of packages with missing dependencies that need fixing:
(If they are not fixed by sunday, which is the scheduled releaase freeze, what 
should be done with them?)



did a little research to hopefully help a bit, on packages still in the 
list.

( used http://rpmfind.net/linux/ )



chiliproject

spec says the following rubygems libraries :
 coderay = 0.9.7 ; but error msg says 1.0.8 installed
 rack = 1.1.2 ; but error msg says 1.4.5 installed
 rails = 2.3.14 ; but error msg says 3.2.13 installed
Note that there is a comment somewhere in the documentation that 
chiliproject doesn't work with rail 3.x.


Cauldron has version 2.3.0 (as for mga2),
but upstream is at 2.11.0 or 3.8.0 (both published 2013/03/19)
For 2.x up, there is a module that is supposed to determine the required 
versions.  (see below)


Some upstream pages :
https://www.chiliproject.org/projects/chiliproject
https://www.chiliproject.org/projects/chiliproject/files
https://www.chiliproject.org/projects/chiliproject/wiki/Installation
https://www.chiliproject.org/projects/chiliproject/wiki/Requirements



cross-avr-gcc

libmgc.so.2 not found
libmgc.so in xfce4-mpc-plugin-0.4.4-2.mga3.i586.html
+  qmmp-musepack-0.5.4-1.mga2.i586.html
+  qmmp-musepack-0.5.4-1.mga2.tainted.i586.html
+  qmmp-0.6.8-1.mga3.i586.html
+  qmmp-0.6.8-1.mga3.tainted.i586.html
But libmgc.so.2 not found by rpmfind



mcabber

libotr.so.2 not found
in libotr2-3.2.0-5.2.mga2.i586.html



openstack-glance

package = python-glance
upstream doesn't seem to package even tarballs.
in fedora/updates/18/x86_64/python-glance-2012.2.3-1.fc18.noarch.html
an upgrade will probably correct the 3 version error messages

pysendfile not found
in fedora/devel/rawhide/src/p/pysendfile-2.0.0-5.fc19.src.html (not in mga)
site = http://code.google.com/p/pysendfile/

python-crypto not found
in fedora/devel/rawhide/src/p/python-crypto-2.6-5.fc19.src.html (not in mga)
site = http://www.pycrypto.org/

pythonegg(kombu) not found
Maybe part of newer version of python-glance ?



openstack-keystone
pythonegg(sqlalchemy) found with incorrect range == 0.7.10 (needed = 
0.7.9)
newer version in 
fedora/updates/18/x86_64/openstack-keystone-2012.2.3-3.fc18.noarch.html

( cauldron has 2012.2.1-2 )



perl-B-C

perlapi-5.14.2 not found
It is in CPAN  http://search.cpan.org/dist/B-C



perl-Task-Dist-Zilla

perl(Dist::Zilla::PluginBundle::CJM) not found
according to CPAN, it is a depreciated module for CJM
Maybe see jquelin about this ?



prosody

/usr/bin/lua not found
Must be a missing requires, since that is where lua is installed.
(I thought lua was required on mageia ?)



qutecom

upstream site is no longer accessible
libavcodec.so.53 not found
in libavcodec53 in mga2 core + tainted ; missing requires ?

libavutil.so.51 not found
in libavutil51 in mga2 ; missing requires ?

libboost_program_options-mt.so.1.48.0 not found
in libboost_program_options1.48.0 ; missing requires ?

libboost_serialization-mt.so.1.48.0 not found
in libboost_serialization1.48.0 ; missing requires ?

libboost_signals-mt.so.1.48.0 not found
in libboost_signals1.48.0 ; missing requires ?

libboost_thread-mt.so.1.48.0 not found
in libboost_thread1.48.0 ; missing requires ?



redmine

ruby-ruby-debug not found
in mga1 and mga2, tagged only mga1 ; removed from cauldron ?



x11-driver-video-newport

xserver-abi(videodrv-12) not found
???



x11-driver-video-sisimedia

xserver-abi(videodrv-11) not found
???


--
André