Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
unmet dependencies: libcurl4-openssl-dev
669 views
Skip to first unread message
Sivaram Neelakantan
Feb 4, 2015, 2:20:04 AM2/4/15
to
How does one go about fixing broken packages? I've recently started
using debian and apart some fiddling to get the latest emacs24.4 on
wheezy I have not done anything on the system. When I tried to
install libcurl4, I get the following error.
apt-get install libcurl4-openssl-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed.
[snipped 5 lines]
The following packages have unmet dependencies:
libcurl4-openssl-dev : Depends: librtmp-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages
Googling around and checking a few forums with various incantations of
apt-get with autoremove/clean/install/dist-upgrade didn't sort out
the problem. I now have no idea how to fix this issue.
I have a stock install of debian-kde iso and the current version seems
to be
cat /etc/debian_version
7.8
uname -a
Linux sivaram 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u1 x86_64 GNU/Linux
What should I do please to get the package installed?
sivaram
p.s first time user of debian
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87a90ur...@gmail.com
Ric Moore
Feb 4, 2015, 2:40:05 AM2/4/15
to
On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
>
> How does one go about fixing broken packages? I've recently started
> using debian and apart some fiddling to get the latest emacs24.4 on
> wheezy I have not done anything on the system. When I tried to
> install libcurl4, I get the following error.
As root user, apt-get install synaptic
>
> How does one go about fixing broken packages? I've recently started
> using debian and apart some fiddling to get the latest emacs24.4 on
> wheezy I have not done anything on the system. When I tried to
> install libcurl4, I get the following error.
Let it install your programs for you. It's a great GUI package tool,
that most use. It's point n click and installs all dependences for you. Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 4, 2015, 4:10:04 AM2/4/15
to
On Wed, Feb 04 2015,Ric Moore wrote:
> On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
>>
>> How does one go about fixing broken packages? I've recently started
>> using debian and apart some fiddling to get the latest emacs24.4 on
>> wheezy I have not done anything on the system. When I tried to
>> install libcurl4, I get the following error.
>
> As root user, apt-get install synaptic
> Let it install your programs for you. It's a great GUI package tool,
> that most use. It's point n click and installs all dependences for
> you. Ric
err...right. But will synaptic fix the above issue at all that I have
> On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
>>
>> How does one go about fixing broken packages? I've recently started
>> using debian and apart some fiddling to get the latest emacs24.4 on
>> wheezy I have not done anything on the system. When I tried to
>> install libcurl4, I get the following error.
>
> As root user, apt-get install synaptic
> Let it install your programs for you. It's a great GUI package tool,
> that most use. It's point n click and installs all dependences for
> you. Ric
currently? And does it matter that I'm using KDE version of debian
(debian-kde iso live cd version)
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 4, 2015, 4:50:04 AM2/4/15
to
On Wed, Feb 04 2015,Sivaram Neelakantan wrote:
> On Wed, Feb 04 2015,Ric Moore wrote:
>
>> On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
>>>
[snipped 5 lines]
> On Wed, Feb 04 2015,Ric Moore wrote:
>
>> On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
>>>
>> As root user, apt-get install synaptic
>> Let it install your programs for you. It's a great GUI package tool,
>> that most use. It's point n click and installs all dependences for
>> you. Ric
>
> err...right. But will synaptic fix the above issue at all that I have
> currently? And does it matter that I'm using KDE version of debian
> (debian-kde iso live cd version)
tool but it too gives the same error.
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Rusi Mody
Feb 4, 2015, 5:40:05 AM2/4/15
to
Note: apt-get, synaptic, and aptitude have different 'solvers' so its
good to have all three handy
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Dejan Jocic
Feb 4, 2015, 6:30:04 AM2/4/15
to
aptitude why-not libcurl4-openssl-dev
i task-kde-desktop Recommends system-config-printer
i A system-config-printer Depends python-cupshelpers (= 1.3.7-4)
i A python-cupshelpers Depends python-pycurl
i A python-pycurl Suggests libcurl4-gnutls-dev
p libcurl4-gnutls-dev Conflicts libcurl4-openssl-dev
That is what I get on Wheezy KDE.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Lisi Reisz
Feb 4, 2015, 6:30:05 AM2/4/15
to
On Wednesday 04 February 2015 07:35:29 Ric Moore wrote:
> As root user, apt-get install synaptic
> Let it install your programs for you. It's a great GUI package tool,
> that most use.
And you have got your statistics from?? I would seriously query that most
> As root user, apt-get install synaptic
> Let it install your programs for you. It's a great GUI package tool,
> that most use.
users, on this list anyhow, use synaptic. Personally, I greatly prefer
aptitude.
Lisi
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 4, 2015, 6:50:06 AM2/4/15
to
On Wed, Feb 04 2015,Dejan Jocic wrote:
[snipped 57 lines]
> aptitude why-not libcurl4-openssl-dev
> i task-kde-desktop Recommends system-config-printer
> i A system-config-printer Depends python-cupshelpers (= 1.3.7-4)
> i A python-cupshelpers Depends python-pycurl
> i A python-pycurl Suggests libcurl4-gnutls-dev
> p libcurl4-gnutls-dev Conflicts libcurl4-openssl-dev
>
> That is what I get on Wheezy KDE.
>
Which is *exactly* the same message for me too. I did try to uninstall
curl and reinstall it again but that didn't work. I still got the
same error as above.
Any suggestions on how to proceed to fix it?
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87iofh7...@gmail.com
[snipped 57 lines]
> aptitude why-not libcurl4-openssl-dev
> i task-kde-desktop Recommends system-config-printer
> i A system-config-printer Depends python-cupshelpers (= 1.3.7-4)
> i A python-cupshelpers Depends python-pycurl
> i A python-pycurl Suggests libcurl4-gnutls-dev
> p libcurl4-gnutls-dev Conflicts libcurl4-openssl-dev
>
> That is what I get on Wheezy KDE.
>
curl and reinstall it again but that didn't work. I still got the
same error as above.
Any suggestions on how to proceed to fix it?
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 4, 2015, 7:00:04 AM2/4/15
to
On Wed, Feb 04 2015,Lisi Reisz wrote:
> On Wednesday 04 February 2015 11:41:53 Sivaram Neelakantan wrote:
>> On Wed, Feb 04 2015,Dejan Jocic wrote:
[snipped 15 lines]
>
> Do you need libcurl4-openssl-dev? If not, have you tried just uninstalling
> it?
erm...yes, that's what I need to install as that's a requirement for
another R package that I need to install after this installs.
[snipped 6 lines]
>
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87egq57...@gmail.com
> On Wednesday 04 February 2015 11:41:53 Sivaram Neelakantan wrote:
>> On Wed, Feb 04 2015,Dejan Jocic wrote:
>
> Do you need libcurl4-openssl-dev? If not, have you tried just uninstalling
> it?
erm...yes, that's what I need to install as that's a requirement for
another R package that I need to install after this installs.
[snipped 6 lines]
>
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Lisi Reisz
Feb 4, 2015, 7:00:05 AM2/4/15
to
On Wednesday 04 February 2015 11:41:53 Sivaram Neelakantan wrote:
> On Wed, Feb 04 2015,Dejan Jocic wrote:
>
>
> [snipped 57 lines]
>
> > aptitude why-not libcurl4-openssl-dev
> > i task-kde-desktop Recommends system-config-printer
> > i A system-config-printer Depends python-cupshelpers (= 1.3.7-4)
> > i A python-cupshelpers Depends python-pycurl
> > i A python-pycurl Suggests libcurl4-gnutls-dev
> > p libcurl4-gnutls-dev Conflicts libcurl4-openssl-dev
> >
> > That is what I get on Wheezy KDE.
>
> Which is *exactly* the same message for me too. I did try to uninstall
> curl and reinstall it again but that didn't work. I still got the
> same error as above.
>
>
> Any suggestions on how to proceed to fix it?
>
>
> [snipped 57 lines]
>
> > aptitude why-not libcurl4-openssl-dev
> > i task-kde-desktop Recommends system-config-printer
> > i A system-config-printer Depends python-cupshelpers (= 1.3.7-4)
> > i A python-cupshelpers Depends python-pycurl
> > i A python-pycurl Suggests libcurl4-gnutls-dev
> > p libcurl4-gnutls-dev Conflicts libcurl4-openssl-dev
> >
> > That is what I get on Wheezy KDE.
>
> Which is *exactly* the same message for me too. I did try to uninstall
> curl and reinstall it again but that didn't work. I still got the
> same error as above.
>
>
> Any suggestions on how to proceed to fix it?
Do you need libcurl4-openssl-dev? If not, have you tried just uninstalling
it?
And come to that can anyone explain why a "suggests" is holding things up?
it?
Perhaps a change to aptitude's default settings to not hold up for suggests?
Lisi
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Dejan Jocic
Feb 4, 2015, 3:30:04 PM2/4/15
to
On Wed, Feb 04 2015,Dejan Jocic wrote:
[snipped 57 lines]
> aptitude why-not libcurl4-openssl-dev
> i task-kde-desktop Recommends system-config-printer
> i A system-config-printer Depends python-cupshelpers (= 1.3.7-4)
> i A python-cupshelpers Depends python-pycurl
> i A python-pycurl Suggests libcurl4-gnutls-dev
> p libcurl4-gnutls-dev Conflicts libcurl4-openssl-dev
>
> That is what I get on Wheezy KDE.
>
Which is *exactly* the same message for me too. I did try to uninstall
curl and reinstall it again but that didn't work. I still got the
same error as above.
Any suggestions on how to proceed to fix it?
sivaram
[snipped 57 lines]
> aptitude why-not libcurl4-openssl-dev
> i task-kde-desktop Recommends system-config-printer
> i A system-config-printer Depends python-cupshelpers (= 1.3.7-4)
> i A python-cupshelpers Depends python-pycurl
> i A python-pycurl Suggests libcurl4-gnutls-dev
> p libcurl4-gnutls-dev Conflicts libcurl4-openssl-dev
>
> That is what I get on Wheezy KDE.
>
Which is *exactly* the same message for me too. I did try to uninstall
curl and reinstall it again but that didn't work. I still got the
same error as above.
Any suggestions on how to proceed to fix it?
Well, I can not tell, there is not enough informations for that. What I
said about aptitude why-not was just as example. As far as I could see
from start of your thread, you said that problem is:
"The following packages have unmet dependencies:
libcurl4-openssl-dev : Depends: librtmp-dev but it is not going to be
installed
E: Unable to correct problems, you have held broken packages"
installed without problems on my system. Try aptitude -h and see all
options it will give you. For example, there is option for trying to
aggressively fix broken packages. And if you have broken packages, it
was most likely done by some of your previous actions(you did
mention some fiddling) . You can try to find out what went wrong and
to reverse your actions. Also, you can try to use aptitude instead of
apt-get when you are trying to install libcurl4-openssl-dev, think that it
might give you more informations and options in this case. On other
hand, do not know why you are trying to install libcurl4-openssl-dev,
why not directly emacs24 for Wheezy backports? Not that I can
understand why would anyone want that abomination of self called
text editor(just kidding, not trying to start religious war about text
editors).
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Feb 4, 2015, 3:30:05 PM2/4/15
to
On 02/04/2015 06:26 AM, Lisi Reisz wrote:
> On Wednesday 04 February 2015 07:35:29 Ric Moore wrote:
>> As root user, apt-get install synaptic
>> Let it install your programs for you. It's a great GUI package tool,
>> that most use.
>
> And you have got your statistics from?? I would seriously query that most
> users, on this list anyhow, use synaptic. Personally, I greatly prefer
> aptitude.
Well, there ya go. The people I hang with seem to prefer it and have for
> On Wednesday 04 February 2015 07:35:29 Ric Moore wrote:
>> As root user, apt-get install synaptic
>> Let it install your programs for you. It's a great GUI package tool,
>> that most use.
>
> And you have got your statistics from?? I would seriously query that most
> users, on this list anyhow, use synaptic. Personally, I greatly prefer
> aptitude.
eons. It's simple point n click, and rarely gums things up. I seriously
doubt that the OP would be where he is now, had he used it to start with.
So, my response was to suggest something pretty much dead easy to use,
especially for a first time user. You've been around forever, so
aptitude and it's interface is easy for you. I've been around forever,
as well, and I don't like it, ergo I don't recommend it. To each their
own, eh?
The only thing synaptic and aptitude cannot save you from is using dpkg
to manually shoehorn some package in. I suspect that this may be the
case. :) Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54D27EF...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Bob Proulx
Feb 4, 2015, 4:40:04 PM2/4/15
to
Sivaram Neelakantan wrote:
> How does one go about fixing broken packages?
Double check every entry being used in /etc/apt/sources.list and any
> How does one go about fixing broken packages?
additional file /etc/apt/sources.list.d/*. You said you were using
Wheezy. In that case you should have *only* these entries.
deb http://http.debian.net/debian wheezy main contrib non-free
deb-src http://http.debian.net/debian wheezy main contrib non-free
deb http://http.debian.net/debian wheezy-updates main contrib non-free
deb-src http://http.debian.net/debian wheezy-updates main contrib non-free
deb http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free
Okay to use local specific mirror sets such as ftp.us.debian.org
instead of http.debian.net in the above.
If you have any extra entries or any extra files of entries please
remove them. If you have extra files in /etc/apt/sources.list.d/* say
where they came from. Some 3rd party packages install files then
people have problems and ask about broken packages.
After fixing your sources.list entries run apt-get update.
# apt-get update
At that point all of the available packages should be known good and
not have any dependency problems.
Then run the -f,--fix-broken option.
# apt-get install -f
That has a good chance of fixing everything. However if you have
installed newer packages from another archive it won't be able to
downgrade them.
> I've recently started using debian and apart some fiddling to get
> the latest emacs24.4 on wheezy I have not done anything on the
> system.
24 on Wheezy? Wheezy released with Emacs 23 of course.
Say exactly what you did and people on this list have a good chance to
tell you how to repair it.
> When I tried to install libcurl4, I get the following error.
>
> apt-get install libcurl4-openssl-dev
> Reading package lists... Done
> Building dependency tree
> Reading state information... Done
> Some packages could not be installed.
>
> [snipped 5 lines]
>
> The following packages have unmet dependencies:
> libcurl4-openssl-dev : Depends: librtmp-dev but it is not going to be installed
breakage as referenced above. What is the output of:
apt-cache policy librtmp-dev
> p.s first time user of debian
car, remove the fuel injection system, partially replace it with
another, then your fuel economy may suffer. :-)
Bob
Ric Moore
Feb 4, 2015, 7:10:04 PM2/4/15
to
On 02/04/2015 04:35 PM, Bob Proulx wrote:
> Welcome to Debian! But as with anything if you open the hood of your
> car, remove the fuel injection system, partially replace it with
> another, then your fuel economy may suffer. :-)
The standing rule is that if you break it, you get to keep both pieces.
> Welcome to Debian! But as with anything if you open the hood of your
> car, remove the fuel injection system, partially replace it with
> another, then your fuel economy may suffer. :-)
At least that used to be the rule.
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54D2B2ED...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Lisi Reisz
Feb 4, 2015, 7:20:04 PM2/4/15
to
On Wednesday 04 February 2015 20:20:10 Ric Moore wrote:
> On 02/04/2015 06:26 AM, Lisi Reisz wrote:
> > On Wednesday 04 February 2015 07:35:29 Ric Moore wrote:
> >> As root user, apt-get install synaptic
> >> Let it install your programs for you. It's a great GUI package tool,
> >> that most use.
> >
> > And you have got your statistics from?? I would seriously query that
> > most users, on this list anyhow, use synaptic. Personally, I greatly
> > prefer aptitude.
>
> Well, there ya go. The people I hang with seem to prefer it and have for
> eons. It's simple point n click, and rarely gums things up. I seriously
> doubt that the OP would be where he is now, had he used it to start with.
>
> So, my response was to suggest something pretty much dead easy to use,
> especially for a first time user. You've been around forever, so
> aptitude and it's interface is easy for you. I've been around forever,
> as well, and I don't like it, ergo I don't recommend it. To each their
> own, eh?
Of course! I wasn't objecting to your using synaptic. I can't imagine why
> On 02/04/2015 06:26 AM, Lisi Reisz wrote:
> > On Wednesday 04 February 2015 07:35:29 Ric Moore wrote:
> >> As root user, apt-get install synaptic
> >> Let it install your programs for you. It's a great GUI package tool,
> >> that most use.
> >
> > And you have got your statistics from?? I would seriously query that
> > most users, on this list anyhow, use synaptic. Personally, I greatly
> > prefer aptitude.
>
> Well, there ya go. The people I hang with seem to prefer it and have for
> eons. It's simple point n click, and rarely gums things up. I seriously
> doubt that the OP would be where he is now, had he used it to start with.
>
> So, my response was to suggest something pretty much dead easy to use,
> especially for a first time user. You've been around forever, so
> aptitude and it's interface is easy for you. I've been around forever,
> as well, and I don't like it, ergo I don't recommend it. To each their
> own, eh?
you want to. ;-) I have more than once used aptitude to sort out synpatic
snafus. But as you say, to each his own. No, I was objecting to your trying
to claim that, because you use it, it follows ipso facto that *most* people
do the same.
Lisi
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 4, 2015, 10:10:04 PM2/4/15
to
On Wed, Feb 04 2015,Bob Proulx wrote:
> Sivaram Neelakantan wrote:
>> How does one go about fixing broken packages?
>
> Double check every entry being used in /etc/apt/sources.list and any
> additional file /etc/apt/sources.list.d/*. You said you were using
> Wheezy. In that case you should have *only* these entries.
>
> deb http://http.debian.net/debian wheezy main contrib non-free
> deb-src http://http.debian.net/debian wheezy main contrib non-free
>
> deb http://http.debian.net/debian wheezy-updates main contrib non-free
> deb-src http://http.debian.net/debian wheezy-updates main contrib non-free
>
> deb http://security.debian.org/ wheezy/updates main contrib non-free
> deb-src http://security.debian.org/ wheezy/updates main contrib non-free
>
> Okay to use local specific mirror sets such as ftp.us.debian.org
> instead of http.debian.net in the above.
This is what I have.
> Sivaram Neelakantan wrote:
>> How does one go about fixing broken packages?
>
> Double check every entry being used in /etc/apt/sources.list and any
> additional file /etc/apt/sources.list.d/*. You said you were using
> Wheezy. In that case you should have *only* these entries.
>
> deb http://http.debian.net/debian wheezy main contrib non-free
> deb-src http://http.debian.net/debian wheezy main contrib non-free
>
> deb http://http.debian.net/debian wheezy-updates main contrib non-free
> deb-src http://http.debian.net/debian wheezy-updates main contrib non-free
>
> deb http://security.debian.org/ wheezy/updates main contrib non-free
> deb-src http://security.debian.org/ wheezy/updates main contrib non-free
>
> Okay to use local specific mirror sets such as ftp.us.debian.org
> instead of http.debian.net in the above.
--8<---------------cut here---------------start------------->8---
cat /etc/apt/sources.list
#
# deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20141121-01:55]/ wheezy main
#deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20141121-01:55]/ wheezy main
deb http://kartolo.sby.datautama.net.id/debian/ wheezy main
deb-src http://kartolo.sby.datautama.net.id/debian/ wheezy main
# wheezy-updates, previously known as 'volatile'
deb http://kartolo.sby.datautama.net.id/debian/ wheezy-updates main
deb-src http://kartolo.sby.datautama.net.id/debian/ wheezy-updates main
#wheezy backports
#deb http://kartolo.sby.datautama.net.id/debian wheezy-backports main
#wheezy R packages
deb http://ftp5.gwdg.de/pub/misc/cran/bin/linux/debian wheezy-cran3/
#deb http://cran.uni-muenster.de/bin/linux/debian wheezy-cran3/
--8<---------------cut here---------------end--------------->8---
The backports line, I added to get emacs24.4 and then commented it out
again. The cran3 line is for R packages as suggested in the CRAN
website. I also downloaded the rstudio deb package from rstudio site
and installed that.
>
> If you have any extra entries or any extra files of entries please
> remove them. If you have extra files in /etc/apt/sources.list.d/* say
> where they came from. Some 3rd party packages install files then
> people have problems and ask about broken packages.
> After fixing your sources.list entries run apt-get update.
>
> # apt-get update
>
> At that point all of the available packages should be known good and
> not have any dependency problems.
>
> Then run the -f,--fix-broken option.
>
> # apt-get install -f
>
> That has a good chance of fixing everything. However if you have
> installed newer packages from another archive it won't be able to
> downgrade them.
>
libcurl4 install still fails
>> I've recently started using debian and apart some fiddling to get
>> the latest emacs24.4 on wheezy I have not done anything on the
>> system.
>
> Alarm bells! Alarm bells! Exactly what did you do to install Emacs
> 24 on Wheezy? Wheezy released with Emacs 23 of course.
install of emacs24.4 and that installed what I wanted.
>
> Say exactly what you did and people on this list have a good chance to
> tell you how to repair it.
>
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87oap9x...@gmail.com
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Bob Proulx
Feb 5, 2015, 3:20:06 AM2/5/15
to
Sivaram Neelakantan wrote:
> This is what I have.
>
> --8<---------------cut here---------------start------------->8---
> cat /etc/apt/sources.list
> #
>
> # deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20141121-01:55]/ wheezy main
>
> #deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20141121-01:55]/ wheezy main
The above looks noisy to me. I suggest removing those commented out
> This is what I have.
>
> --8<---------------cut here---------------start------------->8---
> cat /etc/apt/sources.list
> #
>
> # deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20141121-01:55]/ wheezy main
>
> #deb cdrom:[Debian GNU/Linux 7 _Wheezy_ - Official Snapshot amd64 LIVE/INSTALL Binary 20141121-01:55]/ wheezy main
entries to simplify.
> deb http://kartolo.sby.datautama.net.id/debian/ wheezy main
> deb-src http://kartolo.sby.datautama.net.id/debian/ wheezy main
>
> deb http://security.debian.org/ wheezy/updates main
> deb-src http://security.debian.org/ wheezy/updates main
>
> # wheezy-updates, previously known as 'volatile'
> deb http://kartolo.sby.datautama.net.id/debian/ wheezy-updates main
> deb-src http://kartolo.sby.datautama.net.id/debian/ wheezy-updates main
mirror. Looks okay.
Wheezy backports is okay.
> #wheezy R packages
> deb http://ftp5.gwdg.de/pub/misc/cran/bin/linux/debian wheezy-cran3/
> #deb http://cran.uni-muenster.de/bin/linux/debian wheezy-cran3/
party repositories. They tend to be the problem. I would comment
that out while you are debugging the current problem.
> The backports line, I added to get emacs24.4 and then commented it out
> again.
> Tried the above, nothing happens. No errors or anything. And the
> libcurl4 install still fails
$ apt-cache policy libcurl4-openssl-dev librtmp-dev
libcurl4-openssl-dev:
Installed: (none)
Candidate: 7.26.0-1+wheezy11
Version table:
7.26.0-1+wheezy11 0
500 http://security.debian.org/ wheezy/updates/main amd64 Packages
7.26.0-1+wheezy10 0
500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages
librtmp-dev:
Installed: (none)
Candidate: 2.4+20111222.git4e06e21-1
Version table:
2.4+20111222.git4e06e21-1 0
500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages
Your previous error said it could not install librtmp-dev as a
dependency. But it should be in the archive right next to it.
> >> I've recently started using debian and apart some fiddling to get
> >> the latest emacs24.4 on wheezy I have not done anything on the
> >> system.
> >
> > Alarm bells! Alarm bells! Exactly what did you do to install Emacs
> > 24 on Wheezy? Wheezy released with Emacs 23 of course.
>
> After adding the backports to the sources.list, I did a apt-get
> install of emacs24.4 and that installed what I wanted.
people sometimes do really scary things. But emacs from backports
should be just fine.
Bob
Brian
Feb 5, 2015, 7:10:05 AM2/5/15
to
On Thu 05 Feb 2015 at 01:17:04 -0700, Bob Proulx wrote:
> Sivaram Neelakantan wrote:
>
Not only does it look okay but it also behaves okay for me.
> Sivaram Neelakantan wrote:
>
With that as the only line in sources.list I had no problem installing
libcurl4-openssl-dev.
[Snip]
> Your previous error said it could not install librtmp-dev as a
> dependency. But it should be in the archive right next to it.
apt-get install librtmp-dev
If there is any failure we would want to see the complete output of the
command.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 5, 2015, 12:10:05 PM2/5/15
to
On Thu, Feb 05 2015,Bob Proulx wrote:
> Sivaram Neelakantan wrote:
[snipped 36 lines]
> Sivaram Neelakantan wrote:
>
> When tracking down installation errors I am always suspicious of third
> party repositories. They tend to be the problem. I would comment
> that out while you are debugging the current problem.
>
>> Tried the above, nothing happens. No errors or anything. And the
>> libcurl4 install still fails
>
> What is your output for this? Here is what it should show.
>
> $ apt-cache policy libcurl4-openssl-dev librtmp-dev
> libcurl4-openssl-dev:
> Installed: (none)
> Candidate: 7.26.0-1+wheezy11
> Version table:
> 7.26.0-1+wheezy11 0
> 500 http://security.debian.org/ wheezy/updates/main amd64 Packages
> 7.26.0-1+wheezy10 0
> 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages
> librtmp-dev:
> Installed: (none)
> Candidate: 2.4+20111222.git4e06e21-1
> Version table:
> 2.4+20111222.git4e06e21-1 0
> 500 http://ftp.us.debian.org/debian/ wheezy/main amd64 Packages
apt-cache policy libcurl4-openssl-dev librtmp-dev
libcurl4-openssl-dev:
Installed: (none)
Version table:
7.26.0-1+wheezy12 0
500 http://security.debian.org/ wheezy/updates/main amd64 Packages
7.26.0-1+wheezy11 0
500 http://kartolo.sby.datautama.net.id/debian/ wheezy/main amd64 Packages
librtmp-dev:
Installed: (none)
Candidate: 2.4+20111222.git4e06e21-1
Version table:
2.4+20111222.git4e06e21-1 0
500 http://kartolo.sby.datautama.net.id/debian/ wheezy/main amd64 Packages
Installed: (none)
Candidate: 2.4+20111222.git4e06e21-1
Version table:
2.4+20111222.git4e06e21-1 0
--8<---------------cut here---------------end--------------->8---
I still have the same errors.
[snipped 15 lines]
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 5, 2015, 12:10:06 PM2/5/15
to
On Thu, Feb 05 2015,Brian wrote:
> On Thu 05 Feb 2015 at 01:17:04 -0700, Bob Proulx wrote:
>
>> Sivaram Neelakantan wrote:
[snipped 16 lines]
> On Thu 05 Feb 2015 at 01:17:04 -0700, Bob Proulx wrote:
>
>> Sivaram Neelakantan wrote:
> Perhaps the OP can have a single line as I did and try
>
> apt-get install librtmp-dev
>
> If there is any failure we would want to see the complete output of the
> command.
>
>
--8<---------------cut here---------------start------------->8---
apt-get install libcurl4-openssl-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
Reading package lists... Done
Building dependency tree
Reading state information... Done
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:
Depends: libkrb5-dev but it is not going to be installed
Depends: librtmp-dev but it is not going to be installed
Depends: libssl-dev but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
--8<---------------cut here---------------end--------------->8---
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Feb 5, 2015, 1:10:04 PM2/5/15
to
On Thu 05 Feb 2015 at 22:38:28 +0530, Sivaram Neelakantan wrote:
> On Thu, Feb 05 2015,Brian wrote:
>
> > On Thu 05 Feb 2015 at 01:17:04 -0700, Bob Proulx wrote:
> >
> >> Sivaram Neelakantan wrote:
>
> [snipped 16 lines]
>
> > Perhaps the OP can have a single line as I did and try
> >
> > apt-get install librtmp-dev
> >
> > If there is any failure we would want to see the complete output of the
> > command.
> >
> >
>
> Tried that, no cigar. Got more errors. Now what? :)
First we point out the command you were invited to run *and* give the
> On Thu, Feb 05 2015,Brian wrote:
>
> > On Thu 05 Feb 2015 at 01:17:04 -0700, Bob Proulx wrote:
> >
> >> Sivaram Neelakantan wrote:
>
> [snipped 16 lines]
>
> > Perhaps the OP can have a single line as I did and try
> >
> > apt-get install librtmp-dev
> >
> > If there is any failure we would want to see the complete output of the
> > command.
> >
> >
>
> Tried that, no cigar. Got more errors. Now what? :)
output of was
apt-get install librtmp-dev
Next we look at the output you did give.
> --8<---------------cut here---------------start------------->8---
> apt-get install libcurl4-openssl-dev
> 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:
> libcurl4-openssl-dev : Depends: libcurl3 (= 7.26.0-1+wheezy11) but 7.26.0-1+wheezy12 is to be installed
is version 7.26.0-1+wheezy11. So the question becomes: Why does your
system want to install this version when 7.26.0-1+wheezy12 is on your
mirror and 'apt-cache policy libcurl4-openssl-dev' has it as an
installation candidate?
If you are becoming desparate you could download 7.26.0-1+wheezy12,
install with
dpkg -i <package>
and run 'apt-get -f install'. This should stand some chance of success.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Bob Proulx
Feb 5, 2015, 4:10:04 PM2/5/15
to
Brian wrote:
Do you have an /etc/apt/preferences file? Or /etc/apt/preferences.d/*
files? If so what is in it? Remove it and try the apt-get update and
apt-get install again.
Bob
> Sivaram Neelakantan wrote:
> > libcurl4-openssl-dev : Depends: libcurl3 (= 7.26.0-1+wheezy11) but 7.26.0-1+wheezy12 is to be installed
>
> The libcurl4-openssl-dev which depends on libcurl3 (= 7.26.0-1+wheezy11)
> is version 7.26.0-1+wheezy11. So the question becomes: Why does your
> system want to install this version when 7.26.0-1+wheezy12 is on your
> mirror and 'apt-cache policy libcurl4-openssl-dev' has it as an
> installation candidate?
Bad pinning?
> > libcurl4-openssl-dev : Depends: libcurl3 (= 7.26.0-1+wheezy11) but 7.26.0-1+wheezy12 is to be installed
>
> The libcurl4-openssl-dev which depends on libcurl3 (= 7.26.0-1+wheezy11)
> is version 7.26.0-1+wheezy11. So the question becomes: Why does your
> system want to install this version when 7.26.0-1+wheezy12 is on your
> mirror and 'apt-cache policy libcurl4-openssl-dev' has it as an
> installation candidate?
Do you have an /etc/apt/preferences file? Or /etc/apt/preferences.d/*
files? If so what is in it? Remove it and try the apt-get update and
apt-get install again.
Bob
Ric Moore
Feb 5, 2015, 4:30:06 PM2/5/15
to
from the sources list after. What he REALLY needs is a fresh install to
Jessie to get what he wants. That would be the simplest way to go. :) Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54D3DEB4...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 6, 2015, 1:40:05 AM2/6/15
to
On Thu, Feb 05 2015,Bob Proulx wrote:
> Brian wrote:
[snipped 12 lines]
> Do you have an /etc/apt/preferences file? Or /etc/apt/preferences.d/*
> files? If so what is in it? Remove it and try the apt-get update and
> apt-get install again.
directory. And if I comment out everything except the first wheezy
main, and try to install rtmp-dev, I get libgnutls-dev broken packages
error.
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Feb 6, 2015, 9:10:05 AM2/6/15
to
On Fri 06 Feb 2015 at 12:05:15 +0530, Sivaram Neelakantan wrote:
> On Thu, Feb 05 2015,Bob Proulx wrote:
>
> > Brian wrote:
>
> [snipped 12 lines]
>
> > Do you have an /etc/apt/preferences file? Or /etc/apt/preferences.d/*
> > files? If so what is in it? Remove it and try the apt-get update and
> > apt-get install again.
>
> No, I don't have any preferences or anything in preferences.d
> directory. And if I comment out everything except the first wheezy
> main, and try to install rtmp-dev, I get libgnutls-dev broken packages
> error.
It is good that you have provided sufficient information in this thread
> On Thu, Feb 05 2015,Bob Proulx wrote:
>
> > Brian wrote:
>
> [snipped 12 lines]
>
> > Do you have an /etc/apt/preferences file? Or /etc/apt/preferences.d/*
> > files? If so what is in it? Remove it and try the apt-get update and
> > apt-get install again.
>
> No, I don't have any preferences or anything in preferences.d
> directory. And if I comment out everything except the first wheezy
> main, and try to install rtmp-dev, I get libgnutls-dev broken packages
> error.
to be able to follow in your footsteps as I am now able to reproduce
your problem.
My sources list has the security entry followed by kartolo lines for
wheezy and wheezy-backports. The mirror used for the second two lines is
of no consequence.
I installed emacs24:
apt-get -t wheezy-backports install emacs24
Then
apt-get install libcurl4-openssl-dev
produces exactly the same outcome you describe in your first post.
I never use backports so am not overly familiar with its operation or
how it fits with the rest of the archives. However, this does not look
like something that should happen. If we understood what is happening
we can produce a solution. (Other than purging emacs24 :)).
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Feb 6, 2015, 10:10:05 AM2/6/15
to
On Fri 06 Feb 2015 at 14:04:25 +0000, Brian wrote:
> I never use backports so am not overly familiar with its operation or
> how it fits with the rest of the archives. However, this does not look
> like something that should happen. If we understood what is happening
> we can produce a solution. (Other than purging emacs24 :)).
As far as I can see, purging emacs24 may be the only solution.
> I never use backports so am not overly familiar with its operation or
> how it fits with the rest of the archives. However, this does not look
> like something that should happen. If we understood what is happening
> we can produce a solution. (Other than purging emacs24 :)).
libcurl4-openssl-dev requires libp11-kit-dev and the latter depends on
libp11-kit0 (= 0.12-3).
The installation of emacs24 upgrades libp11-kit0 to 0.20.7-1~bpo70+1, so
libcurl4-openssl-dev cannot be installed.
This looks like a bug against the emacs24 backport. Opinions?
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 6, 2015, 11:40:05 AM2/6/15
to
On Fri, Feb 06 2015,Brian wrote:
[snipped 17 lines]
> It is good that you have provided sufficient information in this thread
> to be able to follow in your footsteps as I am now able to reproduce
> your problem.
>
> My sources list has the security entry followed by kartolo lines for
> wheezy and wheezy-backports. The mirror used for the second two lines is
> of no consequence.
>
> I installed emacs24:
>
> apt-get -t wheezy-backports install emacs24
>
> Then
>
> apt-get install libcurl4-openssl-dev
>
> produces exactly the same outcome you describe in your first post.
Thanks for helping me out. Appreciate your follow ups with a new user
like me.
>
> I never use backports so am not overly familiar with its operation or
> how it fits with the rest of the archives. However, this does not look
> like something that should happen. If we understood what is happening
> we can produce a solution. (Other than purging emacs24 :)).
>
err....purging Emacs24? The only reason I added backports was to get
the latest release of Emacs. Well, I'd probably give up on doing
anything with Rcurl/libcurl CRAN library which is a small price to
pay. It's not like I don't know wget and shell escapes to scrape
websites.
Again, thanks for the help, appreciated.
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87pp9nn...@gmail.com
[snipped 17 lines]
> It is good that you have provided sufficient information in this thread
> to be able to follow in your footsteps as I am now able to reproduce
> your problem.
>
> My sources list has the security entry followed by kartolo lines for
> wheezy and wheezy-backports. The mirror used for the second two lines is
> of no consequence.
>
> I installed emacs24:
>
> apt-get -t wheezy-backports install emacs24
>
> Then
>
> apt-get install libcurl4-openssl-dev
>
> produces exactly the same outcome you describe in your first post.
like me.
>
> I never use backports so am not overly familiar with its operation or
> how it fits with the rest of the archives. However, this does not look
> like something that should happen. If we understood what is happening
> we can produce a solution. (Other than purging emacs24 :)).
>
the latest release of Emacs. Well, I'd probably give up on doing
anything with Rcurl/libcurl CRAN library which is a small price to
pay. It's not like I don't know wget and shell escapes to scrape
websites.
Again, thanks for the help, appreciated.
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 6, 2015, 11:50:07 AM2/6/15
to
On Fri, Feb 06 2015,Brian wrote:
> On Fri 06 Feb 2015 at 14:04:25 +0000, Brian wrote:
>
>> I never use backports so am not overly familiar with its operation or
>> how it fits with the rest of the archives. However, this does not look
>> like something that should happen. If we understood what is happening
>> we can produce a solution. (Other than purging emacs24 :)).
>
> As far as I can see, purging emacs24 may be the only solution.
>
Oh well, that's not something I want to do.
>
>> I never use backports so am not overly familiar with its operation or
>> how it fits with the rest of the archives. However, this does not look
>> like something that should happen. If we understood what is happening
>> we can produce a solution. (Other than purging emacs24 :)).
>
> As far as I can see, purging emacs24 may be the only solution.
>
> libcurl4-openssl-dev requires libp11-kit-dev and the latter depends on
> libp11-kit0 (= 0.12-3).
>
> The installation of emacs24 upgrades libp11-kit0 to 0.20.7-1~bpo70+1, so
> libcurl4-openssl-dev cannot be installed.
>
> This looks like a bug against the emacs24 backport. Opinions?
>
backporting.
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
David Wright
Feb 6, 2015, 12:20:05 PM2/6/15
to
Quoting Sivaram Neelakantan (nsivar...@gmail.com):
> On Fri, Feb 06 2015,Brian wrote:
> > On Fri 06 Feb 2015 at 14:04:25 +0000, Brian wrote:
> > As far as I can see, purging emacs24 may be the only solution.
>
> Oh well, that's not something I want to do.
Would installing jessie (has emacs24) instead of wheezy be an option?
> On Fri, Feb 06 2015,Brian wrote:
> > On Fri 06 Feb 2015 at 14:04:25 +0000, Brian wrote:
> > As far as I can see, purging emacs24 may be the only solution.
>
> Oh well, that's not something I want to do.
You said you were new to Debian, so perhaps there's little point in
getting comfortable on a system that's about to be superceded (and,
in the minds of many, already has been).
Cheers,
David.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Lisi Reisz
Feb 6, 2015, 12:20:05 PM2/6/15
to
On Friday 06 February 2015 16:36:43 Sivaram Neelakantan wrote:
> err....purging Emacs24? The only reason I added backports was to get
> the latest release of Emacs. Well, I'd probably give up on doing
> anything with Rcurl/libcurl CRAN library which is a small price to
> pay. It's not like I don't know wget and shell escapes to scrape
> websites.
Unfortunately, it looks as though you may have to .... but had you thought of
> err....purging Emacs24? The only reason I added backports was to get
> the latest release of Emacs. Well, I'd probably give up on doing
> anything with Rcurl/libcurl CRAN library which is a small price to
> pay. It's not like I don't know wget and shell escapes to scrape
> websites.
Jessie? That might let you have both! Or is there a reason why you don't
want Jessie?
Or you could live with what you have got for now and upgrade to Jessie fairly
soon after it becomes Stable.
Or just live with what you have got.
Anyhow, welcome to Debian. I don't think anyone has said that. ;-)
Lisi
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Feb 6, 2015, 12:50:04 PM2/6/15
to
On Fri 06 Feb 2015 at 11:11:32 -0600, David Wright wrote:
> Quoting Sivaram Neelakantan (nsivar...@gmail.com):
> > On Fri, Feb 06 2015,Brian wrote:
> > > On Fri 06 Feb 2015 at 14:04:25 +0000, Brian wrote:
> > > As far as I can see, purging emacs24 may be the only solution.
> >
> > Oh well, that's not something I want to do.
>
> Would installing jessie (has emacs24) instead of wheezy be an option?
> You said you were new to Debian, so perhaps there's little point in
> getting comfortable on a system that's about to be superceded (and,
> in the minds of many, already has been).
This might be something Sivaram Neelakantan is prepared to do to get
> Quoting Sivaram Neelakantan (nsivar...@gmail.com):
> > On Fri, Feb 06 2015,Brian wrote:
> > > On Fri 06 Feb 2015 at 14:04:25 +0000, Brian wrote:
> > > As far as I can see, purging emacs24 may be the only solution.
> >
> > Oh well, that's not something I want to do.
>
> Would installing jessie (has emacs24) instead of wheezy be an option?
> You said you were new to Debian, so perhaps there's little point in
> getting comfortable on a system that's about to be superceded (and,
> in the minds of many, already has been).
over this problem in his situation. But remember that Wheezy will be
with us for at least another year and this bug would remain in the
backports archive.
I'd be prepared to report it (if Sivaram Neelakantan doesn't) but is it
in the emacs package? Also, what severity? If it is seen as breaking
unrelated software on the system it would be "critical".
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 6, 2015, 12:50:05 PM2/6/15
to
On Fri, Feb 06 2015,David Wright wrote:
> Quoting Sivaram Neelakantan (nsivar...@gmail.com):
>> On Fri, Feb 06 2015,Brian wrote:
>> > On Fri 06 Feb 2015 at 14:04:25 +0000, Brian wrote:
>> > As far as I can see, purging emacs24 may be the only solution.
>>
>> Oh well, that's not something I want to do.
>
> Would installing jessie (has emacs24) instead of wheezy be an option?
> You said you were new to Debian, so perhaps there's little point in
> getting comfortable on a system that's about to be superceded (and,
> in the minds of many, already has been).
>
Since I have nothing of import (personal data wise in /home) on this
> Quoting Sivaram Neelakantan (nsivar...@gmail.com):
>> On Fri, Feb 06 2015,Brian wrote:
>> > On Fri 06 Feb 2015 at 14:04:25 +0000, Brian wrote:
>> > As far as I can see, purging emacs24 may be the only solution.
>>
>> Oh well, that's not something I want to do.
>
> Would installing jessie (has emacs24) instead of wheezy be an option?
> You said you were new to Debian, so perhaps there's little point in
> getting comfortable on a system that's about to be superceded (and,
> in the minds of many, already has been).
>
debian-kde iso wheezy install, is there an upgrade path that will give
me jessie with the installers, as is?
I just want the kde toolkits(upgraded of course) of wheezy in jessie
too. Is that possible?
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 6, 2015, 1:10:04 PM2/6/15
to
On Fri, Feb 06 2015,Lisi Reisz wrote:
[snipped 7 lines]
> Unfortunately, it looks as though you may have to .... but had you thought of
> Jessie?
The missus is asking "who's Jessie and why are you thinking of her?" ;)
Sure, I'd upgrade to Jessie
>That might let you have both! Or is there a reason why you don't
>want Jessie?
Nothing, I just went the latest kde iso I could find on the web for
debian in November last which was debian 7.7 kde. after a few
upgrades the debian version shows 7.8 on my system today. A path to
upgrade, preferably a netinstall upgrade would be great. A document to
read BEFORE I invariably hose the system would also help if its
available somewhere on the debian site.
>
> Or you could live with what you have got for now and upgrade to Jessie fairly
> soon after it becomes Stable.
All I'm looking for is the following
KDE framework; I don't want GNOME
Emacs
R
Rstudio(I know it's a separate download)
Python 2.7 and 3.x
Python package system to install additional libraries
Hadoop/Spark bits and bobs
If the upgrade provides for the bare minimum first and then allows to
incrementally add software (like the LIVE CDs that I found), it would
be gold.
>
> Or just live with what you have got.
>
> Anyhow, welcome to Debian. I don't think anyone has said that. ;-)
>
Thank you, the responses to my queries have been more than a welcome
with people going out of their way to diagnose my usual knackering of
the system.
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/878ugao...@gmail.com
[snipped 7 lines]
> Unfortunately, it looks as though you may have to .... but had you thought of
> Jessie?
Sure, I'd upgrade to Jessie
>That might let you have both! Or is there a reason why you don't
>want Jessie?
debian in November last which was debian 7.7 kde. after a few
upgrades the debian version shows 7.8 on my system today. A path to
upgrade, preferably a netinstall upgrade would be great. A document to
read BEFORE I invariably hose the system would also help if its
available somewhere on the debian site.
>
> Or you could live with what you have got for now and upgrade to Jessie fairly
> soon after it becomes Stable.
KDE framework; I don't want GNOME
Emacs
R
Rstudio(I know it's a separate download)
Python 2.7 and 3.x
Python package system to install additional libraries
Hadoop/Spark bits and bobs
If the upgrade provides for the bare minimum first and then allows to
incrementally add software (like the LIVE CDs that I found), it would
be gold.
>
> Or just live with what you have got.
>
> Anyhow, welcome to Debian. I don't think anyone has said that. ;-)
>
with people going out of their way to diagnose my usual knackering of
the system.
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 6, 2015, 1:20:05 PM2/6/15
to
On Fri, Feb 06 2015,Brian wrote:
[snipped 18 lines]
>
> I'd be prepared to report it (if Sivaram Neelakantan doesn't) but is it
> in the emacs package? Also, what severity? If it is seen as breaking
> unrelated software on the system it would be "critical".
poking around and I'd not be of much help in describing the issue in a
manner that would help the bug fixers.
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Renaud OLGIATI
Feb 6, 2015, 1:50:05 PM2/6/15
to
On Fri, 06 Feb 2015 23:31:51 +0530
Sivaram Neelakantan <nsivar...@gmail.com> wrote:
> The missus is asking "who's Jessie and why are you thinking of her?" ;)
>
> Sure, I'd upgrade to Jessie
That will please the missus...
Sivaram Neelakantan <nsivar...@gmail.com> wrote:
> The missus is asking "who's Jessie and why are you thinking of her?" ;)
>
> Sure, I'd upgrade to Jessie
Cheers,
Ron.
--
Against logic there is no armor like ignorance.
-- Laurence J. Peter
-- http://www.olgiati-in-paraguay.org --
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Feb 6, 2015, 2:00:06 PM2/6/15
to
On Fri 06 Feb 2015 at 23:35:18 +0530, Sivaram Neelakantan wrote:
> On Fri, Feb 06 2015,Brian wrote:
>
>
> [snipped 18 lines]
>
> >
> > I'd be prepared to report it (if Sivaram Neelakantan doesn't) but is it
> > in the emacs package? Also, what severity? If it is seen as breaking
> > unrelated software on the system it would be "critical".
>
>
> If it is a bug, please go ahead in reporting it. I've just started
> poking around and I'd not be of much help in describing the issue in a
> manner that would help the bug fixers.
Ok, I'll do it later this evening if no one has grounds to dissuade me.
> On Fri, Feb 06 2015,Brian wrote:
>
>
> [snipped 18 lines]
>
> >
> > I'd be prepared to report it (if Sivaram Neelakantan doesn't) but is it
> > in the emacs package? Also, what severity? If it is seen as breaking
> > unrelated software on the system it would be "critical".
>
>
> If it is a bug, please go ahead in reporting it. I've just started
> poking around and I'd not be of much help in describing the issue in a
> manner that would help the bug fixers.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Feb 6, 2015, 2:20:04 PM2/6/15
to
great a gap between Jessie and Wheezy for me to trust upgrading. This
way you get it all right, from the get-go. It would be like "upgrading"
8.04 Ubuntu to 14.10 in one go. Do a backup and let /home get clobbered
too. That went flawlessly for me. Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54D5129A...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Brian
Feb 6, 2015, 2:50:06 PM2/6/15
to
On Fri 06 Feb 2015 at 14:14:34 -0500, Ric Moore wrote:
> Do a CLEAN install to Jessie, if at all possible. There is just too
> great a gap between Jessie and Wheezy for me to trust upgrading.
> This way you get it all right, from the get-go. It would be like
> "upgrading" 8.04 Ubuntu to 14.10 in one go. Do a backup and let
> /home get clobbered too. That went flawlessly for me. Ric
Upgrading is a foundation stone of Debian. Not being able to do it with
> Do a CLEAN install to Jessie, if at all possible. There is just too
> great a gap between Jessie and Wheezy for me to trust upgrading.
> This way you get it all right, from the get-go. It would be like
> "upgrading" 8.04 Ubuntu to 14.10 in one go. Do a backup and let
> /home get clobbered too. That went flawlessly for me. Ric
confidence would greatly detract from its usefulness. Sorry, but, after
doing an upgrade for nearly 20 years, I would have to disagree with you.
Debian is not Ubuntu (a fine distribution about which I know nothing in
this regard).
I'm not saying there may not be a slight problem or two but that is a
far cry from a "great gap".
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Bob Proulx
Feb 7, 2015, 10:20:04 PM2/7/15
to
Brian wrote:
installing emacs24 and all of the X components I was able to reproduce
it installing only emacs24-nox which is much smaller. I used a chroot.
> libcurl4-openssl-dev requires libp11-kit-dev and the latter depends on
> libp11-kit0 (= 0.12-3).
>
> The installation of emacs24 upgrades libp11-kit0 to 0.20.7-1~bpo70+1, so
> libcurl4-openssl-dev cannot be installed.
# apt-show-versions | grep backports
emacs24-bin-common/wheezy-backports uptodate 24.4+1-4.1~bpo70+1
emacs24-common/wheezy-backports uptodate 24.4+1-4.1~bpo70+1
emacs24-nox/wheezy-backports uptodate 24.4+1-4.1~bpo70+1
libgnutls-deb0-28/wheezy-backports uptodate 3.3.8-4~bpo70+1
libhogweed2/wheezy-backports uptodate 2.7.1-1~bpo70+1
libnettle4/wheezy-backports uptodate 2.7.1-1~bpo70+1
libp11-kit0/wheezy-backports uptodate 0.20.7-1~bpo70+1
libsystemd-login0/wheezy-backports uptodate 204-14~bpo70+1
libtasn1-6/wheezy-backports uptodate 4.2-2~bpo70+1
shared-mime-info/wheezy-backports uptodate 1.3-1~bpo70+1
> This looks like a bug against the emacs24 backport. Opinions?
In for a penny, in for a pound. I think this is just a natural
consequence of using backport software. Sivaram should keep going
with backports.
Since the goal is to get emacs24 installed I would keep going.
Insteall libcurl4-openssl-dev using the backports target. The trace
is long so will include it after my signature.
apt-get -t wheezy-backports install libcurl4-openssl-dev
Bob
# apt-get -t wheezy-backports install libcurl4-openssl-dev
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
binutils ca-certificates comerr-dev cpp cpp-4.7 gcc gcc-4.7 krb5-locales
krb5-multidev libc-dev-bin libc6-dev libcurl3 libgcrypt11-dev libgnutls-dev
libgnutls-openssl27 libgnutlsxx27 libgomp1 libgpg-error-dev libgpg-error0
libgssapi-krb5-2 libgssrpc4 libidn11-dev libitm1 libk5crypto3
libkadm5clnt-mit8 libkadm5srv-mit8 libkdb5-6 libkeyutils1 libkrb5-3
libkrb5-dev libkrb5support0 libldap-2.4-2 libldap2-dev libmpc2 libmpfr4
libp11-kit-dev libquadmath0 librtmp-dev librtmp0 libsasl2-2 libsasl2-modules
libssh2-1 libssh2-1-dev libssl-dev libssl-doc libtasn1-3-dev linux-libc-dev
manpages-dev openssl pkg-config zlib1g-dev
Suggested packages:
binutils-doc doc-base cpp-doc gcc-4.7-locales gcc-multilib make autoconf
automake1.9 libtool flex bison gdb gcc-doc gcc-4.7-multilib
libmudflap0-4.7-dev gcc-4.7-doc libgcc1-dbg libgomp1-dbg libitm1-dbg
libquadmath0-dbg libmudflap0-dbg libcloog-ppl0 libppl-c2 libppl7
binutils-gold krb5-doc glibc-doc libcurl3-dbg libgcrypt11-doc gnutls26-doc
krb5-user libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql
libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal
The following NEW packages will be installed:
binutils ca-certificates comerr-dev cpp cpp-4.7 gcc gcc-4.7 krb5-locales
krb5-multidev libc-dev-bin libc6-dev libcurl3 libcurl4-openssl-dev
libgcrypt11-dev libgnutls-dev libgnutls-openssl27 libgnutlsxx27 libgomp1
libgpg-error-dev libgssapi-krb5-2 libgssrpc4 libidn11-dev libitm1
libk5crypto3 libkadm5clnt-mit8 libkadm5srv-mit8 libkdb5-6 libkeyutils1
libkrb5-3 libkrb5-dev libkrb5support0 libldap-2.4-2 libldap2-dev libmpc2
libmpfr4 libp11-kit-dev libquadmath0 librtmp-dev librtmp0 libsasl2-2
libsasl2-modules libssh2-1 libssh2-1-dev libssl-dev libssl-doc
libtasn1-3-dev linux-libc-dev manpages-dev openssl pkg-config zlib1g-dev
The following packages will be upgraded:
libgpg-error0
1 upgraded, 51 newly installed, 0 to remove and 8 not upgraded.
Inst libgnutls-openssl27 (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Inst libgpg-error0 [1.10-3.1] (1.12-0.2~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libkeyutils1 (1.5.5-3+deb7u1 Debian:7.8/stable [amd64])
Inst libkrb5support0 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libk5crypto3 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libkrb5-3 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libgssapi-krb5-2 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libgssrpc4 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libkadm5clnt-mit8 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libkdb5-6 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libkadm5srv-mit8 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libsasl2-2 (2.1.25.dfsg1-6+deb7u1 Debian:7.8/stable [amd64])
Inst libldap-2.4-2 (2.4.31+really2.4.40-3~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst librtmp0 (2.4+20111222.git4e06e21-1 Debian:7.8/stable [amd64])
Inst libssh2-1 (1.4.2-1.1 Debian:7.8/stable [amd64])
Inst libcurl3 (7.26.0-1+wheezy11 Debian:7.8/stable [amd64])
Inst libgomp1 (4.7.2-5 Debian:7.8/stable [amd64])
Inst libitm1 (4.7.2-5 Debian:7.8/stable [amd64])
Inst libmpfr4 (3.1.0-5 Debian:7.8/stable [amd64])
Inst libquadmath0 (4.7.2-5 Debian:7.8/stable [amd64])
Inst libgnutlsxx27 (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Inst libmpc2 (0.9-4 Debian:7.8/stable [amd64])
Inst krb5-locales (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [all])
Inst binutils (2.22-8 Debian:7.8/stable [amd64])
Inst openssl (1.0.1e-2+deb7u13 Debian:7.8/stable [amd64])
Inst ca-certificates (20130119+deb7u1 Debian:7.8/stable [all])
Inst cpp-4.7 (4.7.2-5 Debian:7.8/stable [amd64])
Inst cpp (4:4.7.2-1 Debian:7.8/stable [amd64])
Inst gcc-4.7 (4.7.2-5 Debian:7.8/stable [amd64])
Inst gcc (4:4.7.2-1 Debian:7.8/stable [amd64])
Inst libc-dev-bin (2.13-38+deb7u6 Debian:7.8/stable [amd64])
Inst linux-libc-dev (3.16.7-ckt2-1~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libc6-dev (2.13-38+deb7u6 Debian:7.8/stable [amd64])
Inst comerr-dev (2.1-1.42.5-1.1 Debian:7.8/stable [amd64])
Inst krb5-multidev (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst pkg-config (0.26-1 Debian:7.8/stable [amd64])
Inst libidn11-dev (1.25-2 Debian:7.8/stable [amd64])
Inst libkrb5-dev (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libldap2-dev (2.4.31+really2.4.40-3~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libgpg-error-dev (1.12-0.2~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libgcrypt11-dev (1.5.0-5+deb7u2 Debian:7.8/stable [amd64])
Inst zlib1g-dev (1:1.2.7.dfsg-13 Debian:7.8/stable [amd64])
Inst libtasn1-3-dev (2.13-2+deb7u1 Debian:7.8/stable [amd64])
Inst libp11-kit-dev (0.20.7-1~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libgnutls-dev (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Inst librtmp-dev (2.4+20111222.git4e06e21-1 Debian:7.8/stable [amd64])
Inst libssh2-1-dev (1.4.2-1.1 Debian:7.8/stable [amd64])
Inst libssl-dev (1.0.1e-2+deb7u13 Debian:7.8/stable [amd64])
Inst libcurl4-openssl-dev (7.26.0-1+wheezy11 Debian:7.8/stable [amd64])
Inst libsasl2-modules (2.1.25.dfsg1-6+deb7u1 Debian:7.8/stable [amd64])
Inst libssl-doc (1.0.1e-2+deb7u13 Debian:7.8/stable [all])
Inst manpages-dev (3.44-1 Debian:7.8/stable [all])
Conf libgnutls-openssl27 (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Conf libgpg-error0 (1.12-0.2~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libkeyutils1 (1.5.5-3+deb7u1 Debian:7.8/stable [amd64])
Conf libkrb5support0 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libk5crypto3 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libkrb5-3 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libgssapi-krb5-2 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libgssrpc4 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libkadm5clnt-mit8 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libkdb5-6 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libkadm5srv-mit8 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libsasl2-2 (2.1.25.dfsg1-6+deb7u1 Debian:7.8/stable [amd64])
Conf libldap-2.4-2 (2.4.31+really2.4.40-3~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf librtmp0 (2.4+20111222.git4e06e21-1 Debian:7.8/stable [amd64])
Conf libssh2-1 (1.4.2-1.1 Debian:7.8/stable [amd64])
Conf libcurl3 (7.26.0-1+wheezy11 Debian:7.8/stable [amd64])
Conf libgomp1 (4.7.2-5 Debian:7.8/stable [amd64])
Conf libitm1 (4.7.2-5 Debian:7.8/stable [amd64])
Conf libmpfr4 (3.1.0-5 Debian:7.8/stable [amd64])
Conf libquadmath0 (4.7.2-5 Debian:7.8/stable [amd64])
Conf libgnutlsxx27 (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Conf libmpc2 (0.9-4 Debian:7.8/stable [amd64])
Conf krb5-locales (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [all])
Conf binutils (2.22-8 Debian:7.8/stable [amd64])
Conf openssl (1.0.1e-2+deb7u13 Debian:7.8/stable [amd64])
Conf ca-certificates (20130119+deb7u1 Debian:7.8/stable [all])
Conf cpp-4.7 (4.7.2-5 Debian:7.8/stable [amd64])
Conf cpp (4:4.7.2-1 Debian:7.8/stable [amd64])
Conf gcc-4.7 (4.7.2-5 Debian:7.8/stable [amd64])
Conf gcc (4:4.7.2-1 Debian:7.8/stable [amd64])
Conf libc-dev-bin (2.13-38+deb7u6 Debian:7.8/stable [amd64])
Conf linux-libc-dev (3.16.7-ckt2-1~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libc6-dev (2.13-38+deb7u6 Debian:7.8/stable [amd64])
Conf comerr-dev (2.1-1.42.5-1.1 Debian:7.8/stable [amd64])
Conf krb5-multidev (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf pkg-config (0.26-1 Debian:7.8/stable [amd64])
Conf libidn11-dev (1.25-2 Debian:7.8/stable [amd64])
Conf libkrb5-dev (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libldap2-dev (2.4.31+really2.4.40-3~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libgpg-error-dev (1.12-0.2~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libgcrypt11-dev (1.5.0-5+deb7u2 Debian:7.8/stable [amd64])
Conf zlib1g-dev (1:1.2.7.dfsg-13 Debian:7.8/stable [amd64])
Conf libtasn1-3-dev (2.13-2+deb7u1 Debian:7.8/stable [amd64])
Conf libp11-kit-dev (0.20.7-1~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libgnutls-dev (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Conf librtmp-dev (2.4+20111222.git4e06e21-1 Debian:7.8/stable [amd64])
Conf libssh2-1-dev (1.4.2-1.1 Debian:7.8/stable [amd64])
Conf libssl-dev (1.0.1e-2+deb7u13 Debian:7.8/stable [amd64])
Conf libcurl4-openssl-dev (7.26.0-1+wheezy11 Debian:7.8/stable [amd64])
Conf libsasl2-modules (2.1.25.dfsg1-6+deb7u1 Debian:7.8/stable [amd64])
Conf libssl-doc (1.0.1e-2+deb7u13 Debian:7.8/stable [all])
Conf manpages-dev (3.44-1 Debian:7.8/stable [all])
> Brian wrote:
> > It is good that you have provided sufficient information in this
> > thread to be able to follow in your footsteps as I am now able to
> > reproduce your problem.
> >
> > It is good that you have provided sufficient information in this
> > thread to be able to follow in your footsteps as I am now able to
> > reproduce your problem.
> >
> > I installed emacs24:
> > apt-get -t wheezy-backports install emacs24
> > Then
> > apt-get install libcurl4-openssl-dev
> > produces exactly the same outcome you describe in your first post.
Good work! I followed you and have this same setup now. Instead of
> > apt-get -t wheezy-backports install emacs24
> > Then
> > apt-get install libcurl4-openssl-dev
> > produces exactly the same outcome you describe in your first post.
installing emacs24 and all of the X components I was able to reproduce
it installing only emacs24-nox which is much smaller. I used a chroot.
> libcurl4-openssl-dev requires libp11-kit-dev and the latter depends on
> libp11-kit0 (= 0.12-3).
>
> The installation of emacs24 upgrades libp11-kit0 to 0.20.7-1~bpo70+1, so
> libcurl4-openssl-dev cannot be installed.
emacs24-bin-common/wheezy-backports uptodate 24.4+1-4.1~bpo70+1
emacs24-common/wheezy-backports uptodate 24.4+1-4.1~bpo70+1
emacs24-nox/wheezy-backports uptodate 24.4+1-4.1~bpo70+1
libgnutls-deb0-28/wheezy-backports uptodate 3.3.8-4~bpo70+1
libhogweed2/wheezy-backports uptodate 2.7.1-1~bpo70+1
libnettle4/wheezy-backports uptodate 2.7.1-1~bpo70+1
libp11-kit0/wheezy-backports uptodate 0.20.7-1~bpo70+1
libsystemd-login0/wheezy-backports uptodate 204-14~bpo70+1
libtasn1-6/wheezy-backports uptodate 4.2-2~bpo70+1
shared-mime-info/wheezy-backports uptodate 1.3-1~bpo70+1
> This looks like a bug against the emacs24 backport. Opinions?
consequence of using backport software. Sivaram should keep going
with backports.
Since the goal is to get emacs24 installed I would keep going.
Insteall libcurl4-openssl-dev using the backports target. The trace
is long so will include it after my signature.
apt-get -t wheezy-backports install libcurl4-openssl-dev
Bob
# apt-get -t wheezy-backports install libcurl4-openssl-dev
Reading package lists...
Building dependency tree...
Reading state information...
The following extra packages will be installed:
binutils ca-certificates comerr-dev cpp cpp-4.7 gcc gcc-4.7 krb5-locales
krb5-multidev libc-dev-bin libc6-dev libcurl3 libgcrypt11-dev libgnutls-dev
libgnutls-openssl27 libgnutlsxx27 libgomp1 libgpg-error-dev libgpg-error0
libgssapi-krb5-2 libgssrpc4 libidn11-dev libitm1 libk5crypto3
libkadm5clnt-mit8 libkadm5srv-mit8 libkdb5-6 libkeyutils1 libkrb5-3
libkrb5-dev libkrb5support0 libldap-2.4-2 libldap2-dev libmpc2 libmpfr4
libp11-kit-dev libquadmath0 librtmp-dev librtmp0 libsasl2-2 libsasl2-modules
libssh2-1 libssh2-1-dev libssl-dev libssl-doc libtasn1-3-dev linux-libc-dev
manpages-dev openssl pkg-config zlib1g-dev
Suggested packages:
binutils-doc doc-base cpp-doc gcc-4.7-locales gcc-multilib make autoconf
automake1.9 libtool flex bison gdb gcc-doc gcc-4.7-multilib
libmudflap0-4.7-dev gcc-4.7-doc libgcc1-dbg libgomp1-dbg libitm1-dbg
libquadmath0-dbg libmudflap0-dbg libcloog-ppl0 libppl-c2 libppl7
binutils-gold krb5-doc glibc-doc libcurl3-dbg libgcrypt11-doc gnutls26-doc
krb5-user libsasl2-modules-otp libsasl2-modules-ldap libsasl2-modules-sql
libsasl2-modules-gssapi-mit libsasl2-modules-gssapi-heimdal
The following NEW packages will be installed:
binutils ca-certificates comerr-dev cpp cpp-4.7 gcc gcc-4.7 krb5-locales
krb5-multidev libc-dev-bin libc6-dev libcurl3 libcurl4-openssl-dev
libgcrypt11-dev libgnutls-dev libgnutls-openssl27 libgnutlsxx27 libgomp1
libgpg-error-dev libgssapi-krb5-2 libgssrpc4 libidn11-dev libitm1
libk5crypto3 libkadm5clnt-mit8 libkadm5srv-mit8 libkdb5-6 libkeyutils1
libkrb5-3 libkrb5-dev libkrb5support0 libldap-2.4-2 libldap2-dev libmpc2
libmpfr4 libp11-kit-dev libquadmath0 librtmp-dev librtmp0 libsasl2-2
libsasl2-modules libssh2-1 libssh2-1-dev libssl-dev libssl-doc
libtasn1-3-dev linux-libc-dev manpages-dev openssl pkg-config zlib1g-dev
The following packages will be upgraded:
libgpg-error0
1 upgraded, 51 newly installed, 0 to remove and 8 not upgraded.
Inst libgnutls-openssl27 (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Inst libgpg-error0 [1.10-3.1] (1.12-0.2~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libkeyutils1 (1.5.5-3+deb7u1 Debian:7.8/stable [amd64])
Inst libkrb5support0 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libk5crypto3 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libkrb5-3 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libgssapi-krb5-2 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libgssrpc4 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libkadm5clnt-mit8 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libkdb5-6 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libkadm5srv-mit8 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libsasl2-2 (2.1.25.dfsg1-6+deb7u1 Debian:7.8/stable [amd64])
Inst libldap-2.4-2 (2.4.31+really2.4.40-3~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst librtmp0 (2.4+20111222.git4e06e21-1 Debian:7.8/stable [amd64])
Inst libssh2-1 (1.4.2-1.1 Debian:7.8/stable [amd64])
Inst libcurl3 (7.26.0-1+wheezy11 Debian:7.8/stable [amd64])
Inst libgomp1 (4.7.2-5 Debian:7.8/stable [amd64])
Inst libitm1 (4.7.2-5 Debian:7.8/stable [amd64])
Inst libmpfr4 (3.1.0-5 Debian:7.8/stable [amd64])
Inst libquadmath0 (4.7.2-5 Debian:7.8/stable [amd64])
Inst libgnutlsxx27 (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Inst libmpc2 (0.9-4 Debian:7.8/stable [amd64])
Inst krb5-locales (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [all])
Inst binutils (2.22-8 Debian:7.8/stable [amd64])
Inst openssl (1.0.1e-2+deb7u13 Debian:7.8/stable [amd64])
Inst ca-certificates (20130119+deb7u1 Debian:7.8/stable [all])
Inst cpp-4.7 (4.7.2-5 Debian:7.8/stable [amd64])
Inst cpp (4:4.7.2-1 Debian:7.8/stable [amd64])
Inst gcc-4.7 (4.7.2-5 Debian:7.8/stable [amd64])
Inst gcc (4:4.7.2-1 Debian:7.8/stable [amd64])
Inst libc-dev-bin (2.13-38+deb7u6 Debian:7.8/stable [amd64])
Inst linux-libc-dev (3.16.7-ckt2-1~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libc6-dev (2.13-38+deb7u6 Debian:7.8/stable [amd64])
Inst comerr-dev (2.1-1.42.5-1.1 Debian:7.8/stable [amd64])
Inst krb5-multidev (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst pkg-config (0.26-1 Debian:7.8/stable [amd64])
Inst libidn11-dev (1.25-2 Debian:7.8/stable [amd64])
Inst libkrb5-dev (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Inst libldap2-dev (2.4.31+really2.4.40-3~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libgpg-error-dev (1.12-0.2~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libgcrypt11-dev (1.5.0-5+deb7u2 Debian:7.8/stable [amd64])
Inst zlib1g-dev (1:1.2.7.dfsg-13 Debian:7.8/stable [amd64])
Inst libtasn1-3-dev (2.13-2+deb7u1 Debian:7.8/stable [amd64])
Inst libp11-kit-dev (0.20.7-1~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Inst libgnutls-dev (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Inst librtmp-dev (2.4+20111222.git4e06e21-1 Debian:7.8/stable [amd64])
Inst libssh2-1-dev (1.4.2-1.1 Debian:7.8/stable [amd64])
Inst libssl-dev (1.0.1e-2+deb7u13 Debian:7.8/stable [amd64])
Inst libcurl4-openssl-dev (7.26.0-1+wheezy11 Debian:7.8/stable [amd64])
Inst libsasl2-modules (2.1.25.dfsg1-6+deb7u1 Debian:7.8/stable [amd64])
Inst libssl-doc (1.0.1e-2+deb7u13 Debian:7.8/stable [all])
Inst manpages-dev (3.44-1 Debian:7.8/stable [all])
Conf libgnutls-openssl27 (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Conf libgpg-error0 (1.12-0.2~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libkeyutils1 (1.5.5-3+deb7u1 Debian:7.8/stable [amd64])
Conf libkrb5support0 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libk5crypto3 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libkrb5-3 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libgssapi-krb5-2 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libgssrpc4 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libkadm5clnt-mit8 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libkdb5-6 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libkadm5srv-mit8 (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libsasl2-2 (2.1.25.dfsg1-6+deb7u1 Debian:7.8/stable [amd64])
Conf libldap-2.4-2 (2.4.31+really2.4.40-3~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf librtmp0 (2.4+20111222.git4e06e21-1 Debian:7.8/stable [amd64])
Conf libssh2-1 (1.4.2-1.1 Debian:7.8/stable [amd64])
Conf libcurl3 (7.26.0-1+wheezy11 Debian:7.8/stable [amd64])
Conf libgomp1 (4.7.2-5 Debian:7.8/stable [amd64])
Conf libitm1 (4.7.2-5 Debian:7.8/stable [amd64])
Conf libmpfr4 (3.1.0-5 Debian:7.8/stable [amd64])
Conf libquadmath0 (4.7.2-5 Debian:7.8/stable [amd64])
Conf libgnutlsxx27 (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Conf libmpc2 (0.9-4 Debian:7.8/stable [amd64])
Conf krb5-locales (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [all])
Conf binutils (2.22-8 Debian:7.8/stable [amd64])
Conf openssl (1.0.1e-2+deb7u13 Debian:7.8/stable [amd64])
Conf ca-certificates (20130119+deb7u1 Debian:7.8/stable [all])
Conf cpp-4.7 (4.7.2-5 Debian:7.8/stable [amd64])
Conf cpp (4:4.7.2-1 Debian:7.8/stable [amd64])
Conf gcc-4.7 (4.7.2-5 Debian:7.8/stable [amd64])
Conf gcc (4:4.7.2-1 Debian:7.8/stable [amd64])
Conf libc-dev-bin (2.13-38+deb7u6 Debian:7.8/stable [amd64])
Conf linux-libc-dev (3.16.7-ckt2-1~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libc6-dev (2.13-38+deb7u6 Debian:7.8/stable [amd64])
Conf comerr-dev (2.1-1.42.5-1.1 Debian:7.8/stable [amd64])
Conf krb5-multidev (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf pkg-config (0.26-1 Debian:7.8/stable [amd64])
Conf libidn11-dev (1.25-2 Debian:7.8/stable [amd64])
Conf libkrb5-dev (1.10.1+dfsg-5+deb7u2 Debian:7.8/stable [amd64])
Conf libldap2-dev (2.4.31+really2.4.40-3~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libgpg-error-dev (1.12-0.2~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libgcrypt11-dev (1.5.0-5+deb7u2 Debian:7.8/stable [amd64])
Conf zlib1g-dev (1:1.2.7.dfsg-13 Debian:7.8/stable [amd64])
Conf libtasn1-3-dev (2.13-2+deb7u1 Debian:7.8/stable [amd64])
Conf libp11-kit-dev (0.20.7-1~bpo70+1 Debian Backports:/wheezy-backports [amd64])
Conf libgnutls-dev (2.12.20-8+deb7u2 Debian:7.8/stable [amd64])
Conf librtmp-dev (2.4+20111222.git4e06e21-1 Debian:7.8/stable [amd64])
Conf libssh2-1-dev (1.4.2-1.1 Debian:7.8/stable [amd64])
Conf libssl-dev (1.0.1e-2+deb7u13 Debian:7.8/stable [amd64])
Conf libcurl4-openssl-dev (7.26.0-1+wheezy11 Debian:7.8/stable [amd64])
Conf libsasl2-modules (2.1.25.dfsg1-6+deb7u1 Debian:7.8/stable [amd64])
Conf libssl-doc (1.0.1e-2+deb7u13 Debian:7.8/stable [all])
Conf manpages-dev (3.44-1 Debian:7.8/stable [all])
Bob Proulx
Feb 7, 2015, 10:30:04 PM2/7/15
to
Brian wrote:
> Ric Moore wrote:
> > Do a CLEAN install to Jessie, if at all possible. There is just too
> > great a gap between Jessie and Wheezy for me to trust upgrading.
> > This way you get it all right, from the get-go. It would be like
> > "upgrading" 8.04 Ubuntu to 14.10 in one go. Do a backup and let
> > /home get clobbered too. That went flawlessly for me. Ric
>
> Upgrading is a foundation stone of Debian. Not being able to do it with
> confidence would greatly detract from its usefulness. Sorry, but, after
> doing an upgrade for nearly 20 years, I would have to disagree with you.
I also strongly disagree. Being able to upgrade is one of the best
> Ric Moore wrote:
> > Do a CLEAN install to Jessie, if at all possible. There is just too
> > great a gap between Jessie and Wheezy for me to trust upgrading.
> > This way you get it all right, from the get-go. It would be like
> > "upgrading" 8.04 Ubuntu to 14.10 in one go. Do a backup and let
> > /home get clobbered too. That went flawlessly for me. Ric
>
> Upgrading is a foundation stone of Debian. Not being able to do it with
> confidence would greatly detract from its usefulness. Sorry, but, after
> doing an upgrade for nearly 20 years, I would have to disagree with you.
features of Debian. Since the original poster just recently installed
it is already a very fresh installation. No need to start again. If
the goal is to go to Jessie at this time the typical way would be to
use the Stable installer and then upgrade to Testing. That is a very
well tested path.
> Debian is not Ubuntu (a fine distribution about which I know nothing in
> this regard).
>
> I'm not saying there may not be a slight problem or two but that is a
> far cry from a "great gap".
all of the major releases between. That would be equivalent to
upgrading from Etch 4 to Jessie 8 without upgrading to the major
releases Lenny 5, Squeeze 6, Wheezy 7 in between. Skipping releases
would be a gap. But Wheezy 7 to Jessie 8 is the normal expected
upgrade path.
Bob
Sivaram Neelakantan
Feb 7, 2015, 11:50:03 PM2/7/15
to
On Sat, Feb 07 2015,Bob Proulx wrote:
[snipped 36 lines]
> In for a penny, in for a pound. I think this is just a natural
> consequence of using backport software. Sivaram should keep going
> with backports.
>
> Since the goal is to get emacs24 installed I would keep going.
> Insteall libcurl4-openssl-dev using the backports target. The trace
> is long so will include it after my signature.
>
> apt-get -t wheezy-backports install libcurl4-openssl-dev
>
Emacs24.4 is working for me. What fails to install was the swirl
package in R which needed Lcurl or libcurl which needed the ssl
libs. From yours and Brian's research it seems that the backports
install of Emacs messes with R package installation.
Looks like I'll pass the backports install of libcurl4 if it almost
installs all the base packages, sort of. Besides, I'll move to Jessie
when it's declared stable or the moment I see the kde iso available on
the web.
[snipped 141 lines]
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/87twyxv...@gmail.com
[snipped 36 lines]
> In for a penny, in for a pound. I think this is just a natural
> consequence of using backport software. Sivaram should keep going
> with backports.
>
> Since the goal is to get emacs24 installed I would keep going.
> Insteall libcurl4-openssl-dev using the backports target. The trace
> is long so will include it after my signature.
>
> apt-get -t wheezy-backports install libcurl4-openssl-dev
>
package in R which needed Lcurl or libcurl which needed the ssl
libs. From yours and Brian's research it seems that the backports
install of Emacs messes with R package installation.
Looks like I'll pass the backports install of libcurl4 if it almost
installs all the base packages, sort of. Besides, I'll move to Jessie
when it's declared stable or the moment I see the kde iso available on
the web.
[snipped 141 lines]
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Bob Proulx
Feb 8, 2015, 1:10:04 AM2/8/15
to
Sivaram Neelakantan wrote:
> Emacs24.4 is working for me. What fails to install was the swirl
> package in R which needed Lcurl or libcurl which needed the ssl
> libs. From yours and Brian's research it seems that the backports
> install of Emacs messes with R package installation.
You say "messes with" but I say installs later versions of backported
> Emacs24.4 is working for me. What fails to install was the swirl
> package in R which needed Lcurl or libcurl which needed the ssl
> libs. From yours and Brian's research it seems that the backports
> install of Emacs messes with R package installation.
packages. Which is exactly what you want but was confusing when it
wasn't known what was happening.
> Looks like I'll pass the backports install of libcurl4 if it almost
> installs all the base packages, sort of. Besides, I'll move to Jessie
> when it's declared stable or the moment I see the kde iso available on
> the web.
in for emacs the answer is easy. Simply install it using backports to
backfill the dependencies.
apt-get -t wheezy-backports install r-base
Where r-base is whatever you would normally install. I am not an R
person so don't know the packages that are needed. That will work
fine.
https://wiki.debian.org/R
Bob
Brian
Feb 8, 2015, 6:30:04 AM2/8/15
to
On Sat 07 Feb 2015 at 23:05:00 -0700, Bob Proulx wrote:
> Sivaram Neelakantan wrote:
> > Emacs24.4 is working for me. What fails to install was the swirl
> > package in R which needed Lcurl or libcurl which needed the ssl
> > libs. From yours and Brian's research it seems that the backports
> > install of Emacs messes with R package installation.
>
> You say "messes with" but I say installs later versions of backported
> packages. Which is exactly what you want but was confusing when it
> wasn't known what was happening.
I think my lack of familiarity with backports has muddied the waters. I
> Sivaram Neelakantan wrote:
> > Emacs24.4 is working for me. What fails to install was the swirl
> > package in R which needed Lcurl or libcurl which needed the ssl
> > libs. From yours and Brian's research it seems that the backports
> > install of Emacs messes with R package installation.
>
> You say "messes with" but I say installs later versions of backported
> packages. Which is exactly what you want but was confusing when it
> wasn't known what was happening.
didn't try
apt-get -t wheezy-backports install libcurl4-openssl-dev
site. Not finding it there lead me to believe there was bug. There isn't.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 8, 2015, 8:20:06 AM2/8/15
to
On Sat, Feb 07 2015,Bob Proulx wrote:
[snipped 15 lines]
> Why? Now that we understand that it was dependencies that were pulled
> in for emacs the answer is easy. Simply install it using backports to
> backfill the dependencies.
>
> apt-get -t wheezy-backports install r-base
>
as far as I can remember.
Installed Debian
Installed Emacs24.4 from backports
Installed R from debian CRAN vide instructions from CRAN site
Installed Rstudio.deb community edition from Rstudio site
While installing packages via Rstudio, lCurl fails due to the error I
documented in prior posts
You and Brian now recommend libcurl4-* from backports which will
download a boatload of other stuff just to get this swirl/Lcurl
package working.
1. Do I have to uninstall & reinstall the cran packages, Rstudio before
proceeding? And this needs to be done from backports?
2. Will this impact Rstudio installation if the R install is from
backports?
3. And if I do get the above working, how will my planned upgrade to
Jessie affect the installed packages from backports.
I think I'm confused whether I should remember that some bits of
software are from backports and it's incumbent on me to track all this
while upgrading to Jessie or installing anything else from stable. I
really don't want to do that and if Debian takes care of the magic in
the background, that'd be wonderful.
[snipped 11 lines]
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Ric Moore
Feb 8, 2015, 8:40:04 PM2/8/15
to
On 02/04/2015 04:03 AM, Sivaram Neelakantan wrote:
> On Wed, Feb 04 2015,Ric Moore wrote:
>
>> On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
>>>
>>> How does one go about fixing broken packages? I've recently started
>>> using debian and apart some fiddling to get the latest emacs24.4 on
>>> wheezy I have not done anything on the system. When I tried to
>>> install libcurl4, I get the following error.
>>
>> As root user, apt-get install synaptic
>> Let it install your programs for you. It's a great GUI package tool,
>> that most use. It's point n click and installs all dependences for
>> you. Ric
>
> err...right. But will synaptic fix the above issue at all that I have
> currently? And does it matter that I'm using KDE version of debian
> (debian-kde iso live cd version)
YOU broke things when you installed an experimental package to wheezy
and then proceeded to erase experimental from your sources list. If you
must have that version of <cough cough> emacs then install Jessie
cleanly, as in a fresh install. You can't easily put a size 12 foot into
a size 10 shoe and not expect pain. Nor, do we expect the unpaid
developers to spend their time to maintain a complete list of depends
for the one user who would install an experimental version of something
to wheezy.
Here is what you had to have read:
"Quoting the Debian FAQ: "project/experimental/: This directory contains
packages and tools which are still being developed, and are still in the
alpha testing stage. Users shouldn't be using packages from here,
because they can be dangerous and harmful even for the most experienced
people."
You have been warned
Unlike the Debian Releases unstable and testing, experimental isn't a
complete distribution. Even if there are a lot less consistency
requirements for packages in experimental, they are autobuilt on the
best effort basis by official Debian Package Auto-Building infrastructure. "
It's not even built by humans. :/ Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
> On Wed, Feb 04 2015,Ric Moore wrote:
>
>> On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
>>>
>>> How does one go about fixing broken packages? I've recently started
>>> using debian and apart some fiddling to get the latest emacs24.4 on
>>> wheezy I have not done anything on the system. When I tried to
>>> install libcurl4, I get the following error.
>>
>> As root user, apt-get install synaptic
>> Let it install your programs for you. It's a great GUI package tool,
>> that most use. It's point n click and installs all dependences for
>> you. Ric
>
> err...right. But will synaptic fix the above issue at all that I have
> currently? And does it matter that I'm using KDE version of debian
> (debian-kde iso live cd version)
YOU broke things when you installed an experimental package to wheezy
and then proceeded to erase experimental from your sources list. If you
must have that version of <cough cough> emacs then install Jessie
cleanly, as in a fresh install. You can't easily put a size 12 foot into
a size 10 shoe and not expect pain. Nor, do we expect the unpaid
developers to spend their time to maintain a complete list of depends
for the one user who would install an experimental version of something
to wheezy.
Here is what you had to have read:
"Quoting the Debian FAQ: "project/experimental/: This directory contains
packages and tools which are still being developed, and are still in the
alpha testing stage. Users shouldn't be using packages from here,
because they can be dangerous and harmful even for the most experienced
people."
You have been warned
Unlike the Debian Releases unstable and testing, experimental isn't a
complete distribution. Even if there are a lot less consistency
requirements for packages in experimental, they are autobuilt on the
best effort basis by official Debian Package Auto-Building infrastructure. "
It's not even built by humans. :/ Ric
--
My father, Victor Moore (Vic) used to say:
"There are two Great Sins in the world...
..the Sin of Ignorance, and the Sin of Stupidity.
Only the former may be overcome." R.I.P. Dad.
http://linuxcounter.net/user/44256.html
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: https://lists.debian.org/54D80E2E...@gmail.com
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Lisi Reisz
Feb 8, 2015, 8:50:04 PM2/8/15
to
On Monday 09 February 2015 01:32:30 Ric Moore wrote:
> On 02/04/2015 04:03 AM, Sivaram Neelakantan wrote:
> > On Wed, Feb 04 2015,Ric Moore wrote:
> >> On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
> >>> How does one go about fixing broken packages? I've recently started
> >>> using debian and apart some fiddling to get the latest emacs24.4 on
> >>> wheezy I have not done anything on the system. When I tried to
> >>> install libcurl4, I get the following error.
> >>
> >> As root user, apt-get install synaptic
> >> Let it install your programs for you. It's a great GUI package tool,
> >> that most use. It's point n click and installs all dependences for
> >> you. Ric
> >
> > err...right. But will synaptic fix the above issue at all that I have
> > currently? And does it matter that I'm using KDE version of debian
> > (debian-kde iso live cd version)
>
> YOU broke things when you installed an experimental package to wheezy
He didn't, Ric!!! He used wheezy-backports. Many of us routinely use
> On 02/04/2015 04:03 AM, Sivaram Neelakantan wrote:
> > On Wed, Feb 04 2015,Ric Moore wrote:
> >> On 02/04/2015 02:13 AM, Sivaram Neelakantan wrote:
> >>> How does one go about fixing broken packages? I've recently started
> >>> using debian and apart some fiddling to get the latest emacs24.4 on
> >>> wheezy I have not done anything on the system. When I tried to
> >>> install libcurl4, I get the following error.
> >>
> >> As root user, apt-get install synaptic
> >> Let it install your programs for you. It's a great GUI package tool,
> >> that most use. It's point n click and installs all dependences for
> >> you. Ric
> >
> > err...right. But will synaptic fix the above issue at all that I have
> > currently? And does it matter that I'm using KDE version of debian
> > (debian-kde iso live cd version)
>
> YOU broke things when you installed an experimental package to wheezy
wheezy-backports and regard it as a perfectly reasonable thing to do. One
does not necessarily expect any pain from backports, which are a completely
different kettle of fish from Experimental.
Backports aren't supported as well as Stable itself, but they are quite well
supported and I personally have never had a problem with them.
> and then proceeded to erase experimental from your sources list.
sources.list. I really don't think he did, Ric. You must be muddling him
with someone else. He doesn't need warning off it because he isn't doing it
in the first place.
Lisi
Brian
Feb 9, 2015, 9:00:05 AM2/9/15
to
On Sun 08 Feb 2015 at 18:45:16 +0530, Sivaram Neelakantan wrote:
> Installed Debian
> Installed Emacs24.4 from backports
> Installed R from debian CRAN vide instructions from CRAN site
> Installed Rstudio.deb community edition from Rstudio site
> While installing packages via Rstudio, lCurl fails due to the error I
> documented in prior posts
>
> You and Brian now recommend libcurl4-* from backports which will
> download a boatload of other stuff just to get this swirl/Lcurl
> package working.
>
> 1. Do I have to uninstall & reinstall the cran packages, Rstudio before
> proceeding? And this needs to be done from backports?
No uninstallation is necessary when you get libcurl4-openssl-dev from
> Installed Debian
> Installed Emacs24.4 from backports
> Installed R from debian CRAN vide instructions from CRAN site
> Installed Rstudio.deb community edition from Rstudio site
> While installing packages via Rstudio, lCurl fails due to the error I
> documented in prior posts
>
> You and Brian now recommend libcurl4-* from backports which will
> download a boatload of other stuff just to get this swirl/Lcurl
> package working.
>
> 1. Do I have to uninstall & reinstall the cran packages, Rstudio before
> proceeding? And this needs to be done from backports?
backports.
> 2. Will this impact Rstudio installation if the R install is from
> backports?
is said about backports on the rstudio site. I believe the answer is
"no".
> 3. And if I do get the above working, how will my planned upgrade to
> Jessie affect the installed packages from backports.
upgraded. The rstudio site mentions a new Jessie cran archive.
> I think I'm confused whether I should remember that some bits of
> software are from backports and it's incumbent on me to track all this
> while upgrading to Jessie or installing anything else from stable. I
> really don't want to do that and if Debian takes care of the magic in
> the background, that'd be wonderful.
upgrade and finally dist-upgrade with apt-get. This is all the magic you
require. :)
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Lisi Reisz
Feb 9, 2015, 10:20:06 AM2/9/15
to
On Sunday 08 February 2015 13:15:16 Sivaram Neelakantan wrote:
> I think I'm confused whether I should remember that some bits of
> software are from backports and it's incumbent on me to track all this
> while upgrading to Jessie or installing anything else from stable. I
> really don't want to do that
That's why we love Debian, apt and its children I use aptitude from choice.
> I think I'm confused whether I should remember that some bits of
> software are from backports and it's incumbent on me to track all this
> while upgrading to Jessie or installing anything else from stable. I
> really don't want to do that
I am lazy! I don't mind someone else doing the work!
> and if Debian takes care of the magic in
> the background, that'd be wonderful.
Especially with a fresh installation.
Any problems that arise are usually due to our falling into traps and
installing non-Debian versions and stuff. I don't have much that isn't
Debian. I just uninstall e.g. Google-Chrome, upgrade, reinstall
Google-Chrome. Of course, if I were a true believer I would still be using
chromium anyway and would not have to uninstall anything.
Lisi
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Sivaram Neelakantan
Feb 9, 2015, 11:30:05 AM2/9/15
to
On Mon, Feb 09 2015,Brian wrote:
> On Sun 08 Feb 2015 at 18:45:16 +0530, Sivaram Neelakantan wrote:
>
[snipped 11 lines]
> On Sun 08 Feb 2015 at 18:45:16 +0530, Sivaram Neelakantan wrote:
>
>> 1. Do I have to uninstall & reinstall the cran packages, Rstudio before
>> proceeding? And this needs to be done from backports?
>
> No uninstallation is necessary when you get libcurl4-openssl-dev from
> backports.
>
>> 2. Will this impact Rstudio installation if the R install is from
>> backports?
>
> You may have more confidence in the outcome if you read and noted what
> is said about backports on the rstudio site. I believe the answer is
> "no".
[snipped 7 lines]
>> I think I'm confused whether I should remember that some bits of
>> software are from backports and it's incumbent on me to track all this
>> while upgrading to Jessie or installing anything else from stable. I
>> really don't want to do that and if Debian takes care of the magic in
>> the background, that'd be wonderful.
>
> Change "wheezy" to "jessie" in sources.list for all archives. Update,
> upgrade and finally dist-upgrade with apt-get. This is all the magic you
> require. :)
sivaram
--
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Bob Proulx
Feb 9, 2015, 3:20:04 PM2/9/15
to
Sivaram Neelakantan wrote:
> OK, here's the thing that's nagging me a bit. This is what happened
> as far as I can remember.
>
> Installed Debian
> Installed Emacs24.4 from backports
> Installed R from debian CRAN vide instructions from CRAN site
> Installed Rstudio.deb community edition from Rstudio site
> While installing packages via Rstudio, lCurl fails due to the error I
> documented in prior posts
Sounds like a plausible series of events. That description in the
> OK, here's the thing that's nagging me a bit. This is what happened
> as far as I can remember.
>
> Installed Debian
> Installed Emacs24.4 from backports
> Installed R from debian CRAN vide instructions from CRAN site
> Installed Rstudio.deb community edition from Rstudio site
> While installing packages via Rstudio, lCurl fails due to the error I
> documented in prior posts
beginning would have explained everything right at the start.
Basically you are mixing a bunch of packages that are from various
sources. Each source is focused on their part of the universe. They
aren't cross testing against each other's repositories. It is that
mixing and matching that often trips over problems because none of
them test against every other repository. Each will think their end
is completely consistent. But in combination they probably phase in
and out of consistency. That is simply the nature of mixing sources.
> You and Brian now recommend libcurl4-* from backports which will
> download a boatload of other stuff just to get this swirl/Lcurl
> package working.
dependencies. Normally apt is barred from pulling packges from
backports due to the backports configuration. Using backports as a
target overrides that so that it can install from it.
> 1. Do I have to uninstall & reinstall the cran packages, Rstudio before
> proceeding? And this needs to be done from backports?
repository. But if it were me I would push forward with using the mix
since you have already done so until you find a reason not to.
> 2. Will this impact Rstudio installation if the R install is from
> backports?
> 3. And if I do get the above working, how will my planned upgrade to
> Jessie affect the installed packages from backports.
reasons everyone likes backports. All of the backports packages are
backports from Jessie. Therefore when you decide to upgrade to Jessie
they will upgrade seamlessly.
That is not a guarentee of other 3rd party repositories. However I am
sure they will try to do the right thing. Until there is an example
of an incompatibility I must give them the benefit of the doubt.
> I think I'm confused whether I should remember that some bits of
> software are from backports and it's incumbent on me to track all this
> while upgrading to Jessie or installing anything else from stable. I
> really don't want to do that and if Debian takes care of the magic in
> the background, that'd be wonderful.
care of for you. Use backports with Stable (currently Wheezy 7) and
then upgrading when Testing becomes the new Stable will all work fine.
Don't know anything about other 3rd party repositories such as the R
repositories. Any problems using them should be reported to them.
Bob
0 new messages