| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Submitted-by: Ilya Mochalov <chrootsu@gmail.com>
Closes: https://bugs.gentoo.org/636776
Closes: https://github.com/gentoo/gentoo/pull/6709
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
|
|
| |
Reported-by: nomadictype@tutanota.com
Closes: https://bugs.gentoo.org/645524
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
|
|
|
|
|
|
| |
This wasn't actually enabling SWT in the build as providing the jar
location actually disables it. There is no other way to provide the
jar location so enabling SWT simply breaks the build. The latest
version probably handles this better but no one cares about this
package.
Package-Manager: Portage-2.3.20, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
Package implements (as it says):
"guile bindings of git"
Bug: https://bugs.gentoo.org/644866
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
|
|
|
|
| |
Package implements (as it says):
"Structured access to bytevector contents."
Bug: https://bugs.gentoo.org/644866
Package-Manager: Portage-2.3.19, Repoman-2.3.6
|
|
|
|
| |
Closes: #6866
|
|
|
|
| |
Closes:#6766
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
|
| |
Submitted-by: eroen <gentoo@eroen.eu>
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
| |
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/614966
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
|
|
|
|
| |
Package-Manager: Portage-2.3.16, Repoman-2.3.6
Closes: https://github.com/gentoo/gentoo/pull/6385
|
| |
|
|
|
|
|
| |
Closes: https://bugs.gentoo.org/613986
Package-Manager: Portage-2.3.13, Repoman-2.3.3
|
| |
|
| |
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.16, Repoman-2.3.6
|
|
|
|
| |
Package-Manager: Portage-2.3.13, Repoman-2.3.4
|
| |
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
|
|
| |
Submitted-by: Guillaume LE VAILLANT <glv@posteo.net>
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.2
|
|
|
|
| |
Package-Manager: Portage-2.3.6, Repoman-2.3.1
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This new ebuild comes with a lot of fixes:
1. Dropped the unused eutils eclass.
2. Updated the LICENSE to LGPL-3 from LGPL-2 (upstream change). I've
also included GPL-3+ in there, because I see some plain-GPLed code
in the source tree.
3. Added some missing dependencies, and a comment mentioning why
they're needed. This includes pango per bug 486016.
4. Added a blocker on dev-tex/slatex to avoid file collisions. This
is bug 547398, and the solution isn't entirely satisfactory, so
I've left a comment explaining what I know.
5. Added --disable-strip to the configure flags to avoid some QA
warnings.
6. Changed a few "make" commands that are used with USE=jit, to
ensure that two executables are pax-marked before they're
used. Along with some commands to pax-mark the installed
binaries, this fixes bug 613634.
7. Removed the *.desktop file DESTDIR mangling; it looks like
whatever problem this solved has been fixed upstream.
However, this new ebuild comes with one new problem:
1. The build randomly crashes with racketcgc segfaults. This seems
to only happen with USE=jit. I've filed a bug upstream at
http://bugs.racket-lang.org/query/?cmd=view&pr=15433, but even
changing the GC doesn't appear to fix it. I get a different
backtrace, but it's always racketcgc that segfaults. I'm not
sure what to do about this (mask the "jit" flag?), so this
new ebuild is committed package.masked.
Gentoo-Bug: 486016
Gentoo-Bug: 547398
Gentoo-Bug: 613634
Gentoo-Bug: 613918
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: portage-2.3.3
|
| |
|
|
|
|
|
|
| |
Gentoo-Bug: 613758
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Closes:#4304
|
|
|
|
|
|
| |
Submitted-by: Bill Six <billsix@gmail.com>
Package-Manager: portage-2.3.0
|
|
|
|
| |
Signed-off-by: Robin H. Johnson <robbat2@gentoo.org>
|
| |
|
|
|
|
|
|
|
| |
guile-snarf should be fixed upstream as it's a sensitive
and brittle sed script.
This reverts commit aa3c28baa056846ebd14dfbb48058b91018188fd.
|
|
|
|
|
|
|
|
|
|
|
|
| |
guile-snarf uses cpp to get rid of comments, #defines
and type declarations in C code. But in -ggdb3 mode gcc
leaves all of them in the output.
The workaround is to downgrade -ggdb3 down to -ggdb2.
Bug: https://bugs.gentoo.org/608190
Package-Manager: Portage-2.3.3, Repoman-2.3.1
|
|
|
|
| |
Package-Manager: portage-2.3.0
|