date:20180102

Re: lang/ghc -8.0.2_2 mismatched checksums

2018-01-02 Thread Kevin Oberman

On Tue, Jan 2, 2018 at 4:42 AM, Mike Clarke 
wrote:

>
> My daily periodic security run comes up with with these errors:
>
> Checking for packages with mismatched checksums:
> ghc-8.0.2_2: /usr/local/bin/haddock
> ghc-8.0.2_2: /usr/local/lib/ghc-8.0.2/package.conf.d/package.cache
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-33.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-36.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-43.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-46.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-58.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-60.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-61.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-62.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-92.h
> tml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-A.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-All.
> html
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-B.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-C.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-D.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-E.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-F.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-G.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-H.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-I.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-J.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-K.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-L.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-M.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-N.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-O.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-P.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Q.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-R.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-S.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-T.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-U.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-V.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-W.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Y.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Z.ht
> ml
> ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/index.html
>
> -- End of security output --
>
> I've reinstalled the package but still get the errors.
>
> curlew:/home/mike% pkg info  ghc
> ghc-8.0.2_2
> Name   : ghc
> Version: 8.0.2_2
> Installed on   : Mon Jan  1 09:35:19 2018 GMT
> Origin : lang/ghc
> Architecture   : FreeBSD:11:amd64
> Prefix : /usr/local
> Categories : haskell lang
> Licenses   : BSD3CLAUSE
> Maintainer : hask...@freebsd.org
> WWW: http://www.haskell.org/ghc/
> Comment: Compiler for the functional language Haskell
> Options:
> BOOT   : off
> BOOTH  : off
> DOCS   : on
> DYNAMIC: on
> PROFILE: on
> Shared Libs required:
> libgmp.so.10
> libiconv.so.2
> libcharset.so.1
> Shared Libs provided:
> libHSrts_thr-ghc8.0.2.so
> libHSrts-ghc8.0.2.so
> libHSfilepath-1.4.1.1-ghc8.0.2.so
> libHSghc-boot-th-8.0.2-ghc8.0.2.so
> libffi.so.6
> libHSghc-prim-0.5.0.0-ghc8.0.2.so
> libHSCabal-1.24.2.0-ghc8.0.2.so
> libHSrts_thr_debug-ghc8.0.2.so
> libHSrts_debug-ghc8.0.2.so
> libHSpretty-1.1.3.3-ghc8.0.2.so
> libHSarray-0.5.1.1-ghc8.0.2.so
> libHStransformers-0.5.2.0-ghc8.0.2.so
> libHShoopl-3.10.2.1-ghc8.0.2.so
> libHShpc-0.6.0.3-ghc8.0.2.so
> libHSghc-boot-8.0.2-ghc8.0.2.so
> libHStemplate-haskell-2.11.1.0-ghc8.0.2.so
> libHSghc-8.0.2-ghc8.0.2.so
> libHSbinary-0.8.3.0-ghc8.0.2.so
> libHSghci-8.0.2-ghc8.0.2.so
> libHSdirectory-1.3.0.0-ghc8.0.2.so
> libHShaskeline-0.7.3.0-ghc8.0.2.so
> libHSunix-2.7.2.1-ghc8.0.2.so
>

Re: I've started getting ^@^@> in my xterms w/mutt

2018-01-02 Thread Kurt Jaeger

Hi!

> I recently updated my system (base OS and ports) that I read mail on using
> mutt (accessed via an xterm on a separate system) and am now seeing this sort
> of character string ^@^@> rather than the much more user friently characters I
> used to get.
> 
> Anyone know what I can do to get back the more readable stuff? Is there some
> setting that I need to perform?

I had the same problem. Since then I use the SLANG option instead of NCURSES
to build mutt.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208659

-- 
p...@opsec.eu+49 171 3101372 2 years to go !
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

mail/phpmailer abandoned?

2018-01-02 Thread Ken

Is the ports maintainer in charge of mail/phpmailer no longer updating it?

I've sent 2 emails a couple months ago and heard nothing back. Also, I
submitted a bug report stating an update is needed - and that is now
collecting dust.

PHPMailer 5.2.26 was released on November 4th. Also, the new v6.0.2 was
released on November 30th.

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=223828
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Ports with binary bootstrap packages and CURRENT+ino64

2018-01-02 Thread Jan Beich

Anthony Jenkins writes:

> (gdb) where
> #0  stat () at freebsd11_stat.S:3
> #1  0x016a94a0 in std::sys::imp::fs::stat () at 
> /checkout/src/libstd/sys/unix/fs.rs:732
> #2  0x016a1a76 in std::fs::metadata<::path::Path> () at 
> /checkout/src/libstd/fs.rs:1271
> #3  std::path::Path::exists () at /checkout/src/libstd/path.rs:2247
> #4  0x014e4f19 in home::cargo_home_with_cwd ()
> #5  0x0130a7f4 in cargo::util::config::homedir ()
> #6  0x012fa71b in cargo::util::config::Config::default ()
> #7  0x010c396e in cargo::main ()
> #8  0x016b5bbd in panic_unwind::__rust_maybe_catch_panic () at 
> /checkout/src/libpanic_unwind/lib.rs:99
> #9  0x016af58c in std::panicking::try<(),closure> () at 
> /checkout/src/libstd/panicking.rs:459
> #10 std::panic::catch_unwind () at 
> /checkout/src/libstd/panic.rs:361
> #11 std::rt::lang_start () at /checkout/src/libstd/rt.rs:61
> #12 0x01080db1 in _start ()

Not sure how you've hit this after
https://svnweb.freebsd.org/changeset/ports/441843

Can you show output for the following?

  $ make -V OSVERSION

For 423586ee (aka r326754) it should be 1200054.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

I've started getting ^@^@> in my xterms w/mutt

2018-01-02 Thread Bob Willcox

I recently updated my system (base OS and ports) that I read mail on using
mutt (accessed via an xterm on a separate system) and am now seeing this sort
of character string ^@^@> rather than the much more user friently characters I
used to get.

Anyone know what I can do to get back the more readable stuff? Is there some
setting that I need to perform?

Thanks,
Bob

-- 
Bob Willcox| If everything is coming your way, you're in the
b...@immure.com | wrong lane.
Austin, TX |
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: mail/mutt && security/gnupg (after gnupg20 -> gnupg) weirdness

2018-01-02 Thread David Wolfskill

I *think* the issue is that I needed to update ~/.muttrc for the change
in gnupg; in particular:

set pgp_decrypt_command="gpg --keyserver pgp.mit.edu --passphrase-fd 0 
--no-verbose --batch -o - %f"

was changed to

set pgp_decrypt_command="gpg2 %?p?--passphrase-fd 0 --pinentry-mode=loopback? 
--no-verbose --batch --output - %f"

(based on ).

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
If you want the best Fake News, go to the best source of it: Donald J. Trump.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

Re: DEFAULT_VERSIONS conflicts

2018-01-02 Thread Roger Marquis


Sorry, the language there is unclear. It should say "ssl=[name of the port]".
You just want the ssl=libressl line.


Ah, so the "base" specified here is a constant whereas "port" is a
variable, to be expanded before writing make.conf.  If I might then
suggest a potential documentation update:

< WITH_OPENSSL_BASE  DEFAULT_VERSIONS+= ssl=base
< WITH_OPENSSL_PORT  DEFAULT_VERSIONS+= ssl=port


WITH_OPENSSL_BASE  DEFAULT_VERSIONS+= ssl=base
or
WITH_OPENSSL_PORT  DEFAULT_VERSIONS+= ssl=[openssl|libressl|...]


Roger
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: DEFAULT_VERSIONS conflicts

2018-01-02 Thread Adam Weinberger


On 2 Jan, 2018, at 10:47, Roger Marquis  wrote:

Per the 20171214 UPDATING entry:

  Support for some deprecated variables is going to be removed soon. If
  you use any of the following constructs (usually in /etc/make.conf),
  you must switch to the new incantations:
  ...
  WITH_OPENSSL_BASE  DEFAULT_VERSIONS+= ssl=base
  WITH_OPENSSL_PORT  DEFAULT_VERSIONS+= ssl=port

Question is what occurrs when the port version is also specified:

  DEFAULT_VERSIONS+=ssl=libressl

Some builds report an error when both are specified depending on the
order of, for example:

  DEFAULT_VERSIONS+=ssl=libressl
  DEFAULT_VERSIONS+=ssl=port

Is there documentation on how to specify multiple port options?


Sorry, the language there is unclear. It should say "ssl=[name of the port]".
You just want the ssl=libressl line.

# Adam


--
Adam Weinberger
ad...@adamw.org
http://www.adamw.org

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

mail/mutt && security/gnupg (after gnupg20 -> gnupg) weirdness

2018-01-02 Thread David Wolfskill

I have been using mail/mutt & security/gnupg (latter switched to
security/gnupg20 back when gnupg20 port was created because of a
similar-looking issue to what's described in the first part of the
below narrative) for several years -- without enabling "gpgme" (in
case that turns out to be relevant).

As a result, I have a collection of messages that were sent to me that
contain information that was deemed suitable for encryption; I still
have occasion to refer to the contents of some of these messages, and
prefer to leave them stored in encrypted form when I am not actively
reading them.

This morning, during the daily update of installed ports on my
laptop, I saw:

===>>> The security/gnupg20 port moved to security/gnupg
===>>> Reason: Has expired: Will reach EOL upstream on 2017-12-31


OK.  I had vague memories that things didn't work very well last time
there was a "minor" upgrade to gnupg, so I deferred that part of the
upgrade until I could do a bit more research.

I soon found "Bug 196382 - security/gnupg breaks keyring on 2.1.1"
.  So I tried
the recipe listed in Comment 4, then verified that decryption still
worked (while gnupg20 was the version of gnupg that was installed).

That was successful, so I deleted security/gnupg20, then installed
security/gnupg; that done, I re-tried the decryption, which failed
("Could not decrypt PGP message"; "Could not copy message" -- these
messages from mutt).

I then re-did the recipe from Comment 4 (now that security/gnupg was
installed), then re-tried the decryption test; it (still) failed the
same way.

Trying the decryption again (under "ktrace -di") showed the following
messages being issued by gpg:

   "gpg: WARNING: no command supplied.  Trying to guess what you mean ..."

   "gpg: encrypted with 2048-bit RSA key, ID C8A5439CFA5A0A07, created 201\
5-11-29"

   "  "David H. Wolfskill "

   "gpg: public key decryption failed: Invalid IPC response"

   "gpg: decryption failed: No secret key"



Following a hint obtained by searching on the above (particularly
the "gpg: public key decryption failed: Invalid IPC response" message),
I logged in to a machine that still has security/gnupg20 and used

gpg -e /etc/rc.conf

to encrypt a copy of that file with me as a recipient.  Decrypting
worked (as expected).

I then copied the rc.conf.gpg from that machine to my laptop (which now
has security/gnupg installed) and attempted the decryption -- and it
worked.

Given that, I thought that perhaps the (re-)installation of mail/mutt
had been what got things working again; I was thus quite surprised when
(about 3.5 hrs. later) I got in to work and had need to decrypt a
message on my laptop, and it -- again -- failed as described above.

As a reality check, I then re-tried the decryption of rc.conf.gpg (from
above); that worked.

After a couple quick shakes of my head to help ensure that I wasn't
hallucinating, I tried reading an encrypted email message (on the
laptop) again... and this time, it worked.

In fact, going back to the first "mutt" invocation that failed at work,
merely requesting to read a message Just Worked -- my passphrase was not
requested (as I had entered it less than 2 hours earlier).

This leaves me wondering if all of the above means that before
attempting to decrypt an encrypted email message via mutt, one is
supposed to (first) use bare gpg to decrypt a file -- but that seems
ridiculous to thye point of hostility

Does anyone have insights, clues, or pointers to same to share?

Thanks!

Peace,
david
-- 
David H. Wolfskill  da...@catwhisker.org
If you want the best Fake News, go to the best source of it: Donald J. Trump.

See http://www.catwhisker.org/~david/publickey.gpg for my public key.


signature.asc
Description: PGP signature

DEFAULT_VERSIONS conflicts

2018-01-02 Thread Roger Marquis


Per the 20171214 UPDATING entry:

  Support for some deprecated variables is going to be removed soon. If
  you use any of the following constructs (usually in /etc/make.conf),
  you must switch to the new incantations:
  ...
  WITH_OPENSSL_BASE  DEFAULT_VERSIONS+= ssl=base
  WITH_OPENSSL_PORT  DEFAULT_VERSIONS+= ssl=port

Question is what occurrs when the port version is also specified:

  DEFAULT_VERSIONS+=ssl=libressl

Some builds report an error when both are specified depending on the
order of, for example:

  DEFAULT_VERSIONS+=ssl=libressl
  DEFAULT_VERSIONS+=ssl=port

Is there documentation on how to specify multiple port options?

Roger
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

lang/ghc -8.0.2_2 mismatched checksums

2018-01-02 Thread Mike Clarke


My daily periodic security run comes up with with these errors:

Checking for packages with mismatched checksums:
ghc-8.0.2_2: /usr/local/bin/haddock
ghc-8.0.2_2: /usr/local/lib/ghc-8.0.2/package.conf.d/package.cache
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-33.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-36.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-43.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-46.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-58.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-60.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-61.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-62.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-92.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-A.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-All.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-B.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-C.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-D.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-E.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-F.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-G.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-H.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-I.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-J.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-K.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-L.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-M.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-N.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-O.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-P.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Q.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-R.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-S.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-T.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-U.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-V.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-W.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Y.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/doc-index-Z.html
ghc-8.0.2_2: /usr/local/share/doc/ghc-8.0.2/html/libraries/index.html

-- End of security output --

I've reinstalled the package but still get the errors.

curlew:/home/mike% pkg info  ghc  
ghc-8.0.2_2
Name   : ghc
Version: 8.0.2_2
Installed on   : Mon Jan  1 09:35:19 2018 GMT
Origin : lang/ghc
Architecture   : FreeBSD:11:amd64
Prefix : /usr/local
Categories : haskell lang
Licenses   : BSD3CLAUSE
Maintainer : hask...@freebsd.org
WWW: http://www.haskell.org/ghc/
Comment: Compiler for the functional language Haskell
Options:
BOOT   : off
BOOTH  : off
DOCS   : on
DYNAMIC: on
PROFILE: on
Shared Libs required:
libgmp.so.10
libiconv.so.2
libcharset.so.1
Shared Libs provided:
libHSrts_thr-ghc8.0.2.so
libHSrts-ghc8.0.2.so
libHSfilepath-1.4.1.1-ghc8.0.2.so
libHSghc-boot-th-8.0.2-ghc8.0.2.so
libffi.so.6
libHSghc-prim-0.5.0.0-ghc8.0.2.so
libHSCabal-1.24.2.0-ghc8.0.2.so
libHSrts_thr_debug-ghc8.0.2.so
libHSrts_debug-ghc8.0.2.so
libHSpretty-1.1.3.3-ghc8.0.2.so
libHSarray-0.5.1.1-ghc8.0.2.so
libHStransformers-0.5.2.0-ghc8.0.2.so
libHShoopl-3.10.2.1-ghc8.0.2.so
libHShpc-0.6.0.3-ghc8.0.2.so
libHSghc-boot-8.0.2-ghc8.0.2.so
libHStemplate-haskell-2.11.1.0-ghc8.0.2.so
libHSghc-8.0.2-ghc8.0.2.so
libHSbinary-0.8.3.0-ghc8.0.2.so
libHSghci-8.0.2-ghc8.0.2.so
libHSdirectory-1.3.0.0-ghc8.0.2.so
libHShaskeline-0.7.3.0-ghc8.0.2.so
libHSunix-2.7.2.1-ghc8.0.2.so
libHStime-1.6.0.1-ghc8.0.2.so
libHSrts_l-ghc8.0.2.so
libHSprocess-1.4.3.0-ghc8.0.2.so
libHSbytestring-0.10.8.1-ghc8.0.2.so
libHSrts_thr_l-ghc8.0.2.so
libHSdeepseq-1.4.2.0-ghc8.0.2.so
libHSinteger-gmp-1.0.0.1-ghc8.0.2.so
libHScontainers-0.5.7.1-ghc8.0.2.so
libHSterminfo-0.4.0.2-ghc8.0.2.so
libHSbase-4.9.1.0-ghc8.0.2.so

Re: Creating patch files, skip post-patch

2018-01-02 Thread Matthias Fechner

Am 02.01.2018 um 10:19 schrieb Jan Beich:
> Try do-patch e.g.,
>
>   $ make clean extract do-patch makepatch EXTRA_PATCHES= BATCH=

thanks a lot Jan!


Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Thanks!

2018-01-02 Thread Torfinn Ingolfsen

On Mon, Jan 1, 2018 at 7:52 PM, George Mitchell  wrote:
> On 01/01/18 13:33, Jos Chrispijn wrote:
>> I would like to thank all programmers and port maintainers for their
>> excellent work in 2017.
>> Without you we would never enjoy BSD as we do until this very day.
>>
>> I really hope that you will keep up the good work in 2018 also!
>>
>> Thanks,
>> Jos Chrispijn
>> [...]
>
> And an enthusiastic second from me!  Especially because portmaster
> has been revived and I can still keep up with security updates.

Hear, hear!
The work done by everyone who works on FreeBSD and the ports
collection (and the rest of it) is very much appreciated!

May 2018 be a great year for everyone!
-- 
Regards,
Torfinn Ingolfsen
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Creating patch files, skip post-patch

2018-01-02 Thread Jan Beich

Matthias Fechner  writes:

> Dear all,
>
> I have some ports I maintain and in some of them I have
> post-patch-{{OPTION}}-on Makefile targets in that is patching files.
> But to update the files I need a file where only the patches from
> files/patch-* are applied.
>
> Is there a possibility to skip the post-patch target from the Makefile
> so I can do:
>
> make patch (without post-patch from Makefile)
> modify the files
> make makepatch

Try do-patch e.g.,

  $ make clean extract do-patch makepatch EXTRA_PATCHES= BATCH=
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Creating patch files, skip post-patch

2018-01-02 Thread Matthias Fechner

Dear all,

I have some ports I maintain and in some of them I have
post-patch-{{OPTION}}-on Makefile targets in that is patching files.
But to update the files I need a file where only the patches from
files/patch-* are applied.

Is there a possibility to skip the post-patch target from the Makefile
so I can do:

make patch (without post-patch from Makefile)
modify the files
make makepatch

Thanks a lot.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: lang/ghc -8.0.2_2 mismatched checksums

Re: I've started getting ^@^@> in my xterms w/mutt

mail/phpmailer abandoned?

Re: Ports with binary bootstrap packages and CURRENT+ino64

I've started getting ^@^@> in my xterms w/mutt

Re: mail/mutt && security/gnupg (after gnupg20 -> gnupg) weirdness

Re: DEFAULT_VERSIONS conflicts

Re: DEFAULT_VERSIONS conflicts

mail/mutt && security/gnupg (after gnupg20 -> gnupg) weirdness

DEFAULT_VERSIONS conflicts

lang/ghc -8.0.2_2 mismatched checksums

Re: Creating patch files, skip post-patch

Re: Thanks!

Re: Creating patch files, skip post-patch

Creating patch files, skip post-patch

15 matches

Site Navigation

Mail list logo

Footer information