Github messages for voidlinux
 help / color / mirror / Atom feed
From: p-kraszewski <p-kraszewski@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Current live-DVD's won't update due to mozjs.so switch
Date: Wed, 17 Feb 2021 06:50:13 +0100	[thread overview]
Message-ID: <20210217055013.F8BKdGdTH_x-wF_vQnreI86Xy0zm2u1MDfiVdSZJmTw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28779@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 886 bytes --]

New comment by p-kraszewski on void-packages repository

https://github.com/void-linux/void-packages/issues/28779#issuecomment-780316947

Comment:
@powerelastic Yes, for me `xbps-install` was globally broken, too. Fortunately, being trained on Gentoo I knew the drill :)

@ericonr Is there any info, what **exactly** `removed-packages.xbps` is and how it interacts with system? Assuming your workaround does what _I mean_ it does (that is updates some sort of explicit package blacklist), it might be relatively safe to include a flag in `xbps-install` to temporarily disable `removed-packages` parsing altogether. 

I see 2 problems here: 
* there might be a better error message indicating, that installed software depends on package marked for hard-removal and a hint for your workaround.
* there might be a bug in dependency resolving algorithm causing the early termination.

  parent reply	other threads:[~2021-02-17  5:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 12:36 [ISSUE] " p-kraszewski
2021-02-17  0:44 ` powerelastic
2021-02-17  0:48 ` powerelastic
2021-02-17  1:14 ` ericonr
2021-02-17  5:47 ` p-kraszewski
2021-02-17  5:50 ` p-kraszewski [this message]
2021-02-17  5:51 ` p-kraszewski
2021-02-17  7:40 ` Chocimier
2021-02-17  8:16 ` p-kraszewski
2021-02-17  9:39 ` p-kraszewski
2021-02-17 10:00 ` p-kraszewski
2021-02-17 14:53 ` powerelastic
2021-02-17 19:18 ` [ISSUE] [CLOSED] " Chocimier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210217055013.F8BKdGdTH_x-wF_vQnreI86Xy0zm2u1MDfiVdSZJmTw@z \
    --to=p-kraszewski@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).