| One of my packages failed the mass rebuild, but only on ppc64le and
aarch64. The error they both hit is this:
Error: package or namespace load failed for 'BiocParallel' in
dyn.load(file, DLLpath = DLLpath, ...):
unable to load shared object
'/builddir/build/BUILDROOT/R-BiocParallel-1.16.5-1.
Tom Callaway wrote on 2019/02/07 3:39:
One of my packages failed the mass rebuild, but only on ppc64le and
aarch64. The error they both hit is this:
Error: package or namespace load failed for 'BiocParallel' in
dyn.load(file, DLLpath = DLLpath, ...):
unable to load shared object
'/builddir/bui
Alexander Ploumistos wrote:
> Hello,
>
> While ironing out the kinks in the upcoming version of Molsketch with
> the upstream developer, we noticed that we weren't seeing the same
> dialogs. He is on KDE (OpenSuSE) and I was testing in GNOME and MATE.
> Molsketch has an option to save a single mo
On Wed, 2019-02-06 at 13:59 -0800, Adam Williamson wrote:
> On Wed, 2019-02-06 at 16:44 -0500, Przemek Klosowski wrote:
> > On 2/6/19 4:17 PM, Adam Williamson wrote:
> > > Rawhide isn't really utterly broken: a GTK+ change broke lots of openQA
> > > needles (screenshots) so the tests are failing. I
On Wed, 2019-02-06 at 16:44 -0500, Przemek Klosowski wrote:
> On 2/6/19 4:17 PM, Adam Williamson wrote:
> > Rawhide isn't really utterly broken: a GTK+ change broke lots of openQA
> > needles (screenshots) so the tests are failing. I'm in the middle of
> > re-taking all those now, and will re-run t
On 2/6/19 4:17 PM, Adam Williamson wrote:
Rawhide isn't really utterly broken: a GTK+ change broke lots of openQA
needles (screenshots) so the tests are failing. I'm in the middle of
re-taking all those now, and will re-run the tests on prod when it's
done, and send a new compose check report.
On Wednesday, 06 February 2019 at 19:39, Tom Callaway wrote:
> One of my packages failed the mass rebuild, but only on ppc64le and
> aarch64. The error they both hit is this:
>
> Error: package or namespace load failed for 'BiocParallel' in
> dyn.load(file, DLLpath = DLLpath, ...):
> unable to lo
On Wednesday, 06 February 2019 at 20:37, Kevin Fenzi wrote:
> On 2/6/19 9:07 AM, Vít Ondruch wrote:
> > Dne 06. 02. 19 v 17:58 Kevin Fenzi napsal(a):
[...]
> >> Our autosigning machine seems to have a failed tpm in it, which has
> >> caused signing to fail to work. ;(
> >>
> >> We are working on ge
On Tue, 2019-02-05 at 13:01 +, Fedora compose checker wrote:
> No missing expected images.
>
> Compose FAILS proposed Rawhide gating check!
> 22 of 47 required tests failed, 21 results missing
> openQA tests matching unsatisfied gating requirements shown with **GATING**
> below
>
> Failed op
Am Mittwoch, den 06.02.2019, 15:04 +0100 schrieb Miro Hrončok:
> Hi,
>
> due to https://fedoraproject.org/wiki/Changes/Python_Extension_Flags
> it is no
> longer correct to just call `python3 setup.py build` or `python3
> setup.py
> build_ext` in spec without setting the proper flags (for arched
On 2/6/19 11:49 AM, Chris Murphy wrote:
> On Wed, Feb 6, 2019 at 9:59 AM Kevin Fenzi wrote:
>>
>> On 2/6/19 7:23 AM, Vít Ondruch wrote:
>>>
>>> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
On 2/5/19 3:50 AM, Peter Robinson wrote:
>> There seems to be an issue with moving builds over. Eve
On Wed, Feb 6, 2019 at 9:59 AM Kevin Fenzi wrote:
>
> On 2/6/19 7:23 AM, Vít Ondruch wrote:
> >
> > Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
> >> On 2/5/19 3:50 AM, Peter Robinson wrote:
> There seems to be an issue with moving builds over. Everything seems to
> be stuck in f30-pen
On 2/6/19 9:07 AM, Vít Ondruch wrote:
>
> Dne 06. 02. 19 v 17:58 Kevin Fenzi napsal(a):
>> On 2/6/19 7:23 AM, Vít Ondruch wrote:
>>> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
On 2/5/19 3:50 AM, Peter Robinson wrote:
>> There seems to be an issue with moving builds over. Everything see
On Wed, 2019-02-06 at 08:58 -0800, Kevin Fenzi wrote:
> This is really a anoying time for hardware to die, but of course
> sometimes it seems like it _knows_ when that is so it can fail.
This is the beginning of the rise of the machines.
signature.asc
Description: This is a digitally signed mess
Hello,
While ironing out the kinks in the upcoming version of Molsketch with
the upstream developer, we noticed that we weren't seeing the same
dialogs. He is on KDE (OpenSuSE) and I was testing in GNOME and MATE.
Molsketch has an option to save a single molecule/structure with the
.msk extension.
One of my packages failed the mass rebuild, but only on ppc64le and
aarch64. The error they both hit is this:
Error: package or namespace load failed for 'BiocParallel' in
dyn.load(file, DLLpath = DLLpath, ...):
unable to load shared object
'/builddir/build/BUILDROOT/R-BiocParallel-1.16.5-1.fc30.
Samuel Rakitničan wrote:
> Got via e-mail that libdxflib's ABI changed in comparison to previous
> release, yet nothing changed in the package except version bump for the mass
> rebuild. Why is that?
I got similar mails about mysql++ – type changes that seem to consist
entirely of "type size has
On Wed, 6 Feb 2019 at 11:15, Vít Ondruch wrote:
>
>
> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
>
> On 2/5/19 3:50 AM, Peter Robinson wrote:
>
> There seems to be an issue with moving builds over. Everything seems to be
> stuck in f30-pending and not getting tagged with f30.
>
> That'll be th
Dne 06. 02. 19 v 17:58 Kevin Fenzi napsal(a):
> On 2/6/19 7:23 AM, Vít Ondruch wrote:
>> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
>>> On 2/5/19 3:50 AM, Peter Robinson wrote:
> There seems to be an issue with moving builds over. Everything seems to
> be stuck in f30-pending and not g
On Wed, 2019-02-06 at 14:37 +, Richard W.M. Jones wrote:
> On Mon, Feb 04, 2019 at 09:26:00PM +0100, Miro Hrončok wrote:
> > avgtime (maintained by: rjones)
> > avgtime-0.5.1-0.17.git20150501.fc30.src requires ldc =
> > 1:1.12.0-2.fc30
>
> Hopefully fixed in avgtime-0.5.1-0.19.
On 2/6/19 7:23 AM, Vít Ondruch wrote:
>
> Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
>> On 2/5/19 3:50 AM, Peter Robinson wrote:
There seems to be an issue with moving builds over. Everything seems to be
stuck in f30-pending and not getting tagged with f30.
>>> That'll be the signing
On Wed, Feb 6, 2019 at 5:11 AM Miroslav Suchý wrote:
>
> Dne 06. 02. 19 v 1:47 Christoph Junghans napsal(a):
> > Is there a good way (qemu or something) to debug this interactively?
>
> https://github.com/rpm-software-management/mock/wiki/Feature-forcearch
Thanks, "mock -r epel-7-ppc64le --forcear
On 06. 02. 19 16:24, Richard Shaw wrote:
Just commited option 1 to Rawhide for python-pivy
Is it needed for other releases?
Not needed. But also not dangerous.
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lis
Just commited option 1 to Rawhide for python-pivy
Is it needed for other releases?
Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https:
Dne 05. 02. 19 v 21:19 Kevin Fenzi napsal(a):
> On 2/5/19 3:50 AM, Peter Robinson wrote:
>>> There seems to be an issue with moving builds over. Everything seems to be
>>> stuck in f30-pending and not getting tagged with f30.
>> That'll be the signing queue
> Yeah, it wasn't processing these corr
On 06/02/2019 14:45, Richard W.M. Jones wrote:
https://koji.fedoraproject.org/koji/taskinfo?taskID=32577327
This says it's failing because:
DEBUG util.py:490: BUILDSTDERR: - nothing provides
ocaml(Migrate_parsetree_driver) = 296ee343a6c2118db57c2ee01f0e5e88 needed by
ocaml-ppx-tools-versio
On Wed, Feb 06, 2019 at 02:45:54PM +, Richard W.M. Jones wrote:
> https://koji.fedoraproject.org/koji/taskinfo?taskID=32577327
>
> This says it's failing because:
>
> DEBUG util.py:490: BUILDSTDERR: - nothing provides
> ocaml(Migrate_parsetree_driver) = 296ee343a6c2118db57c2ee01f0e5e88 ne
On Wed, 6 Feb 2019 at 04:50, Miro Hrončok wrote:
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for
> sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraprojec
https://koji.fedoraproject.org/koji/taskinfo?taskID=32577327
This says it's failing because:
DEBUG util.py:490: BUILDSTDERR: - nothing provides
ocaml(Migrate_parsetree_driver) = 296ee343a6c2118db57c2ee01f0e5e88 needed by
ocaml-ppx-tools-versioned-5.2-1.fc29.x86_64
But that's because it's us
On Mon, Feb 04, 2019 at 09:26:00PM +0100, Miro Hrončok wrote:
> avgtime (maintained by: rjones)
> avgtime-0.5.1-0.17.git20150501.fc30.src requires ldc =
> 1:1.12.0-2.fc30
Hopefully fixed in avgtime-0.5.1-0.19.git20150501.fc30.
Rich.
--
Richard Jones, Virtualization Group, R
Hi,
due to https://fedoraproject.org/wiki/Changes/Python_Extension_Flags it is no
longer correct to just call `python3 setup.py build` or `python3 setup.py
build_ext` in spec without setting the proper flags (for arched builds with
Python extension modules at least).
That is without setting
Dne 06. 02. 19 v 1:47 Christoph Junghans napsal(a):
> Is there a good way (qemu or something) to debug this interactively?
https://github.com/rpm-software-management/mock/wiki/Feature-forcearch
Miroslav
___
devel mailing list -- devel@lists.fedoraprojec
Hi Everyone,
Happy to announce that Transtats[1] (v0.1.6) is now deployed in
production[2].
Please follow quick writeup[3] for getting started.
Changelog is here:
https://github.com/transtats/transtats/blob/master/CHANGELOG.md
And contribution guide:
https://github.com/transtats/transtats/blob/ma
Il 2/5/19 6:16 PM, Miro Hrončok ha scritto:
>
> I've used dnf repoquery to check what requires python2-libiptcdata, instead of
> checking what requires libiptcdata.
>
> That would be:
>
>* rawtherapee
>* tracker-miners
>* gstreamer(1)-plugins-bad-free
>
> So apparently, I broke this. My
Hello Chris,
On Wed, Feb 6, 2019 at 5:28 AM Chris Murphy wrote:
>
> https://fedoraproject.org/wiki/Changes/BootLoaderSpecByDefault
>
> I want this change to succeed but I'm experiencing a regression, and
> while trying to troubleshoot it I'm finding it difficult to understand
> the myriad differe
35 matches
Mail list logo
