pacman output for archhaskell packages

When (re)installing ArchHaskell packages, pacman produces some unusual and typically uninformative output compared to for non-haskell packages. I mean, things like: Reading package info from stdin ... done. and, worse, there is often an "error" when upgrading a package "command failed to execute correctly", which appears to be harmless but is confronting nevertheless. Would it be possible to engineer the ArchHaskell PKGBUILDs so as to suppress these messages?

On 8 May 2015 at 05:01, Ramana Kumar
When (re)installing ArchHaskell packages, pacman produces some unusual and typically uninformative output compared to for non-haskell packages.
I mean, things like: Reading package info from stdin ... done.
and, worse, there is often an "error" when upgrading a package "command failed to execute correctly", which appears to be harmless but is confronting nevertheless.
Would it be possible to engineer the ArchHaskell PKGBUILDs so as to suppress these messages?
A fairly recent change to `cblrepo`[1] should take care of the "Reading package..." bit. I have opted to not spend the hours necessary to rebuild all packages, instead all added and updated packages will be more silent. When the next version of ghc comes out all packages will be quieter. I'd really like to get a reliable way to reproduce the second issue, so I can see what changes to the install script that's necessary to deal with it. /M [1]: http://is.gd/s26Bd9 -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

On 8 May 2015 at 07:11, Magnus Therning
A fairly recent change to `cblrepo`[1] should take care of the "Reading package..." bit. I have opted to not spend the hours necessary to rebuild all packages, instead all added and updated packages will be more silent. When the next version of ghc comes out all packages will be quieter.
Awesome! Thanks.
I'd really like to get a reliable way to reproduce the second issue, so I can see what changes to the install script that's necessary to deal with it.
When I next come across it I'll try to isolate it.
/M
[1]: http://is.gd/s26Bd9
-- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus

On 8 May 2015 at 08:48, Ramana Kumar
On 8 May 2015 at 07:11, Magnus Therning
wrote: A fairly recent change to `cblrepo`[1] should take care of the "Reading package..." bit. I have opted to not spend the hours necessary to rebuild all packages, instead all added and updated packages will be more silent. When the next version of ghc comes out all packages will be quieter.
Awesome! Thanks.
Yeah, it's been irritating me for a long time too, so I decided to actually do something about it :) /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: magnus@therning.org jabber: magnus@therning.org twitter: magthe http://therning.org/magnus
participants (2)
-
Magnus Therning
-
Ramana Kumar