× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

RAIDiator 4.2.19 apt-get repos broken?

jmalmlund
Aspirant

RAIDiator 4.2.19 apt-get repos broken?

Hi,

I ran into a little snag when I had updated my ReadyNAS to the latest 4.2.19 release, when I logged in with ssh to install the dev tools I ran into this:


# apt-get install build-essential bzip2 comerr-dev g++ g++-4.1 libapr1-dev libc6-dev libc6-dev-amd64 libcurl4-openssl-dev \
libexpat1-dev libgd2-noxpm libkrb5-dev libncurses5-dev libpcre3-dev libpq-dev libssl-dev libstdc++6-4.1-dev libxml2-dev uuid-dev zlib1g-dev

Reading package lists... Done
Building dependency tree... 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:
bzip2: Depends: libbz2-1.0 (= 1.0.3-6) but 1.0.5-6 is to be installed
libc6-dev: Depends: libc6 (= 2.7-18lenny2) but 2.7-18lenny7 is to be installed
libc6-dev-amd64: Depends: libc6-amd64 (= 2.7-18lenny2) but 2.7-18lenny7 is to be installed
libncurses5-dev: Depends: ncurses-bin (= 5.7+20100313-5) but 5.5-5 is to be installed
libpcre3-dev: Depends: libpcre3 (= 6.7+7.4-4) but 7.6-2.1 is to be installed
libxml2-dev: Depends: libxml2 (= 2.6.27.dfsg-6+etch1) but 2.6.32.dfsg-5+lenny4 is to be installed
E: Broken packages

Any other developer that has stumbled across the same problem or is just me??

ps. sources.list content, ie. default

deb http://www.readynas.com/packages 4.2.19/

deb http://archive.debian.org/debian etch main
Message 1 of 5
mdgm-ntgr
NETGEAR Employee Retired

Re: RAIDiator 4.2.19 apt-get repos broken?

Try doing an "apt-get update" to read the new list first


Edit: Looking again it seems you may be trying to install stuff that you can't.
Message 2 of 5
jmalmlund
Aspirant

Re: RAIDiator 4.2.19 apt-get repos broken?

Well I shortened the my post a bit too much I guess 😐

I updated the system to 4.2.19 and then logged on and did
1. "apt-get update"
2. "apt-get -f install" (like I've done on previous system updates) and this has updated all installed packages to match the binaries installed by the system update

But! This time this is what happened...

apt-get -f install
Reading package lists... Done
Building dependency tree... Done
Correcting dependencies... Done
The following packages will be REMOVED:
build-essential bzip2 comerr-dev g++ g++-4.1 libapr1-dev libc6-dev libc6-dev-amd64 libcurl4-openssl-dev libexpat1-dev libgd2-noxpm libkrb5-dev
libncurses5-dev libpcre3-dev libpq-dev libssl-dev libstdc++6-4.1-dev libxml2-dev uuid-dev zlib1g-dev
0 upgraded, 0 newly installed, 20 to remove and 28 not upgraded.
Need to get 0B of archives.
After unpacking 60.1MB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 26528 files and directories currently installed.)
Removing build-essential ...
Removing bzip2 ...
Removing libpq-dev ...
Removing libkrb5-dev ...
Removing comerr-dev ...
Removing g++ ...
Removing libapr1-dev ...
Removing libpcre3-dev ...
Removing libexpat1-dev ...
Removing libcurl4-openssl-dev ...
Removing libssl-dev ...
Removing zlib1g-dev ...
Removing uuid-dev ...
Removing libc6-dev-amd64 ...
Removing libncurses5-dev ...
Removing libgd2-noxpm ...
Removing libxml2-dev ...
Removing libstdc++6-4.1-dev ...
Removing libc6-dev ...
Removing g++-4.1 ...


I didn't think twice about it as I've had to remove old versions of some packages on other systems before when doing system updates, I just assumed that I simply could do a "re-install" when I had all that taken care of.

As for installing stuff that I can't, well, I've had all of those packages installed since 4.2.15 so that's why I accepted the fact that I had to remove them but now even

apt-get install build-essential
Reading package lists... Done
Building dependency tree... 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.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
build-essential: Depends: libc6-dev but it is not going to be installed or
libc-dev
Depends: g++ (>= 4:4.1.1) but it is not going to be installed
E: Broken packages

apt-get install g++
Reading package lists... Done
Building dependency tree... 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.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
g++: Depends: g++-4.1 (>= 4.1.1-2) but it is not going to be installed
E: Broken packages

apt-get install g++-4.1
Reading package lists... Done
Building dependency tree... 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.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
g++-4.1: Depends: libstdc++6-4.1-dev (= 4.1.1-21) but it is not going to be installed
E: Broken packages

apt-get install libstdc++6-4.1-dev
Reading package lists... Done
Building dependency tree... 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.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libstdc++6-4.1-dev: Depends: libc6-dev (>= 2.3.6-7) but it is not going to be installed
E: Broken packages

apt-get install libc6-dev
Reading package lists... Done
Building dependency tree... 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.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libc6-dev: Depends: libc6 (= 2.7-18lenny2) but 2.7-18lenny7 is to be installed
E: Broken packages

fails!!

And I most certainly think that I should be able to install the "build-essential" package just like with previous releases of RAIDiator.

EDIT 2: Edit 1 had a type which pointed in a wrong direction, new back-tracking and I still end up with the same type of version mismatch...
Message 3 of 5
the_evaluator
Aspirant

Re: RAIDiator 4.2.19 apt-get repos broken?

if you look for my java crashplan post, i also saw a similar issue when i tried to do a dpkg-reconfigure, it appears something changed or is broken, so i'm bumping this.
Message 4 of 5
stephenc01
Aspirant

Re: RAIDiator 4.2.19 apt-get repos broken?

im having a similar issue.

dasupernas:/c/tmp/CrashPlan-install# apt-get install libc6-dev
Reading package lists... Done
Building dependency tree... 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.

Since you only requested a single operation it is extremely likely that
the package is simply not installable and a bug report against
that package should be filed.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
libc6-dev: Depends: libc6 (= 2.7-18lenny2) but 2.7-18lenny7 is to be installed
E: Broken packages
Message 5 of 5
Top Contributors
Discussion stats
  • 4 replies
  • 3714 views
  • 0 kudos
  • 4 in conversation
Announcements