Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #169663 > unrolled thread

wheezy packages problems

Back to article view | Back to linux.debian.user

Contents

  wheezy packages problems Giovanni Gigante <giov-debian@deepsky.it> - 2016-07-04 17:00 +0200
    Re: wheezy packages problems Cindy-Sue Causey <butterflybytes@gmail.com> - 2016-07-04 17:20 +0200
      Re: Re: wheezy packages problems Giovanni Gigante <giovanni.gigante@deepsky.it> - 2016-07-04 18:30 +0200
    Re: wheezy packages problems Lisi Reisz <lisi.reisz@gmail.com> - 2016-07-04 18:50 +0200
    Re: wheezy packages problems Sven Joachim <svenjoac@gmx.de> - 2016-07-04 19:10 +0200
      Re: wheezy packages problems Giovanni Gigante <giov-debian@deepsky.it> - 2016-07-04 20:00 +0200

#169663 — wheezy packages problems

Hello,
I have a wheezy installation (itself upgraded from previous versions) 
that I now want to upgrade to jessie.
I was following the instructions for the preparation to the upgrade to 
jessie, and I got this:

# dpkg --audit
The following packages are missing the md5sums control file in the
database, they need to be reinstalled:
  java-gcj-compat      Java runtime environment using GIJ

However, reinstalling this package seems impossible, as it apparently 
does not exist anymore:

# apt-get install --reinstall java-gcj-compat
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reinstallation of java-gcj-compat is not possible, it cannot be downloaded.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

There are other strange things. For example, gcj-jre is not installed on 
this system (?), but if I try to install it, I get:

# apt-get install gcj-jre
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
  gcj-jre : Depends: gcj-jre-headless (>= 4:4.7.2-1) but it is not going 
to be installed
E: Unable to correct problems, you have held broken packages.

Apart from this the systems seem up to date. I have tried apt-get clean, 
apt-get dist-upgrade and aptitude, and none of them complain.
I have no idea what to do next, in order to have a trouble-free system 
that I can safely upgrade to jessie. Suggestions?

Thanks
Giovanni

[toc] | [next] | [standalone]

#169665

On 7/4/16, Giovanni Gigante <giov-debian@deepsky.it> wrote:
> Hello,
> I have a wheezy installation (itself upgraded from previous versions)
> that I now want to upgrade to jessie.
> I was following the instructions for the preparation to the upgrade to
> jessie, and I got this:
>
> # dpkg --audit
> The following packages are missing the md5sums control file in the
> database, they need to be reinstalled:
>   java-gcj-compat      Java runtime environment using GIJ
>
> However, reinstalling this package seems impossible, as it apparently
> does not exist anymore:
>
> # apt-get install --reinstall java-gcj-compat
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reinstallation of java-gcj-compat is not possible, it cannot be downloaded.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> There are other strange things. For example, gcj-jre is not installed on
> this system (?), but if I try to install it, I get:
>
> # apt-get install gcj-jre
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>   gcj-jre : Depends: gcj-jre-headless (>= 4:4.7.2-1) but it is not going
> to be installed
> E: Unable to correct problems, you have held broken packages.
>
> Apart from this the systems seem up to date. I have tried apt-get clean,
> apt-get dist-upgrade and aptitude, and none of them complain.
> I have no idea what to do next, in order to have a trouble-free system
> that I can safely upgrade to jessie. Suggestions?


I have a couple thoughts while you wait for others to chime in.. Did
you run "apt-get update"? I'm a-suming most likely yes since you speak
other related things but asking anyway in case it was overlooked.

Also... I used to get that message a lot about holding packages back..
People talk about "pinning" packages here. I've never done that but it
might be one answer if you've ever actively done that yourself. I
*a-sume* you'd have to unpin something to correct that, but I have no
firsthand experience to base that on.

The other is it can be referencing our *_CHOICE_* of package
repositories. For me, that "held back" error message sometimes turned
out to mean I wasn't allowing APT to reach into the right corner of
the web to pull what I was asking it to pull.

My APT pulls from one repository and only one repository... so far. I
often avoided that "held back" message for myself by using "apt-cache
search" to see if something even existed for my setup before I asked
that it be installed.

The error message also references unstable, packages not being
created, yada-yada. In that instance, it means developers haven't
uploaded the package update that is being requested. That situation is
usually (DISCLAIMER: but not always) remedied by waiting a few days
then trying again.

In the meantime, this is the point where the more curious among us
waste the time in between by nosing around in the developers' neck of
the woods via places like:

https://tracker.debian.org/pkg/java-gcj-compat

Ooh.. Package is not... currently available... like for an extended
amount of time. Sorry to be the bearer of that particular news.

That's all I got.. Good luck!

Cindy :)

-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA

* runs with duct tape *

[toc] | [prev] | [next] | [standalone]

#169674

Cindy-Sue Causey wrote:
> Did you run "apt-get update"?


Sure.

> Also... I used to get that message a lot about holding packages back..
> People talk about "pinning" packages here. I've never done that but it
> might be one answer if you've ever actively done that yourself. I
> *a-sume* you'd have to unpin something to correct that, but I have no
> firsthand experience to base that on.

I don't think I ever did that. For the record, here is my whole /etc/apt/sources.list:

deb http://ftp.it.debian.org/debian wheezy main contrib non-free
deb-src http://ftp.it.debian.org/debian wheezy main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free

Also I have never used unstable or testing, just a long string of stable debians.

gg

[toc] | [prev] | [next] | [standalone]

#169682

On Monday 04 July 2016 14:50:21 Giovanni Gigante wrote:
> Hello,
> I have a wheezy installation (itself upgraded from previous versions)
> that I now want to upgrade to jessie.
> I was following the instructions for the preparation to the upgrade to
> jessie, and I got this:
>
> # dpkg --audit
> The following packages are missing the md5sums control file in the
> database, they need to be reinstalled:
>   java-gcj-compat      Java runtime environment using GIJ
>
> However, reinstalling this package seems impossible, as it apparently
> does not exist anymore:
>
> # apt-get install --reinstall java-gcj-compat
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Reinstallation of java-gcj-compat is not possible, it cannot be downloaded.
> 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
>
> There are other strange things. For example, gcj-jre is not installed on
> this system (?), but if I try to install it, I get:
>
> # apt-get install gcj-jre
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>   gcj-jre : Depends: gcj-jre-headless (>= 4:4.7.2-1) but it is not going
> to be installed
> E: Unable to correct problems, you have held broken packages.
>
> Apart from this the systems seem up to date. I have tried apt-get clean,
> apt-get dist-upgrade and aptitude, and none of them complain.
> I have no idea what to do next, in order to have a trouble-free system
> that I can safely upgrade to jessie. Suggestions?

Have you tried simply uninstalling them?  

You are supposed to do something with Java on Wheezy to go from, I think, jdk6 
to jdk7, and there has been a problem with jre for some time.  I rather think 
that you need the Oracle repositories or something...  I didn't take the 
details in because I have upgraded everybody to Jessie.

You can always put back anything you want after the upgrade.

Lisi

[toc] | [prev] | [next] | [standalone]

#169688

On 2016-07-04 15:50 +0200, Giovanni Gigante wrote:

> I have a wheezy installation (itself upgraded from previous versions)
> that I now want to upgrade to jessie.
> I was following the instructions for the preparation to the upgrade to
> jessie, and I got this:
>
> # dpkg --audit
> The following packages are missing the md5sums control file in the
> database, they need to be reinstalled:
>  java-gcj-compat      Java runtime environment using GIJ
>
> However, reinstalling this package seems impossible, as it apparently
> does not exist anymore:

This is correct, it has been removed in 2010[1], so it's not part of wheezy.

> There are other strange things. For example, gcj-jre is not installed
> on this system (?), but if I try to install it, I get:
>
> # apt-get install gcj-jre
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed. This may mean that you have
> requested an impossible situation or if you are using the unstable
> distribution that some required packages have not yet been created
> or been moved out of Incoming.
> The following information may help to resolve the situation:
>
> The following packages have unmet dependencies:
>  gcj-jre : Depends: gcj-jre-headless (>= 4:4.7.2-1) but it is not
> going to be installed
> E: Unable to correct problems, you have held broken packages.

Apparently java-gcj-compat depends on java-gcj-compat-headless, on which
gcj-jre-headless conflicts.  Now why apt-get refuses to uninstall
java-gcj-compat-headless in favor of gcj-jre-headless is unclear, but
apt-get *never* tells _why_ some package "is not going to be installed",
so you have to figure that out yourself.

Good luck,
          Sven


1. https://packages.qa.debian.org/j/java-gcj-compat/news/20100411T094718Z.html

[toc] | [prev] | [next] | [standalone]

#169697

Sven Joachim wrote:
> Apparently java-gcj-compat depends on java-gcj-compat-headless, on 
> which gcj-jre-headless conflicts. Now why apt-get refuses to uninstall 
> java-gcj-compat-headless in favor of gcj-jre-headless is unclear, but 
> apt-get *never* tells _why_ some package "is not going to be 
> installed", so you have to figure that out yourself.

It seems that doing it in two steps worked: first "apt-get install 
gcj-jre-headless" (which removed all java-gcj- things) and then "apt-get 
install gcj-jre".
I still have no clear idea of what happened, but now "dpkg --audit" 
seems satisfied.

Thanks everybody!

gg

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web