New installation of P2009 + ~123 updates = DBus error

[atolboo]

This bug report shows the problem.
For the moment I can't tell more 

[caitlyn]

Your solution in comment #48 at http://bugs.pardus.org.tr/show_bug.cgi?id=11110#c48 works well for me 

[atolboo]

Your solution in comment #48 at ..........

This is not my solution, it's from Comment #29+#35 From Faik Uygur
And here is how you can apply his solution.
Open a Konsole and give the following three commands

Code:

wget http://cekirdek.pardus.org.tr/~faik/pisi/fix-zero-file-bug.py

Code:

chmod 755 fix-zero-file-bug.py

Code:

sudo python fix-zero-file-bug.py

[dpeirce]

I've just installed Pardus 2009 in Virtualbox 2.2.4 in an Antix M-8.2 host. I was unable to complete my initial upgrade after a bunch of tries and several reinstalls, but Pisi is not among the packages listed for upgrade so I couldn't try updating it by itself. I downloaded the fix...py script and got these error messages when I ran it:

Code:

Searching for broken packages...
0 broken package found...
Re-installing broken packages...

After 4 cycles of start... stopped, restart... stopped, etc, Pisi refused to access the internet any longer.

Gee whizzz!!! Any fix in sight?

In faith, Dave
Viva Texas

[dpeirce]

Looking around in y'alls documentation, it looks like Pisi is the ONLY package manager in Pardus. There's an old proverb about putting all your eggs in one basket :^).

Anyway, I decided to see if Pisi on the command line was any better than Pisi at the GUI.

Code:

# pisi update-repo
# pisi upgrade firefox

Well, that worked! Now I have Firefox 3.5.3. So:

Code:

# pisi update-repo
# pisi upgrade

Wow!!! It went through a LOT of packages which apparently had been cached, then downloaded a few, then went to installing. 124 out of 124 (it had been 135 before I upgraded firefox). Now the GUI Pisi shows no updates due and looks like it's ready to go.

So, until Pisi gets fixed, use the command line pisi for your updates according to the instructions HERE:
http://en.pardus-wiki.org/Pisi_CLI_Usage#Updating_Repositories

Wish I had done this before I made my last post!

In faith, Dave
Viva Texas

Take the Pepsi challenge -- choose Linux.

[James T]

Looking around in y'alls documentation, it looks like Pisi is the ONLY package manager in Pardus. There's an old proverb about putting all your eggs in one basket :^).

I think that fundamentally that's true of any distribution. While on the surface, Debian & Ubuntu have many: dpkg, apt-get, aptitude, synaptic, adept ... in reality, apt-get is a wrapper for dpkg and the others are wrappers for apt-get, and I think the situation is similar on the rpm side with apt-rpm and yum being wrappers for the low-level rpm.

[atolboo]

So, until Pisi gets fixed, use the command line pisi for your updates according to the instructions HERE:
http://en.pardus-wiki.org/Pisi_CLI_Usage#Updating_Repositories

This is not a 100% fix for this problem.
The change for the occurrence of this bug are (highly) reduced  with the command

Code:

sudo pisi up -y

I found out about this during the many tests for Comment #45, Comment #51,  Comment #52 and Comment #60.

[dpeirce]

That possibly confirms my suspician, that it's a problem of something not being there when Pisi (GUI) gets there and wants it, _IF_ I understood that command: pisi up -y would mean 'Pisi, do an upgrade, answer all questions with 'yes".' ('up' is short for upgrade?)

So I reinstalled from the ISO into Virtualbox, and immediately did '# pisi ur', and then '#pisi up -yN' (some of the colors were awful hard to read, so I addad the N). It went through to conclusion just fine, no hangups. Then I rebooted, and my login screen was trashed, but that's a subject for a different post.

"Can't win!" :^)

In faith, Dave
Viva Texas

[atolboo]

......('up' is short for upgrade?)

Yes, for more info do a "pisi help"

[atolboo]

The problem has apparently been solved, see Comment #61