public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Packages up for grabs: dev-python/pycxx, dev-python/pysvn
Date: Sun, 06 Oct 2019 13:05:50 +0200	[thread overview]
Message-ID: <0fb7e581b97877bf7a017a3718e30e754472322b.camel@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 546 bytes --]

Hi,

The following packages are now up for grabs:

dev-python/pycxx
dev-python/pysvn

pysvn is used by two packages.  pycxx is only used by pysvn.

Both need version bumps, and are awful to maintain.  While pycxx is only
used by pysvn, we needed to hack it to make pysvn build it in the first
place.  It'd really nice if someone could take a deeper look at what's
wrong there and give both ebuilds a major cleanup.

pysvn has also test failure reported.  pycxx's ebuild doesn't have
tests.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

                 reply	other threads:[~2019-10-06 11:06 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=0fb7e581b97877bf7a017a3718e30e754472322b.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox