How to install a pacjage I compiled

[stan]

On Sat, Apr 04, 2020 at 02:41:20PM -0500, C de-Avillez wrote:
> On Sat, Apr 4, 2020 at 1:54 PM stan <stanb at panix.com> wrote:
> >
> > I cannot find instructions as to how to properly create a modified Debian
> > package for a package that has been migrated to the quilt build process, so
> > finally I just made the request change in debian/rules and followed the
> > build instructions from
> > https://www.debian.org/doc/manuals/maint-guide/build.en.html
> 
> Wait. This is Ubuntu, not Debian; there may be differences in
> (pre|co)-reqs, so you should be careful.

Sorry for not being precise on this. I am pointed at the appropriate Ubuntu
repositories, BTW.
> 
> > This did result in the creation of a package
> > -rw-r--r-- 1 root root  843396 Apr  4 14:08 openssl_1.1.1d-0+deb10u2_amd64.deb
> > so, I did a dpkg -i of this package, yet I still see
> > -rwxr-xr-x 1 root root 736776 Oct 12 15:56 /usr/bin/openssl
> 
> I am sorry, but I am not sure what is it you are asking. I am
> *guessing* it is related to the
> timestamp on /usr/bin/openssl.

Yes, if it had installed the binary I compiled it would have todays
datestamp.
> 
> One thing you can do is 'dkpg -l openssl', and check if the installed
> version matches your
> package version.

You mean dpkg, I am thinking:

Here is the output of that command:

root at openssl-test:/usr/local/bin# dpkg -l openssl
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version          Architecture Description
+++-==============-================-============-================================
ii  openssl        1.1.1d-0+deb10u2 amd64        Secure Sockets Layer
toolkit - c


> 
> If it does, then 'dpkg -L openssl' will list the package files --
> check if /usr/bin/openssl is there.

It is, but I believe this just confirms that the original, upstream built
binary is there, right?
> 
> Then check the build log for something strange. I cannot be really
> precise because I
> do not know what is it you changed...

The build succeeded, and I have an openssl binary in the build tree and a
package file 

-rw-r--r-- 1 root root  843396 Apr  4 14:08
openssl_1.1.1d-0+deb10u2_amd64.deb

I added this flag in debian/rules

enable-weak-ssl-ciphers


> 
> > I recognize that the kludge I used does not change the name of the package,
> > but should this not reinstall it using the newly compiled package?
> 
> Indeed 'dpkg -i ,package>' will replace the named package. Version
> checking will be
> performed, and may affect the operation.
> 
And I believe that is where the issue lies. Since I cannot find
instructions as to how to build a renamed package using the quilt
mechanism, only the mechanism prior to that, my modified package, I
believe, has the exact same name as the original upstream package. I did
try add the --force-all to the dpkg -i <package-name> but that did not change
anything.


Thanks for the help.
-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
						-- Benjamin Franklin