unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: 30345@debbugs.gnu.org
Subject: bug#30345: guix refreh --type=kde does not update all KF5 packages
Date: Sun, 4 Feb 2018 14:56:32 +0100	[thread overview]
Message-ID: <27ba96a9-4963-dc78-f7bf-e83f0f0f6881@crazy-compilers.com> (raw)

Hi,

I'm again experiencing issues with "guix refresh" and KDE packages:

./pre-inst-env guix refresh --update --type=kde

does not update

* kirigami: the archive is named "kirigami2-*"

  For this, I thought there is some way to tweak guix, but I did not
find it in the manual.

* kdelibs4suport and all other "porting Aids" living in the
sub-directory "/portingAids"

This is like bugs [25020] and [29071]. 25020 says,
026f6a42b680207a59beadf0b0b9cc1753f55605 should solve part of the issue,
but if you look at the second line for the "guix refresh" output in
[#31], you can see that it does not handle the sub-directory

[25020] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25020
[29071] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=29071
[#31] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=25020#31

-- 

Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

             reply	other threads:[~2018-02-04 13:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04 13:56 Hartmut Goebel [this message]
2018-02-04 15:37 ` bug#30345: Other KDE updates are not working, too Hartmut Goebel
2018-02-05 11:16 ` bug#30345: guix refreh --type=kde does not update all KF5 packages Ludovic Courtès
2018-02-05 11:21 ` Ludovic Courtès
     [not found] ` <handler.30345.B.151775261618436.ack@debbugs.gnu.org>
2019-09-10 17:11   ` bug#30345: Acknowledgement (guix refreh --type=kde does not update all KF5 packages) Hartmut Goebel

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

  List information: https://guix.gnu.org/

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

  git send-email \
    --in-reply-to=27ba96a9-4963-dc78-f7bf-e83f0f0f6881@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=30345@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).