unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: Lakshmi Prasannakumar <lakshmiprasannakumaran@gmail.com>,
	33214@debbugs.gnu.org
Subject: [bug#33214] Video Documentation for GNU GUIX (an Outreachy project)
Date: Fri, 2 Nov 2018 15:23:04 +0100	[thread overview]
Message-ID: <CAE4v=phu1kOMVYFC2-Kus71wroXPxW5O1sY_TMuH2UsdSXDWvg@mail.gmail.com> (raw)
In-Reply-To: <20181102143154.555e711f@alma-ubu>

Björn Höfling <bjoern.hoefling@bjoernhoefling.de> ezt írta (időpont:
2018. nov. 2., P, 14:31):
>
> Hi Lakshmi,
>
> On Fri, 2 Nov 2018 18:25:49 +0530
> Lakshmi Prasannakumar <lakshmiprasannakumaran@gmail.com> wrote:
>
> > Sure, I'll rebase it to the current master and try to bring in the
> > change for commit message .
> >
> > Regards,
> >
>
> (For the reference, applied it on top of
> 7b63047c943a68717b1fc21dc078e44c2415e694 where it applies without trouble).
>
> I have some more remarks:
>
> * Could you please keep the bug-tracker on CC. In that way other people
> can follow the discussions and it is saved for later reference. That is
> especially useful if the patch gets forgotten and is only later being
> picked up again (though I don't think that will be the case here):
>
> 33214@debbugs.gnu.org
>
> * As Gabor already said, the period "." was missing. See other commit
> messages to get used to the strict rules.
>
> * License field should look like this:
>
>   (license license:gpl2+)))
>
> I.e. it is prefixed  by "license:". That is because in line 31 the
> license module was imported with that prefix:
>
>   #:use-module ((guix licenses) #:prefix license:)
>
> Some package modules use this syntax to prevent namespace pollution,
> others not.
>
> * Did you execute `guix lint` before submitting the patch? I have
> found some linter complaints:
>
> /home/bjoern/guix/guix/gnu/packages/cran.scm:6652:0: r-weights@1.0: sentences in description should be followed by two spaces; possible infractions at 197, 389
> /home/bjoern/guix/guix/gnu/packages/cran.scm:6652:0: r-weights@1.0: line 6671 is way too long (468 characters)
>
> * The first one just means what it says. That is because the
> descriptions use texinfo syntax and there are two spaces used.
>
> * The second can be solved by breaking long lines of the description
> before 80 characters. See how it was done in other packages above.
>
> * Homepage:
>
> gnu/packages/cran.scm:6652:0: r-weights@1.0: permanent redirect
> from http://cran.r-project.org/web/packages/weights
> to   http://cran.r-project.org/web/packages/weights/
>
> So please add a trailing "/" to the URL.
>
> Also could you use "https"? instead of just plain "http"? We use the
> encrypted URL wherever it is available.
>

Thanks Björn. It seems that currently Lakshmi has no working
guix, because of problems related to missing substiutes.

> * I'm currently trying to build it but that looks like it takes more
> time than usual because substitutes are missing. If anything goes
> wrong, I will report back. Did you try to build the package?
>
> Thank you,
>
> Björn

  reply	other threads:[~2018-11-02 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA+H0LRPUfE=LmSETuasan3bEjEkGPXRFoE5Qrd-9G8DYO8buTQ@mail.gmail.com>
     [not found] ` <20181029212738.75de1734@alma-ubu>
     [not found]   ` <CA+H0LRMuXJ9Ehsf0XmpUkvYpSccb4FHaieOaJaVD55T=wExR+Q@mail.gmail.com>
     [not found]     ` <CAE4v=pjXFW+BKmE8=Rvto+zFX0LvKb=SFWzhuHRqcm0LLP71CA@mail.gmail.com>
     [not found]       ` <CA+H0LROFhPkbcarAW+QqxrX0bfZW1F+o9XEigpM43jPHpVhJUA@mail.gmail.com>
     [not found]         ` <CA+H0LRN=N_ZoOZYjmFYR4fQtt1pyjTuV0+udreYutJkOuLqFtQ@mail.gmail.com>
     [not found]           ` <CAE4v=piSd5+PN-HRh2doenC_bHG6BXmzeK3sD9W5avA-xRYSzw@mail.gmail.com>
     [not found]             ` <CAE4v=phejzy7KDG5P3QdmOz4-7UJb50bScn0uhcrSWpDHQoGjw@mail.gmail.com>
     [not found]               ` <CAE4v=pge_rd-BKs6tfkZD96=5QSrjjG21VqX+sG5SgcWCBuHVw@mail.gmail.com>
     [not found]                 ` <CA+H0LRPq4nMAH0vdZjYcKakBCvDiFZf-C0C1JWXKHT3Ex+ZqsA@mail.gmail.com>
     [not found]                   ` <CA+H0LRPuwTtrh2d=TD+qtmUoibmLaAPCrjSSwZ=QBZv-8+8vZA@mail.gmail.com>
     [not found]                     ` <CAE4v=pjYyO26JxMthvUA0YPp2t2_XEpuuQaAkFU-zYuEdOLbcQ@mail.gmail.com>
     [not found]                       ` <CAE4v=pgsDnW6RkJfVcNFXcT_yB+ptht7BGJzBT4xeR2=ETg5bQ@mail.gmail.com>
     [not found]                         ` <CA+H0LRPnqd9AdH8C59ai74pm=1o9a92hFdJsuP-P-TasSof=SA@mail.gmail.com>
2018-11-02 13:31                           ` [bug#33214] Video Documentation for GNU GUIX (an Outreachy project) Björn Höfling
2018-11-02 14:23                             ` Gábor Boskovits [this message]
2018-11-02 16:29                               ` Björn Höfling
2018-11-02 19:16                                 ` Lakshmi Prasannakumar

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='CAE4v=phu1kOMVYFC2-Kus71wroXPxW5O1sY_TMuH2UsdSXDWvg@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=33214@debbugs.gnu.org \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=lakshmiprasannakumaran@gmail.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).