I have seen an earlier attempt to add lvm support to guixsd.
I would like to know the status of lvm support, and willing to assist with
it.
This is updated version of patch following guidelines more closely. Please
ignore previous.
2017-02-07 0:13 GMT+01:00 Boskovits, Gábor :
> * gnu/packages/lshw.scm: New file.
> ---
> gnu/packages/lshw.scm | 34 ++
> 1 file changed, 34
I would like to get some suggestion about which category this package
belongs to.
2017-02-06 18:21 GMT+01:00 Boskovits, Gábor :
> ---
> gnu/packages/lshw.scm | 34 ++
> 1 file changed, 34 insertions(+)
> create mode 100644
Hello!
Sorry for my english!
This will be the my first contribution, so i hope all went well.
I would like to get some assistance in selecting a category for this
package.
Should it be networking, or something else?
I would be glad if someone could also verify if my licese selection is
Hello!
#1 A post on the list cought my attention regarding security of packages
with both server and client. I think that should also apply to this package.
I am waiting for follow ups on that.
#2 I have discussed the licensing issues with Thomas Danckaert, but waiting
for confirmation wether the
/hexedit.scm
@@ -1,5 +1,6 @@
;;; GNU Guix --- Functional package management for GNU
;;; Copyright © 2016 Kei Kebreau <k...@openmailbox.org>
+;;; Copyright © 2017 Gábor Boskovits <boskov...@gmail.com>
;;;
;;; This file is part of GNU Guix.
;;;
@@ -44,3 +45,23 @@ file can be a device as the
Sorry, wrong address.
I also have a question reqarding this package.
This package uses minilzo. I guess it can stay that way. If I should take
it out, please let me know.
2017-06-23 18:13 GMT+02:00 Gábor Boskovits <boskov...@gmail.com>:
> * gnu/packages/hexedit.scm (ht): New
Ok, I just made a branch, basically only changing that single line in
java.scm.
It's base on current core-updates.
You can clone from: https://github.com/Boskovits/guix.git
branch: change-default-icedtea-8.
How do we know where you need further assistance with that?
As first step it is not
Hello!
I just run a quick grep to see which files might be interesting.
We use ant-build-system in:
axoloti.scm *
bioinformatics.scm *
compression.scm *
icu4c.scm
java.scm *
libusb.scm *
music.scm *
textutlis.scm
uml.scm *
version-control.scm *
web.scm *
xml.scm
Only the ant-build system uses
Hello!
It seems, that one of the source of the reporoducibilty issues with the gcc
build output is that it contains la files with libdir recorded.
Libtool records that in those la files.
I wonder if we have any solution to that already, because it seems to
affect every project using libtool.
If
Boskovits <boskov...@gmail.com>:
> I just pushed what I have right now. It's on branch gcc-ddc on my github.
> Should I post a patch here?
>
> 2017-11-21 0:16 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
>
>> The only problematic one seems to be standard_libexec
executable_checksum in cc1 and
cc1plus still differ. No other differences remained.
I'm now investigating the checksum issue.
2017-11-23 12:23 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Hello!
>
> It seems, that one of the source of the reporoducibilty issues with the
>
Oops, I missed one. we have libstdc++.so.6.0.17-gdb.py, which is similar
to the first two cases above, records installation diretory, in source
form, I don't think we have to fix that either.
2017-11-29 10:43 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Hello!
>
> It se
,
checkpoints and bootstraps.
Also with java9 coming we should be prepared to do another iteration on
this, and a cleaner sturcture might make that easier.
2017-11-29 8:12 GMT+01:00 Chris Marusich <cmmarus...@gmail.com>:
> Chris Marusich <cmmarus...@gmail.com> writes:
>
> >
It seems, that the libtool file differences leak into the checksum.
I will try to contact developers on how to bypass that issue.
2017-11-29 16:57 GMT+01:00 Jan Nieuwenhuizen <jann...@gnu.org>:
> Gábor Boskovits writes:
>
> > It seems, that I can make really good progress here
I agree with this.
I would add a few more to the list of states I would like to see managed in
some standard way.
One of these is hardware state, for example do some automated action if a
raid array degrades, or a disk removed/added...
Another on that would be great to have is some way to manage
2017-12-03 22:46 GMT+01:00 Chris Marusich <cmmarus...@gmail.com>:
> Gábor Boskovits <boskov...@gmail.com> writes:
>
> > Any news on this icu4c thing?
>
> After about 2 days of running git bisect, my computer has informed me
> that the first bad commit is 67d527e
It seems, that the fix is already included in the 60.1 release for the
xlocal problem. I think we can ignore that.
2017-12-03 23:20 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> It seems, that they issued that already:
> http://bugs.icu-project.org/trac/changeset/40603
>
>
we do something about this.
2017-12-03 23:04 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> I've found that simply reverting the update to icu4c 60 commit brings up
> the issue you just mentioned, with missing xlocale.h.
> So it seems, that the one you found introduced the
It seems, that they issued that already:
http://bugs.icu-project.org/trac/changeset/40603
2017-12-03 23:08 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Ok, I found this one:
> https://sourceware.org/glibc/wiki/Release/2.26#Removal_of_.27xlocale.h.27
>
> It seems, tha
status: 1
This is the log.
2017-12-04 20:15 GMT+01:00 Leo Famulari <l...@famulari.name>:
> On Mon, Dec 04, 2017 at 04:44:00PM +0100, Gábor Boskovits wrote:
> > Now that this problem around glibc is resolved, I think I will do some
> > history rewrite, so that these reverts,
Hello!
I've just checked the current build status of packages on hyrda. I could
filter out a few that currently seems not to build anyway, we might try to
fix those first.
I'll send a quick list:
*java-htsjdk@1.129 -> newer version (2.3.0) in master, does not build;
java-testng@6.12
I'll have a look at testng.
2017-12-13 3:06 GMT+01:00 Chris Marusich <cmmarus...@gmail.com>:
> Gábor Boskovits <boskov...@gmail.com> writes:
>
> > I will wait for your results for now...
>
> I apologize for the delay. It took 20 hours to build the "covering&q
error: download from '
https://mirror.hydra.gnu.org/guix/nar/2i6pbhjlwzjcjpfd1jjv67hwg98ms6nw-java-testng-6.12.tar.gz'
failed: 504, "Gateway Time-out"
I get this for java-testng.
It seems reproducible.
2017-12-13 10:59 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> java-o
ich wrote:
> > Gábor Boskovits <boskov...@gmail.com> writes:
> >
> > > I will wait for your results for now...
> >
>
> >
> > * kodi@18.0_alpha-7-67fd70f: failed because of "potential infinite
> > recursion"; also it seems that it's
clojure ok
2017-12-13 9:53 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> I'll have a look at testng.
>
> 2017-12-13 3:06 GMT+01:00 Chris Marusich <cmmarus...@gmail.com>:
>
>> Gábor Boskovits <boskov...@gmail.com> writes:
>>
>> > I will
java-osgi-service-jdbc ok
2017-12-13 10:54 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> clojure ok
>
> 2017-12-13 9:53 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
>
>> I'll have a look at testng.
>>
>> 2017-12-13 3:06 GMT+01:00 Chris Mar
2017-12-17 19:59 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Yes, we could do that, however, I would prefer to fix these if we can.
>
>
> 2017-12-17 15:26 GMT+01:00 Ricardo Wurmus <rek...@elephly.net>:
>
>>
>> Gábor Boskovits <boskov...@gmail.com&g
Ok, it seems, that java-asm does not currently uses test anyway, so I can
remove the junit native input.
Will check if it is also true on master...
2017-12-15 14:52 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> I've found the problem with java-hamcrest-core.
> Th
-(native-inputs
- `(("java-junit" ,java-junit)))
(home-page "http://asm.ow2.org/;)
(synopsis "Very small and fast Java bytecode manipulation framework")
(description "ASM is an all purpose Java bytecode manipulation and
2017-12-15 15:21
.
WDYT?
2017-12-13 23:50 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> I've built the whole covering on my wip-change-default-java8 branch.
> The covering is 42 packages.
> 19 builds fine.
> 19 does not build because java-hamcrest-core does not build.
> I'll have
rness.")
(native-inputs
`(("jdk" ,icedtea-7 "jdk")
+(define-public ant ant/java7)
+
(define-public ant-apache-bcel
(package
(inherit ant/java8)
2017-12-13 12:07 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Hello!
>
> It was getting qu
r-seurat is ok.
2017-12-12 17:57 GMT+01:00 Chris Marusich :
> Chris Marusich writes:
>
> > Now that things are hopefully fixed up a bit more in core-updates I am
> > trying again to build the "covering" of icedtea to see what still needs
> > to be
hamcrest-core 1.3 fails.
Exception in thread "main" java.lang.NoClassDefFoundError:
org/hamcrest/generator/qdox/JavaDocBuilder
2017-12-12 23:49 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> r-seurat is ok.
>
> 2017-12-12 17:57 GMT+01:00 Chris Marusich <cmmar
2017-12-19 10:11 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
>
>
> 2017-12-19 9:07 GMT+01:00 Chris Marusich <cmmarus...@gmail.com>:
>
>> Hi Gábor and Ricardo,
>>
>> I see that Gábor made this GitHub issue to track their work:
>>
2017-12-19 23:11 GMT+01:00 Ricardo Wurmus <rek...@elephly.net>:
>
> Gábor Boskovits <boskov...@gmail.com> writes:
>
> > Now I have another blocking issue:
> > https://github.com/Boskovits/guix/issues/24
>
> > Error message:
> >
> > BUILD FAI
2017-12-20 11:34 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> 2017-12-19 23:11 GMT+01:00 Ricardo Wurmus <rek...@elephly.net>:
>
>>
>> Gábor Boskovits <boskov...@gmail.com> writes:
>>
>> > Now I have another blocking issue:
>> &g
I wait
> until after Gábor pushes the fix(es) for java-hamcrest-core, so we can
> build the covering of icedtea-8 after that and see what still breaks?
>
>
I'm quite near to get a fix for java-hamcrest-core. Only java-jarjar has to
be modified now, so I think you can wait until I get
between java7 and java8 definition of Map,
affecting multiple projects.
I will focus on fixing that for now, and file a bug upstream.
2017-12-15 15:33 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> It seems, that it is aslo safe to apply this on master.
> This is the pat
Yes, we could do that, however, I would prefer to fix these if we can.
2017-12-17 15:26 GMT+01:00 Ricardo Wurmus <rek...@elephly.net>:
>
> Gábor Boskovits <boskov...@gmail.com> writes:
>
> > Currently I cannot compile java-aqute-bndlib,
> > because java-classp
/Boskovits/guix/issues/16
2017-12-13 19:04 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> The patches I made:
>
> This is the trivial:
>
> From f53ad84059786e0769a21a3a90a15189bcf2d61f Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?G=C3=A1bor=20Boskovits?= <boskov...@gmail.com&g
.
In gcc/gcc.c this pattern is guarded by if(gcc_exec_prefix) basically.(it
is in an else block)
It is not so in gcc/gcc-ar.c.
This is how far I could get with it by now.
2017-11-20 23:14 GMT+01:00 Ricardo Wurmus <rek...@elephly.net>:
>
> Jan Nieuwenhuizen <jann...@gnu.org> w
We had a discussion about that on the irc channel, and it seems, that we
can make a boostrap path to another architecture by using a bootstrapped
toolchain and cross compiling. It is not very confortable, but I think we
can extend the list of bootstrappable software considerably by that.
The wrapper approach eliminated those three, we still have in prefix.c the
prefix used as static initializer. I have to investigate further, but it's
only 300 lines, should be tractable.
2017-11-21 0:16 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> The only problematic
I just pushed what I have right now. It's on branch gcc-ddc on my github.
Should I post a patch here?
2017-11-21 0:16 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> The only problematic one seems to be standard_libexec_prefix, because that
> is used in line 3654 of gcc/gcc
Yesteday we had a discussion about that on irc.
Here it goes:
[15:15:16] hello guix!
[15:16:01] do we have a proposed way to build pyc files
reproducibly?
[15:16:50] I've read in the report, that we are not there yet, but
is someone working on it?
[15:17:58] g_bor: This is the report you
Ok, I think we should try the patch the bytecode complier way.
WDYT?
Rekado mentioned that setting the times would be an easier way to go, but
breaks some tests...
I guess they were also discussing options on irc.
You are right, backporting does not seem to be a good option here.
Regarding
I have seen, that several package definitions add write permissions to
files in the build.
I just had a package, where this issue came up. (python-networkx2)
The first issue I had was that in the build log the filenames were
truncated in the stacktrace.
Do we have any mean to avoid that? It
start up a few vm-s with guixsd, and have
those involved in rebuilding if needed...
2017-12-08 7:55 GMT+01:00 Chris Marusich <cmmarus...@gmail.com>:
> Gábor Boskovits <boskov...@gmail.com> writes:
>
> > sra-tools2.8.2-1 builds with no problem.
>
> Now that things are
sra-tools2.8.2-1 builds with no problem.
2017-12-07 18:50 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Hello!
>
> The gtk+ patch is now in core-updates.
>
>
> 2017-12-05 8:07 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
>
>>
I don't know what we are currently doing to get the installer iso image
sized down, but I caught some discussion yesterday on irc, that the image
is actually very well compressible, and checking the sizes it really is.
Might that be possible to do something like compressing the root filesystem
Sometimes while working in guix I run into problems because:
1. a tarball was removed or modified upstream
It would be great to have the ability to install the latest release in all
the supported ways on all supported architectures, and have the ability do
guix pull without problems.
Last time I
I agree with that.
It would however mean additional metadata on the packages.
If there is consent, that this is a good idea, we could find out what
additional information is needed, and how to integrate that.
It could be done like test, or strip-binaries...
Then if we have the current behaviour as
when I compile with clang. The differences
are the same, so we can do this. The rest is just "cosmetics".
2017-12-02 15:48 GMT+01:00 Jan Nieuwenhuizen <jann...@gnu.org>:
> Gábor Boskovits writes:
>
> > Aside from these libtool files we can now say, that this ddc p
, that this package is not
recommended for general use.
WDYT?
2017-11-30 15:32 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> It seems, that the libtool file differences leak into the checksum.
> I will try to contact developers on how to bypass that issue.
>
>
> 2017-11-2
: FUNC ARGS, \
long double: FUNC ## l ARGS, \
_Float128: FUNC ## f128 ARGS)
2017-12-03 23:25 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> It seems, that the fix is already included in the 60.1 release for the
> xlocal problem. I
_SELECTION 0
#endif
This does not seem right.
We should not have this defined when compiling c++.
WDYT?
2017-12-04 13:03 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> This minimal file reproduces the problem in icu4c 60.1 in guix environment
> icu4c on current core-updates.
>
>
DC_VERSION__ >= 201112L))
# define __HAVE_GENERIC_SELECTION 1
#else
# define __HAVE_GENERIC_SELECTION 0
2017-12-04 13:21 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> We also have this in bits/floatn.h, but this seems right.
>
> #if (defined __x86_64__
I think the problem is caused by HAVE_GENERIC_SELECTION defined when we are
in C++.
2017-12-04 13:18 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> We have this in cdefs.h:
> #if __GNUC_PREREQ (4, 9) \
> || __glibc_clang_has_extension (c_generic_selections) \
> ||
Upstream corrected the issue in commit
6913ad65e00bb32417ad39c41d292b976171e27e.
It is not yet included in 2.26.
The patch is basically the same as I proposed.
I think we should get the upstream version.
2017-12-04 13:33 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> I think
Boskovits <boskov...@gmail.com>:
> Upstream corrected the issue in commit 6913ad65e00bb32417ad39c41d292b
> 976171e27e.
>
> It is not yet included in 2.26.
>
> The patch is basically the same as I proposed.
>
> I think we should get the upstream version.
>
> 2017-1
failure in the meanwhile. I'll
report back if I find something.
2017-12-02 8:06 GMT+01:00 Chris Marusich <cmmarus...@gmail.com>:
> Gábor Boskovits <boskov...@gmail.com> writes:
>
> > Hello!
> >
> > I've just checked the current build status of packages on
Ok, thanks for clarification.
I
2017-12-03 0:29 GMT+01:00 Leo Famulari <l...@famulari.name>:
> On Sat, Dec 02, 2017 at 05:28:51PM +0100, Gábor Boskovits wrote:
> > Sometimes while working in guix I run into problems because:
> > 1. a tarball was removed or modified upst
I was aware of the discussion thread, however I could not find out what the
current state is? Do we plan to modify this behaviour in the next release?
The core-updates thing makes sense, thanks.
2017-12-03 8:19 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Ok, thanks for clarifica
GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Ok, so it seems, that the latest glibc update was made to fix the icu4c
> thing.
> It just broke the locales.
> Fix for that has just been pushed, making core-updates usable again.
> I pushed to my icedtea branch also.
> I'
Hello!
The gtk+ patch is now in core-updates.
2017-12-05 8:07 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> FAIL: abicheck.sh
> PASS: pltcheck.sh
>
>
> Testsuite sum
8:01 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Ok, hopefully that will work out. However there was a hint yesterday, that
> newest core-updates is broken again after a recent merge...
> It might worth to have a look around to see if it's woth to do on an older
>
minced is ok.
2017-12-12 12:30 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Ok I've built ant 1.9.9 with ant/java8 and icedtea8. It is ok.
>
> 2017-12-10 16:56 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
>
>> I've seen package:
>> java-jgit-4
Ok I've built ant 1.9.9 with ant/java8 and icedtea8. It is ok.
2017-12-10 16:56 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> I've seen package:
> java-jgit-4.2 explicitly depending on icedtea-7
> other explicit dependencies are for:
> icedtea-7
> ant
>
> Thes
java-testng also dies on icu4c.
It seems like we will have to fix that first to do anything else.
2017-12-03 10:58 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Any news on this icu4c thing?
>
> We had a problem on core-updates, reverting
> ee3ebf1a357bd4eb36a2fa1790a7b5
now I'm trying to build sra-tools.
2017-12-04 17:34 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> New branch name is: change-default-icedtea-8-wip
> <https://github.com/Boskovits/guix/tree/change-default-icedtea-8-wip>
> I left the original intact, but that does not
ervlet@4.1
java-eclipse-jetty-servlet@9.2.22 java-eclipse-jetty-servlet@9.4.6
axoloti-patcher@1.0.12
2017-12-04 16:44 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Now that this problem around glibc is resolved, I think I will do some
> history rewrite, so that these reverts, re
2017-12-20 13:29 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> 2017-12-20 11:34 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
>
>> 2017-12-19 23:11 GMT+01:00 Ricardo Wurmus <rek...@elephly.net>:
>>
>>>
>>> Gábor Boskovits <boskov...
2018-05-13 20:45 GMT+02:00 Tatiana Sholokhova :
> Hi all,
>
> Thank you for your help and the provided resources which are very useful
> for me at the first stage of the project.
>
> I have built Cuirass on my local computer but I have encountered a few
> problems while
2018-05-20 11:40 GMT+02:00 Ricardo Wurmus :
>
> Hi Sahithi,
>
> >> While this achieves the goal for a single character it does not
> >> constitute a custom port. Have you read the documentation for
> >> “make-custom-port” in the Guile manual?
> >
> > I have tried with the
2018-05-15 10:57 GMT+02:00 Ludovic Courtès :
> Hi Pjotr,
>
> Pjotr Prins skribis:
>
> > So I have been using Icecate for 10 days. It is frustrating because it
> > does crash every other hour on some JS load. The error always looks like
> >
> > Extension
2018-06-11 14:14 GMT+02:00 Sahitihi :
> Hi Ricardo,
>
> > You should see the same as I did.
> This worked for me too.
> > To see what’s going on with your modifications to “(guix ui)” it would
> > help if you could go through your changes once more (use “git diff” to
> > be sure to inspect all
+1
2018-06-10 15:33 GMT+02:00 Christopher Lemmer Webber :
> Nils Gillmann writes:
>
> > Hi,
> >
> > I think it would be best if everyone involved would cool down for a
> couple of
> > days, restructure their thoughts and reflect on this thread. Look at what
> > they are doing, and at how they
2018-06-10 13:26 GMT+02:00 Thorsten Wilms :
> On 10.06.2018 11:54, Pierre Neidhardt wrote:
>
>> Then intention of the Arch post-install script is good (that is,
>> informing the user) but I find the implementation brittle: if the
>> messages are too many or too long, it can be very easy to miss a
>
>
>
Hello uniq10,
Thanks for letting us know!
I hope to see you again in the community when your issues
are resolved.
Best regards,
g_bor
2018-06-12 13:43 GMT+02:00 Fis Trivial :
>
> Jonathan Brielmaier writes:
>
> > Maybe you should use a different mail provider. Hotmail is known to have
> > sometimes issues like this.
> >
> > On 6/12/18 1:07 PM, Fis Trivial wrote:
> >>
> >> Fis Trivial writes:
> >>
> >>> Please help sending this
Ricardo Wurmus ezt írta (időpont: 2018. jún. 15., P
21:20):
>
> Hi Marius,
>
> > Now that 'core-updates' is merged, it's time to get 'staging' rolling
> > again. We have lots of minor updates this round, mostly on the
> > graphical side. Is there anything we're missing that's eligible (<1200
>
Ricardo Wurmus ezt írta (időpont: 2018. jún. 16., Szo
12:25):
>
> Hi Gábor,
>
> > Ricardo Wurmus ezt írta (időpont: 2018. jún. 15., P
> > 21:20):
> >
> >>
> >> Hi Marius,
> >>
> >> > Now that 'core-updates' is merged, it's time to get 'staging' rolling
> >> > again. We have lots of minor
2018-06-16 12:58 GMT+02:00 Gábor Boskovits :
>
>
> Ricardo Wurmus ezt írta (időpont: 2018. jún. 16.,
> Szo 12:25):
>
>>
>> Hi Gábor,
>>
>> > Ricardo Wurmus ezt írta (időpont: 2018. jún. 15.,
>> P
>> > 21:20):
>> >
>> >&g
2018-06-13 0:43 GMT+02:00 Tatiana Sholokhova :
> Hello,
>
> Thank you for your reviews!
>
> I've just fixed codestyle issues and replaced HTML5 preamble with XHTML.
>
>
> respond-static-file: We should not second-guess the VFS layer. Checking
>> for ".." gives an illusion of security when in
Joshua Branson ezt írta (időpont: 2018. jún. 13.,
Sze 15:52):
> Tatiana Sholokhova writes:
>
> > Hello,
> >
> > Thank you for your reviews!
> >
> > I've just fixed codestyle issues and replaced HTML5 preamble with XHTML.
>
> Just cause I'm curious, why XHTML instead HTML5? Is XHTML better to
Ricardo Wurmus ezt írta (időpont: 2018. jún. 19., K,
0:17):
> Hi Guix,
>
> I wrote almost 6 days ago:
>
> > Here are a bunch of things that we should look into:
> >
> > * Outstanding patches. There are many patches in the queue at
> > guix-patches[1] that we should go through, comment on,
2018-05-26 23:20 GMT+02:00 Ricardo Wurmus :
>
> Hi Sahithi,
>
> > I went wrong in squashing. Please check the current attachment.
>
> Thank you.
>
> I’ve made a couple of minor changes and pushed it to the branch
> “wip-sahithi”.
Nice, so now here is a branch where we can
2018-06-02 18:46 GMT+02:00 Nils Gillmann :
> Hi Jeremiah,
>
> jerem...@pdp10.guru transcribed 946 bytes:
> > As running make clean breaks the bootstrap script.
> > I propose we leverage git's shallow clones (git clone --depth 1 $URL)
> > and include the .git directory with the repo such that we
2018-05-29 18:07 GMT+02:00 Ludovic Courtès :
> Hello Tatiana & all,
>
> Ricardo Wurmus skribis:
>
> >> I am a bit confused about the database structure. As far as I
> understand,
> >> there are project_name (project) and branch_name (jobset) properties,
> but
> >> project_name is a primary key,
Mark H Weaver ezt írta (időpont: 2018. júl. 2., H, 6:58):
> Ricardo Wurmus writes:
>
> > git takes a very long time to build, because it has an extensive test
> > suite. Most of the time is spent in running the SVN interoperability
> > tests, though, which are not really all that interesting
Hello, could you please send us an update on your project?
Can you please send us an update on your project?
Ricardo Wurmus ezt írta (időpont: 2018. jún. 25., H
22:29):
>
> Hi Sahithi,
>
> > I think I am done with basic changes for 4th task. File is attached. As
> > mentioned in IRC output is in escape code sequence when I tried in REPL.
>
> Great. Please change ui.scm directly and send a patch that
Ricardo Wurmus ezt írta (időpont: 2018. júl. 1., V,
1:20):
> Hi Guix,
>
> git takes a very long time to build, because it has an extensive test
> suite. Most of the time is spent in running the SVN interoperability
> tests, though, which are not really all that interesting for most uses
> of
Actually we still have a couple of build failures, some test failures, and
the
commit messages are not conformant to the policy. Currently making the few
remainig
failures work should be the primary task. I will check the details.
I already have an integration branch where I reorder commits and
2018-01-06 21:16 GMT+01:00 Gábor Boskovits <boskov...@gmail.com>:
> Actually we still have a couple of build failures, some test failures, and
> the
> commit messages are not conformant to the policy. Currently making the few
> remainig
> failures work should be the prima
2018-01-07 18:25 GMT+01:00 Ricardo Wurmus <rek...@elephly.net>:
>
> Gábor Boskovits <boskov...@gmail.com> writes:
>
> > https://github.com/Boskovits/guix/issues/58
> …
> > What I don't understand, is why setting source and target to 1.7,
> > like I did on
2018-01-05 16:44 GMT+01:00 Ricardo Wurmus <rek...@elephly.net>:
>
> Gábor Boskovits <boskov...@gmail.com> writes:
>
> > If I understand well, then the check phase in ant-build-system
> > runs without make-flags.
> > In the definition of java-asm we
I don't believe that making a microcode update available makes the situation
worse. An earlier version is a non-free component of the system anyway.
I believe, that it might well worth to provide the possibility to update it.
I think it would be beneficial, if we got a singned blob for that,
1 - 100 of 524 matches
Mail list logo