On Tue, 2006-06-27 at 15:10 +0200, Josselin Mouette wrote:
> You should file a bug report against update-notifier, as in this case
> the dependencies have to be changed by hand.
I think it's update-manager which needs changing, not update-notifier.
I did raise a bug against update-manager. In fa
On Tue, 2006-06-27 at 09:39 +0200, Josselin Mouette wrote:
> The update-notifier package has to be rebuilt, that's all.
How does that happen, generally? Is there something in place which is
supposed to rebuild packages when they need rebuilding? Or should I
raise a bug report requesting the rebu
On Sun, 2006-06-25 at 06:33 -0700, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> #375153: update-manager: not installable in unstable,
> which was filed against the python-gnome2 package.
>
> It has been closed by Josselin Mouette <[EMAIL PROTECT
Package: update-manager
Version: 0.42.2ubuntu22-2
Severity: grave
Justification: renders package unusable
A recent update for unstable caused the removal of update-manager (and
consequently update-notifier).
Upon trying to reinstall update-manager, I'm told:
The following packages have unmet de
/usr/share/python/pyversions.py defines requested_versions(), which
returns either a list:
versions = [current]
or a set:
versions = vinfo['versions'].intersection(supported)
Then /usr/bin/pycentral calls that function, and expects it to return a list:
def set_default_runtime_from_version_info
5 matches
Mail list logo
