No missing expected images.
Passed openQA tests: 2/2 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
No missing expected images.
Failed openQA tests: 83/137 (x86_64), 24/24 (i386), 1/2 (arm)
ID: 203982 Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/203982
ID: 203983 Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedorapro
No missing expected images.
Failed openQA tests: 17/137 (x86_64), 5/23 (i386), 1/2 (arm)
ID: 203825 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/203825
ID: 203831 Test: x86_64 Server-dvd-iso server_role_deploy_database_serv
FTR, patches to convert at-spi2-core to use dbus-broker:
https://github.com/GNOME/at-spi2-core/pull/2
https://src.fedoraproject.org/rpms/at-spi2-core/pull-request/1
Zbyszek
On Tue, Mar 13, 2018 at 05:32:20PM +0100, Jan Kurik wrote:
> = Proposed System Wide Change: Make dbus-broker the default DB
Hello,
Yesterday I received a couple of new FTBFS bugs, apparently triggered by
the F28 mass rebuild:
https://bugzilla.redhat.com/show_bug.cgi?id=1556047
https://bugzilla.redhat.com/show_bug.cgi?id=1556162
As the mentioned koji builds are back in February, I am wondering if
those are something I
Did I miss something? The xinetd package cannot be built because of that.
Cheers,
--
Jan Synacek
Software Engineer, Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On Thu, Mar 15, 2018 at 11:30:32AM +0100, Jan Synacek wrote:
> Did I miss something? The xinetd package cannot be built because of that.
GLibc dropped the RPC functionality. You need to change the code to
use tirpc instead. It is API compatible, but your build system will
need to know to link the
On Thu, 15 Mar 2018 11:30:32 +0100
Jan Synacek wrote:
> Did I miss something? The xinetd package cannot be built because of
> that.
https://fedoraproject.org/wiki/Changes/SunRPCRemoval
Dan
___
devel mailing list -- devel@lists.fedorap
On Thu, Mar 15, 2018 at 11:43 AM, Dan Horák wrote:
> On Thu, 15 Mar 2018 11:30:32 +0100
> Jan Synacek wrote:
>
>> Did I miss something? The xinetd package cannot be built because of
>> that.
>
> https://fedoraproject.org/wiki/Changes/SunRPCRemoval
So I missed something. Thank you for pointing me
El jue, 15-03-2018 a las 11:01 +0100, Daiki Ueno escribió:
> Hello,
>
> Yesterday I received a couple of new FTBFS bugs, apparently triggered
> by
> the F28 mass rebuild:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1556047
> https://bugzilla.redhat.com/show_bug.cgi?id=1556162
>
> As the ment
On Thu, 15 Mar 2018 11:01:00 +0100, Daiki Ueno wrote:
> Hello,
>
> Yesterday I received a couple of new FTBFS bugs, apparently triggered by
> the F28 mass rebuild:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1556047
> https://bugzilla.redhat.com/show_bug.cgi?id=1556162
>
> As the mentioned
A new Fedora Atomic Host update is available via an OSTree update:
Version: 27.100
Commit(x86_64): 326f62b93a5cc836c97d31e73a71b6b6b6955c0f225f7651b52a693718e6aa91
Commit(aarch64):
ba2aa19d99466c53e614651f014c8b97ae1940f87885b7c7dfed1fb62ae91567
Commit(ppc64le):
ca0ea3a6e15b6270aefe3c7b55ffbee3
On Wed, Mar 14, 2018 at 10:55 PM, James Antill
wrote:
#topic #694 Packaging guidelines for application independence
.fpc 694
https://pagure.io/packaging-committee/issue/694
I had been hoping to attend the meeting to discuss this change, but
it's been on the meeting agenda for five months now,
Is this header deprecated? It's no longer shipped in the Rawhide package.
Thanks,
Michael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On Thu, Mar 15, 2018 at 09:55:09AM -0500, Michael Cronenworth wrote:
> Is this header deprecated? It's no longer shipped in the Rawhide package.
Yes, deprecated in 2.27 and gone in 2.28
https://sourceware.org/ml/libc-announce/2018/msg0.html
[quote]
* The nonstandard header files and <_G_con
On 03/15/2018 09:55 AM, Michael Cronenworth wrote:
Is this header deprecated? It's no longer shipped in the Rawhide package.
Answering myself: Yes.
https://sourceware.org/git/?p=glibc.git;a=commit;h=48a8f8328122ab8d06b7333cb87be46feeaf7cca
___
devel
Hi all,
If you maintain any application in Fedora Infra (or outside) that
tries to parse things out of RPM names, you might be interested in
this.
For those wondering where I've been spending most of my time the last
few weeks: I've been deep in the internals of Bodhi fixing all kinds
of issues I
On 03/15/2018 10:14 AM, Patrick Uiterwijk wrote:
Hi all,
If you maintain any application in Fedora Infra (or outside) that
tries to parse things out of RPM names, you might be interested in
this.
For those wondering where I've been spending most of my time the last
few weeks: I've been deep in
>
>
> This does not affect traditional RPM/SRPM packages, right?
Correct, this only impacts modules.
>
> Thanks,
> -Mat
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
___
On Thu, Mar 15, 2018 at 7:24 PM, wrote:
>
> A new Fedora Atomic Host update is available via an OSTree update:
>
> Version: 27.100
> Commit(x86_64):
> 326f62b93a5cc836c97d31e73a71b6b6b6955c0f225f7651b52a693718e6aa91
> Commit(aarch64):
> ba2aa19d99466c53e614651f014c8b97ae1940f87885b7c7dfed1fb62a
On 15/03/18 15:30, Patrick Uiterwijk wrote:
This does not affect traditional RPM/SRPM packages, right?
Correct, this only impacts modules.
Well currently at any rate? What's the long term story?
Only when some module rpms accidentally leaked into rawhide
recently they definitely had the ki
The following Fedora EPEL 7 Security updates need testing:
Age URL
1102 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-1087
dokuwiki-0-0.24.20140929c.el7
864 https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2015-dac7ed832f
mcollective-2.8.4-1.el7
447 https://bodhi.fedorap
On Thu, Mar 15, 2018 at 11:14 AM, Patrick Uiterwijk
wrote:
> Hi all,
>
> If you maintain any application in Fedora Infra (or outside) that
> tries to parse things out of RPM names, you might be interested in
> this.
>
> For those wondering where I've been spending most of my time the last
> few we
> On 15/03/18 15:30, Patrick Uiterwijk wrote:
>
> Well currently at any rate? What's the long term story?
>
> Only when some module rpms accidentally leaked into rawhide
> recently they definitely had the kind of rather unhelpful names
> that you described in your post and I got the impression at
On 15/03/18 00:54 +0100, René Genz wrote:
On 14.03.2018 14:40, Jonathan Wakely wrote:
On 14/03/18 01:02 +0100, René Genz wrote:
On 13.03.2018 15:13, Jonathan Wakely wrote:
On 12/03/18 21:02 -0300, Athos Ribeiro wrote:
[snip]
You could add a link saying something like "To make a one-off
cont
On Thu, Mar 15, 2018 at 04:14:34PM +0100, Patrick Uiterwijk wrote:
> Hi all,
>
> If you maintain any application in Fedora Infra (or outside) that
> tries to parse things out of RPM names, you might be interested in
> this.
>
> For those wondering where I've been spending most of my time the last
On 15/03/18 16:09, Jonathan Wakely wrote:
And since you can't write to it, there is not point creating your own
fork. You might as well just create the fork somewhere else like
pagure.io
Explaining that you can't write to your fork is not necessary if you
don't encourage people to create useles
On Thu, 2018-03-15 at 16:14 +0100, Patrick Uiterwijk wrote:
> One of the interesting things they wanted to also allow: dashes in streams.
> As a consequence, when you get an N-S-V.C as modules are represented
> in Koji builds, doing a .rsplit('-', 2) will not give you Name,
> Stream, Version.Contex
On Thu, Mar 15, 2018 at 04:19:46PM +, Daniel P. Berrangé wrote:
> On Thu, Mar 15, 2018 at 04:14:34PM +0100, Patrick Uiterwijk wrote:
> > For user consumption, they are Name:Stream:Version:Context, so you may
> > need to manually convert between one representation and the other if
> > you need t
On Thu, 2018-03-15 at 06:25 +, Vascom wrote:
> Hi.
>
> GCC 8.0.1-0.16 in F28 repo is freezed until F28 release?
> Or it will be updated soon so we can build some packages failed to
> build now?
> Or better use build override new gcc for this packages?
the freeze is only until beta compose is
On Thu, 2018-03-15 at 12:49 +0100, Jan Synacek wrote:
> On Thu, Mar 15, 2018 at 11:43 AM, Dan Horák wrote:
> > On Thu, 15 Mar 2018 11:30:32 +0100
> > Jan Synacek wrote:
> >
> > > Did I miss something? The xinetd package cannot be built because
> > > of
> > > that.
> >
> > https://fedoraproject.
On Thu, Mar 15, 2018 at 6:25 AM, Vascom wrote:
> Hi.
>
> GCC 8.0.1-0.16 in F28 repo is freezed until F28 release?
> Or it will be updated soon so we can build some packages failed to build
> now?
> Or better use build override new gcc for this packages?
Is there a particular bug fix that you need
Did I miss something?
Both machines were dnf system-upgraded from f27. Static IP settings were
set at f27 install time and worked before the respective upgrades.
f28 was working correctly until a couple of days ago to the best of my
knowledge.
E.g.——
%cat /etc/sysconfig/network-scripts/ifcfg-e
OLD: Fedora-Rawhide-20180314.n.2
NEW: Fedora-Rawhide-20180315.n.1
= SUMMARY =
Added images:1
Dropped images: 6
Added packages: 3
Dropped packages:0
Upgraded packages: 83
Downgraded packages: 1
Size of added packages: 6.45 MiB
Size of dropped packages:0 B
OK.
It is not so important build, only for clearness.
чт, 15 мар. 2018 г., 20:12 Peter Robinson :
> On Thu, Mar 15, 2018 at 6:25 AM, Vascom wrote:
> > Hi.
> >
> > GCC 8.0.1-0.16 in F28 repo is freezed until F28 release?
> > Or it will be updated soon so we can build some packages failed to build
On Thu, Mar 15, 2018 at 01:13:09PM -0400, Kaleb S. KEITHLEY wrote:
>
> Did I miss something?
>
> Both machines were dnf system-upgraded from f27. Static IP settings were
> set at f27 install time and worked before the respective upgrades.
>
> f28 was working correctly until a couple of days ago
On 15/03/18 16:24 +, Tom Hughes wrote:
On 15/03/18 16:09, Jonathan Wakely wrote:
And since you can't write to it, there is not point creating your own
fork. You might as well just create the fork somewhere else like
pagure.io
Explaining that you can't write to your fork is not necessary if
On Thu, 15 Mar 2018 17:11:49 +
Peter Robinson wrote:
> On Thu, Mar 15, 2018 at 6:25 AM, Vascom wrote:
> > Hi.
> >
> > GCC 8.0.1-0.16 in F28 repo is freezed until F28 release?
> > Or it will be updated soon so we can build some packages failed to
> > build now?
> > Or better use build overrid
On Thu, 2018-03-15 at 18:23 +0100, Tomasz Torcz 👁️ wrote:
> On Thu, Mar 15, 2018 at 01:13:09PM -0400, Kaleb S. KEITHLEY wrote:
> >
> > Did I miss something?
> >
> > Both machines were dnf system-upgraded from f27. Static IP settings were
> > set at f27 install time and worked before the respectiv
On 03/15/2018 12:28 PM, Chuck Anderson wrote:
> : doesn't work very well in filenames due to it being a pathname separator in
> some filesystems among other things.
It sounds like this breaks a great deal of tooling. Can we reconsider
switching away from - separators in modules? Is allowing strea
On 03/15/2018 01:23 PM, Tomasz Torcz 👁️ wrote:
> On Thu, Mar 15, 2018 at 01:13:09PM -0400, Kaleb S. KEITHLEY wrote:
>>
>> Did I miss something?
>>
>> Both machines were dnf system-upgraded from f27. Static IP settings were
>> set at f27 install time and worked before the respective upgrades.
>>
>>
On Thu, 2018-03-15 at 14:40 -0400, Kaleb S. KEITHLEY wrote:
> On 03/15/2018 01:23 PM, Tomasz Torcz 👁️ wrote:
> > On Thu, Mar 15, 2018 at 01:13:09PM -0400, Kaleb S. KEITHLEY wrote:
> > >
> > > Did I miss something?
> > >
> > > Both machines were dnf system-upgraded from f27. Static IP settings wer
> On 03/15/2018 01:23 PM, Tomasz Torcz 👁️ wrote:
>
> It's not. Now it's enp0s3.
>
> And renaming /etc/sysconfig/network-scripts/ifcfg-ens3 to ifcfg-enp0s3
> doesn't do anything.
Note that the files themselves also contain a DEVICE= line that would need to
be updated for it to apply again.
Patr
OLD: Fedora-28-20180314.n.2
NEW: Fedora-28-20180315.n.0
= SUMMARY =
Added images:2
Dropped images: 0
Added packages: 0
Dropped packages:1
Upgraded packages: 0
Downgraded packages: 0
Size of added packages: 0 B
Size of dropped packages:121.15 MiB
Size of
I no longer have the time/resources/interest to maintain jemmy:
https://src.fedoraproject.org/rpms/jemmy/
I have orphaned it. If anyone wants to take over maintainership, please
do so.
Thanks,
Omair
--
PGP Key: B157A9F0 (http://pgp.mit.edu/)
Fingerprint = 9DB5 2F0B FD3E C239 E108 E7BD DF99 7AF
On Thu, Mar 15, 2018 at 9:27 PM, Patrick マルタインアンドレアス Uiterwijk <
puiterw...@redhat.com> wrote:
> > On 03/15/2018 01:23 PM, Tomasz Torcz 👁️ wrote:
> >
> > It's not. Now it's enp0s3.
> >
> > And renaming /etc/sysconfig/network-scripts/ifcfg-ens3 to ifcfg-enp0s3
> > doesn't do anything.
>
> Note that
On Thu, 2018-03-15 at 14:06 -0400, Randy Barlow wrote:
> On 03/15/2018 12:28 PM, Chuck Anderson wrote:
> > : doesn't work very well in filenames due to it being a pathname separator
> > in some filesystems among other things.
>
> It sounds like this breaks a great deal of tooling. Can we reconsid
> Greetings fellow Fedorans!
>
> I would like to kick off a general discussion about how we might gate
> packages in Rawhide. I think it would be nice to get something in place
> for the Fedora 29 timeframe.
>
> As one of the Bodhi contributors, I am inclined to suggest that we could
> use Bodhi
On 03/15/2018 04:57 PM, Mohan Boddu wrote:
>> As one of the Bodhi contributors, I am inclined to suggest that we could
>> use Bodhi on Rawhide, similar to how we use it for our stable/branched
>> releases, with more relaxed rules (perhaps 1 day in testing or something
>> simple).
> We need a bette
On Thu, 15 Mar 2018, 10:26 Dan Horák, wrote:
> On Thu, 15 Mar 2018 17:11:49 +
> Peter Robinson wrote:
>
> > On Thu, Mar 15, 2018 at 6:25 AM, Vascom wrote:
> > > Hi.
> > >
> > > GCC 8.0.1-0.16 in F28 repo is freezed until F28 release?
> > > Or it will be updated soon so we can build some pac
No missing expected images.
Failed openQA tests: 84/137 (x86_64), 24/24 (i386), 1/2 (arm)
ID: 204419 Test: x86_64 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/204419
ID: 204420 Test: x86_64 Server-boot-iso install_default@uefi
URL: https://openqa.fedorapro
No missing expected images.
Failed openQA tests: 16/137 (x86_64), 5/23 (i386), 1/2 (arm)
ID: 204706 Test: x86_64 Server-dvd-iso server_role_deploy_domain_controller
URL: https://openqa.fedoraproject.org/tests/204706
ID: 204712 Test: x86_64 Server-dvd-iso server_role_deploy_database_serv
upstream made a patch
https://github.com/open-eid/chrome-token-signing/issues/80#issuecomment-373545367
but it looks like it does not work.
Could you please check if I made any mistake in applying the patch in
the RPM?
failed build
https://koji.fedoraproject.org/koji/taskinfo?taskID=25733909
Pack
On 03/15/2018 04:31 PM, Simo Sorce wrote:
On Thu, 2018-03-15 at 14:06 -0400, Randy Barlow wrote:
On 03/15/2018 12:28 PM, Chuck Anderson wrote:
: doesn't work very well in filenames due to it being a pathname separator in
some filesystems among other things.
It sounds like this breaks a great
On 15.03.2018 17:09, Jonathan Wakely wrote:
> On 15/03/18 00:54 +0100, René Genz wrote:
>> On 14.03.2018 14:40, Jonathan Wakely wrote:
>>> On 14/03/18 01:02 +0100, René Genz wrote:
On 13.03.2018 15:13, Jonathan Wakely wrote:
> On 12/03/18 21:02 -0300, Athos Ribeiro wrote:
[snip]
>>
>> Taki
On Thu, 2018-03-15 at 18:26 +0100, Dan Horák wrote:
> On Thu, 15 Mar 2018 17:11:49 +
> Peter Robinson wrote:
>
> > On Thu, Mar 15, 2018 at 6:25 AM, Vascom wrote:
> > > Hi.
> > >
> > > GCC 8.0.1-0.16 in F28 repo is freezed until F28 release?
> > > Or it will be updated soon so we can build s
I'm seeing a strange error when building wxGTK3 on F28. This only happens
on x86_64. The same package built fine on Rawhide. Anyone have any ideas
what's going on here?
This is the Koji task:
https://koji.fedoraproject.org/koji/taskinfo?taskID=25734989
Here's the error:
`_ZN8wxThread8OnDeleteE
On Thu, 2018-03-15 at 19:57 -0400, langdon wrote:
> On 03/15/2018 04:31 PM, Simo Sorce wrote:
> > On Thu, 2018-03-15 at 14:06 -0400, Randy Barlow wrote:
> > > On 03/15/2018 12:28 PM, Chuck Anderson wrote:
> > > > : doesn't work very well in filenames due to it being a pathname
> > > > separator in
Germano Massullo wrote:
> upstream made a patch
> https://github.com/open-eid/chrome-token-signing/issues/80#issuecomment-373545367
> but it looks like it does not work.
> Could you please check if I made any mistake in applying the patch in
> the RPM?
The patch should be fine, but you also need t
Randy Barlow wrote:
> It sounds like this breaks a great deal of tooling. Can we reconsider
> switching away from - separators in modules? Is allowing streams to have
> -'s in them important enough to break so many tools?
+1, I think allowing this ambiguity is a very bad idea.
Kevin Kofle
On 2018-02-18 09:09 AM, Igor Gnatenko wrote:
> Over this weekend I've performed scratch-mass-rebuild without having
> gcc and
> gcc-c++ in buildroot of all Fedora packages, many of which failed due
> to random
> reasons and I grepped all logs for some common errors found by analyzing
> hundreds of
It looks like some Blender dependencies such as openvdb and embree
failed to build with gcc 8.x while they successfully compiled with GCC
7.x. Not sure what caused the issue but I can provide the result:
Failure to build openvdb with gcc 8.0.1
https://koji.fedoraproject.org/koji/taskinfo?taskID=2
On Thu, 2018-03-15 at 23:18 -0700, Luya Tshimbalanga wrote:
> It looks like some Blender dependencies such as openvdb and embree
> failed to build with gcc 8.x while they successfully compiled with GCC
> 7.x. Not sure what caused the issue but I can provide the result:
>
> Failure to build openvdb
On 2018-03-15 11:29 PM, Adam Williamson wrote:
> On Thu, 2018-03-15 at 23:18 -0700, Luya Tshimbalanga wrote:
>> It looks like some Blender dependencies such as openvdb and embree
>> failed to build with gcc 8.x while they successfully compiled with GCC
>> 7.x. Not sure what caused the issue but I c
64 matches
Mail list logo
