-
Notifications
You must be signed in to change notification settings - Fork 0
Conversation
@thomas, it was probably still in your branch. How did you create the branch update-libidn? |
|
||
# BEE_VERSION libidn-1.33-0 | ||
|
||
SRCURL[0]="http://ftp.gnu.org/gnu/libidn/libidn-${PKGVERSION}.tar.gz" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use https
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
whatfor ?
Anyway will test amending
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To have a little bit more security, meaning, we at least know we connect to the GNU server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
have you tested it with https?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not with this package, but with other GNU software. I can access https://ftp.gnu.org too.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
Could you please also delete the old libidn beefile? |
a) git branch update-libidn, status said 1 file |
a) Well, the jemalloc commit was probably still in your branch you were in, when you executed |
how could jemalloc be in the branch if i did a |
The jemalloc commit was already present in whatever branch you were. Then |
I'll see if i can reproduce it. |
nb. installation auf |
Funny, how did
jemalloc
get in?