User Details
- User Since
- May 30 2017, 11:42 AM (440 w, 4 d)
Thu, Nov 6
Just to make sure I'm on the same page, because to me having FreeBSD-blocklist-lib and FreeBSD-blocklist would be like having FreeBSD-ssh and FreeBSD-ssh-lib.
I do not see a working FreeBSD-ssh package without FreeBSD-blocklist, that is, I was going to ask you if we should add a deps block to ssh.ucl?
On the other hand, if we decide to split, where should we stop? Should FreeBSD-blocklist be split into FreeBSD-blocklist-client and FreeBSD-blocklist-daemon?
At this point I'm not opposed nor in favor, I just need to gather more information. Thank you for taking a look at this issue.
Wed, Nov 5
Sun, Nov 2
Thu, Oct 30
Tue, Oct 28
Mon, Oct 27
Address suggestions:
Sun, Oct 26
This is the simplest fix I can think of to fix PR 280516.
Feel free to commandeer, this or the parent revision. My main objective is to ship blocklist without defects or misleading warnings.
Ignore stderr for now, it throws a bogus warning about an (ethernet) anchor not found (PR 280516).
Remove patch file for bugzila.
Sat, Oct 25
Fri, Oct 24
Thu, Oct 23
Wed, Oct 22
Tue, Oct 21
- The first line of the user data file cannot be empty
These are the current checks:
At this point I'm lost against the file specifications:
- Guard earlier against line being empty
- Guard against content being empty
- Fix typos
