В Вск, 16/11/2008 в 21:13 +0100, Gilles Dartiguelongue пишет:
here is a list of packages gnome herd would like to get rid of since
no-one seem to take care of them and users are not so verbose about it
either:
* app-text/ggv https://bugs.gentoo.org/show_bug.cgi?id=223427
Upstream there was
В Вск, 16/11/2008 в 15:33 -0600, Ryan Hill пишет:
- FEATURES=test failures;
And what we are supposed to do if upstream states that tests are not
supposed to be ran on users systems and exists for package development
only? For
Peter Volkov a écrit :
В Вск, 16/11/2008 в 21:13 +0100, Gilles Dartiguelongue пишет:
here is a list of packages gnome herd would like to get rid of since
no-one seem to take care of them and users are not so verbose about it
either:
* app-text/ggv
dev-util/cvs2svn
If anyone wants it, please have at it. I haven't used it in 2 years.
On 11:27 Mon 17 Nov , Doug Goldstein wrote:
dev-util/cvs2svn
If anyone wants it, please have at it. I haven't used it in 2 years.
This is the tool I've been using for git conversions, FWIW, so I'll
maintain it as long as it's relevant there.
--
Thanks,
Donnie
Donnie Berkholz
Tobias Scherbaum [EMAIL PROTECTED] posted
[EMAIL PROTECTED], excerpted below, on Mon, 17
Nov 2008 19:08:39 +0100:
Process might be as easy
as CC'ing a arch-tinderbox on a bug, a script does parse the bug number
out of the mail being sent out and using gatt it catches the ebuild to
test,
Peter Alfredsen wrote:
I've given this some thought and I think I've been convinced that
dberkholz' position is probably the most tenable. If this is to be
done, we should do it in a documented Gentooish way. The problem with
going down the FEATURES road are two-fold:
1) What should the
I ask it here as a favour, please avoid using absolute paths in the
filenames of patched files. This mean avoid having stuff like
--- foobar/foo.c
+++ /tmp/foobar/foobar.c
This tends to break from time to time, and I had to fix at least three
packages since I started my treewide build for these
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This check was added to epatch all of a sudden breaking all working
patches in the tree, although defending those patches having absolute
paths, we as Java team had several bugs filed due to that. Maybe the
tree should be scanned for those and fixed.
Serkan Kaba [EMAIL PROTECTED] writes:
This check was added to epatch all of a sudden breaking all working
patches in the tree, although defending those patches having absolute
paths, we as Java team had several bugs filed due to that. Maybe the
tree should be scanned for those and fixed.
[EMAIL PROTECTED] (Diego 'Flameeyes' Pettenò) writes:
Fun, I didn't really notice it was an epatch specific code that failed,
I know it fails when the paths don't add up between systems and I
thought that was it.. Okay, I guess I'll get to fix the rest tonight
after Bones...
All the tree
On Mon, 2008-11-17 at 20:24 +0100, Diego 'Flameeyes' Pettenò wrote:
I ask it here as a favour, please avoid using absolute paths in the
filenames of patched files. This mean avoid having stuff like
--- foobar/foo.c
+++ /tmp/foobar/foobar.c
This tends to break from time to time, and I had
On Mon, 17 Nov 2008 10:10:57 -0500
Daniel Gryniewicz [EMAIL PROTECTED] wrote:
On Sun, 2008-11-16 at 18:38 -0600, Ryan Hill wrote:
snip
The maintainer MUST NOT NEVER EVER NOT EVEN A LITTLE BIT remove the
latest stable ebuild of an arch without the approval of the arch
team or he/she
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mart Raudsepp yazmış:
On Mon, 2008-11-17 at 20:24 +0100, Diego 'Flameeyes' Pettenò wrote:
I ask it here as a favour, please avoid using absolute paths in the
filenames of patched files. This mean avoid having stuff like
--- foobar/foo.c
+++
14 matches
Mail list logo
