From: Ken Brown <kbrown@cornell.edu>
To: cygwin-apps@cygwin.com
Subject: Re: duplicate between packages
Date: Thu, 20 May 2021 12:26:04 -0400 [thread overview]
Message-ID: <5ea5b8e4-c2b9-5280-d4a4-f85d022b7b00@cornell.edu> (raw)
In-Reply-To: <a48da719-51cd-ea3d-6328-9b8ff94a5eab@gmail.com>
On 4/26/2021 11:45 PM, Marco Atzeri via Cygwin-apps wrote:
> Hi Maintainers,
>
> as I just found 2 of my packages colliding with same program name
>
> $ cygcheck -f /usr/bin/ncgen
> hdf4-4.2.15-3
> netcdf-4.8.0-2
>
> as one is much older than the other, the installation sequence
> can give some inconsistencies in the system.
>
> So I checked on my /etc/setup how many duplicates there are
> and it seems also other package has the same problem
> 2 usr/bin/pygmentex
This and the other pygmentex duplicates you found are due to a packaging error,
in which I included pygmentex in both texlive-collection-latexextra and
texlive-collection-mathscience. I've just fixed this with an update of
texlive-collection-mathscience.
> 2 usr/bin/t1ascii.exe
> 2 usr/bin/t1asm.exe
> 2 usr/bin/t1binary.exe
> 2 usr/bin/t1disasm.exe
> 2 usr/bin/t1mac.exe
> 2 usr/bin/t1unmac.exe
These are in t1utils as well as texlive. The t1utils package is currently
orphaned, and the upstream package is included in TeX Live
(https://ctan.org/pkg/t1utils?lang=en). So I'm inclined to ignore this for now.
If anyone ever wants to take over maintainership of t1utils, we can discuss
what to do.
> 2 usr/share/man/man1/pdfdetach.1.gz
> 2 usr/share/man/man1/pdffonts.1.gz
> 2 usr/share/man/man1/pdfimages.1.gz
> 2 usr/share/man/man1/pdfinfo.1.gz
> 2 usr/share/man/man1/pdftohtml.1.gz
> 2 usr/share/man/man1/pdftoppm.1.gz
> 2 usr/share/man/man1/pdftops.1.gz
> 2 usr/share/man/man1/pdftotext.1.gz
This is another packaging bug. The files are included in both xpdf and poppler,
but they should only be in poppler. I'll fix it when xpdf is next updated.
> 2 usr/share/texmf-dist/doc/generic/tex-ini-files/README.md
And another one. This is in both texlive-collection-basic and
texlive-collection-basic-doc. I'll fix it in the next update.
Ken
prev parent reply other threads:[~2021-05-20 16:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 3:45 Marco Atzeri
2021-05-01 21:48 ` Ken Brown
2021-05-02 1:47 ` duplicate between packages (libuninameslist) Lemures Lemniscati
2021-05-02 4:54 ` Marco Atzeri
2021-05-02 5:49 ` Achim Gratz
2021-05-04 17:13 ` duplicate between packages Jon Turney
2021-05-20 16:26 ` Ken Brown [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5ea5b8e4-c2b9-5280-d4a4-f85d022b7b00@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-apps@cygwin.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.
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).