Re: Problem using "dpkg -i"

[Brian]

On Sun 28 Jan 2018 at 14:18:02 -0600, Richard Owlett wrote:

> On 01/28/2018 11:13 AM, Curt wrote:
> > On 2018-01-28, Richard Owlett  wrote:
> > > > > 
> > > > > There is bluefish, but it only supports previews via an external 
> > > > > browser
> > > > > (according to the package description, I have not used it myself).
> > > > > 
> > > > 
> > > > Not for this project. But the manual hints it would useful for other
> > > > things. Much reading ahead.
> > > 
> > > 
> > > I just installed version 2.2.9 from Debian repository for an new project.
> > > I just went to the bluefish web site. The manual is difficult to use as
> > > I frequently have minimal access. Is it available somewhere as a single
> > > HTML file?
> > > TIA
> > 
> > Seems you can download the manual source files from sourceforge.net and
> > build an HTML/Postscript/PDF version yourself (although the rigmarole
> > involved may be more than you're willing to endure).
> > 
> > http://bluefish.openoffice.nl/manual/apcs03.html
> > (and the following page too)
> > 
> 
> That link led me to http://bluefish.openoffice.nl/manual/bk01-toc.html which
> I downloaded with WebHTTrack Website Copier.
> 
> That is a *MUCH* more useful format than
>   
> to which
>   
> points.
> 
> Problem solved :}
> Thank you.

WebHTTrack or wget, it doesn't matter. Both get you what you want.

-- 
Brian.

Re: Problem using "dpkg -i"

[Richard Owlett]

On 01/28/2018 11:13 AM, Curt wrote:

On 2018-01-28, Richard Owlett  wrote:


There is bluefish, but it only supports previews via an external browser
(according to the package description, I have not used it myself).



Not for this project. But the manual hints it would useful for other
things. Much reading ahead.



I just installed version 2.2.9 from Debian repository for an new project.
I just went to the bluefish web site. The manual is difficult to use as
I frequently have minimal access. Is it available somewhere as a single
HTML file?
TIA


Seems you can download the manual source files from sourceforge.net and
build an HTML/Postscript/PDF version yourself (although the rigmarole
involved may be more than you're willing to endure).

http://bluefish.openoffice.nl/manual/apcs03.html
(and the following page too)



That link led me to http://bluefish.openoffice.nl/manual/bk01-toc.html 
which I downloaded with WebHTTrack Website Copier.


That is a *MUCH* more useful format than
  
to which
  
points.

Problem solved :}
Thank you.

Re: Problem using "dpkg -i"

[Brian]

On Sun 28 Jan 2018 at 17:13:54 +, Curt wrote:

> On 2018-01-28, Richard Owlett  wrote:
> >>>
> >>> There is bluefish, but it only supports previews via an external browser
> >>> (according to the package description, I have not used it myself).
> >>>
> >> 
> >> Not for this project. But the manual hints it would useful for other 
> >> things. Much reading ahead.
> >
> >
> > I just installed version 2.2.9 from Debian repository for an new project.
> > I just went to the bluefish web site. The manual is difficult to use as 
> > I frequently have minimal access. Is it available somewhere as a single 
> > HTML file?
> > TIA
> 
> Seems you can download the manual source files from sourceforge.net and
> build an HTML/Postscript/PDF version yourself (although the rigmarole
> involved may be more than you're willing to endure).
> 
> http://bluefish.openoffice.nl/manual/apcs03.html
> (and the following page too)

Looks like an interesting link and an opportunity to learn about CVS and
DocBook. Using wget could be more convenient.

-- 
Brian.

Re: Problem using "dpkg -i"

[Curt]

On 2018-01-28, Richard Owlett  wrote:
>>>
>>> There is bluefish, but it only supports previews via an external browser
>>> (according to the package description, I have not used it myself).
>>>
>> 
>> Not for this project. But the manual hints it would useful for other 
>> things. Much reading ahead.
>
>
> I just installed version 2.2.9 from Debian repository for an new project.
> I just went to the bluefish web site. The manual is difficult to use as 
> I frequently have minimal access. Is it available somewhere as a single 
> HTML file?
> TIA

Seems you can download the manual source files from sourceforge.net and
build an HTML/Postscript/PDF version yourself (although the rigmarole
involved may be more than you're willing to endure).

http://bluefish.openoffice.nl/manual/apcs03.html
(and the following page too)

-- 
“True terror is to wake up one morning and discover that your high school class
is running the country.” – Kurt Vonnegut

Re: Problem using "dpkg -i"

[Richard Owlett]

On 01/15/2018 01:23 PM, Richard Owlett wrote:

On 01/15/2018 11:38 AM, Sven Joachim wrote:

On 2018-01-15 01:32 -0600, Richard Owlett wrote:

[snip]
2. Is there a recommended HTML editor in the repository that"
    A. simple UI
    B. can render the code so I can tell if my changes display
   as intended?


There is bluefish, but it only supports previews via an external browser
(according to the package description, I have not used it myself).



Not for this project. But the manual hints it would useful for other 
things. Much reading ahead.



I just installed version 2.2.9 from Debian repository for an new project.
I just went to the bluefish web site. The manual is difficult to use as 
I frequently have minimal access. Is it available somewhere as a single 
HTML file?

TIA

Re: Problem using "dpkg -i"

[Richard Owlett]

On 01/22/2018 09:57 AM, Karol Augustin wrote:

On 2018-01-15 9:17, Richard Owlett wrote:

On 01/15/2018 02:25 AM, Bernd Gruber wrote:

Richard Owlett wrote:


Received error message:
dpkg: dependency problems prevent configuration of amaya:
amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
 Package libssl0.9.8 is not installed.


I know you have mentioned that the problem is fixed now but I feel that
it's worth mentioning a few things here:

libssl1.1 and libssl0.9.8 are completely different packages and you can
install them both at the same time. As it seems to be the only
dependency that is missing I would just download missing package that
seems to be available from Ubuntu repos:

https://pkgs.org/download/libssl0.9.8

And run apt-get install -f

It should fix your problem. The only downside (besides from using
abandonware) is that libssl0.9.8 might depend on something else and if
you decide to follow this route you might end up in a situation when
package you want to install is breaking/downgrading package from the
distribution you are using.

But as far as I remember obsolete libssl should be OK to just install
and use (and it won't have any impact on the other software).



I have Debian installed on one partition whose sole purpose is 
experimenting. I may be able to try it this weekend.

Thank you.

Re: Problem using "dpkg -i"

[Karol Augustin]

On 2018-01-15 9:17, Richard Owlett wrote:
> On 01/15/2018 02:25 AM, Bernd Gruber wrote:
>> Richard Owlett wrote:
>>>
>>> Received error message:
>>> dpkg: dependency problems prevent configuration of amaya:
>>>amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
>>> Package libssl0.9.8 is not installed.

I know you have mentioned that the problem is fixed now but I feel that
it's worth mentioning a few things here:

libssl1.1 and libssl0.9.8 are completely different packages and you can
install them both at the same time. As it seems to be the only
dependency that is missing I would just download missing package that
seems to be available from Ubuntu repos:

https://pkgs.org/download/libssl0.9.8

And run apt-get install -f

It should fix your problem. The only downside (besides from using
abandonware) is that libssl0.9.8 might depend on something else and if
you decide to follow this route you might end up in a situation when
package you want to install is breaking/downgrading package from the
distribution you are using.

But as far as I remember obsolete libssl should be OK to just install
and use (and it won't have any impact on the other software).

Karol



>>
>> try apt-get -f install
>>
>> Bernd
> 
> I had already tried "fix broken" option in Synaptic.
> All it did was remove all pieces of Amaya.
> 
> I repeated
> dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb
> followed by
> apt-get -f install
> with the same result ;<
> 
> Thanks.

-- 
Karol Augustin
ka...@augustin.pl
http://karolaugustin.pl/
+353 85 775 5312

Re: Problem using "dpkg -i"

[SDA]

On Mon, Jan 15, 2018 at 01:23:30PM -0600, Richard Owlett wrote:
> On 01/15/2018 11:38 AM, Sven Joachim wrote:
> > On 2018-01-15 01:32 -0600, Richard Owlett wrote:
> > > [snip]
> > > 2. Is there a recommended HTML editor in the repository that"
> > > A. simple UI
> > > B. can render the code so I can tell if my changes display
> > >as intended?
> > 
> > There is bluefish, but it only supports previews via an external browser
> > (according to the package description, I have not used it myself).
> > 
> 
> Not for this project. But the manual hints it would useful for other things.
> Much reading ahead.
> 
> Thanks
 
Bluefish isn't WYSIWYG, whereas Blue Griffon is - It's a pretty fair WebPage 
Editor. If you're not comfortable with markup, best use BlueGriffon. I've 
been happy with the latest version.
 

Re: Problem using "dpkg -i"

[Michael Lange]

On Wed, 17 Jan 2018 06:50:09 -0600
Richard Owlett  wrote:

(...)
> *HOWEVER* your post leads to solving a more important problem.
> It has been suggested several times "to build from source". I couldn't
> find instructions suitable to my lack of background. The closest I've 
> come was working in 8080 assembler ~40 years ago ;} Your reference and 
> the educational material at https://www.mercurial-scm.org/ should 
> resolve that problem.

The most common way to build applications from source on linux systems
uses a "configure" script; the way to build such an app is usually quite
straightforward. 
First thing I usually do is to cd into the source directory and call

$ .configure --help

which will print out a number of available options how the build can be
configured. Next thing is to actually run the configure script with

$ .configure 
followed by 
$ make
and
$ make install
That's it (if all went well)!

One problem that may cause confusion in that procedure is when .configure
stops with an error message saying something like "libfoo not found"
although libfoo is installed. In such a case the solution is to install
the missing header files, usually in a package as "libfoo-dev". 
By default programs compiled like this will install into /usr/local; if
it is desired to neatly separate that app from the system this
can be overridden with configure's --prefix option, as in
$ .configure --prefix=/opt/appname

Some apps of course (as apparently that blue griffon) use a different
approach, so reading the build instructions first is certainly always a
good idea :-)

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Change is the essential process of all existence.
-- Spock, "Let That Be Your Last Battlefield", stardate
5730.2

Re: Problem using "dpkg -i"

[Richard Owlett]

On 01/16/2018 03:51 PM, Michael Lange wrote:

On Tue, 16 Jan 2018 15:29:57 -0600
Richard Owlett  wrote:


On 01/16/2018 04:17 AM, Michael Lange wrote:

[snip]

To the OP:
a quick web search showed another alternative that (iirc) has not been
mentioned before, see http://bluegriffon.org/ . I don't know anything
about this program, except that it appears to be commercial but open
source and they have a deb package available (which may or may not
work with debian) and it apparently can be used for free with a
somewhat reduced feature set.



That looks interesting. The only problem is I'm still using i386 flavor.


Maybe you could try to build from source? The instructions at
https://github.com/therealglazou/bluegriffon
at a quick glance look quite detailed, and I assume you are not
interested in the expensive extra-features from the binary packages
anyway?


Thank you.
The original problem which originally prompted me to investigate
"dpkg -i" has been resolved.

*HOWEVER* your post leads to solving a more important problem.
It has been suggested several times "to build from source". I couldn't
find instructions suitable to my lack of background. The closest I've 
come was working in 8080 assembler ~40 years ago ;} Your reference and 
the educational material at https://www.mercurial-scm.org/ should 
resolve that problem.




Or, the (maybe) easier way, try to pick one of the older releases from
http://bluegriffon.org/freshmeat/ and see if one of these can be installed
and run on your system (2.3.1 appears to be the latest that comes with a
386 deb).

Regards

Michael

Re: Problem using "dpkg -i"

[Curt]

On 2018-01-16, Michael Lange  wrote:
> On Tue, 16 Jan 2018 18:52:51 +0100
> deloptes  wrote:
>
>> Curt wrote:
>> > 
>> > I thought it was merely not recommended for upgrades.
>> > 
>> 
>> might be we check to see what is official statement on that
>
> Maybe Curt refers to the following from
> https://www.debian.org/releases/stretch/amd64/release-notes/ch-upgrading.en.html#upgradingpackages
>
> "The recommended way to upgrade from previous Debian releases is to use
> the package management tool apt-get. In previous releases, aptitude was
> recommended for this purpose, but recent versions of apt-get provide
> equivalent functionality and also have proven to more consistently give
> the desired upgrade results. "

I was indeed; beyond that caveat above, I'm unaware of any obsolatation
(yeah, I made that word up) of aptitude.

> Regards
>
> Michael
>
>
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>
> It would be illogical to kill without reason.
>   -- Spock, "Journey to Babel", stardate 3842.4
>
>


-- 
Though I speak with the tongues of men and of angels, and have not charity, I
am become as sounding brass, or a tinkling cymbal.  And though I have the gift
of prophecy, and understand all mysteries, and all knowledge; and though I have
all faith, so that I could remove mountains, and have not charity, I am nothing.

Re: Problem using "dpkg -i"

[Curt]

On 2018-01-16, Michael Lange  wrote:
> On Tue, 16 Jan 2018 11:13:05 + (UTC)
> Curt  wrote:
>
>> On 2018-01-16, Michael Lange  wrote:
>> >
>> > To the OP: 
>> > a quick web search showed another alternative that (iirc) has not been
>> > mentioned before, see http://bluegriffon.org/ . I don't know anything
>> > about this program, except that it appears to be commercial but open
>> > source and they have a deb package available (which may or may not
>> > work with debian) and it apparently can be used for free with a
>> > somewhat reduced feature set. 
>> 
>>  Buy User's Manual
>>  €7.50 (+VAT inside EU).
>> 
>> Software whose user manual is for sale; sign me up, please, that's for
>> me!
>
> Yes sure, I did not intend to advertise that app. 
> But then, if you buy the "basic" license (for just 75.00 €) you get the
> manual for free!! :-)

I was wondering about that. So you if you download the free and crippled
version, and don't want to pay 7.50 €, you're on your own.

Apparently they like decimal multiples of 7.50 (I'm guessing a lifetime update
and license option must cost 750.00).

My brief visit to the site did not reveal to me the system requirements
for the app; maybe I missed them somehow (or maybe they're not there).

> Still, if one is looking for such a tool there are not too many
> competitors out there. If the free version is usable without buying the
> manual I cannot tell (and I do not feel much inclination to find out).
> And besides, I don't think we should condemn the developers because they
> try to earn money with the work they are doing. Some way or other all of
> us have to earn their living. At least they give away a free and open
> source version of their app and sell the manual, I think that is better
> than the other way around.

Yes, but before I take a test drive I like to read the manual first.
Maybe I'm funny that way.

> Regards
>
> Michael
>
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>
> Without followers, evil cannot spread.
>   -- Spock, "And The Children Shall Lead", stardate 5029.5
>
>


-- 
Though I speak with the tongues of men and of angels, and have not charity, I
am become as sounding brass, or a tinkling cymbal.  And though I have the gift
of prophecy, and understand all mysteries, and all knowledge; and though I have
all faith, so that I could remove mountains, and have not charity, I am nothing.

Re: Problem using "dpkg -i"

[Michael Lange]

On Tue, 16 Jan 2018 15:29:57 -0600
Richard Owlett  wrote:

> On 01/16/2018 04:17 AM, Michael Lange wrote:
> > [snip]
> > 
> > To the OP:
> > a quick web search showed another alternative that (iirc) has not been
> > mentioned before, see http://bluegriffon.org/ . I don't know anything
> > about this program, except that it appears to be commercial but open
> > source and they have a deb package available (which may or may not
> > work with debian) and it apparently can be used for free with a
> > somewhat reduced feature set.
> > 
> 
> That looks interesting. The only problem is I'm still using i386 flavor.

Maybe you could try to build from source? The instructions at 
https://github.com/therealglazou/bluegriffon
at a quick glance look quite detailed, and I assume you are not
interested in the expensive extra-features from the binary packages
anyway?

Or, the (maybe) easier way, try to pick one of the older releases from 
http://bluegriffon.org/freshmeat/ and see if one of these can be installed
and run on your system (2.3.1 appears to be the latest that comes with a
386 deb).

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

In the strict scientific sense we all feed on death -- even vegetarians.
-- Spock, "Wolf in the Fold", stardate 3615.4

Re: Problem using "dpkg -i"

[Richard Owlett]

On 01/16/2018 04:17 AM, Michael Lange wrote:

[snip]

To the OP:
a quick web search showed another alternative that (iirc) has not been
mentioned before, see http://bluegriffon.org/ . I don't know anything
about this program, except that it appears to be commercial but open
source and they have a deb package available (which may or may not work
with debian) and it apparently can be used for free with a somewhat
reduced feature set.



That looks interesting. The only problem is I'm still using i386 flavor.

Re: Problem using "dpkg -i"

[Michael Lange]

On Tue, 16 Jan 2018 18:52:51 +0100
deloptes  wrote:

> Curt wrote:
> > 
> > I thought it was merely not recommended for upgrades.
> > 
> 
> might be we check to see what is official statement on that

Maybe Curt refers to the following from
https://www.debian.org/releases/stretch/amd64/release-notes/ch-upgrading.en.html#upgradingpackages

"The recommended way to upgrade from previous Debian releases is to use
the package management tool apt-get. In previous releases, aptitude was
recommended for this purpose, but recent versions of apt-get provide
equivalent functionality and also have proven to more consistently give
the desired upgrade results. "

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It would be illogical to kill without reason.
-- Spock, "Journey to Babel", stardate 3842.4

Re: Problem using "dpkg -i"

[Michael Lange]

On Tue, 16 Jan 2018 11:13:05 + (UTC)
Curt  wrote:

> On 2018-01-16, Michael Lange  wrote:
> >
> > To the OP: 
> > a quick web search showed another alternative that (iirc) has not been
> > mentioned before, see http://bluegriffon.org/ . I don't know anything
> > about this program, except that it appears to be commercial but open
> > source and they have a deb package available (which may or may not
> > work with debian) and it apparently can be used for free with a
> > somewhat reduced feature set. 
> 
>  Buy User's Manual
>  €7.50 (+VAT inside EU).
> 
> Software whose user manual is for sale; sign me up, please, that's for
> me!

Yes sure, I did not intend to advertise that app. 
But then, if you buy the "basic" license (for just 75.00 €) you get the
manual for free!! :-)

Still, if one is looking for such a tool there are not too many
competitors out there. If the free version is usable without buying the
manual I cannot tell (and I do not feel much inclination to find out).
And besides, I don't think we should condemn the developers because they
try to earn money with the work they are doing. Some way or other all of
us have to earn their living. At least they give away a free and open
source version of their app and sell the manual, I think that is better
than the other way around.

Regards

Michael

.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Without followers, evil cannot spread.
-- Spock, "And The Children Shall Lead", stardate 5029.5

Re: Problem using "dpkg -i"

[Brian]

On Tue 16 Jan 2018 at 18:52:51 +0100, deloptes wrote:

> Curt wrote:
> 
> > Obsolated: portmanteau of deprecated and obsolete?
> > 
> > I thought it was merely not recommended for upgrades.
> > 
> 
> might be we check to see what is official statement on that

Section 4.4 of the Release Notes is probably as official as it gets:

https://www.debian.org/releases/stable/amd64/release-notes.en.txt

Should aptitude users really be bothered?

-- 
Brian.

Re: Problem using "dpkg -i"

[deloptes]

Curt wrote:

> Obsolated: portmanteau of deprecated and obsolete?
> 
> I thought it was merely not recommended for upgrades.
> 

might be we check to see what is official statement on that

> PS: Have you ever performed 'apt-get moo'? (You don't need to be root.)
> Gives you a cow.
> 'aptitude moo' (if you persist by increasing the verbosity with ever more
> v's) produces a snake eating an elephant. Maybe that's why it may have
> been obsolated (illogical, Captain).
> 

that's really funny I never had time or desire to ask apt-get to make moo :D

> PSS:
> Knock knock.
> Who's there?
> The interruptive cow.
> The interruptive c...
> Moo!

$ apt-get moo
 (__)
 (oo)
   /--\/
  / |||
 *  /\---/\
~~   ~~
..."Have you mooed today?"...

:D :D :D :D :D :D :D :D :D :D :D :D

Re: Problem using "dpkg -i"

[Jimmy Johnson]

On 01/15/2018 11:17 PM, deloptes wrote:

Jimmy Johnson wrote:


Instead of using apt, next time use aptitude -f install, reason is if
aptitude can not fix the problem it will give you a clue as what you can
do.  Also if you apt install and run 'upgrade-system' upgrade-system
will tell what to do, and clean your system too.


I thought aptitude was obsolated - never used it, but I think there was a
thread on the list about


In my post I should have said: Instead of using apt-get, next time use 
apt -f install or aptitude -f install because the newer apt is also 
verbose like aptitude is. Aptitude is old but still verbose. Personally 
I use all of Debian's tools and when there is a problem, the more 
verbose the better.


Interesting, both aptitude and gdebi got upgrades in the wee hours of my 
morning.  Thank you Debian. :)

--
Jimmy Johnson

Debian Sid/Testing - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda8
Registered Linux User #380263

Re: Problem using "dpkg -i"

[Curt]

On 2018-01-16, Michael Lange  wrote:
>
> To the OP: 
> a quick web search showed another alternative that (iirc) has not been
> mentioned before, see http://bluegriffon.org/ . I don't know anything
> about this program, except that it appears to be commercial but open
> source and they have a deb package available (which may or may not work
> with debian) and it apparently can be used for free with a somewhat
> reduced feature set. 

 Buy User's Manual
 €7.50 (+VAT inside EU).

Software whose user manual is for sale; sign me up, please, that's for
me!

> Regards
>
> Michael
>
>
> .-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.
>
> Madness has no purpose.  Or reason.  But it may have a goal.
>   -- Spock, "The Alternative Factor", stardate 3088.7
>
>


-- 
Though I speak with the tongues of men and of angels, and have not charity, I
am become as sounding brass, or a tinkling cymbal.  And though I have the gift
of prophecy, and understand all mysteries, and all knowledge; and though I have
all faith, so that I could remove mountains, and have not charity, I am nothing.

Re: Problem using "dpkg -i"

[Michael Lange]

On Tue, 16 Jan 2018 08:16:04 +0100
deloptes  wrote:

> Michael Lange wrote:
> 
> > Oddly, so far as I have followed this thread, no one seems to
> > consider the possibility to try and compile the application from the
> > sources. I wonder if the debian developers should quit shipping the
> > build system when nobody wants to use it anyway ;-)
> 
> well this was going to be my next suggestion as people are not familiar
> with building code, however it is also possible that build fails
> because code must be adapted to newer version of libraries.
> 

Sure, that's true, but if one wants to use such a (somewhat dated) app it
might be worth a try, and at least it would be a quick one.
But iirc the OP was talking about required javascript support which would
rule out amaya anyway.

To the OP: 
a quick web search showed another alternative that (iirc) has not been
mentioned before, see http://bluegriffon.org/ . I don't know anything
about this program, except that it appears to be commercial but open
source and they have a deb package available (which may or may not work
with debian) and it apparently can be used for free with a somewhat
reduced feature set. 

Regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

Madness has no purpose.  Or reason.  But it may have a goal.
-- Spock, "The Alternative Factor", stardate 3088.7

Re: Problem using "dpkg -i"

[Curt]

On 2018-01-16, deloptes  wrote:
> Jimmy Johnson wrote:
>
>> Instead of using apt, next time use aptitude -f install, reason is if
>> aptitude can not fix the problem it will give you a clue as what you can
>> do.  Also if you apt install and run 'upgrade-system' upgrade-system
>> will tell what to do, and clean your system too.
>
> I thought aptitude was obsolated - never used it, but I think there was a
> thread on the list about
>

Obsolated: portmanteau of deprecated and obsolete?

I thought it was merely not recommended for upgrades.

PS: Have you ever performed 'apt-get moo'? (You don't need to be root.)
Gives you a cow.
'aptitude moo' (if you persist by increasing the verbosity with ever more
v's) produces a snake eating an elephant. Maybe that's why it may have been 
obsolated (illogical, Captain).

PSS:
Knock knock.
Who's there?
The interruptive cow.
The interruptive c...
Moo!

-- 
Though I speak with the tongues of men and of angels, and have not charity, I
am become as sounding brass, or a tinkling cymbal.  And though I have the gift
of prophecy, and understand all mysteries, and all knowledge; and though I have
all faith, so that I could remove mountains, and have not charity, I am nothing.

Re: Problem using "dpkg -i"

[deloptes]

Jimmy Johnson wrote:

> Instead of using apt, next time use aptitude -f install, reason is if
> aptitude can not fix the problem it will give you a clue as what you can
> do.  Also if you apt install and run 'upgrade-system' upgrade-system
> will tell what to do, and clean your system too.

I thought aptitude was obsolated - never used it, but I think there was a
thread on the list about

Re: Problem using "dpkg -i"

[deloptes]

Michael Lange wrote:

> Oddly, so far as I have followed this thread, no one seems to consider the
> possibility to try and compile the application from the sources. I
> wonder if the debian developers should quit shipping the build system
> when nobody wants to use it anyway ;-)

well this was going to be my next suggestion as people are not familiar with
building code, however it is also possible that build fails because code
must be adapted to newer version of libraries.

Installing debian for chroot is not trivial job with debootstrap and for a
user a better way (IMO)

regards

Re: Problem using "dpkg -i"

[Jimmy Johnson]

On 01/15/2018 01:17 AM, Richard Owlett wrote:

On 01/15/2018 02:25 AM, Bernd Gruber wrote:

Richard Owlett wrote:


Received error message:
dpkg: dependency problems prevent configuration of amaya:
   amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
    Package libssl0.9.8 is not installed.


try apt-get -f install

Bernd


I had already tried "fix broken" option in Synaptic.
All it did was remove all pieces of Amaya.

I repeated
dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb
followed by
apt-get -f install
with the same result ;<


Instead of using apt, next time use aptitude -f install, reason is if 
aptitude can not fix the problem it will give you a clue as what you can 
do.  Also if you apt install and run 'upgrade-system' upgrade-system 
will tell what to do, and clean your system too.


Also there is a GUI package that installs downloaded packages called 
'gdebi', 'apt install gdebi' and right click on the package you want to 
install, choose other, check the box to remember so you don't have to do 
this again and choose '/usr/bin/gdebi-gtk' and install your package, the 
next time just click on the package you want to install.


There is a gdebi-kde version but never seems to work.

Cheers,
--
Jimmy Johnson

Debian Buster - KDE Plasma 5.10.5 - AMD A8-7600 - EXT4 at sda7
Registered Linux User #380263

Re: Problem using "dpkg -i"

[Michael Lange]

On Mon, 15 Jan 2018 20:36:59 +0100
deloptes  wrote:

> Richard Owlett wrote:
> 
> > I repeated
> > dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb
> > followed by
> > apt-get -f install
> > with the same result ;
> 
> 
> If this app depends on ssl 0.98, it might have been working on jessy or
> wheezy - it is very likely that it will have some other missing
> features.
> 
> better would be to install the system it was working on in chroot and
> provide those dependencies, or better get a newer working version of the
> application with correct dependencies.

There is apparently no newer version available. And installing a new
system for one single app sounds like considerable effort. 

Oddly, so far as I have followed this thread, no one seems to consider the
possibility to try and compile the application from the sources. I
wonder if the debian developers should quit shipping the build system
when nobody wants to use it anyway ;-)

Best regards

Michael


.-.. .. ...- .   .-.. --- -. --.   .- -. -..   .--. .-. --- ... .--. . .-.

It [being a Vulcan] means to adopt a philosophy, a way of life which is
logical and beneficial.  We cannot disregard that philosophy merely for
personal gain, no matter how important that gain might be.
-- Spock, "Journey to Babel", stardate 3842.4

Re: Problem using "dpkg -i"

[deloptes]

Richard Owlett wrote:

> I repeated
> dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb
> followed by
> apt-get -f install
> with the same result ;


If this app depends on ssl 0.98, it might have been working on jessy or
wheezy - it is very likely that it will have some other missing features.

better would be to install the system it was working on in chroot and
provide those dependencies, or better get a newer working version of the
application with correct dependencies.

regards

Re: Problem using "dpkg -i"

[Richard Owlett]

On 01/15/2018 11:38 AM, Sven Joachim wrote:

On 2018-01-15 01:32 -0600, Richard Owlett wrote:

[snip]
2. Is there a recommended HTML editor in the repository that"
A. simple UI
B. can render the code so I can tell if my changes display
   as intended?


There is bluefish, but it only supports previews via an external browser
(according to the package description, I have not used it myself).



Not for this project. But the manual hints it would useful for other 
things. Much reading ahead.


Thanks

Re: Installing and running legacy software (was Re: Problem using "dpkg -i")

[Richard Owlett]

On 01/15/2018 11:26 AM, Richard Owlett wrote:

On 01/15/2018 10:12 AM, bw wrote:



On Mon, 15 Jan 2018, Richard Owlett wrote:


*ROFL* 
I started with Netscape 4 and have ignored Firefox/Thunderbird.
I currently have SeaMonkey 2.49.1
. 



Composer choked on the file I was trying to edit.
Years ago I had run into a particular file which Composer had problems.
At the time I discovered Amaya.

I solved the problem using brute force. So time pressure is reduced.

Thank you.







I used seamonkey yrs ago also, then iceape composer when it was in the
repo.  The composer wrote awful code, but for a simple wysiwyg, it wasn't
bad.

For simple html these days I find nano/dillo combination very nice.  
Dillo

browser is very good at finding mistakes in html, and nano... well what
can I say?




As I'm retired, snowed in, and not interested in house cleaning I'll 
download both and experiment.


It is advertised as small, not as full-featured.
For the page that started this JavaScript turned out to be part of the 
problem. It doesn't do that ;/


I found Amayaon my dusty WinXP box. It also doesn't do JavaScript.

I'd have another problem with it. I see no way to increase the font size 
to make it readable.


Thank you

Re: Problem using "dpkg -i"

[Sven Joachim]

On 2018-01-15 01:32 -0600, Richard Owlett wrote:

> A long time ago I had used Amaya, a HTML editor available at
> .
> I know, it's OLD. But I've used it ;/
>
> I did:
> dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb
>
> Received error message:
> dpkg: dependency problems prevent configuration of amaya:
>  amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
>   Package libssl0.9.8 is not installed.

> Questions:
> 1. Can I "fix" the install?

Get libssl0.9.8 from snapshot.debian.org[1].  Probably version
0.9.8o-4squeeze23[2] is the one you want, it appears to be the last
security upload for squeeze-lts.

> 2. Is there a recommended HTML editor in the repository that"
>A. simple UI
>B. can render the code so I can tell if my changes display
>   as intended?

There is bluefish, but it only supports previews via an external browser
(according to the package description, I have not used it myself).

Cheers,
   Sven


1. http://snapshot.debian.org/binary/libssl0.9.8/
2. 
http://snapshot.debian.org/archive/debian-archive/20160313T130328Z/debian/pool/main/o/openssl/libssl0.9.8_0.9.8o-4squeeze23_i386.deb

Re: Installing and running legacy software (was Re: Problem using "dpkg -i")

[Richard Owlett]

On 01/15/2018 10:12 AM, bw wrote:



On Mon, 15 Jan 2018, Richard Owlett wrote:


*ROFL* 
I started with Netscape 4 and have ignored Firefox/Thunderbird.
I currently have SeaMonkey 2.49.1
.

Composer choked on the file I was trying to edit.
Years ago I had run into a particular file which Composer had problems.
At the time I discovered Amaya.

I solved the problem using brute force. So time pressure is reduced.

Thank you.







I used seamonkey yrs ago also, then iceape composer when it was in the
repo.  The composer wrote awful code, but for a simple wysiwyg, it wasn't
bad.

For simple html these days I find nano/dillo combination very nice.  Dillo
browser is very good at finding mistakes in html, and nano... well what
can I say?




As I'm retired, snowed in, and not interested in house cleaning I'll 
download both and experiment.

Re: Installing and running legacy software (was Re: Problem using "dpkg -i")

[Richard Owlett]

On 01/15/2018 06:42 AM, Carl Fink wrote:

On 01/15/2018 06:53 AM, Richard Owlett wrote:

On 01/15/2018 03:57 AM, Jonathan Dowland wrote:

[big snip]



2. Is there a recommended HTML editor in the repository that"
  A. simple UI
  B. can render the code so I can tell if my changes display
 as intended?


I can't answer this question because I am not familiar with a 
particular tool that does this, but I would recommend investigating 
this option

thoroughly before resorting to #1.




No argument ;/
I've WinXP box. I'll try the Windows version. It wont be as convenient 
but as it has no internet connectivity the security issues should be 
minimized.



You might look at SeaMonkey, a community continuation of the old integrated
browser/mailer/HTML editor that Netscape originally released. I found 
its HTML

editing function pretty usable back when I needed it.

https://wiki.debian.org/Seamonkey



*ROFL* 
I started with Netscape 4 and have ignored Firefox/Thunderbird.
I currently have SeaMonkey 2.49.1 
.


Composer choked on the file I was trying to edit.
Years ago I had run into a particular file which Composer had problems.
At the time I discovered Amaya.

I solved the problem using brute force. So time pressure is reduced.

Thank you.

Re: Installing and running legacy software (was Re: Problem using "dpkg -i")

[Carl Fink]

On 01/15/2018 06:53 AM, Richard Owlett wrote:

On 01/15/2018 03:57 AM, Jonathan Dowland wrote:

[big snip]



2. Is there a recommended HTML editor in the repository that"
  A. simple UI
  B. can render the code so I can tell if my changes display
 as intended?


I can't answer this question because I am not familiar with a 
particular tool that does this, but I would recommend investigating 
this option

thoroughly before resorting to #1.




No argument ;/
I've WinXP box. I'll try the Windows version. It wont be as convenient 
but as it has no internet connectivity the security issues should be 
minimized.



You might look at SeaMonkey, a community continuation of the old integrated
browser/mailer/HTML editor that Netscape originally released. I found 
its HTML

editing function pretty usable back when I needed it.

https://wiki.debian.org/Seamonkey

--
Carl Fink  c...@finknetwork.com
Thinking and logic and stuff at Reasonably Literate
http://reasonablyliterate.com

Re: Installing and running legacy software (was Re: Problem using "dpkg -i")

[Richard Owlett]

On 01/15/2018 03:57 AM, Jonathan Dowland wrote:

On Mon, Jan 15, 2018 at 01:32:07AM -0600, Richard Owlett wrote:
A long time ago I had used Amaya, a HTML editor available at 
.

I know, it's OLD. But I've used it ;/

I did:
dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb

Received error message:
dpkg: dependency problems prevent configuration of amaya:
amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
 Package libssl0.9.8 is not installed.

However Synaptic indicates that libssl1.0.2 is installed.

Questions:
1. Can I "fix" the install?


The short answer is: yes, there are several approaches, I'll outline the
skeletons of some below, but they are quite complex and have caveats and
I would not recommend trying these for beginners (not that you are a
beginner...)


Years do not necessarily mean expertise ;/



[snip]

If *that* worked, you could investigate repacking the amaya .deb with the
compatibility symlink in it and the dependencies edited, and installing
the result; or, just run it out of the unpacked location above.

However this is awkward, error prone etc.; out of scope for my mail here
but this class of problem is better addressed using container technology
IMHO, like Flatpak (or Docker at a pinch); but the work needs to be done
to prepare containers with legacy dependencies within them for such
software and that has not been done yet so far as I know.


Not sure I've competency to effectively follow your outline.
I was assuming I had a syntax error of some sort.



2. Is there a recommended HTML editor in the repository that"
  A. simple UI
  B. can render the code so I can tell if my changes display
 as intended?


I can't answer this question because I am not familiar with a particular 
tool that does this, but I would recommend investigating this option

thoroughly before resorting to #1.




No argument ;/
I've WinXP box. I'll try the Windows version. It wont be as convenient 
but as it has no internet connectivity the security issues should be 
minimized.


Thanks.

Re: Problem using "dpkg -i"

[Richard Hector]

On 15/01/18 20:32, Richard Owlett wrote:
> dpkg: dependency problems prevent configuration of amaya:
>  amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
>   Package libssl0.9.8 is not installed.
> 
> However Synaptic indicates that libssl1.0.2 is installed.

The different (libssl) package name (not just the version) suggests that
it's probably not compatible (ABI change).

You'd probably need to build it yourself.

Richard



signature.asc
Description: OpenPGP digital signature

Installing and running legacy software (was Re: Problem using "dpkg -i")

[Jonathan Dowland]

On Mon, Jan 15, 2018 at 01:32:07AM -0600, Richard Owlett wrote:
A long time ago I had used Amaya, a HTML editor available at 
.

I know, it's OLD. But I've used it ;/

I did:
dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb

Received error message:
dpkg: dependency problems prevent configuration of amaya:
amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
 Package libssl0.9.8 is not installed.

However Synaptic indicates that libssl1.0.2 is installed.

Questions:
1. Can I "fix" the install?


The short answer is: yes, there are several approaches, I'll outline the
skeletons of some below, but they are quite complex and have caveats and
I would not recommend trying these for beginners (not that you are a
beginner...)

If you can source a package for libssl0.9.8, then you could try to
install that before the Amaya deb. However, depending on where you
got it from, you may find that it itself has other package dependencies
that you cannot satisfy in current Debian releases, and would need to
chase down too; if libssl0.9.8 or any other package like this conflicts
with another package that you have installed you could get into
problems, and there's also the issue of libssl0.9.8 being a security
critical package and out of security support.

You could try unpacking the Amaya deb, and seeing whether the binary
within would run even without the dependencies installed. Something
like:

   $ dpkg-deb -x ~richard/Downloads/amaya_11.4.7-1_i386.deb some-path
   $ ./some-path/usr/bin/amaya

If it complains specifically about libssl0.9.8 upon starting up, you
could experiment to see whether your more recent libssl would still work
in its place, as follows (something a bit like this)

   $ cd some-path # where you extracted the deb, above
   $ mkdir -p usr/lib
   $ cd usr/lib
   $ ln -s /usr/lib/i386*/libssl.so.1.0.0 libssl.so.0.9.8
   $ export LD_LIBRARY_PATH=$(pwd)
   $ cd ../../
   $ ./usr/bin/amaya

If *that* worked, you could investigate repacking the amaya .deb with the
compatibility symlink in it and the dependencies edited, and installing
the result; or, just run it out of the unpacked location above.

However this is awkward, error prone etc.; out of scope for my mail here
but this class of problem is better addressed using container technology
IMHO, like Flatpak (or Docker at a pinch); but the work needs to be done
to prepare containers with legacy dependencies within them for such
software and that has not been done yet so far as I know.


2. Is there a recommended HTML editor in the repository that"
  A. simple UI
  B. can render the code so I can tell if my changes display
 as intended?


I can't answer this question because I am not familiar with a particular 
tool that does this, but I would recommend investigating this option

thoroughly before resorting to #1.


--

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄ Please do not CC me, I am subscribed to the list.

Re: Problem using "dpkg -i"

[Richard Owlett]

On 01/15/2018 02:25 AM, Bernd Gruber wrote:

Richard Owlett wrote:


Received error message:
dpkg: dependency problems prevent configuration of amaya:
   amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
Package libssl0.9.8 is not installed.


try apt-get -f install

Bernd


I had already tried "fix broken" option in Synaptic.
All it did was remove all pieces of Amaya.

I repeated
dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb
followed by
apt-get -f install
with the same result ;<

Thanks.

Re: Problem using "dpkg -i"

[Bernd Gruber]

Richard Owlett wrote:
> 
> Received error message:
> dpkg: dependency problems prevent configuration of amaya:
>   amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
>Package libssl0.9.8 is not installed.

try apt-get -f install

Bernd

Problem using "dpkg -i"

[Richard Owlett]

A long time ago I had used Amaya, a HTML editor available at 
.

I know, it's OLD. But I've used it ;/

I did:
dpkg -i /home/richard/Downloads/amaya_11.4.7-1_i386.deb

Received error message:
dpkg: dependency problems prevent configuration of amaya:
 amaya depends on libssl0.9.8 (>= 0.9.8m-1); however:
  Package libssl0.9.8 is not installed.

However Synaptic indicates that libssl1.0.2 is installed.

Questions:
1. Can I "fix" the install?
2. Is there a recommended HTML editor in the repository that"
   A. simple UI
   B. can render the code so I can tell if my changes display
  as intended?

TIA