public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: dotnet@gentoo.org
Subject: [gentoo-dev] Important problems to maintain gtk-sharp ebuilds in their current splitted way
Date: Sun, 04 Mar 2012 14:09:55 +0100	[thread overview]
Message-ID: <1330866595.10135.56.camel@belkin4> (raw)

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

Hello

We (dotnet team) are having a lot of problems to get gtk-sharp packages
updated and fixed. All started time ago when we were unable to bump it
due:
https://bugs.gentoo.org/show_bug.cgi?id=382491

Now, a new important bug has appeared and we are lose about what is
wrong and why has it broken recently:
https://bugs.gentoo.org/show_bug.cgi?id=404139

Any help with this is appreciated, if nobody can help us, we will
probably move back to monolithic gtk-sharp ebuild and hope that also
helps to fix bug #404139

Thanks a lot for your help

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

                 reply	other threads:[~2012-03-04 13:10 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=1330866595.10135.56.camel@belkin4 \
    --to=pacho@gentoo.org \
    --cc=dotnet@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