[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libidn2 build requires network + wget

From: Tim Ruehsen
Subject: Re: libidn2 build requires network + wget
Date: Tue, 27 Dec 2016 14:42:53 +0100
User-agent: KMail/5.2.3 (Linux/4.8.0-2-amd64; KDE/5.28.0; x86_64; ; )

On Tuesday, December 27, 2016 1:43:36 PM CET Simon Josefsson wrote:
> Hi Tim. There is a separate git repo for libidn2's debian packaging, I
> prefer it that way. There are hundreds of linux distributions and it
> doesn't scale to support them all in upstream git repo.

Hi Simon.

That's fine for me - but as long as I don't have access to that repo, I have to 
work in my own copy of your Gitlab repo. Maybe you can give me some infos 
about that Debian repo so at least I could stay in sync. I have an Alioth 
guest account if that helps (rockdaboot-guest).

> We can't download anything during build, that has to be changed.
> Debian policies forbids that, and it is generally a bad idea. We can include 
the files if the licenses permit.

Got it, will work on a solution this afternoon and let you know.

> If we include the file, doing the checksum is less important.

Meanwhile, I pushed a checksum solution to my repo ( - 
you are currently working on your repo, so maybe it is better if you merge/
cherry-pick commits from me.


> Tim Ruehsen <address@hidden> skrev: (27 december 2016 12:30:23 CET)
> >On Monday, December 26, 2016 11:22:30 PM CET Simon Josefsson wrote:
> >> Hi Tim.  I released 0.12 and will try to upload to Debian, however I
> >> suspect it will fail because ./configure+make will attempt to
> >
> >download
> >
> >> files from the Internet.  Can you think of some way to fix this?  The
> >> files could be included, or some prepared form of the files could be
> >> included, in the tarball.  We should also add a checksum test to make
> >> sure anyone building libidn2 get the files that we expect them to
> >
> >get.
> >
> >Hi Simon, the release is great news !
> >
> >Currently, I am learning a lot about Debian packaging from your
> >comments and
> >your commits after tag libidn2-0.12.
> >
> >How do you like it to be organized ?
> >- putting the changes into my 'debian' branch (as patch set), so you
> >can
> >package based on 0.12.
> >- or basing those changes onto your current 'master', so they go into
> >0.13.
> >
> >Regarding the checksums... those downloaded files should never change
> >upstream,
> >so a hard-coded checksum should do it (sha1 should be fine).
> >The caveat here is that recent OSX removed checksumming tools like
> >'sha1sum'
> >without replacement. Since we use Perl anyways, we could include a
> >small sha1
> >Perl script. WDYT ?
> >
> >Regards, Tim

Attachment: signature.asc
Description: This is a digitally signed message part.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]