On Mon, Nov 2, 2020 at 12:02 AM Felix Yan wrote:
>
> ibus 1.5.23+1+gdd4cc5b0-1 has been pushed into [testing]. Sorry for the
> delay.
Excellent, thank you! I just installed ibus 1.5.23 from [testing] and
it is working great.
-Alex
Eli,
> The files should definitely be owned, though... I suspect your issue
> is due to upgrading the pacman version, resulting in some files that
> could not be deleted due to not existing, but were not part of the new
> package and therefore did not exist afterward either.
thanks. in theory
Yash,
i (according to the pacman log) explicitly installed npm-check-updates.
(i've just now removed it; i think i installed it when i was initially
flailing around, trying to understand the npm-verse.)
in terms of arch packages, the arch package page
On 11/4/20 1:03 PM, Greg Minshall via arch-general wrote:
> this is just a status update, mostly for anyone in the future who might
> find this useful for their problem. but, if anyone in the near-present
> has any comment, i'm happy. (and, i appreciate all the help up to now!)
>
> presumably
On 11/4/20 12:03 PM, Greg Minshall via arch-general wrote:
> (145/192) upgrading npm-check-updates
>
Did you explicitly install npm-check-updates or was it a dependency of
something else?
>
> .../rc/package.json shows a dependency on minimist.
Looks like npm-check-updates depends on
this is just a status update, mostly for anyone in the future who might
find this useful for their problem. but, if anyone in the near-present
has any comment, i'm happy. (and, i appreciate all the help up to now!)
presumably this is all fallout from some historic "npm update -g".
way too many
thanks, Nick and Maarten. i guess all paths include some trepidation on
my part.
Nick -- i think it's a good assumption i *did* do some sort of "npm
... -g" action.
i've often wondered how distributions (arch and others) deal with users
of R, (now) npm, etc., doing a system-wide install of
On Wed, 4 Nov 2020 at 15:17, Nick Shvelidze via arch-general <
arch-general@archlinux.org> wrote:
> I think running `pacman -Syu --overwrite '/usr/lib/node_modules/*'` is
> safe.
> I have no idea how those files would end up there without using `sudo
> npm install -g`
>
It would be good to also
I think running `pacman -Syu --overwrite '/usr/lib/node_modules/*'` is safe.
I have no idea how those files would end up there without using `sudo
npm install -g`
On Wed, Nov 4, 2020 at 11:56 AM Greg Minshall via arch-general
wrote:
>
> hi. [hope all are well, etc.]
>
> i use the npm package
hi, Toni,
thanks for the question. actually, i don't know, but if i bothered to
sudo, it would have been to do -g (global). do you know (maybe it's a
stupid, "well, duh!", question...) if, in that case, my system would
become "un-pacman'able"? especially, in such as way as i've described.
Hi Greg
> first off, i wonder if anyone has ideas of how i ended up in this
> situation? i know that occasionally npm will exclaim, with enthusiasm,
> that a new, updated version, is available, and offer me a chance to
> update it. normally i don't run as root. but, if i had, in the past,
>
hi. [hope all are well, etc.]
i use the npm package (for managing javascript packages).
today i tried "pacman -Syu", and i got a number of errors about files
under /usr/lib/node_modules/npm/node_modules that "exists in
filesystem":
(182/182) checking for file conflicts
error: failed to
12 matches
Mail list logo
