Mark H Weaver writes:
> Here's the declaration of QChar::byteOrderMark from qtools/qstring.h,
> included in the doxygen tarball:
>
> class Q_EXPORT Q_PACKED QChar {
> public:
> QChar();
> QChar( char c );
> QChar( uchar c );
> QChar( uchar c, uchar r );
> QChar( const QChar& c
It looks like this may be fixed in upstream commit
cee22450ee30e79952f594796721dc6b17798ee6 [0], which has not ended up in a
release. I have not verified yet, but it looks like commit would address
the problem.
[0]
https://github.com/haskell/haskell-mode/commit/cee22450ee30e79952f594796721dc
Hi, first of all, thanks for the improvement. It's really exciting know
progress in guix.
But I have a few questions around this change. Just curiosity. :)
> Hello Guix!
>
> Here is the “new” ‘guix pull’ that we discussed notably in this thread:
>
> https://bugs.gnu.org/22629
>
> The major dif
I'm running guix (GNU Guix) 19b662ea7c53a28270a783f10ca033d8c9d2a954, and
have /gnu/store/s32nba6rxx9x2kibsn6wsm1ixzhv64nl-emacs-26.1 installed.
When I then try to install haskell-mode with
guix package -i haskell-mode
the derivation build fails with
haskell-process.el:160:1:Error: Unused
2018-06-05 14:45 GMT+02:00 Leo Famulari :
> On Tue, Jun 05, 2018 at 01:49:12PM +0200, Gábor Boskovits wrote:
> > Do you think we can do something like rebuild icedtea3 with icedtea3, and
> > then rewrite the references? I guess this way the dependency loop could
> be
> > broken, as we could detach
Julien Lepiller writes:
> Le 2018-06-05 12:52, Ricardo Wurmus a écrit:
>> The package java-bouncycastle has a failing test suite on core-updates.
>> After the first test fails there is no more progress and the build
>> eventually times out.
>>
>> I have disabled the test suite for now, but we s
On Tue, Jun 05, 2018 at 01:49:12PM +0200, Gábor Boskovits wrote:
> Do you think we can do something like rebuild icedtea3 with icedtea3, and
> then rewrite the references? I guess this way the dependency loop could be
> broken, as we could detach the last icedtea3 build from the packages used
> for
Do you think we can do something like rebuild icedtea3 with icedtea3, and
then rewrite the references? I guess this way the dependency loop could be
broken, as we could detach the last icedtea3 build from the packages used
for bootstrapping.
We could even make on more rebuilding, if necessary. WDYT
Hi Ludo,
>> Just wondering: does this mean that I could substitute Guix from my local
>> source tree simply by doing
>>
>>./pre-inst-env guix package -p ~/.config/guix/current -i guix
>
> That would just install the snapshot that the ‘guix’ package refers to
> (it’s defined in (gnu packages pa
Le 2018-06-05 12:52, Ricardo Wurmus a écrit :
The package java-bouncycastle has a failing test suite on core-updates.
After the first test fails there is no more progress and the build
eventually times out.
I have disabled the test suite for now, but we should try to fix this.
The failing test
The “generate-jar-indices” phase fails on a couple of packages, such as
java-picard (all variants)
dropseq-tools
java-cisd-jhdf5
The errors are either about duplicates as in java-picard-2.10.3:
duplicate entry: htsjdk/samtools/AbstractBAMFileIndex$1.class
or about missing files as in
The package java-bouncycastle has a failing test suite on core-updates.
After the first test fails there is no more progress and the build
eventually times out.
I have disabled the test suite for now, but we should try to fix this.
The failing test is “org.bouncycastle.mail.smime.test.AllTests”.
Many binaries of the icedtea-3 package contain references to icedtea-2,
which was used to build it. Because of these references users of
icedtea-3 have to *also* download icedtea-2. And because icedtea-2
contains references to icedtea-1, they *also* need to download that
version.
It is possible
13 matches
Mail list logo
