Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#54571 - Haskell updates, registering modules that don't exist

Attached to Project: Community Packages
Opened by storrgie (storrgie) - Saturday, 24 June 2017, 14:43 GMT
Last edited by Doug Newgard (Scimmia) - Tuesday, 04 July 2017, 15:23 GMT
Task Type General Gripe
Category Upstream Bugs
Status Closed
Assigned To No-one
Architecture All
Severity Very Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description: Haskell updates triggered registration of modules, spews many "doesn't exist (ignoring)" messages to the terminal.


Additional info:

https://gist.githubusercontent.com/storrgie/8fced892ca23273bf72db035301b6ce0/raw/ce26e1169a32ceb389507c222fd477290881a8d7/gistfile1.txt


Steps to reproduce:

I've not tested on other systems that have the same package set yet, just a report for awareness in case others see something similar.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Tuesday, 04 July 2017, 15:23 GMT
Reason for closing:  Not a bug
Comment by Daniel M. Capella (polyzen) - Saturday, 24 June 2017, 17:50 GMT
In future issues, please make sure not to include the use of an AUR helper as they are unsupported and may complicate investigations.
Comment by storrgie (storrgie) - Saturday, 24 June 2017, 18:02 GMT
Understood, above I'm not reporting against packages in the AUR or pacaur itself though.
Comment by Daniel M. Capella (polyzen) - Saturday, 24 June 2017, 18:14 GMT
That may be the case, but one would have to sort through all those (108) packages to find that out.
Comment by storrgie (storrgie) - Saturday, 24 June 2017, 18:30 GMT
Well, I can understand not having familiarity with pacauar because its unsupported, but if you look at the output the pacaur portion is at the very end and updates no packages:

```
:: Starting AUR upgrade...
:: pass-netconf is not present in AUR -- skipping
there is nothing to do
```
Comment by Daniel M. Capella (polyzen) - Saturday, 24 June 2017, 18:39 GMT
I see.
Comment by storrgie (storrgie) - Saturday, 24 June 2017, 18:44 GMT
Right, I should have been running pacman to do the system update but I was being a bit lazy. I've got two other systems that have a similar package set that I plan to test with (but are at the office so have to wait until next week).
Comment by Daniel M. Capella (polyzen) - Saturday, 24 June 2017, 18:45 GMT
I imagine the packager/s is/are aware of this. Foxboron told me others have been reporting this, and I have reproduced it myself.
Comment by Doug Newgard (Scimmia) - Tuesday, 27 June 2017, 16:47 GMT
So these are modules from outside the official repos? Looks normal to me.
Comment by Daniel M. Capella (polyzen) - Wednesday, 28 June 2017, 18:07 GMT
Doug, this is with packages/modules from the repos.
Comment by Felix Yan (felixonmars) - Friday, 30 June 2017, 19:48 GMT
The reason for the message is that the package list passed to pacman hooks are not in their installation/uninstallation order.

Since "--force" was always passed to the script this should be fine.

Loading...