On Mon, Apr 20, 2009 at 11:54:43PM +0200, frantisek holop wrote:
hi there,
it is time for another of my biweekly snapshot upgrade.
this is what i see this time during the update process:
Candidates for updating php5-gd-5.2.9 - php5-gd-5.2.9 php5-gd-5.2.9-no_x11
Ambiguous: choose package
hi there,
it is time for another of my biweekly snapshot upgrade.
this is what i see this time during the update process:
Candidates for updating php5-gd-5.2.9 - php5-gd-5.2.9 php5-gd-5.2.9-no_x11
Ambiguous: choose package for php5-gd-5.2.9
0: None
1: php5-gd-5.2.9
2:
On Mon, Apr 20, 2009 at 11:54:43PM +0200, frantisek holop wrote:
midnight commander suddenly had another package as run dependancy
that the previous version did not have
it will install this dependency, to meet dependency rules from the
packing list instructions. You can see those
Marc Espie wrote:
On Fri, Mar 20, 2009 at 04:14:40AM +0100, frantisek holop wrote:
hi there,
i am just thinking out loud, but would it make sense
that pkg_add -u not-yet-installed-package would
instead of complaining about unresolvable package name
just go ahead and try to install that
On Fri, Mar 20, 2009 at 04:14:40AM +0100, frantisek holop wrote:
hi there,
i am just thinking out loud, but would it make sense
that pkg_add -u not-yet-installed-package would
instead of complaining about unresolvable package name
just go ahead and try to install that package?
this could
hi there,
i am just thinking out loud, but would it make sense
that pkg_add -u not-yet-installed-package would
instead of complaining about unresolvable package name
just go ahead and try to install that package?
this could allow for the scenario of updating and
installing packages from the same
