François Bissey | 1 Jul 07:54 2010
Picon
Picon

gl2ps

Hi all,

any reason why there is gl2ps-1.35 both in the tree and the
science overlay. What's more the overlay version is ~arch while the tree
one is arch:
eix gl2ps
[I] x11-libs/gl2ps
     Available versions:  ~1.3.3 1.3.5 (~)1.3.5[1] {doc (+)png (+)zlib}
     Installed versions:  1.3.5[1](21:18:49 26/11/09)(png zlib)
     Homepage:            http://www.geuz.org/gl2ps/
     Description:         OpenGL to PostScript printing library

[1] "science" /usr/local/portage/layman/science

I will also fill a bug against it as there is a missing deps for pdflatex
probably for documentation, but it screwed up the revdep-rebuild
order for the png-1.4 update. pdflatex wasn't rebuilt before gl2ps
and boom since png-1.2 is not there anymore for pdflatex.

Francois

justin | 1 Jul 09:31 2010
Picon

Re: gl2ps

On 01/07/10 07:54, François Bissey wrote:
> Hi all,
> 
> any reason why there is gl2ps-1.35 both in the tree and the
> science overlay. What's more the overlay version is ~arch while the tree
> one is arch:
> eix gl2ps
> [I] x11-libs/gl2ps
>      Available versions:  ~1.3.3 1.3.5 (~)1.3.5[1] {doc (+)png (+)zlib}
>      Installed versions:  1.3.5[1](21:18:49 26/11/09)(png zlib)
>      Homepage:            http://www.geuz.org/gl2ps/
>      Description:         OpenGL to PostScript printing library
> 
> [1] "science" /usr/local/portage/layman/science
> 
Please sync you overlay. It was gone sometime ago

For any other issues, please ping me with patches, I will proxy them to
the tree.

jusitn

justin | 1 Jul 09:34 2010
Picon

Re: gl2ps

This is the list with dupes, but most of them are mpi.eclass related.

dev-ml/ocamlgraph
  Portage: 0.99b
  Overlay: 1.2
dev-python/pytables
  Portage: 2.1.2
  Overlay: 2.2_rc2
dev-tcltk/togl
  Portage: 2.0-r1
  Overlay: 1.7-r1
sci-biology/mrbayes
  Portage: 3.1.2
  Overlay: 3.1.2-r1
sci-chemistry/burrow-owl
  Portage: 1.4
  Overlay: 1.4 9999_pre15
sci-chemistry/coot
  Portage: 0.6.1 0.6
  Overlay: 9999
sci-chemistry/gromacs
  Portage: 3.3.1-r1 3.3.3 4.0.4 4.0.5 4.0.7-r3
  Overlay: 4.0.9999 9999
sci-chemistry/jmol
  Portage: 11.0.3-r1
  Overlay: 11.6
sci-chemistry/pymol
  Portage: 0.99_rc10 1.2.3-r1 1.3.0
  Overlay: 9999
sci-chemistry/pymol-apbs-plugin
(Continue reading)

François Bissey | 1 Jul 10:59 2010
Picon
Picon

Re: gl2ps

> On 01/07/10 07:54, François Bissey wrote:
> > Hi all,
> > 
> > any reason why there is gl2ps-1.35 both in the tree and the
> > science overlay. What's more the overlay version is ~arch while the tree
> > one is arch:
> > eix gl2ps
> > [I] x11-libs/gl2ps
> > 
> >      Available versions:  ~1.3.3 1.3.5 (~)1.3.5[1] {doc (+)png (+)zlib}
> >      Installed versions:  1.3.5[1](21:18:49 26/11/09)(png zlib)
> >      Homepage:            http://www.geuz.org/gl2ps/
> >      Description:         OpenGL to PostScript printing library
> > 
> > [1] "science" /usr/local/portage/layman/science
> 
> Please sync you overlay. It was gone sometime ago
> 
Strange I synced this morning and it is there in the copy layman fetched
but it is not there in the private copy I keep for commits that I synced 2 
days ago.
Very curious.

Francois

Thomas Kahle | 1 Jul 12:10 2010
Picon
Picon

Re: gl2ps

Hi,

>>
>> Please sync you overlay. It was gone sometime ago
>>
> Strange I synced this morning and it is there in the copy layman fetched
> but it is not there in the private copy I keep for commits that I synced 2 
> days ago.
> Very curious.

I ran into a similar issue with the combination of using eix-sync to
sync overlays too and the move of the overlay location in layman 1.3*.
In my case eix-sync simply stop syncing overlays because it looked for
them in /var/lib/layman while they were still in /usr/local/portage/layman.

Cheers,

Thomas

> 
> Francois

--

-- 
Thomas Kahle

François Bissey | 1 Jul 12:20 2010
Picon
Picon

Re: gl2ps

> Hi,
> 
> >> Please sync you overlay. It was gone sometime ago
> > 
> > Strange I synced this morning and it is there in the copy layman fetched
> > but it is not there in the private copy I keep for commits that I synced
> > 2 days ago.
> > Very curious.
> 
> I ran into a similar issue with the combination of using eix-sync to
> sync overlays too and the move of the overlay location in layman 1.3*.
> In my case eix-sync simply stop syncing overlays because it looked for
> them in /var/lib/layman while they were still in /usr/local/portage/layman.
> 
Installed layman 1.3.3 in April. Fiddled the setting to leave my overlays
in /usr/local/portage/layman way back when. First time I have an issue
with eix-sync. hum eix updated 23rd of June. Worth checking.

Thanks for the look up Thomas.

Francois

Thomas Kahle | 1 Jul 12:33 2010
Picon
Picon

Re: gl2ps

On 07/01/2010 12:20 PM, François Bissey wrote:
>> Hi,
>>
>>>> Please sync you overlay. It was gone sometime ago
>>>
>>> Strange I synced this morning and it is there in the copy layman fetched
>>> but it is not there in the private copy I keep for commits that I synced
>>> 2 days ago.
>>> Very curious.
>>
>> I ran into a similar issue with the combination of using eix-sync to
>> sync overlays too and the move of the overlay location in layman 1.3*.
>> In my case eix-sync simply stop syncing overlays because it looked for
>> them in /var/lib/layman while they were still in /usr/local/portage/layman.
>>
> Installed layman 1.3.3 in April. Fiddled the setting to leave my overlays
> in /usr/local/portage/layman way back when. First time I have an issue
> with eix-sync. hum eix updated 23rd of June. Worth checking.

I took the same path :) Decided to let things stay in /usr/local when
layman 1.3.3. was installed and ran into the issue one or two weeks ago.
So, eix-0.20.5 might be the culprit here.

Cheers,
Thomas

--

-- 
Thomas Kahle

(Continue reading)

Rafael Goncalves Martins | 2 Jul 06:55 2010
Picon

[ANN] g-octave-0.2

Hi science mates,

I'm glad to send this mail announcing the release of g-octave-0.2 with support
to the installation of packages from the octave-forge SVN repository and with
a fresh package database with the current stable versions.

The ebuild can be found in the Science overlay and the documentation can be
read here:

http://soc.dev.gentoo.org/~rafaelmartins/g-octave/docs/

Until now I had no free time nor free machine to run the tinderbox scripts
against the new package database yet, but I'm sure that I'll have a great
number of broken packages needing patches.

Any thoughts about this release and g-octave in general are welcome, as
always.

Best regards,

--

-- 
Rafael Goncalves Martins
http://rafaelmartins.eng.br/

Rafael Goncalves Martins | 2 Jul 07:07 2010
Picon

Re: [GSoC] g-Octave

On 23:15 Mon 28 Jun     , Alex Tsui wrote:

Moving back to gentoo-science <at> 

> Hi Rafael,
> 
> I'm subscribing to gentoo-science and saw your post. I'm surprised and
> interested to hear you are doing work on g-octave for GSoC, congrats. I was
> interested to work on octave support last summer but was not accepted. I'm
> glad that they found you to work on it. Well, I just wanted to say good luck
> and appreciate your work. I'll be following your reports and maybe test out
> the code for myself :)
> 
> --Alex
> 

Thanks Alex. g-octave 0.2 is out! Please test it if you have the time. :)

The ebuilds are in the Science overlay.

Best regards,

--

-- 
Rafael Goncalves Martins
http://rafaelmartins.eng.br/

Rafael Goncalves Martins | 2 Jul 21:27 2010
Picon

[GSoC] g-Octave - roadmap to 0.3

Hi guys,

g-Octave 0.2 was released, as early announced here by me, then is time to
start the work on the next version (0.3), although the tinderbox tests for the
new package database are still pending. The patches for individual packages can
be done in parallel with the g-Octave main development.

The next version will come with 3 main new features:

Support to optional logging
---------------------------

I'm planning to use the 'logging' module, from the Python standard library in
order to implement this. The implementation will allow the user to enable or
disable the logging feature from the configuration file.

Support to package updates
--------------------------

g-Octave can't do package updates by now. All that the user can do is
reinstall the package manually when he knows that the package is updated by
the upstream.

The idea is to implement an g-octave CLI option that query the package manager
about upgrades in the installed packages and do the update for the user.

Support to Paludis/Pkgcore
--------------------------

g-Octave currently can only use emerge/portage to do the installation of
(Continue reading)


Gmane