I have followed all the indications but I still experiment the same problem ; I
want to update to Gutsy and update-manager doesn't show me the update button.
I deleted my ~/.update-manager-core/meta-release, my
~/.update-manager/meta-release but it didn't fix anything. And I have no
This needs to be verified today, so that people upgrading to gutsy
tomorrow are good.
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
The version 0.59.25 in feisty-proposed should fix this issue as well as
the issue with the missing imports.
Here are instruction to verify the problem:
0. install update-manager 0.59.23 from feisty-updates
1. make sure your time is correct (ntpdate pool.ntp.org)
2. run update-manager
3. close
Using update-manager and update-manager-core 0.59.23 I did not see the
distribution upgrade button. After updating to 0.59.25 in feisty-
proposed I saw that the distribution upgrade button was available.
** Tags added: verification-done
** Tags removed: verification-needed
--
update-manager
Copied to -updates.
** Changed in: update-manager (Ubuntu Feisty)
Status: In Progress = Fix Released
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
I followed the fix here and it works http://www.go2linux.org/upgrading-
to-gutsy
Populating the file /var/lib/update-manager/meta-release with the
attatched file fixes the issue.
Original source:
http://www.go2linux.org/pics/other_files/meta-release.txt
Note: this is not my fix, thanks to
I can confirm this output (notably failing to initialize dbus, and the
NameErrors
--phix
On 9/20/07, ThinkpadUBUNTU [EMAIL PROTECTED] wrote:
I am afraid none of the above allowed the upgrade to run on my system -
here is the output
[EMAIL PROTECTED]:~$ sudo touch -t 19700101
I am afraid none of the above allowed the upgrade to run on my system -
here is the output
[EMAIL PROTECTED]:~$ sudo touch -t 19700101
/var/lib/update-manager/meta-release
[EMAIL PROTECTED]:~$ sudo upgrade-manager -d
sudo: upgrade-manager: command not found
[EMAIL PROTECTED]:~$ sudo
Thanks, Michael Hofmann, for the testing. Patch approved for feisty-
proposed; mvo, can you please upload a new package to -proposed?
** Changed in: update-manager (Ubuntu Feisty)
Status: Fix Committed = In Progress
--
update-manager cannot find meta-release info
I think Pitt is saying that the fix has not yet been approved, but I'll
add this anyway.
As of upgrading Feisty on 2007-09-15 (on 2 computers), I still had to
use:
sudo touch -t 19700101 /var/lib/update-manager/meta-release
To run:
sudo upgrade-manager -d
and get it to work.
--
Fixed in gutsy with the 0.72 upload
** Changed in: update-manager
Status: Fix Committed = Fix Released
** Changed in: update-manager (Ubuntu)
Status: Fix Committed = Fix Released
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received
Looks fine to me.
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Accepted into feisty-proposed, please go ahead and test.
** Changed in: update-manager (Ubuntu Feisty)
Status: In Progress = Fix Committed
** Description changed:
-
- The symptom is that if I do gksudo update-manager -d I get no option to
upgrade and this error:
+ The symptom is that
Works for me, no empty /var/lib/update-manager/meta-release anymore.
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing
I still get:
Traceback (most recent call last):
File /usr/lib/python2.5/site-packages/UpdateManager/UpdateManager.py, line
914, in on_button_dist_upgrade_clicked
fetcher.run()
File
/usr/lib/python2.5/site-packages/UpdateManager/Core/DistUpgradeFetcherCore.py,
line 178, in run
Just had the current dist not found in meta-release error. But at
least for me it was correct since the /var/lib/update-manager/meta-
release file was empty (!!!). Quite strange since I just did an upgrade
from edgy (possible to update edgy-gutsy, would have saved 800MB
download...)
I then
This diff should fix both the sudo and the non-sudo case:
In the sudo case the empty file creates if-modified-since (I-M-S) hits
that are newer than the version on the server so no metarelease file is
downloaded. Empty files now get simply removed.
In the non-sudo case both the meta-release and
** Changed in: update-manager (Ubuntu)
Target: tribe-5 = ubuntu-7.10-beta
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
I put packages online at:
deb http://people.ubuntu.com/~mvo/update-manager /
Please give them a go.
Thanks,
Michael
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
On Mon, September 10, 2007 4:07 am, Michael Vogt wrote:
I put packages online at:
deb http://people.ubuntu.com/~mvo/update-manager /
Please give them a go.
Thanks,
Thank *you*. Seems to work just great, except that running
sudo update-manager -d, I needed to hit Check before the
new
Wanted to note that neither touching nor removing
/var/lib/update-manager/meta-release worked for me. The following solution did
work:
http://www.go2linux.org/upgrading-to-gutsy
Sorry I did not try update-manager_0.59.24 posted above.
--
update-manager cannot find meta-release info
I'd like to report what happend here[1]:
1. procedure as suggested a
href=https://wiki.ubuntu.com/GutsyGibbon/Tribe5#head-81cc88734ebf046f2eea75748ddc33707ae6cc4d;in
ubuntu wiki/a
2. needed the touch cli
3. new release showed up for one but coulnd't carry out the upgrade right away
4. next time
Should we be checking for corrupt meta release info as well as 0
length files here?
Is it that bad to download the meta release file every time when -d is
passed?
On 9/7/07, schnollk [EMAIL PROTECTED] wrote:
I'd like to report what happend here[1]:
1. procedure as suggested a
I am experiencing this bug too, on a fully updated feisty:
After confirming that my system is up to date
$ sudo apt-get update
$ sudo apt-get upgrade
I run
$ gksudo update-manager -c -d
GTK Accessibility Module initialized
warning: could not initiate dbus
current dist not found in meta-release
It's true, making committed instead.
** Changed in: update-manager (Ubuntu)
Status: Fix Released = Fix Committed
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
On Thu, September 6, 2007 4:33 pm, Anders wrote:
I tried
$ sudo touch -t 19700101 /var/lib/update-manager/meta-release
$ update-manager -d
to no avail.
Try using sudo for both commands. Or try:
$ rm ~/.update-manager-core/meta-release
$ update-manager -d
--
update-manager cannot find
I tried
$ sudo touch -t 19700101 /var/lib/update-manager/meta-release
$ update-manager -d
to no avail.
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact
Thanks as
$ sudo touch -t 19700101 /var/lib/update-manager/meta-release
$ update-manager -d
is a fix.
Daniel
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
The recipe give by Daniel Moyne of just touching the file to the epoch
does not work for me, neither does the one from ysth.
mvo's patch does fix it. I would suggest this should be pushed into
feisty pretty soon.
--
update-manager cannot find meta-release info
I can confirm that the patch works in my case.
Please include it into feisty.
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
On Tue, August 28, 2007 3:17 am, Martin Pool wrote:
The recipe give by Daniel Moyne of just touching the file to the epoch
does not work for me, neither does the one from ysth.
Touching the file may not work if you don't sudo update-manager.
I'd like to know what you tried.
mvo's patch does
As of Feisty 2007-07-27, this still occurs:
$ sudo update-manager -c -d
Password:
warning: could not initiate dbus
current dist not found in meta-release file
Has the patch been uploaded to the repositories? I'm not sure how to
merg a .diff file.
--
update-manager cannot find meta-release info
On Mon, 2007-08-27 at 18:22 +, brettalton wrote:
Has the patch been uploaded to the repositories? I'm not sure how to
merg a .diff file.
sudo
patch /usr/lib/python2.5/site-packages/UpdateManager/Core/MetaRelease.py
u-m.diff should do it (I hope).
--
Bruce Cowan [EMAIL PROTECTED]
--
That's really not sufficient. If If-Modified-Since is going to be used at all,
the three different
http://changelogs.ubuntu.com/meta-release* files need to be cached as three
separate files.
(Though I'm not sure how ~/.update-manager/meta-release plays into it.)
A workaround:
sudo touch -t
For an example of when the patch isn't good enough:
# make sure we don't already know about gutsy or have the problematic empty file
sudo rm /var/lib/update-manager/meta-release
sudo update-manager -c
# Close, then:
sudo update-manager -d
/var/lib/update-manager/meta-release created by
I had the same problem -- and the patch seemed to solve the issue... so
far anyways, I'm upgrading as I type
Kyle
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug
I hope this will be pushed int Feisty soon as suggested by Eugene.
I'd apply the patch but I'd like prefer to test the mainstream upgrade path.
Thanks.
// Randy
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you
update-manager (1:0.69) gutsy; urgency=low
[ Michael Vogt ]
* UpdateManager/Core/MetaRelease.py:
- remove zero size meta-release files (LP: #127263)
* utils/demoted.cfg:
- updated to current gutsy
* DistUpgrade/DistUpgrade.cfg:
- added esound, esound-common to forced obsoleted
Thank you, the patch does help.
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Now, after the patch, I was able to successfully upgrade from 7.04 to
7.10
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs
I can confirm this patch too, thank you :)
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Sorry, running update-manager as root works. Sorry about that.
** Changed in: update-manager (Ubuntu)
Status: Fix Committed = Fix Released
** Changed in: update-manager (Ubuntu)
Status: Fix Released = Fix Committed
--
update-manager cannot find meta-release info
Applying the patch doesn't do anything. I even removed the
/usr/lib/python2.5/site-packages/UpdateManager/Core/MetaRelease.pyc file
too.
This is a fairly recent install of a fairly early version of Feisty, I
forgot to get the final release on CD.
--
update-manager cannot find meta-release info
** Changed in: update-manager (Ubuntu)
Importance: Undecided = High
Assignee: (unassigned) = Michael Vogt
Target: None = tribe-5
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of
Just apply straight to:
/usr/lib/python2.5/site-packages/UpdateManager/Core/MetaRelease.py
and let me know if that helps.
Thanks,
Michael
** Attachment added: Patch to fix the issue. Can you please try the attached
patch?
http://launchpadlibrarian.net/8736481/u-m.diff
** Changed in:
This is not a duplicate of bug #103911.
** This bug is no longer a duplicate of bug 103911
Feisty: dbus error message executing update-manager from shell
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are
Indeed it isn't, and I can confirm this issue.
** Changed in: update-manager (Ubuntu)
Status: New = Confirmed
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the
*** This bug is a duplicate of bug 103911 ***
https://bugs.launchpad.net/bugs/103911
Thanks for your bugreport.
This bug is a duplicate of 103911.
** This bug has been marked a duplicate of bug 103911
Feisty: dbus error message executing update-manager from shell
--
update-manager
** Also affects: update-manager (Ubuntu)
Importance: Undecided
Status: New
--
update-manager cannot find meta-release info
https://bugs.launchpad.net/bugs/127263
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
49 matches
Mail list logo
