Package Details: wordnet-common 3.1-8

Git Clone URL: https://aur.archlinux.org/wordnet.git (read-only, click to copy)
Package Base: wordnet
Description: An Electronic Lexical Database from Princeton University
Upstream URL: https://wordnet.princeton.edu/
Licenses: LicenseRef-custom
Submitter: None
Maintainer: envolution
Last Packager: envolution
Votes: 116
Popularity: 0.000064
First Submitted: 2007-01-12 20:32 (UTC)
Last Updated: 2024-12-04 02:01 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

respiranto commented on 2021-06-29 22:54 (UTC) (edited on 2021-06-29 22:56 (UTC) by respiranto)

Most patches are rather small.

I have read through all but the following (large ones):

  • 51_overflows_memcpy
  • 52_wordnet3.0_lib_search_c_memory_patch

The others I deem fine.

Possibly relevant patches:

  • security:

    • 50_CVE-2008-2149_buffer_overflows.patch
    • 51_overflows_memcpy.patch (large patch, by oCert)
    • 51_overflows.patch
    • 60_gcc-4.6.patch
      • incorrectly replaces printf(.) by puts(.) (newline added)
  • possibly security:

    • 52_wordnet3.0_lib_search_c_memory_patch
  • other bugs in code:

    • 30_src_grind.patch
      • the summary is wrong, this does fix two bugs
  • bugs in the data:

    • 20_adj.all_fix.patch
    • 20_verb.social_fix.patch
  • man pages:

    • 20_doc_man_wninput.patch - man page section names
    • 40_doc_man_fix_names.patch - man page NAMEs
    • 41_doc_man_fix_names.patch - man page formatting
  • other (likely unneeded):

    • 01_tcltk8.6.patch
      • i.a., adds -DUSE_INTERP_RESULT to Makefile.am
    • 20_include_wn.h.patch
    • 90_prevent_parallel_build.patch
      • @Stebalien Did you do something to make your PKGBUILD work with `-jN', N > 1?
      • Does not affect Makefile.am.

Stebalien commented on 2021-06-29 14:35 (UTC)

@respiranto any specific patches? Debian has a pretty terrible track record. They tend to:

  1. Run a bunch of static analyzers.
  2. Apply any suggested fixes without thinking.

(introducing security vulnerabilities in the process)

The few patches I sampled were things like "make this thing const".

respiranto commented on 2021-06-28 23:50 (UTC) (edited on 2021-06-28 23:50 (UTC) by respiranto)

I'd like to suggest using some of the patches provided by Debian [0], some of which address security issues. See also the dict-wn PKGBUILD [1] (which I just adapted to use the Debian patches).

[0] https://packages.debian.org/sid/wordnet

[1] https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=dict-wn

Stebalien commented on 2021-04-29 16:02 (UTC)

@ShahinSorkh

It should work now but I can't be sure because I don't know what your specific issue was. In the future, please include error messages when you report build failures.

ShahinSorkh commented on 2021-04-29 06:51 (UTC)

Fails on build

Stebalien commented on 2019-08-12 15:38 (UTC)

WilliamR, you can install artha from the AUR. As specified in the PKGBUILD, you'll need wordnet-common.

WilliamR commented on 2019-08-11 09:47 (UTC)

Artha has been one of my essential utilities on a deb-based system. Recently moved over to an arch-based system due to unresolved heating problems on a Dell running a distro based on Ubuntu. Artha informs that it needs Wordnet. As AUR has different versions of Wordnet, some guidance is needed as to which version or files are needed to get Artha to run. Is this possible at present or are changes needed to be made in the AUR?

Stebalien commented on 2019-04-18 17:45 (UTC)

@dkasak,

wordnet-common currently includes the database, library, and a bunch of manual pages.

It sounds like we need to move the dictionary (/usr/share/wordnet/dict) out of wordnet-common into a wordnet-dict-princeton package that provides wordnet-dict. Would that work for you?

dkasak commented on 2019-04-18 10:38 (UTC) (edited on 2019-04-18 10:41 (UTC) by dkasak)

I just added english-wordnet, which is a fork of the Princeton WordNet that is currently more actively maintained. They recently made the 2019 release and provide an archive with WordNet-compatible files.

I put wordnet-common in my package's provides field, but it currently won't work seamlessly if someone has wordnet-* installed because it is the name of the actual package and therefore I cannot also conflict on it.

It would be nice if this worked seamlessly so both databases could be used with wordnet-cli, wordnet-tk and others. Maybe wordnet-common could be made into a virtual package and the current package renamed to something like princeton-wordnet.

Thoughts?

Stebalien commented on 2018-09-26 18:54 (UTC)

doronbehar: I agree. I've split the package.