I just noticed that both wcstools-devel and wcslib-devel create libraries
named libwcs which causes a problem in linking to libwcs.so
Wondering if you have any thoughts on resolving the conflict.
The other thing that I'm wondering is if anyone has done a family tree of
astronomy software. It
Just wanted to get some input from both Fedora astronomy and mageia about
which astronomy related packages to package next. I'm working in audela.
Also I'll be working on getting mesa as a rpm.
: Joseph Wang joequ...@gmail.com
Date: Sat, Mar 23, 2013 at 6:15 PM
Subject: Re: [fedora-astronomy] IRAF RPM spec files
To: Sergio Pascual sergi...@fedoraproject.org
Cc: astronomy astron...@lists.fedoraproject.org, ad...@iraf.net,
mageia-dev mageia-dev@mageia.org
Here is the latest set up patches
and version number.
Best regards, Sergio
2013/3/23 Joseph Wang joequ...@gmail.com
Here is the latest set up patches. The main difference is that I
found and fixed some fortran declarations and one very subtle but
nasty segfault in fncache.c. I also changed the compile so that it
uses
Also are you set up to run a tree from git? If you can run patches
from the git dev tree, it will be easier to track down the problems.
On Sun, Mar 24, 2013 at 12:03 PM, Joseph Wang joequ...@gmail.com wrote:
I'm trying to figure out why this happens
areadb.x:
areadb:
: cant open
await.x
I've uploaded my changes to
https://github.com/joequant/iraf
There is a branch debug which has a local build.sh script that can
be used to build iraf locally. If you can get that working it will be
easier to swap changes back and forth.
Also if you or anyone else wants commit privileges to the
FYI, I have a working spec file for python-stsci which runs pyraf.
Once we get iraf working then we can work on pyraf.
I've also uploaded my rpm changes up to the debug branch of the iraf
repository on github. That will make it much easier to pull the
changes than through e-mail attachments.
for a while but fails in the
end. I attach the log of the build , probably you know better why is
failing.
Best, Sergio
2013/3/13 Joseph Wang joequ...@gmail.com
Here is the spec file and patch file that gave me a working cl prompt
on mageia, and it should be rather easily portable to other
Here is the spec file and patch file that gave me a working cl prompt
on mageia, and it should be rather easily portable to other RPM
distros. The big issue is that there is a chicken/egg issue in which
you have to build libVO to get xc and xc to get libVO, and I had to
split up the build into a
of the
distribution
as well as the non-astronomy human infrastructure.
On Sun, Mar 3, 2013 at 11:25 AM, Joseph Wang joequ...@gmail.com wrote:
Anyone game for trying to package IRAF (again)?
With 2.16 all of the licensing issues have been fixed. The build
system is ancient but with github we might
I've pretty much given up on GNOME. I've been looking at cinnamon.
There is a version in cauldron which I'm hoping will make it in
post-mageia3, and I've been keeping that updated with cinnamon
development.
Also, I've found that one bottleneck with packagers is that the
mentors are often
Before I reinvent the wheel
There was a request for peazip, and what I'm thinking about doing is
to write a script
called repobuild. This script would pull the .spec and source files
from mgarepo
and then build and install an RPM package.
The use case for this is:
1) so that people who
Just wondering if/where the GNU data language is being packaged with
Mageia 3. It's listed as being in Mageia
https://wiki.mageia.org/en/Science_SIG
But the package gdl is something else.
Found it under gnudl
On Wed, Jan 30, 2013 at 3:22 AM, Joseph Wang joequ...@gmail.com wrote:
Just wondering if/where the GNU data language is being packaged with
Mageia 3. It's listed as being in Mageia
https://wiki.mageia.org/en/Science_SIG
But the package gdl is something else.
I removed fonts-wqy-bitmap and fonts-wqy-unibit from the repository.
I added x11-font-wqy-unibit which has the wqy unibit fonts, and I got
it to work with the same conventions as x11-font-wqy-bitmapfont
I just uploaded the missing WQY (zenhei, unibit, bitmap) fonts to the
repository. No personal opinion as to whether or not they should go
into Mageia 3 or not, but they are there if needed.
The cinnamon conflict with gnome has been fixed in the packages I
have. There is a patch that fixes the problem that I've sent
upstream, and I can package it locally with the patch.
As far as the other packages
peazip - I'm looking at getting that packaged. It's pascal code, but
it open source
I've been avoiding checking anything into the tree so as not to
interfere with the Mageia 3 release. But I've been quite busy at
working on various projects to be checked in as so as Cauldron opens
up. Most of them involve somewhat more than packaging since I've been
sending patches upstream
Just wanted to bring people's attention to this bug
https://bugs.mageia.org/show_bug.cgi?id=8757
The regexp in the packaging script is incorrect.
It's a quick trivial fix to the script, but since it involves a core
packaging script
I wanted people to take a look at it rather than checking in a
Also can someone run pkgsubmit for these two packages
vassal (updated)
raceintospace
Those should be good enough to release in mga3, and they are some nice games.
Question:
I have a large number of packages on my machine that are intended for
Mageia 4 release. Should I wait until after the Mageia 3 release to
check them in, or can I check them in now and not submit a build
request. Either is fine with me, and the only reason for checking
them early is so
Nightfall just got fixed and I'm getting clean i586 builds in iurt.
I'll fix up vstar next. Also if you can look at raceintospace next.
It's a really cool game.
Also I made an effort to clean up the fedora packages. Is there
anything in particular with an issue? I'd also like to fix up
There's a backlog of about 32 packages that I've packaged, but haven't
been built since I don't have build privileges, and I'm adding new
packages at the rate of five or six a week. I was wondering what can
be done to reduce that backlog. If necessary, we can wait until after
the release to add
A lot of the packages seem to be broken because
AM_CONFIG_HEADER(config.h) needs to be replaced with
AC_CONFIG_HEADERS([config.h])
1) I can go through and put in a sed command in the specs that does
the conversion, and e-mail the maintainers. If I check in a change
into the mgarepo does the
Sure thing. I can start patching some of the rpms that aren't haven't
been done yet. However, I was wondering if I can do that with just
subversion commit privileges or do I need to be able to submit build
requests to do this?
I added some things to try on in the bug report.
Basically, it looks like the place where it is reading moduledir is
broken. There are
some configure switches that you can try to change.
I added some info to the bug. Basically what I think is happening is
somewhere in the configure script it's setting the directory to
/usr/lib64 rather than /usr/lib. I'd look at the logs of the 32-bit
build where it's setting the libraries to make sure those are all set
to /usr/lib rather than
FYI, I just checked in a python-elements SRPM. I don't have the
ability to kick off a build, so someone else needs to do it to get
python-elements.
I also have a script python-pyp2rpm which is pending review right now.
This script makes it trivial to generate an SRPM from the PyPi
package. I
Looking over this page:
https://wiki.mageia.org/en/Python_policy
* python-pyp2rpm is undergoing review right now. Once it's in
cauldron, I'd like to
point to that package as something that packagers you should use to
get a first draft
of a spec file, I've been working with the Fedora people so
I just checked in a fix for this (325101). I don't have the
permission to kick off a build, so someone
else needs to do that.
Also, if there are any python related issues let me know. I've been
working a lot on my local
machine on python packages so it is easy for me to work on them right now.
I have a few suggestions for improving packaging communications
* https://wiki.mageia.org/en/Pending_packages
where I'll keep updated the status of my packaging, and I'll try to
forward notices from the mailing list. Having something on the wiki
makes things a bit more organized. I've changed
There has already been zillions of discussions about this. We will not
have Cinnamon. We already have enough environments and not enough
maintainers. And it will cause troubles maintaining different versions.
I volunteer to maintain cinnamon. I've already ported it from fedora. I
did
it
On Mon, Nov 26, 2012 at 9:51 PM, mageia-dev-requ...@mageia.org wrote:
Hmm, have you missed that there will be no Cinnamon in Mageia repos?
Part of packagers job is to keep eye on the dev ml.
Maybe I'll stay on for another day or so. I've been using Mageia/Mandriva
for years,
and so I'll keep
This is true, and there is no doubt that we need more resources, but in
this case it could cost more than it gains. We have had issues in the
past of the packages for these alternative DEs causing issues for the
core DEs due to the packages satisfying dep's required by the core packages.
I
One reason that I kept rather quiet is that e-mail conversations on
mailing lists
have a tendency to become flame wars, and I really want to avoid that. It's
very easy in public conversations to come across as a jerk, and as a newbie
I really wanted to avoid that. I've tried whenever finding
OK. Everything is better.
One reason I hate posting on public e-mail lists is that you get into
silly flame wars
over miscommunication. Putting everything into updates_testing and keeping it
out of the core Mageia 3 is exactly the right thing to do. I can go
ahead with trying
to package
Hi all,
The mentors are helping me get my packages uploaded, so I'm looking for
more things to package. My background is computational astrophysics so
there are about a dozen packages in theoretical astrophysics that I'm
going to package for Mageia once it I get set up. However, I'm
Hi all,
I have a number of packages that are ready to be reviewed for addition to
cauldron, and I'd like to get a mentor to review them. The main problem is
that I'm in Asia so it's going to be difficult for me to attend the IRC
meeting at 3 a.m. :-( :-(
So I'm looking to see how I can get a
I added my name to the wiki a few weeks ago. I haven't been contacted
by anyone, yet.
Would appreciate it if someone gets in touch with me. I have a queue of
several other packages
to add...
Hi all,
Been lurking for a while.
I've gotten the ATI open source drivers to work on my radeonsi with glamor
https://bugs.mageia.org/show_bug.cgi?id=7717
I've also packaged some python packages
https://bugs.mageia.org/show_bug.cgi?id=7515
https://bugs.mageia.org/show_bug.cgi?id=7517
There's
41 matches
Mail list logo
