On Sunday, February 3, 2019 9:45:06 PM CET Neal Gompa wrote:
> Would it be possible to extend COPR to support multiple locations for
> builders? For example, in addition to an OpenStack system, builders
> could be hosted on an oVirt system, or AWS, or GCP, and so on? That way
> it can support
On Wed, Feb 06, 2019 at 12:51:54AM +, Tom Hughes wrote:
> On 06/02/2019 00:47, Christoph Junghans wrote:
>
> >While packaging up votca-csg-1.5, I ran into some tests failing:
> >https://github.com/votca/csg/issues/326
> >but this only happens on ppc64le under epel7. (So I expect boost-1.53
>
On 2/6/19 02:27, Kevin Fenzi wrote:
On 2/5/19 3:36 PM, Kalev Lember wrote:
Is there any chance releng could figure out the list of packages
affected once the signing/tagging is finished and fix all of them? I can
already tell that it's affecting at least 40-50 GNOME builds done in
that time
It’s finally happening!
https://pagure.io/389-ds-base/pull-request/50202
--
Sincerely,
William
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to 389-devel-le...@lists.fedoraproject.org
Fedora Code of
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 differences:
- I can't find the code. I assume all of it is in grub as blscfg.mod
Hi all,
Sagemath 8.6 is out, which means that at long last we can upgrade the
gap package. Upgrading gap means dealing with the fact that some of
the fundamental group libraries have now been split out of the main
package and have their own upstream repositories. That means that I
need reviews
https://fedorapeople.org/groups/389ds/ci/nightly/2019/02/06/report-389-ds-base-1.4.1.1-20190206gite09725e.fc29.x86_64.html
___
389-devel mailing list -- 389-devel@lists.fedoraproject.org
To unsubscribe send an email to
On Tue, Feb 5, 2019 at 9:52 PM Jan Pazdziora wrote:
>
> On Tue, Feb 05, 2019 at 11:36:50AM +0100, Igor Gnatenko wrote:
> > On Mon, Jan 28, 2019, 18:32 Ben Cotton >
> > > ** add SWID metadata awareness to createrepo (but this will not be
> > > used in Fedora, only enabled for user use), agreeing
On Tue, Feb 5, 2019 at 9:34 PM Mátyás Selmeci wrote:
>
> On 2/1/19 10:23 AM, Neal Gompa wrote:
> > On Fri, Feb 1, 2019 at 10:23 AM Sérgio Basto wrote:
> >>
> >> koji-builder, mash and repoview are ready to work without yum ?
> >>
> >
> > There's a pending PR for fixing koji-builder:
> >
https://bugzilla.redhat.com/show_bug.cgi?id=1666094
Fedora Update System changed:
What|Removed |Added
Status|ON_QA |CLOSED
Fixed In Version|
On 05. 02. 19 19:04, Miro Hrončok wrote:
I've just spotted these when working on Python 3.8.0a1. This happens on 3.7 as
well since GCC 9:
python3-debug.x86_64: E: library-not-linked-against-libc
/usr/lib64/python3.7/lib-dynload/_contextvars.cpython-37dm-x86_64-linux-gnu.so
On 2/5/19 3:36 PM, Kalev Lember wrote:
>
> On 2/5/19 21:19, Kevin Fenzi wrote:
>> Yes, thats a danger... we will have to retag those on a case by case
>> basis. The script releng uses to merge side tags won't merge a build if
>> there is a newer one, so those should be fine, it's just if the mass
On 06/02/2019 00:47, Christoph Junghans wrote:
While packaging up votca-csg-1.5, I ran into some tests failing:
https://github.com/votca/csg/issues/326
but this only happens on ppc64le under epel7. (So I expect boost-1.53
being the culprit!)
Is there a good way (qemu or something) to debug
Hi,
While packaging up votca-csg-1.5, I ran into some tests failing:
https://github.com/votca/csg/issues/326
but this only happens on ppc64le under epel7. (So I expect boost-1.53
being the culprit!)
Is there a good way (qemu or something) to debug this interactively?
Cheers,
Christoph
--
On 2/5/19 21:19, Kevin Fenzi wrote:
Yes, thats a danger... we will have to retag those on a case by case
basis. The script releng uses to merge side tags won't merge a build if
there is a newer one, so those should be fine, it's just if the mass
rebuild build was added and then also someone did
Yes, we were aware of this issue and provided a fix in our current
master. Currently, I preparing a patch hpx 1.2.1 [0] to solve this issue
and I added s390x as well.
Patrick
[0] https://koji.fedoraproject.org/koji/taskinfo?taskID=32554858
On 2/4/19 5:18 PM, Jonathan Wakely wrote:
> On 31/01/19
On Mon, 2019-02-04 at 09:56 -0600, Mátyás Selmeci wrote:
> What's the replacement?
Bodhi switched from mash to pungi, and I think Bodhi might have been
the last thing using mash.
signature.asc
Description: This is a digitally signed message part
___
On Tue, 2019-02-05 at 12:06 +, Anderson, Charles R wrote:
> On Mon, Feb 04, 2019 at 03:48:59PM -0500, Mohan Boddu wrote:
> > Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora
> > 30
> > on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the
> > changes
> > listed in:
>
On Tue, Feb 5, 2019, 20:03 Miro Hrončok I've just spotted these when working on Python 3.8.0a1. This happens on
> 3.7 as
> well since GCC 9:
>
> python3-debug.x86_64: E: library-not-linked-against-libc
> /usr/lib64/python3.7/lib-dynload/_
> contextvars.cpython-37dm-x86_64-linux-gnu.so
>
Am Dienstag, den 05.02.2019, 19:04 +0100 schrieb Miro Hrončok:
> I've just spotted these when working on Python 3.8.0a1. This happens
> on 3.7 as
> well since GCC 9:
>
> python3-debug.x86_64: E: library-not-linked-against-libc
> /usr/lib64/python3.7/lib-dynload/_contextvars.cpython-37dm-x86_64-
On Tue, Feb 05, 2019 at 11:13:06AM +0100, Javier Martinez Canillas wrote:
> Hello Zbyszek,
>
> Thanks a lot for your feedback.
>
> On Tue, Feb 5, 2019 at 10:33 AM Zbigniew Jędrzejewski-Szmek
> wrote:
> >
> > On Tue, Jan 29, 2019 at 05:40:30AM -0500, Matthew Miller wrote:
> > > On Tue, Jan 29,
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 correctly I'm afraid.
I did add the mass rebuild
On Tue, Feb 5, 2019 at 8:03 PM Miro Hrončok wrote:
>
> I've just spotted these when working on Python 3.8.0a1. This happens on 3.7 as
> well since GCC 9:
>
> python3-debug.x86_64: E: library-not-linked-against-libc
> /usr/lib64/python3.7/lib-dynload/_contextvars.cpython-37dm-x86_64-linux-gnu.so
>
On 05. 02. 19 18:47, Jan Pazdziora wrote:
** add SWID metadata awareness to createrepo (but this will not be
Do you mean createrepo_c? createrepo is going away.
Yes. Is it OK to update the change page to fix that?
Sure thing, go ahead. That's kinda the point of having a discussion on devel -
I've just spotted these when working on Python 3.8.0a1. This happens on 3.7 as
well since GCC 9:
python3-debug.x86_64: E: library-not-linked-against-libc
/usr/lib64/python3.7/lib-dynload/_contextvars.cpython-37dm-x86_64-linux-gnu.so
python3-debug.x86_64: E: library-not-linked-against-libc
Dear all,
You are kindly invited to the meeting:
EPEL Steering Co on 2019-02-06 from 18:00:00 to 19:00:00 GMT
At freenode@fedora-meeting
The meeting will be about:
This is the weekly EPEL Steering Committee Meeting. Agenda is in the
I must have just overlooked this.
And also, there is no automation, there are just regular expressions ;)
On Tue, Feb 5, 2019 at 5:02 PM Anderson, Charles R wrote:
> Igor, your change broke my package. Whatever automation you used should
> have taken into account that %post sections don't end
On Tue, Feb 05, 2019 at 11:36:50AM +0100, Igor Gnatenko wrote:
> On Mon, Jan 28, 2019, 18:32 Ben Cotton
> > ** add SWID metadata awareness to createrepo (but this will not be
> > used in Fedora, only enabled for user use), agreeing metadata format
> > with dnf team
>
> Since this needs to be
On Tue, Feb 05, 2019 at 09:18:23AM +, Zbigniew Jędrzejewski-Szmek wrote:
> >
> > == Scope ==
> > * Proposal owners:
> > ** Add python SWID tools (swidq, rpm2swidtag)
>
> Does "add" mean "package" here? Or are they to be added to some other
> package? Are the review requests / pull requests
On 05. 02. 19 17:55, Mattia Verga wrote:
Libiptcdata was removed due to
https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
Unfortunately, Rawtherapee needs it and is now broken:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1201565
I would have expected that only the
Libiptcdata was removed due to
https://fedoraproject.org/wiki/Changes/Mass_Python_2_Package_Removal
Unfortunately, Rawtherapee needs it and is now broken:
https://koji.fedoraproject.org/koji/buildinfo?buildID=1201565
I would have expected that only the Python2 subpackage was removed, not
the
Il 2/5/19 12:39 PM, Artur Iwicki ha scritto:
> Lazarus is used to compile a few other Fedora packages, thus I'd want to
> avoid just upgrading it to v.2.0 and calling it a day without checking how it
> affects the dependent packages. I could submit an F30 change proposal, though
> that would be
On Sun, Feb 03, 2019 at 07:24:17PM -, Artur Iwicki wrote:
Hello,
[..]
> The tl;dr version is that there seems to be some kind of race condition in
> the build script, and sometimes it will run into a situation where it tries
> to install a file that hasn't been created yet - this most
Igor, your change broke my package. Whatever automation you used should have
taken into account that %post sections don't end until the next RPM directive.
%ifarch does not end a %post section.
diff --git a/ocp.spec b/ocp.spec
index 0d6fd28..2495ab5 100644
--- a/ocp.spec
+++ b/ocp.spec
@@
#fedora-meeting-3: Weekly Meeting of the Modularity Team
Meeting started by nils at 15:00:10 UTC.
Minutes:
I've been maintaining this for several years since the main admin
(ravenoak) vanished from Fedora. I don't use it anymore (and most of
the world has long since switched to git...) and it has yet again
failed to rebuild during the mass rebuild.
I'm initiating the Non-Responsive Maintainer process
> If you would implement a universal package name translation, then this > could be **really** useful.Yes I want exactly that.___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
https://bugzilla.redhat.com/show_bug.cgi?id=1672325
Upstream Release Monitoring
changed:
What|Removed |Added
Summary|perl-XML-Feed-0.57 is |perl-XML-Feed-0.58 is
Valor Naram writes:
>> Also what you suggest already exists, for example in the form of
>> "pacapt" (but there are alternatives too!). What is the benefit of
>> adding yet another version of these scripts?
>
> `Nimue` doesn't tends to be a wrapper like pacapt which itself tends to
> "emulate"
Hi,
His name sounds familiar to me but I don't know how to contact him. Sorry.
Kind regards,
Silvia
FAS: Lailah
On Tue, 5 Feb 2019 at 13:27, Miro Hrončok wrote:
> Anyone knows how to contact Ryan?
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1627417
>
> --
> Miro Hrončok
> --
> Phone:
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 openQA tests: 82/132 (x86_64), 24/24 (i386), 1/2 (arm)
New failures (same test
> Also what you suggest already exists, for example in the form of
> "pacapt" (but there are alternatives too!). What is the benefit of
> adding yet another version of these scripts?
`Nimue` doesn't tends to be a wrapper like pacapt which itself tends to
"emulate" a Arch Linux environment.
On Tue, Feb 5, 2019 at 6:38 AM Artur Iwicki wrote:
> Just a couple of minutes ago, version 2.0 of Lazarus, the Pascal IDE / GUI
> toolkit was released.
>
> Here's the link to the changelog; there are a few compatibility-breaking
> changes:
>
Anyone knows how to contact Ryan?
https://bugzilla.redhat.com/show_bug.cgi?id=1627417
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Anyone knows how to contact Stefan?
https://bugzilla.redhat.com/show_bug.cgi?id=1627400
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to
Do you have by a chance some test build in Copr, so I could test my
Doublecmd package?
https://copr.fedorainfracloud.org/coprs/vondruch/doublecmd/
I honestly have no idea if it could work with 2.0 or not.
Thx
Vít
Dne 05. 02. 19 v 12:39 Artur Iwicki napsal(a):
> Just a couple of minutes ago,
On Mon, Feb 04, 2019 at 03:48:59PM -0500, Mohan Boddu wrote:
> Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
> on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes
> listed in:
>
> https://pagure.io/releng/issue/8086
>
> Mass rebuild was done in a side
Hi all,
This package used to be part of Ruby on Rails, later it was removed from
the framework and extracted into independent gem mainly for backward
compatibility. This package is FTBFS ATM, presumably since Ruby on Rails
5.2 were imported into F29, because there is one test failure. Upstream
> 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
> I'm also concerned that once the signing queue starts moving, it's going to
> tag older packages over the new builds that have
On 2/5/19 12:44 AM, Eli Young wrote:
Python packages can specify extras dependencies, which are sets of dependencies not
required for core functionality, and which generally correspond to some feature. These
can then be specified by downstream consumers of the package. For example, requests
> fundamental issue: every distro has a different naming scheme for
> packages. Sure, the "big" programs (Firefox for instance) have usually
> the name you'd expect, but with libraries this won't help at all.
https://release-monitoring.org can be used to solve that issue and they also
provide
Just a couple of minutes ago, version 2.0 of Lazarus, the Pascal IDE / GUI
toolkit was released.
Here's the link to the changelog; there are a few compatibility-breaking
changes:
http://wiki.lazarus.freepascal.org/Lazarus_2.0.0_release_notes
Lazarus is used to compile a few other Fedora
No. If count as many times as many maintainers it has it will be about
3300 fails.
вт, 5 февр. 2019 г. в 14:32, Vít Ondruch :
>
>
> Dne 04. 02. 19 v 21:48 Mohan Boddu napsal(a):
>
> Hi all,
>
> Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
> on Jan 31st 2019. We did a mass
There were no dependent packages.
--
Pavel Valena
Software Engineer, Red Hat
Brno, Czech Republic
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On 2/5/19 12:44 AM, Eli Young wrote:
Python packages can specify extras dependencies, which are sets of dependencies not
required for core functionality, and which generally correspond to some feature. These
can then be specified by downstream consumers of the package. For example, requests
Vít Ondruch writes:
> Dne 05. 02. 19 v 11:09 Dan Čermák napsal(a):
>> Hi Sören,
>>
>> while I don't want to discourage you in your work, symlinking the
>> package manager to /usr/bin/nimue isn't going to solve a more
>> fundamental issue: every distro has a different naming scheme for
>>
Dne 05. 02. 19 v 11:09 Dan Čermák napsal(a):
> Hi Sören,
>
> while I don't want to discourage you in your work, symlinking the
> package manager to /usr/bin/nimue isn't going to solve a more
> fundamental issue: every distro has a different naming scheme for
> packages. Sure, the "big" programs
On Mon, Jan 28, 2019, 18:32 Ben Cotton https://fedoraproject.org/wiki/Changes/SWID_Tag_Enablement
>
> == Summary ==
> Provide tools to allow users and developers to create Software
> Identity (SWID) tags for Fedora installs and repositories.
>
> == Owner ==
> * Name: [[User:adelton|Jan
Dne 04. 02. 19 v 21:48 Mohan Boddu napsal(a):
> Hi all,
>
> Per the Fedora 30 schedule[1] we started a mass rebuild for Fedora 30
> on Jan 31st 2019. We did a mass rebuild for Fedora 30 for the changes
> listed in:
>
> https://pagure.io/releng/issue/8086
>
> Mass rebuild was done in a side tag
Hello Zbyszek,
Thanks a lot for your feedback.
On Tue, Feb 5, 2019 at 10:33 AM Zbigniew Jędrzejewski-Szmek
wrote:
>
> On Tue, Jan 29, 2019 at 05:40:30AM -0500, Matthew Miller wrote:
> > On Tue, Jan 29, 2019 at 05:29:51AM -0500, Ben Cotton wrote:
> > > Improve the GRUB menu by only having the
Hi Sören,
while I don't want to discourage you in your work, symlinking the
package manager to /usr/bin/nimue isn't going to solve a more
fundamental issue: every distro has a different naming scheme for
packages. Sure, the "big" programs (Firefox for instance) have usually
the name you'd expect,
I've just orphaned 259 packages listed below. Almost all of them are
Java packages which I will continue to maintain as part of modules.
Intent to orphan them was already announced on java-devel [1] and
devel [2] lists, with detailed reasoning.
Originally planned time of orphaning was delayed
On Tue, Jan 29, 2019 at 05:40:30AM -0500, Matthew Miller wrote:
> On Tue, Jan 29, 2019 at 05:29:51AM -0500, Ben Cotton wrote:
> > Improve the GRUB menu by only having the default boot option for each
> > installed operating system in the main menu, and the other options
> > into a sub-menu. This
There seems to be an issue with moving builds over. Everything seems to be stuck in f30-pending and not getting tagged with f30. I'm also concerned that once the signing queue starts moving, it's going to tag older packages over the new builds that have happened in the mean time. Pete 05.02.2019,
On Mon, Jan 28, 2019 at 12:27:06PM -0500, Ben Cotton wrote:
> https://fedoraproject.org/wiki/Changes/SWID_Tag_Enablement
>
> == Summary ==
> Provide tools to allow users and developers to create Software
> Identity (SWID) tags for Fedora installs and repositories.
>
> == Owner ==
> * Name:
In Rust we have similar problem (we have "features" than "extras") and we
always package them as a subpackages.
https://src.fedoraproject.org/rpms/rust-serde/blob/master/f/rust-serde.spec
rust-serde-devel
rust-serde+alloc-devel
rust-serde+default-devel
rust-serde+derive-devel
rust-serde+rc-devel
On Mon, Feb 4, 2019 at 1:26 PM Stephen John Smoogen wrote:
>
> On Mon, 4 Feb 2019 at 12:14, Mátyás Selmeci wrote:
> >
> > On 1/31/19 1:05 PM, Kevin Fenzi wrote:
> > > On 1/30/19 1:39 PM, Adam Williamson wrote:
> > >
> > >> Question: how plausibly can we sort of "test retire" yum? i.e. just
> >
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://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
I plan
In Rust we have similar problem (we have "features" than "extras") and we
always package them as a subpackages.
https://src.fedoraproject.org/rpms/rust-serde/blob/master/f/rust-serde.spec
rust-serde-devel
rust-serde+alloc-devel
rust-serde+default-devel
rust-serde+derive-devel
rust-serde+rc-devel
69 matches
Mail list logo
