all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: 27468@debbugs.gnu.org
Subject: [bug#27468] Acknowledgement ([PATCH] gnu: Add linkchecker.)
Date: Wed, 23 Aug 2017 05:04:09 +0530	[thread overview]
Message-ID: <d7ec322e.AEAAOxXVZ3oAAAAAAAAAAAPNQHwAAAACwQwAAAAAAAW9WABZnL-B@mailjet.com> (raw)
In-Reply-To: <2307d2c7.AEQAMFHh1HMAAAAAAAAAAAPNQHwAAAACwQwAAAAAAAW9WABZTbIA@mailjet.com>


This package seems to have fallen through the cracks. I just sent a new
patch made against the latest master.

> This package has bundled dependencies -- dnspython and miniboa -- under
> "third_party/". They have been modified as described in
> third_party/dnspython/changelog.txt and
> third_party/miniboa-r42/CHANGES.txt respectively. Should I unbundle
> these dependencies? If so, how do I handle the fact that the bundled
> dependencies have been locally modified?

I have raised the issue of unbundling with upstream. But, there has been
no response after 10 days.

https://github.com/wummel/linkchecker/issues/729

I recommend we don't unbundle anything on our own, and let upstream do
their homework. WDYT?

  reply	other threads:[~2017-08-22 23:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-24  0:17 [bug#27468] [PATCH] gnu: Add linkchecker Arun Isaac
     [not found] ` <handler.27468.B.149826350831000.ack@debbugs.gnu.org>
2017-06-24  0:27   ` [bug#27468] Acknowledgement ([PATCH] gnu: Add linkchecker.) Arun Isaac
2017-08-22 23:34     ` Arun Isaac [this message]
2017-08-23  0:10       ` Marius Bakke
2017-08-22 23:30 ` [bug#27468] [PATCH] gnu: Add linkchecker Arun Isaac
2017-08-23  0:02   ` Marius Bakke
2017-08-23  7:26     ` Arun Isaac
2017-08-23  7:33       ` Arun Isaac
     [not found]     ` <4a4f0a8d.AEEAPL4o3uEAAAAAAAAAAAPFd4cAAAACwQwAAAAAAAW9WABZnS4m@mailjet.com>
2017-08-24 17:43       ` Marius Bakke
2017-08-26  7:41         ` Arun Isaac
2017-08-30  7:29         ` bug#27468: " Arun Isaac

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=d7ec322e.AEAAOxXVZ3oAAAAAAAAAAAPNQHwAAAACwQwAAAAAAAW9WABZnL-B@mailjet.com \
    --to=arunisaac@systemreboot.net \
    --cc=27468@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 external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.