Richard Kettlewell wrote:

> "NotReal"  writes:
> > The Natural Philosopher wrote:
> >> On 25/09/18 10:14, Richard Kettlewell wrote:
> >>>The Natural Philosopher  writes:
> >>>> https://wiki.debian.org/Packaging/SourcePackage
> >>>>
> >>>> Download the source pakage and proceed as indicated. It should 'just
> >>>> build'
> >>>
> >>> You need to install the build-dependencies as well. dpkg-buildpackage[1]
> >>> will tell you what they are.
> >>>
> >>>  [1] http://man7.org/linux/man-pages/man1/dpkg-buildpackage.1.html
> >>>
> >>>> You need to be root probly to build stuff
> >>>
> >>> You don’t need to be root to build Debian packages from source. The
only
> >>> step that needs a root-like environment is the assembly of build
> >>> products into a .deb file, and fakeroot is sufficient for that (and is
> >>> what dpkg-buildpackage uses).
> >>>
> >> I hoped you would step in and provide chapter and verse.
> >>
> >> Cheers!
> >
> > As suggested I ran “sudo dpkg-buildpackage”.  My first attempt failed
> > because, as you suspected, it was missing the following dependencies
>
> You do not need root here. See above.

I did read that in past posts, but when things are giving error messages you
try everything might help.  I did try it without the "sudo" first.

>
> > I also haad a group of eight identical errors one of which is shown below.
> > These errors were same kind as the ones I received previously using
“make”
> >
> >
> > ____________
> >
> > readvmf.c:353:7: error: ‘*fd’ is a pointer; did you mean to use
‘->’?
> >    i = gzgetc(fd);
> >        ^
> >        ->
> > ___________
> >
>
> That’s a bug in sunclock. The Debian package in stretch disabled zlib
> support to work around this issue in 2012:
>
> >  sunclock (3.57-1) unstable; urgency=low
> >
> >    [...]
> >    * Disable ZLIB, because this causes trouble with zlib 1.2.6.
> >
> |  -- Roland Rosenfeld   Mon, 05 Mar 2012 14:52:35 +0100


Glad to know there might be a light at then end of the tunnel that is not a
train coming from the opposite direction.


> Your other post implies you’re not using that but have actually got
> source code from some other, hopelessly out-of-date, source.
>
> Get the source code for the distribution you’re using, from that
> distribution, using ‘apt-get source sunclock’, and try again.


It took me a while to get rid of the message about needing a URI and learning
enough to alter /etc/apt/sources.list.d/raspi.list but I think "apt-get source"
is now working the way it should and the message below is what I receive.

_________

pi@raspberrypi:~/temp $ apt-get source sunclock
Reading package lists... Done
E: Unable to find a source package for sunclock

_________

I then did a

/var/lib/apt/lists $ grep sunclock *

and found the line.

raspbian.raspberrypi.org_raspbian_dists_stretch_main_binary-armhf_Packages:Sour
c
e: sunclock

but it didn't find "sunclock" in any of the

archive.raspberrypi.org_debian_dists_stretch_main_source_Sources

or

archive.raspberrypi.org_debian_dists_stretch_ui_source_Sources

lists.


The one thing that bothers me though is that there are 57020 packages listed in


raspbian.raspberrypi.org_raspbian_dists_stretch_main_binary-armhf_Packages


but only 305 packages listed in


archive.raspberrypi.org_debian_dists_stretch_main_source_Sources


so I am probably not doing something right.   I would not think there would be
so few sources available for that many binaries.  ???

--- SoupGate-Win32 v1.05