unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: zimoun <zimon.toutoune@gmail.com>
To: Marius Bakke <mbakke@fastmail.com>
Cc: 41282@debbugs.gnu.org, Pierre Neidhardt <mail@ambrevar.xyz>
Subject: bug#41282: share/info/images/*.png broken
Date: Sat, 16 May 2020 16:03:35 +0200	[thread overview]
Message-ID: <CAJ3okZ2LC8d9BoUusPavb+VZr5dYdoTOD6zyb++42Km=BMwTfg@mail.gmail.com> (raw)
In-Reply-To: <87sgg1xzru.fsf@ambrevar.xyz>

Dear Marius,

I do not know if it is a bug or if I misconfigured something but some
images under 'share/info/images' are "broken" for some commits, as if
the font is missing.  Because it is 'png' files, it is not related on
the presence or absence of such fonts on my machine, I guess.  Or do I
misunderstand something?  And if it is, why for some commits it
displays nicely and other not.


When I run:

  guix pull --commit=2c8305d -p /tmp/good

then 'display /tmp/good/share/info/images/bootstrap-graph.png'
displays nicely.  However, when I run:

  guix pull --commit=afc46f2 -p /tmp/bad

'display /tmp/bad/share/info/images/bootstrap-graph.png' is not nice,
as if the font is missing.


Well, I suspect it comes from something related to the recent
'core-updates'.  To underline my point, I run this script:

--8<---------------cut here---------------start------------->8---
SRC=/tmp/guix/

MERGE=/tmp/check/merge
LEFT=/tmp/check/left
RIGHT=/tmp/check/right

mkdir -p $MERGE
mkdir -p $LEFT
mkdir -p $RIGHT

for merge in $(git -C $SRC \
                log 2c8305d..afc46f2 \
                --ancestry-path --merges \
                --format="%h")
do
    left=$(git -C $SRC log $merge --format="%p" -n1 | cut -f1 -d' ')
    right=$(git -C $SRC log $merge --format="%p" -n1 | cut -f2 -d' ')

    echo $merge
    guix pull --commit=$merge -p${MERGE}/$merge

    echo $left
    guix pull --commit=$left -p${LEFT}/$left

    echo $right
    guix pull --commit=$right -p${RIGHT}/$right
done
--8<---------------cut here---------------end--------------->8---

which basically pull all the commits corresponding to merges between
the "working" commit and the "broken" commit.  And pull the two parent
commits too.

Based on that, all the merged commits are "broken".  The image
'share/info/images/bootstrap-graph.png' displays uglily for the
commits:

4bdf4182fe
50e6c1bf2e
87a40d7203
8bf8cd9b85
c263cfdcde
f589cbc4dc

Then the "left" are all broken too, except the commit c81457a588.
All the "right" are ok, except the commit 23a59b180b.

Note that these two corresponds to the last core-updates merge:

    git log 4bdf4182fe --format="%h %p %n %s" -n1

as if they were switched.


Last, I have checked the commits:

35c43fcdbb
4ba425060a
45c137e30f
7b07852ddb
2676579dc8

which are the ones just next after the core-updates merge ones and
they appear displaying ugly.


If I misunderstand or misconfigure something, please tell me and I
could correct why I am seeing good images and bad images.
Otherwise, I do not have an idea why it should come from.


Best regards,
simon




      parent reply	other threads:[~2020-05-16 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 10:23 bug#41282: doc: dot graphs display square glyphs instead of letters Pierre Neidhardt
2020-05-15 10:50 ` Marius Bakke
2020-05-15 11:48   ` Pierre Neidhardt
2020-05-15 13:53     ` zimoun
2020-05-15 14:13       ` Pierre Neidhardt
2020-05-15 14:45         ` Pierre Neidhardt
2020-05-15 15:02           ` zimoun
2020-05-15 15:32             ` Pierre Neidhardt
2020-05-15 15:36               ` zimoun
2020-05-15 18:13                 ` zimoun
2020-05-16 14:03 ` zimoun [this message]

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='CAJ3okZ2LC8d9BoUusPavb+VZr5dYdoTOD6zyb++42Km=BMwTfg@mail.gmail.com' \
    --to=zimon.toutoune@gmail.com \
    --cc=41282@debbugs.gnu.org \
    --cc=mail@ambrevar.xyz \
    --cc=mbakke@fastmail.com \
    /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).