Error while apt-get update and upgrading tint2

schemer · 2012-10-25 19:10:36

Earlier tonight, I did an apt-get update and I got the following error:

Reading package lists... Done
W: GPG error: http://packages.crunchbang.org waldorf Release: The following signatures were invalid: BADSIG 9B7C8627EDFD12C1 Philip Newborough <corenominal@corenominal.org>

Then I ran the following command:

$ sudo dpkg --configure -a

I got the following error when I tried an apt-get upgrade immediately. Full output here

Unpacking replacement tint2 ...
dpkg: error processing /var/cache/apt/archives/tint2_0.11+svn20111022-3_i386.deb (--unpack):
 trying to overwrite '/usr/bin/tint2conf', which is also in package tint2conf 0.11~svn649-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to replace lxappearance 0.5.1-1crunchbang2 (using .../lxappearance_0.5.2-1_i386.deb) ...
Unpacking replacement lxappearance ...
Processing triggers for man-db ...
Processing triggers for install-info ...
install-info: warning: no info dir entry in `/usr/share/info/ocaml.info.gz'
Processing triggers for hicolor-icon-theme ...
Processing triggers for desktop-file-utils ...
Processing triggers for menu ...
Errors were encountered while processing:
 /var/cache/apt/archives/tint2_0.11+svn20111022-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Then I tried apt-get purge and it performed some kind of fixing the just installed packages.

Then I tried apt-get upgrade once again and this is the error I got:

Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following packages will be upgraded:
  tint2
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 186 kB of archives.
After this operation, 251 kB of additional disk space will be used.
Do you want to continue [Y/n]? 
Get:1 http://ftp.debian.org/debian/ wheezy/main tint2 i386 0.11+svn20111022-3 [186 kB]
Fetched 186 kB in 2s (84.7 kB/s)                 
(Reading database ... 94358 files and directories currently installed.)
Preparing to replace tint2 0.11~svn649-1 (using .../tint2_0.11+svn20111022-3_i386.deb) ...
Unpacking replacement tint2 ...
dpkg: error processing /var/cache/apt/archives/tint2_0.11+svn20111022-3_i386.deb (--unpack):
 trying to overwrite '/usr/bin/tint2conf', which is also in package tint2conf 0.11~svn649-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/tint2_0.11+svn20111022-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Why do I get a gpg error and why is tint2 failing to upgrade?

porkpiehat · 2012-10-26 01:02:38

Try

sudo apt-get remove tint2
sudo apt-get update 
sudo apt-get dist-upgrade

("dist-upgrade", not "upgrade")

On testing and sid, "dist-upgrade" is the preferred upgrade command.

unfugr · 2012-10-26 01:23:02

tint2 is in the crunchbang waldorf repository (which is usually higher pinned in /etc/apt/preferences) and in the debian wheezy repository. But the debian wheezy version is newer or is a higher version or something. As there are problems with your crunchbang key, apt did ignore the wheezy repo and fetched tint2 from debian instead.
But the debian tint2 version clashes with the cb-tint2 custom package, so if you want to have tint2 until the cb key problem is solved, you have to

sudo apt-get remove cb-tint2

too.
After the key problem is solved, you can install tint2 and cb-tint2 from the crunchbang repo again.

Hm. If it was me, I would try to remove the key and install it anew, but I also would not really know what I was doing, so more knowledgable people can hopefully help you better with this part of the operation.

Last edited by unfugr (2012-10-26 01:27:07)

schemer · 2012-10-26 17:31:45

@unfugr and @porkpiehat: sorry for the delay in reply.

unfugr wrote:

tint2 is in the crunchbang waldorf repository (which is usually higher pinned in /etc/apt/preferences) and in the debian wheezy repository. But the debian wheezy version is newer or is a higher version or something. As there are problems with your crunchbang key, apt did ignore the wheezy repo and fetched tint2 from debian instead.
But the debian tint2 version clashes with the cb-tint2 custom package, so if you want to have tint2 until the cb key problem is solved, you have to
sudo apt-get remove cb-tint2
too.
After the key problem is solved, you can install tint2 and cb-tint2 from the crunchbang repo again.
Hm. If it was me, I would try to remove the key and install it anew, but I also would not really know what I was doing, so more knowledgable people can hopefully help you better with this part of the operation.

porkpiehat wrote:

Try
sudo apt-get remove tint2
sudo apt-get update 
sudo apt-get dist-upgrade
("dist-upgrade", not "upgrade")
On testing and sid, "dist-upgrade" is the preferred upgrade command.

I removed cb-tint2 and tried installing tint2. I still get the error:

Unpacking tint2 (from .../tint2_0.11+svn20111022-3_i386.deb) ...
dpkg: error processing /var/cache/apt/archives/tint2_0.11+svn20111022-3_i386.deb (--unpack):
 trying to overwrite '/usr/bin/tint2conf', which is also in package tint2conf 0.11~svn649-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
 /var/cache/apt/archives/tint2_0.11+svn20111022-3_i386.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

This is probably related, but since two days I noticed that tint2 does not show up at all after logging in. I have to restart it from the right-click menu.

So, in short, I am tint2less for now. I tried other minimal panels like lxpanel, fspanel, hpanel, ltpanel, xfce4-panel, but none of these are similar to tint2 and are reminiscent of windows task bar. neutral

I miss my tint2 too much. No offense to other panels, but tint2 is the only one that felt nixy.

For now, I am on lxpanel.

Can anyone please help?

xaos52 · 2012-10-26 17:52:46

First remove package tint2conf:

sudo apt-get remove tint2conf

Then complete the tint2 install with

sudo apt-get -f install

schemer · 2012-10-26 18:02:45

That worked!

Thank you so much xaos52, you are awesome!

So, when crunchbang's tint2 is fixed/updated, would it clash with Debian's tint2 again?

xaos52 · 2012-10-26 18:49:28

Not if your priorities are set right:
/etc/apt/preferences:

Package: *
Pin: release a=waldorf
Pin-Priority: 1001

Package: *
Pin: release a=wheezy
Pin-Priority: 500

VastOne · 2012-10-26 19:05:31

xaos52 wrote:

First remove package tint2conf:

The tint2conf issue again... I thought this had been resolved, but apparently not.

Nice catch...

schemer · 2012-10-27 02:50:36

xaos52 wrote:

Not if your priorities are set right:
/etc/apt/preferences:
Package: *
Pin: release a=waldorf
Pin-Priority: 1001

Package: *
Pin: release a=wheezy
Pin-Priority: 500

Yes, this is what I have too. Thank you for taking time to answer my question.

CrunchBang Linux

SEARCH

#1 2012-10-25 19:10:36

Error while apt-get update and upgrading tint2

#2 2012-10-26 01:02:38

Re: Error while apt-get update and upgrading tint2

#3 2012-10-26 01:23:02

Re: Error while apt-get update and upgrading tint2

#4 2012-10-26 17:31:45

Re: Error while apt-get update and upgrading tint2

#5 2012-10-26 17:52:46

Re: Error while apt-get update and upgrading tint2

#6 2012-10-26 18:02:45

Re: Error while apt-get update and upgrading tint2

#7 2012-10-26 18:49:28

Re: Error while apt-get update and upgrading tint2

#8 2012-10-26 19:05:31

Re: Error while apt-get update and upgrading tint2

#9 2012-10-27 02:50:36

Re: Error while apt-get update and upgrading tint2

Board footer