headers
Nils Homer | 1 Nov 06:50
Picon

Failed: phase installing

After running "fink selfupdate" and "fink update-all" I keep getting the
following error.  Thanks for any help in advance.

/usr/bin/install -c -m 644 ./builds/unix/ft2unix.h \

/sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/ft2build.h
/usr/bin/install -c -m 644 ./builds/unix/ftconfig.h                        \

/sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/freetype2/free
type/config/ftconfig.h
/usr/bin/install -c -m 644
/sw/src/fink.build/freetype219-2.3.7-7/freetype-2.3.7/objs/ftmodule.h
\

/sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/freetype2/free
type/config/ftmodule.h
/usr/bin/install -c -m 755 ./builds/unix/freetype-config \

/sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/bin/freetype-config
/usr/bin/install -c -m 644 ./builds/unix/freetype2.m4 \

/sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/share/aclocal/freetype
2.m4
/usr/bin/install -c -m 644 ./builds/unix/freetype2.pc \

/sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/lib/pkgconfig/freetype
2.pc
    rm -rf 
/sw/src/fink.build/root-freetype219-2.3.7-7/sw/lib/freetype219/share
    install -d -m 755
(Continue reading)

Permalink | Reply | 0 comments |
headers
Alexander Hansen | 1 Nov 14:44
Picon
Gravatar

Re: Failed: phase installing


On Nov 1, 2008, at 1:50 AM, Nils Homer wrote:

> After running "fink selfupdate" and "fink update-all" I keep getting  
> the
> following error.  Thanks for any help in advance.
>
> /usr/bin/install -c -m 644 ./builds/unix/ft2unix.h \
>
> /sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/ 
> ft2build.h
> /usr/bin/install -c -m 644 ./builds/unix/ 
> ftconfig.h                        \
>
> /sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/ 
> freetype2/free
> type/config/ftconfig.h
> /usr/bin/install -c -m 644
> /sw/src/fink.build/freetype219-2.3.7-7/freetype-2.3.7/objs/ftmodule.h
> \
>
> /sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/ 
> freetype2/free
> type/config/ftmodule.h
> /usr/bin/install -c -m 755 ./builds/unix/freetype-config \
>
> /sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/bin/freetype- 
> config
> /usr/bin/install -c -m 644 ./builds/unix/freetype2.m4 \
>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nils Homer | 1 Nov 09:12
Picon

Re: Failed: phase installing

Thank-you for your help.  That did not work, the same error messages appear.

On 11/1/08 6:44 AM, "Alexander Hansen" <alexanderk.hansen <at> gmail.com> wrote:

> 
> On Nov 1, 2008, at 1:50 AM, Nils Homer wrote:
> 
>> After running "fink selfupdate" and "fink update-all" I keep getting
>> the
>> following error.  Thanks for any help in advance.
>> 
>> /usr/bin/install -c -m 644 ./builds/unix/ft2unix.h \
>> 
>> /sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/
>> ft2build.h
>> /usr/bin/install -c -m 644 ./builds/unix/
>> ftconfig.h                        \
>> 
>> /sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/
>> freetype2/free
>> type/config/ftconfig.h
>> /usr/bin/install -c -m 644
>> /sw/src/fink.build/freetype219-2.3.7-7/freetype-2.3.7/objs/ftmodule.h
>> \
>> 
>> /sw/src/fink.build/root-freetype219-2.3.7-7/usr/local/include/
>> freetype2/free
>> type/config/ftmodule.h
>> /usr/bin/install -c -m 755 ./builds/unix/freetype-config \
>>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nils Homer | 2 Nov 19:32
Picon

Re: Failed: phase installing

Here's wat I did: moved /usr/local, fink self-update, and fink update-all.
See belowfor all the details.  Thanks for your help so far!

$ kdir /tmp
$ sudo mv /usr/local /tmp/.
$ fink self-updatersync -az -q  rsync://msn.wi.us.finkmrrors.net/finkinfo//TIMESTAMP
/sw/fink/TIMESTAMP.tmp
I will now rn the rsync command to retrieve the latest package
descriptions. 
rsync -tz --delete-after --delete -q   --include='10.4/'
--include='10.4/stable/' --nclude='10.4/stable/main/'
--include='10.4/stable/main/finkinf'
--include='10.4/stable/main/finkinfo/*/'
--include='10.4/stable/main/finkino/*'
--include='10.4/stable/main/finkinfo/**/*' --include='10.4/'
--include=10.4/stable/' --include='10.4/stable/crypto/'
--includ='10.4/stable/crypto/finkinfo/'
--include='10.4/stable/cypto/finkinfo/*/'
--include='10.4/stae/crypto/finkinfo/*'
--include='10.4/stable/crypto/finkinfo/**/*' --incude='10.4/'
--include='10.4/unstable/' --include='10.4/unstable/main/'--include='10.4/unstable/main/finkinfo/'
--include='10.4/unstable/main/finkinfo/*/'
--include='10.4/unstable/main/fnkinfo/*'
--include='10.4/unstable/main/finkinfo/**/*' --include='10.4/'
--inlude='10.4/unstable/' --include='10.4/unstable/crypto/'
--include='10.4/unstble/crypto/finkinfo/'
--include='10.4/unstable/crypto/inkinfo/*/'
--include='10.4/unstable/crypto/finkinfo/*'
-include='10.4/unstable/crypto/finkino/**/*' --include='VERSION'
--include='DISTRIBUTION' --include='READE' --exclude='**'
(Continue reading)

Permalink | Reply | 0 comments |
headers
Trevor Harmon | 3 Nov 05:46

Name collision in Fink handling of CLASSPATH

For Java-based packages, Fink keeps track of the current CLASSPATH  
setting in the /sw/share/java/classpath file. Packages also store  
their JAR files in /sw/share/java/%n. This causes a name collision if  
a package happens to be named "classpath": Fink will put the package's  
JARs into a directory called /sw/share/java/classpath, but it will  
also try to create a file called /sw/share/java/classpath. Kaboom!

Of course, this problem only occurs with one package -- the one for  
the GNU Classpath project -- and could be worked around by renaming it  
to gclasspath, for example. Still, packages should not have to be  
renamed just because Fink puts a file in the wrong place. Fink should  
instead use a different file name, such as classpath.txt, to store the  
CLASSPATH.

Thoughts?

Trevor

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
Permalink | Reply | 1 comment |
headers
Daniel Macks | 3 Nov 06:25

Re: Name collision in Fink handling of CLASSPATH

On Sun, Nov 02, 2008 at 11:46:16PM -0500, Trevor Harmon wrote:
> For Java-based packages, Fink keeps track of the current CLASSPATH  
> setting in the /sw/share/java/classpath file. Packages also store  
> their JAR files in /sw/share/java/%n. This causes a name collision if  
> a package happens to be named "classpath": Fink will put the package's  
> JARs into a directory called /sw/share/java/classpath, but it will  
> also try to create a file called /sw/share/java/classpath. Kaboom!
> 
> Of course, this problem only occurs with one package -- the one for  
> the GNU Classpath project -- and could be worked around by renaming it  
> to gclasspath, for example. Still, packages should not have to be  
> renamed just because Fink puts a file in the wrong place. Fink should  
> instead use a different file name, such as classpath.txt, to store the  
> CLASSPATH.
> 
> Thoughts?

Yeah, that's a problem. Some would say it should be stored in var/
instead of share/ per usual FHS meanings (such as we have:) Or in
general not store general metadata or other index files in the same
place as actual fink-installed files. A minor headache to move or
rename it, is that the file is created via scripts from fink itself
(stored in the .deb) but read by init.sh which is from base-files.
Gotta make sure this one package BDep on a new fink but also that all
.deb that are created by new fink Dep on the new base-files. Since
there's only one collision and it's well-characterized (now:/ if
renaming it solves the problem, that's probably easiest. Or does it
also involve altering "any package that uses that class" (I don't know
if java uses CLASSPATH to read the .jar and find the classes that way,
or uses CLASSPATH itself as primary index to find classes).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Remi Mommsen | 5 Nov 11:12
Picon
Picon

Re: [cvs] dists/10.4/unstable/main/finkinfo/gnome libgdl-1.0.info, NONE, 1.1 libgdl1.0.info, 1.4, 1.5

Hi Dan,

the public gdl-gnome shared library is present up to 2.23.90  
inclusive. I have a libgdl1.0 package in my CVS experimental tree for  
this version.
(http://fink.cvs.sourceforge.net/viewvc/*checkout*/fink/experimental/mommsen/10.4/main/libgdl1.0.info?revision=1.1 
)

I need the newer version 2.23.90 for anjuta and gnome-build, both in  
the my experimental tree, too. Shall I commit the 2.23.90 version?

Remi

On Nov 5, 2008, at 6:08 AM, Daniel Macks wrote:

> Update of /cvsroot/fink/dists/10.4/unstable/main/finkinfo/gnome
> In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv3051
>
> Modified Files:
> 	libgdl1.0.info
> Added Files:
> 	libgdl-1.0.info
> Log Message:
> new version; rename because no longer supplies a public lib
>
>
> Index: libgdl1.0.info
> ===================================================================
> RCS file: /cvsroot/fink/dists/10.4/unstable/main/finkinfo/gnome/ 
> libgdl1.0.info,v
(Continue reading)

Permalink | Reply | 2 comments |
headers
Remi Mommsen | 5 Nov 14:11
Picon
Picon

Re: [cvs] dists/10.4/unstable/main/finkinfo/gnome libgdl-1.0.info, NONE, 1.1 libgdl1.0.info, 1.4, 1.5

Hi Dan,

there's now also a revision 1.2 in my experimental tree which merges  
your changes with mine.

Remi

On Nov 5, 2008, at 11:12 AM, Remi Mommsen wrote:

> Hi Dan,
>
> the public gdl-gnome shared library is present up to 2.23.90
> inclusive. I have a libgdl1.0 package in my CVS experimental tree for
> this version. (http://fink.cvs.sourceforge.net/viewvc/*checkout*/fink/experimental/mommsen/10.4/main/libgdl1.0.info?revision=1.1
> )
>
> I need the newer version 2.23.90 for anjuta and gnome-build, both in
> the my experimental tree, too. Shall I commit the 2.23.90 version?
>
> Remi
>
> On Nov 5, 2008, at 6:08 AM, Daniel Macks wrote:
>
>> Update of /cvsroot/fink/dists/10.4/unstable/main/finkinfo/gnome
>> In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv3051
>>
>> Modified Files:
>> 	libgdl1.0.info
>> Added Files:
>> 	libgdl-1.0.info
(Continue reading)

Permalink | Reply | 0 comments |
headers
Daniel Macks | 5 Nov 16:11

Re: [cvs] dists/10.4/unstable/main/finkinfo/gnome libgdl-1.0.info, NONE, 1.1 libgdl1.0.info, 1.4, 1.5

Do you need gdl-gnome, or just "gdl >= 2.23.90"? The second part of
this commit gives you a new "libgdl-1.0" (and -shlibs) package that is
version 2.24.0.

dan

On Wed, Nov 05, 2008 at 11:12:16AM +0100, Remi Mommsen wrote:
> Hi Dan,
> 
> the public gdl-gnome shared library is present up to 2.23.90  
> inclusive. I have a libgdl1.0 package in my CVS experimental tree for  
> this version.
(http://fink.cvs.sourceforge.net/viewvc/*checkout*/fink/experimental/mommsen/10.4/main/libgdl1.0.info?revision=1.1 
> )
> 
> I need the newer version 2.23.90 for anjuta and gnome-build, both in  
> the my experimental tree, too. Shall I commit the 2.23.90 version?
> 
> Remi
> 
> On Nov 5, 2008, at 6:08 AM, Daniel Macks wrote:
> 
> > Update of /cvsroot/fink/dists/10.4/unstable/main/finkinfo/gnome
> > In directory fdv4jf1.ch3.sourceforge.com:/tmp/cvs-serv3051
> >
> > Modified Files:
> > 	libgdl1.0.info
> > Added Files:
> > 	libgdl-1.0.info
> > Log Message:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Pierre-Henri Lavigne | 6 Nov 00:47
Picon
Favicon

[FFmpeg] Gracefuly Enable Swscale


Gnu day,

To resume, VLC 0.8.6i latest issue is ffmpeg :
https://sourceforge.net/tracker2/?func=detail&aid=1924399&group_id=17203&atid=414256
ffmpeg compiled with the swscale mode disables some stuffs like 
img_resample defined now as a deprecated API . I googled patches with 
various sites like freeBSD, Debian, etc... actually it seems the patch 
is simple to re-enable them while keeping the swscale option.

About vlc 0.9.5 :
I verified, VLC is using latest librairies about nearly everything. It 
means providing a newer ffmpeg version (at least march 2008), updating 
other sounds / video stuffs...

To my point of view, to get an other nice player in Fink, I suggest 
first to add the 0.8.6i version instead of restarting from scratch any 
work for the 0.9 bundle and wait again :/
Before the next steps, if anybody has feedback about this patch, like 
"it's evil" - "you'll get troubles with other packages", please tell us 
:D Any clues / advices are welcome(d ?).  Thanks to Matthias I fixed the 
other dependencies (libtar,...) I'm rebuilding a bunch of packages 
depending from ffmpeg, libavformat, libavcodec, ... and everything seems 
fine atm

An other question: I worked with JF Mertens (thanks for the seamonkey 
fix ;) to update wxgtk to the 2.8.7 version a few months ago. I've just 
read on the site that 2.8.9 was considered as "Stable". Is this a 
primary required update regards to Fink ?
(Continue reading)

Permalink | Reply | 6 comments |

Gmane