why is apt 0.8.16~exp12 still in experimental ?
Hi all,
In one of the e-mails exchanged I got a suggestion if I wanted to help
the apt-team it would be nice if I was able to install apt and see if
it works. I am on a Debian sid machine.
While I had been busy with other things came today across bug 639290
(crawling through some stuff) . It seems part of the problem lies with
apt.
As a good citizen (and as I'm already on sid) I thought I will try out
the exp. bit.
After 5-6 various scenarios I simply have to gave up :-
Accept this solution? [Y/n/q/?] n
The following actions will resolve these dependencies:
Remove the following packages:
1) apt-file
2) apt-listbugs
3) apt-rdepends
4) apt-show-versions
5) apt-watch-backend
6) apt-watch-gnome
7) aptitude
8) debtags
9) dpkg-ruby
10) gnome
11) gnome-accessibility
12) gnome-core
13) gnome-desktop-environment
14) gnome-packagekit
15) libapt-pkg-perl
16) libdpkg-ruby1.8
17) libept1
18) lintian
19) packagekit
20) packagekit-backend-aptcc
21) ruby-debian
22) task-desktop
23) task-gnome-desktop
24) task-xfce-desktop
25) tasksel
26) tasksel-data
Install the following packages:
27) libapt-inst1.4 [0.8.16~exp12 (experimental)]
28) libept1.4.12 [1.0.6~exp1 (experimental)]
Upgrade the following packages:
29) apt-utils [0.8.15.9 (now, testing, unstable) -> 0.8.16~exp12
(experimental)]
30) python-apt [0.8.3+nmu1 (now, unstable) -> 0.8.4~exp1
(experimental)]
31) synaptic [0.75.4 (now, testing, unstable) -> 0.75.5~exp6
(experimental)]
Leave the following dependencies unresolved:
32) devscripts recommends lintian
33) libpackagekit-glib2-14 recommends packagekit (= 0.7.2-4) |
python-aptdaemon.pkcompat
34) python-packagekit recommends packagekit |
python-aptdaemon.pkcompat
Accept this solution? [Y/n/q/?] q
I do understand does try various solutions (and most of the times
gives the wrong solutions rather than the right solutions the first
few times around).
At this point it seems it just is breaking lot of things.Am I reading
it right or doing something wrong ?
I know this is not a bug but kind of a flux state (and most probably
fixed by the time wheezy enters into freeze). I am guessing getting
this into unstable would mean multiarching all the related tools as
shown above (IIRC the big move with this version is the multi-arch
thing).
Looking forward to having some sort of clarity. Sorry for the noise.
--
Regards,
Shirish Agarwal शिरीष अग्रवाल
My quotes in this email licensed under CC 3.0
http://creativecommons.org/licenses/by-nc/3.0/
http://flossexperiences.wordpress.com
065C 6D79 A68C E7EA 52B3 8D70 950D 53FB 729A 8B17
Reply to: