Github messages for voidlinux
 help / color / mirror / Atom feed
From: Chocimier <Chocimier@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 08:40:55 +0100	[thread overview]
Message-ID: <20210217074055.FLh_GYi5TRITV4kwxjpKRdJNoqTcyvFDq23HsPF8CIQ@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: 713 bytes --]

New comment by Chocimier on void-packages repository

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

Comment:
What's happening here is that when new xbps version is available (and there is newer than in images), xbps wants update itself in separate, small transaction other than updating rest of system. At the same time it adds all revdeps of xbps, being base-system, and all their dependencies (removed-packages between them) making transaction not small anymore and causing conflicts.

We could remove mozjs60 and mozjs52 from removed-packages for now if there are no file conflicts and updates will actually work, and try to make xbps' transaction smaller for longer term.

  parent reply	other threads:[~2021-02-17  7:40 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
2021-02-17  5:51 ` p-kraszewski
2021-02-17  7:40 ` Chocimier [this message]
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=20210217074055.FLh_GYi5TRITV4kwxjpKRdJNoqTcyvFDq23HsPF8CIQ@z \
    --to=chocimier@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).