David R. Morrison wrote:
[]
One possible fix for this would be to have a mechanism to recognize that
a group of packages need to be updated together, and that Fink::SysState
should not be expected to give a consistent answer until they have all
been updated. I'm not sure how to do this,
On Feb 24, 2006, at 3:00 AM, Michèle Garoche wrote:
Just for the record if it matters.
I've bootstrapped from HEAD in a new empty directory; bootstrapped
was fine: it installed gettext and its dependencies at version
0.10.40-19 on stable branch.
Then I've switched to unstable, removing
Alright, here's the reason SysState exists, and why it gives an
error. Dpkg has a reasonably serious bug in it: when a package is
upgraded, dpkg doesn't check to see if there are any versioned
dependencies that have become invalid. This has yet to be fixed
upstream, here's one of the
On Feb 25, 2006, at 4:55 AM, David R. Morrison wrote:
Well, upon further investigation this is a very curious story.
If I repeat the same steps as Michèle, but starting by
bootstrapping from branch_0_24, then the update goes OK. But if
the bootstrap is from HEAD, the update fails.
The
On Feb 25, 2006, at 6:40 AM, Dave Vasilevsky wrote:
Alright, here's the reason SysState exists, and why it gives an
error. Dpkg has a reasonably serious bug in it: when a package is
upgraded, dpkg doesn't check to see if there are any versioned
dependencies that have become invalid.
On 2/24/06, Chris Zubrzycki [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Feb 24, 2006, at 9:59 PM, Jack Howarth wrote:
I noticed today when doing a 'fink selfupdate' and 'fink update-
all'
from the 10.4-transitional unstable cvs a problem with the
On Feb 25, 2006, at 5:24 AM, David R. Morrison wrote:
The situation is this: foo and bar are initially splitoffs in the
same package, and foo depends on a specific version of bar. But in
the revision, foo and bar are in different packages. Due to
dependencies, fink updates bar before foo
On Feb 25, 2006, at 6:40 AM, Dave Vasilevsky wrote:
Alright, here's the reason SysState exists, and why it gives an
error. Dpkg has a reasonably serious bug in it: when a package is
upgraded, dpkg doesn't check to see if there are any versioned
dependencies that have become invalid.
On Feb 25, 2006, at 9:48 AM, David R. Morrison wrote:
However, there are some pairs of packages (dclib0 and valknut come
to mind) which have been set up so that one depends on a precise
version of another. It seems to me that these would be completely
impossible to update with the strict
On Feb 25, 2006, at 8:14 AM, Dave Vasilevsky wrote:
On Feb 25, 2006, at 9:48 AM, David R. Morrison wrote:
However, there are some pairs of packages (dclib0 and valknut come
to mind) which have been set up so that one depends on a precise
version of another. It seems to me that these
Le 25 févr. 2006 à 17:23, David R. Morrison a écrit :
On Feb 25, 2006, at 8:14 AM, Dave Vasilevsky wrote:
On Feb 25, 2006, at 9:48 AM, David R. Morrison wrote:
However, there are some pairs of packages (dclib0 and valknut
come to mind) which have been set up so that one depends on a
On Feb 25, 2006, at 11:23 AM, David R. Morrison wrote:
2. Even if we don't tell dpkg to install both at once, the
SysState algorithm will figure things out in the simple cases,
when upgrading the depender fixes things. For example, say you
have foo-shlibs-1.0-1 and foo-dev-1.0-1 installed
On Feb 25, 2006, at 9:38 AM, Dave Vasilevsky wrote:
The problem with gettext is that when you build and install
libgettext3-shlibs, the new gettext-tools hasn't been built yet!
Even though SysState *wants* to upgrade them as a unit, it can't do
so until it has .debs for all of them. The
On Feb 25, 2006, at 3:28 PM, David R. Morrison wrote:
To explain: after the update, gettext (which really means gettext-
shlibs but for historical reasons is called gettext) and gettext-
dev are in one package, which is really just a legacy package for
the old version of the library. The
On Feb 25, 2006, at 1:00 PM, Dave Vasilevsky wrote:
On Feb 25, 2006, at 3:28 PM, David R. Morrison wrote:
To explain: after the update, gettext (which really means gettext-
shlibs but for historical reasons is called gettext) and gettext-
dev are in one package, which is really just a
On Feb 25, 2006, at 4:07 PM, David R. Morrison wrote:
So its only because we don't have a deb for (old) gettext-tools?
If I built the old gettext-tools first it would be OK?
Gah, I've been getting things wrong. Lemme see if I can get this
straight. We have these packages in stable:
I believe the BuildConflicts on blt-dev was added to python24
by Daniel Macks to avoid it accidentally being linked into python24.
The note at...
http://cvs.sourceforge.net/viewcvs.py/fink/dists/10.4-transitional/unstable/main/finkinfo/languages/python24.info?rev=1.8view=markup
...indicates
Sorry if I did the wrong thing with the pymol package, but on a fresh install
in which I didn't have blt, the build, which requires Pmw, fails if it is not
present. (It needs blt to build, not blt-dev I am pretty sure.) Pmw seems to
build properly in the absence of blt but some of its
18 matches
Mail list logo
