public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Felipe Ghellar <fghellar2@yahoo.com.br>
To: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] KDE 3.1 rc5 ebuilds
Date: Sun, 08 Dec 2002 18:21:24 -0200	[thread overview]
Message-ID: <3DF3A9C4.7060200@yahoo.com.br> (raw)
In-Reply-To: 200212081713.22252.danarmak@gentoo.org

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii; format=flowed, Size: 1107 bytes --]

I've found a small "bug":

The source tarball for kdelibs unpacks to

/var/tmp/portage/kdelibs-3.1_rc5/work/kdelibs-3.1rc5/

but the ebuild script expects it to be

/var/tmp/portage/kdelibs-3.1_rc5/work/kdelibs-3.1_rc5/

A "_" is missing. The same happens for kdebase, at least.




Dan Armak wrote:
> Hello everyone,
> 
> As you probably know by now, the kde 3.1 release has been delayed to January 
> due to security problems that need to be fixed (and the slow rate of work 
> during the holidays). See http://dot.kde.org/1039281841/ .
> 
> Meanwhile what was intended to be 3.1-final (and almost was) has been released 
> as 3.1 rc5. It's stable, but doesn't have the abovementioned security fixes 
> (and of course other fixes will accumulate in the 3.1 branch during the next 
> month too).
> 
> I'm committing rc5 ebuilds to portage.
> 

--
gentoo-dev@gentoo.org mailing list


_______________________________________________________________________
Busca Yahoo!
O melhor lugar para encontrar tudo o que você procura na Internet
http://br.busca.yahoo.com/

--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2002-12-08 20:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-08 15:13 [gentoo-dev] KDE 3.1 rc5 ebuilds Dan Armak
2002-12-08 19:47 ` Dan Armak
2002-12-08 20:21 ` Felipe Ghellar [this message]
2002-12-08 20:25   ` Felipe Ghellar

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=3DF3A9C4.7060200@yahoo.com.br \
    --to=fghellar2@yahoo.com.br \
    --cc=gentoo-dev@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