psibi / tldr-hs

Haskell tldr client
BSD 3-Clause "New" or "Revised" License
92 stars 14 forks source link

Keeping the Ubuntu APT repo up to date #37

Open CleanMachine1 opened 3 years ago

CleanMachine1 commented 3 years ago

The APT repo(Ubuntu) has tldr within, as you probably know. However it is incredibly out of date, a version from over 2 years ago. Do you have anyway to update it to most recent or am I contacting the wrong place

psibi commented 3 years ago

Unfortunately, I don't maintain the package in Ubuntu.

One easy way to get binaries is via the downloads available here: https://github.com/psibi/tldr-hs/releases/tag/v0.9.0

CleanMachine1 commented 3 years ago

Thanks for the really quick response. Do you know who may be able to help me, I know I can get the binaries easy however I am trying to keep the apt package up to date for others

bl-ue commented 3 years ago

(for future reference: https://github.com/tldr-pages/tldr/issues/5937)

psibi commented 3 years ago

Do you know who may be able to help me,

Unfortunately no... Probably try their mailing list ?

But I think the recent version of Ubuntu ships with a relatively new one: http://manpages.ubuntu.com/manpages/impish/man1/tldr-hs.1.html

CleanMachine1 commented 3 years ago

Thank you, please leave this issue open incase anyone else has anything to add

patricedenis commented 3 years ago

Are the Ubuntu and Debian packages linked together? When I look into the Debian package Tracker, it seems that the tldr client is the haskell package that is included into sid and bullseyes version 0.6.4-1 and others whereas in buster the tldr-client is version 0.4.0-2. see https://packages.debian.org/sid/tldr

patricedenis commented 3 years ago

I even see that your new version 0.9.0 is considered upstream by debian see https://tracker.debian.org/pkg/haskell-tldr for details. Isn't it the case @psibi ?

psibi commented 3 years ago

@patricedenis

Are the Ubuntu and Debian packages linked together?

I don't have much idea on how they package. I guess Ubuntu will be using the upstream Debian packages.

I even see that your new version 0.9.0 is considered upstream by debian see https://tracker.debian.org/pkg/haskell-tldr for details. Isn't it the case @psibi ?

Didn't know about that. But that's a nice news!

patricedenis commented 3 years ago

yeah, this is a good news, in fact. Congrats !! :clap:

For the Ubuntu packaging, it doesn't suprise me as Ubuntu is really based on Debian so sometimes they have Ubuntu specific packages but really often, they share packages as well.

By the way, once again, well done you !

patricedenis commented 3 years ago

Hi @psibi I was trying to update the debian tldr package when I met several errors mainly with missing dependencies. But this one I can't understand. May be you could help me?

. /usr/share/haskell-devscripts/Dh_Haskell.sh && \ install_prof_recipe "libghc-tldr-prof" Running cd debian/tmp-inst-ghc Running mkdir -p usr/lib/haskell-packages/ghc/lib Running find usr/lib/haskell-packages/ghc/lib/ \! \( \! -name \*_p.a \! -name \*.p_hi \) -exe c install -Dm 644 \{\} ../libghc-tldr-prof/\{\} \; Running dh_haskell_provides -plibghc-tldr-prof Running dh_haskell_depends -plibghc-tldr-prof ghc-pkg: cannot parse 'semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK' as a package identifier (exact): "<eitherParsec>" (line 1, column 41): unexpected all digits or a dot in a portion of package name expecting "-" make: *** [/usr/share/cdbs/1/class/hlibrary.mk:212: install/libghc-tldr-prof] Error 1 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 I: copying local configuration E: Failed autobuilding of package

as I understand, the compiler should produce a libghc-tldr-prof target but it fails. what I don't understand is why it refers to the 'semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK' complete ID where I mentionned in the build dependencies only the name of the modules added after tag release 0.6.4. I did'nt mention the complete Id but just semigroups in the dependencies.

By the way is it true that the project depends from these new modules ? libghc-optparse-applicative-prof, libghc-zip-archive-prof, libghc-http-conduit-prof libghc-optparse-applicative-prof, libghc-zip-archive-prof, libghc-http-conduit-prof

I added them in the dependencies to build to debian package.

An other question is : I saw in the commit history that you splited the library. This is from release v0.8.0. should I build other targets than the following ones in my package? libghc-tldr-dev, libghc-tldr-prof, libghc-tldr-doc, libghc-tldr

Thanks for your time.

psibi commented 3 years ago

what I don't understand is why it refers to the 'semigroups-0.19.1-LKdktuRRdRZ1yx9gBXzSbK'

Probably because semigroups is one of the transitive dependency.

By the way is it true that the project depends from these new modules ?

Yeah, that sounds correct.

An other question is : I saw in the commit history that you splited the library. This is from release v0.8.0.

Yeah, that is intentional.

should I build other targets than the following ones in my package? libghc-tldr-dev, libghc-tldr-prof, libghc-tldr-doc, libghc-tldr

I think the only major thing important is libghc-tldr which likely contains the binary. The other ones aren't that important, but I don't know what's Debian policy on these things.

patricedenis commented 3 years ago

Probably because semigroups is one of the transitive dependency.

yeah I included the semigroups lib into the dependencies but at compilation time I've got an error saying that the number should not appear where I did not mention any number to this lib

unexpected all digits or a dot in a portion of package name expecting

I think the only major thing important is libghc-tldr which likely contains the binary. The other ones aren't that important, but I don't know what's Debian policy on these things.

As I saw, all the libraries were built on the previous version, that's why I tried to do the same here.