On 2018-01-23 01:35, Jakub Jelinek wrote:
> On Tue, Jan 23, 2018 at 08:00:08AM +0100, Florian Weimer wrote:
>> On 01/22/2018 10:15 PM, Adam Jackson wrote:
>>> Is -Wredundant-decls just not a thing one should try to use?
>>
>> Certainly with ccache, yes.
>
> The command uses -I /usr/include/tirpc/
On 01/23/2018 08:59 AM, Yaakov Selkowitz wrote:
Is this another reason to move the headers out of /usr/include/tirpc,
once glibc no longer provides conflicting headers?
Seems worth a try. Unlike /usr/include/rpcsvc, /usr/include/rpc was
exclusively used by glibc.
Thanks,
Florian
___
Hi,
simple proof of concept is ready for experimenting:
https://github.com/psss/fmf
http://fmf.readthedocs.io/
Looking for the first impressions & feedback. Thanks.
psss...
On 8 January 2018 at 15:49, Petr Splichal wrote:
> Hi!
>
> In order to keep test execution efficient when numbe
On 23/01/18 07:44, Florian Weimer wrote:
On 01/23/2018 08:16 AM, Tom Hughes wrote:
This seems to be breaking things. I have so's failing to link due to
this even though the man page says -zdefs doesn't affect shared
libraries.
Examples?
It will cause link failures because binutils now report
Hi everyone!
On Tuesday, January 30th, 2018 we will reach the submission deadline
for Self contained Changes proposed for Fedora 28 [1]. After this
deadline you will be asked to schedule your Change Proposals (Self
contained as well as System wide) for the next, Fedora 29. release.
[1] https://fe
On 01/20/2018 06:53 PM, Stephen John Smoogen wrote:
> On 19 January 2018 at 22:53, Dusty Mabe wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>>
>>
>> On 01/19/2018 10:39 PM, Reindl Harald wrote:
>>>
>>>
>>> [harry@srv-rhsoft:~]$ cat /etc/yum.repos.d/koji.repo
>>> [koji]
>>> name
Hi,
let me remind you we have Voting period of the currently running
Fedora Elections in progress.
Please vote for your candidates to Council [1], Mindshare [2] and FESCo [3].
The Voting period ends on January 24th, 2018 at 23:59:00 UTC.
You might also check a Community Blog for interviews with
On 01/23/2018 09:28 AM, Tom Hughes wrote:
On 23/01/18 07:44, Florian Weimer wrote:
On 01/23/2018 08:16 AM, Tom Hughes wrote:
This seems to be breaking things. I have so's failing to link due to
this even though the man page says -zdefs doesn't affect shared
libraries.
Examples?
It will caus
On 23.01.2018 09:28, Tom Hughes wrote:
None the less the man page for ld (at least on F27) says:
defs
Disallows undefined symbols in object files. Undefined symbols
in shared libraries are still allowed.
which says that undefined symbols are allowed when linking a shared
On 01/21/2018 02:46 PM, Lars Seipel wrote:
> Use includepkgs in the repo definition?
>
>> includepkgs Inverse of exclude, yum will exclude any package in the repo.
>> that doesn't match this
>> list. This works in conjunction with exclude and doesn't override it, so
>> if you exclude
Can someone decode what this means? The linked page gives no useful
guidance as far as I can tell.
Rich.
- Forwarded message from upda...@fedoraproject.org -
Date: Tue, 23 Jan 2018 03:01:59 + (UTC)
From: upda...@fedoraproject.org
Subject: [Fedora Update] [comment] ocaml-4.04.0-11.fc
On 23/01/18 08:37, Stephan Bergmann wrote:
On 23.01.2018 09:28, Tom Hughes wrote:
None the less the man page for ld (at least on F27) says:
defs
Disallows undefined symbols in object files. Undefined symbols
in shared libraries are still allowed.
which says that undefin
On Mon, Jan 22, 2018 at 04:24:31PM +0100, Florian Weimer wrote:
> I updated redhat-rpm-config to instruct ld to reject linking shared
> objects with undefined symbols. Such undefined symbols break symbol
> versioning because the are not necessarily bound to the correct
> symbol version at run time
On Mon, Jan 22, 2018 at 05:36:56PM +0100, Igor Gnatenko wrote:
> * Removes exectuable bit (and shows warning) for files where there are no
> shebang
The way this is written implies that ordinary (eg ELF) executables
will be broken by this change, which I'm assuming/hoping is not the
case.
I'm con
Dne 23.1.2018 v 03:55 Jason L Tibbitts III napsal(a):
>> "VO" == Vít Ondruch writes:
> VO> I think FPC does not know.
>
> Certainly we know what we generally try to do, but Fedora changes
> quickly and some things aren't always stated as well as they could be.
> Plus the experts who draft th
> Dne 22.1.2018 v 12:31 Miroslav Suchý napsal(a):
>
> You took pretty basic example without context. So let me give you
> different example.
>
> There were attempts to get Ruby on Rails into EPEL. It is around 80
> packages. Some packages were RHEL contidiontalized. But the effort to
> get Ruby o
On Mon, 2018-01-22 at 19:53 +, Tom Hughes wrote:
> On 22/01/18 15:58, Adam Williamson wrote:
>
> > I have a dual monitor setup with both monitors rotated, using an NVIDIA
> > adapter (9600 GT). Works fine, uses Wayland. Again, you need to be
> > *very specific* about graphics issues. They are
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2018-01-22 at 12:31 +0100, Miroslav Suchý wrote:
>
> Better to introduce bugs?
>
> mock-core-config now requires yum on Fedora because you made wrong if in
> spec...
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1537193
> - --
>
On Mon, Jan 22, 2018 at 4:24 PM, Florian Weimer wrote:
> I updated redhat-rpm-config to instruct ld to reject linking shared objects
> with undefined symbols. Such undefined symbols break symbol versioning
> because the are not necessarily bound to the correct symbol version at run
> time. (rhbz
Dne 23.1.2018 v 10:09 Samuel Rakitničan napsal(a):
>> Dne 22.1.2018 v 12:31 Miroslav Suchý napsal(a):
>>
>> You took pretty basic example without context. So let me give you
>> different example.
>>
>> There were attempts to get Ruby on Rails into EPEL. It is around 80
>> packages. Some packages
Good Morning Fedorans!
On Thursday, a new version of Bodhi was deployed that enabled Bodhi to
gate updates based on test results. You may notice a "Test Gating
Status" message in the right have side of the page.
One thing to know about this is that there is currently a confusing
issue where Bodhi
On Mon, Jan 22, 2018 at 01:57:34PM -0700, Jerry James wrote:
> Here's something I didn't expect from the new ABI gate. Which, before
> I go further, I think will be a great idea nearly all of the time. I
> think avoiding unintentional ABI breaks in stable releases is a worthy
> goal.
>
> But ...
Does it mean we don't have to fix the shebangs in .spec files and we can
ignore rpmlint complaints?
Vít
Dne 22.1.2018 v 17:36 Igor Gnatenko napsal(a):
> Hello,
>
> I'm planning to merge PR[0] somewhere later this week. Essentially it
> does:
>
> For each executable files:
> * Replaces /usr/bin/e
On 01/23/2018 10:55 AM, Richard W.M. Jones wrote:
On Mon, Jan 22, 2018 at 05:36:56PM +0100, Igor Gnatenko wrote:
* Removes exectuable bit (and shows warning) for files where there are no
shebang
The way this is written implies that ordinary (eg ELF) executables
will be broken by this change, w
On Tue, Jan 23, 2018 at 10:28:14AM +0100, Pierre-Yves Chibon wrote:
> Good Morning Fedorans!
>
> On Thursday, a new version of Bodhi was deployed that enabled Bodhi to
> gate updates based on test results. You may notice a "Test Gating
> Status" message in the right have side of the page.
>
> One
Following
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package
I would like to take ownership of the libnice package orphaned yesterday.
I have created the following releng issue for that:
https://pagure.io/releng/issue/7279
Kamil
__
On Tue, Jan 23, 2018 at 08:55:03AM +, Richard W.M. Jones wrote:
> On Mon, Jan 22, 2018 at 05:36:56PM +0100, Igor Gnatenko wrote:
> > * Removes exectuable bit (and shows warning) for files where there are no
> > shebang
>
> The way this is written implies that ordinary (eg ELF) executables
> wi
On 23/01/18 09:42, Richard W.M. Jones wrote:
When I click on the "automated tests" it says:
"Automated Test Results
Failed to talk to Greenwave.
The update can not be pushed: 1 of 2 required tests not found"
and then the only "red" test (ie. failure) is rpmlint which is just a
bunch o
On Tue, Jan 23, 2018 at 1:37 AM, Igor Gnatenko
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Mon, 2018-01-22 at 15:58 -0500, Matthew Miller wrote:
>> On Mon, Jan 22, 2018 at 08:21:19PM +, Tomasz Kłoczko wrote:
>> > Yet anther thought ..
>> > As long as between major EL rele
On Tue, Jan 23, 2018 at 09:42:50AM +, Richard W.M. Jones wrote:
> On Tue, Jan 23, 2018 at 10:28:14AM +0100, Pierre-Yves Chibon wrote:
> > Good Morning Fedorans!
> >
> > On Thursday, a new version of Bodhi was deployed that enabled Bodhi to
> > gate updates based on test results. You may notice
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Tue, 2018-01-23 at 04:56 -0500, Nico Kadel-Garcia wrote:
> On Tue, Jan 23, 2018 at 1:37 AM, Igor Gnatenko
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > On Mon, 2018-01-22 at 15:58 -0500, Matthew Miller wrote:
> > > On
Dne 23.1.2018 v 10:38 Vít Ondruch napsal(a):
> and we can ignore rpmlint complaints?
The problem is that some developers often do not run rpmlint after every change
(including me).
What I would like to see is to have mandatory checks after mock build. It is
tracked here:
https://github.com/rp
Hi, Florian.
On Monday, 22 January 2018 at 16:24, Florian Weimer wrote:
> I updated redhat-rpm-config to instruct ld to reject linking shared objects
> with undefined symbols. Such undefined symbols break symbol versioning
> because the are not necessarily bound to the correct symbol version at r
On Tue, Jan 23, 2018 at 09:47:44AM +, Tom Hughes wrote:
> On 23/01/18 09:42, Richard W.M. Jones wrote:
>
> >When I click on the "automated tests" it says:
> >
> > "Automated Test Results
> > Failed to talk to Greenwave.
> > The update can not be pushed: 1 of 2 required tests not found"
>
On 23 January 2018 at 09:25, Vít Ondruch wrote:
[..]
> > Well I think maintainers should chose the ideal solution for their case.
> If use of macros just complicates things too much, maybe use of branches
> might make more sense. On the other hand does it really make sense to
> enforce maintainin
On 01/23/2018 11:28 AM, Dominik 'Rathann' Mierzejewski wrote:
Hi, Florian.
On Monday, 22 January 2018 at 16:24, Florian Weimer wrote:
I updated redhat-rpm-config to instruct ld to reject linking shared objects
with undefined symbols. Such undefined symbols break symbol versioning
because the a
On Tuesday, 23 January 2018 at 11:28, Dominik 'Rathann' Mierzejewski wrote:
> Hi, Florian.
>
> On Monday, 22 January 2018 at 16:24, Florian Weimer wrote:
> > I updated redhat-rpm-config to instruct ld to reject linking shared objects
> > with undefined symbols. Such undefined symbols break symbol
On 01/20/2018 06:08 AM, Chris Adams wrote:
Once upon a time, Nico Kadel-Garcia said:
I don't see any modern scripting language where a leading 0 would lead
to interpreting a number as octal.
I suggest you check again; I don't see any where a leading 0 does NOT
lead to interpreting a number as
Florian Weimer wrote on 01/23/2018 12:24 AM:
In some cases (such as when a DSO is
loaded as a plugin and is expected to bind to symbols in the main
executable), undefined symbols are expected. In this case, you can
add
%undefine _strict_symbol_defs_build
to the RPM spec file to disable t
- Mail original -
De: "Neal Gompa"
>On Mon, Jan 22, 2018 at 8:33 AM, Dridi Boukelmoune
>
>>> I really do like this. There are only two issues I have with it:
>>>
>>> 1. This seems to mandate that all packages must be named by their
>>> import path. My golang package (snapd) is not, inten
Hello,
for everyone maintaining packages that are derivatives of the Mozilla
Firefox source code:
If you're updating to Firefox 58, I'd like to suggest that you include a
local patch.
Background: We are changing the default NSS database file format, and
Firefox needed to be changed to be compati
On Jan 23, 2018 12:41, wrote:
- Mail original -
De: "Neal Gompa"
>On Mon, Jan 22, 2018 at 8:33 AM, Dridi Boukelmoune
>
>>> I really do like this. There are only two issues I have with it:
>>>
>>> 1. This seems to mandate that all packages must be named by their
>>> import path. My gola
De: "Neal Gompa"
>> The issue is that the new Go macros are tightly wound into the forge
>> macros. I just want to be sure that we can leverage things like the
>> dependency generators without all the other stuff.
Hi Neal,
>I should probably not let this pass without clarifying:
> 3. if your
On 01/23/2018 10:25 AM, Fabio Valentini wrote:
For the record, my affected packages are (according to koschei, and as
of the time of writing this):
- gala (internal plugins)
- maya-calendar("ceil" reference missing, ppc64 only)
So it's a missing -lm on the linker command line.
- noise (intern
On Tue, Jan 23, 2018 at 5:45 AM, wrote:
>
>
> - Mail original -
> De: "Neal Gompa"
>
>>On Mon, Jan 22, 2018 at 8:33 AM, Dridi Boukelmoune
>>
I really do like this. There are only two issues I have with it:
1. This seems to mandate that all packages must be named by their
>>
On Mon, Jan 22, 2018 at 04:24:31PM +0100, Florian Weimer wrote:
> I updated redhat-rpm-config to instruct ld to reject linking shared objects
> with undefined symbols. Such undefined symbols break symbol versioning
> because the are not necessarily bound to the correct symbol version at run
> time
On 01/23/2018 01:49 PM, Daniel P. Berrange wrote:
On Mon, Jan 22, 2018 at 04:24:31PM +0100, Florian Weimer wrote:
I updated redhat-rpm-config to instruct ld to reject linking shared objects
with undefined symbols. Such undefined symbols break symbol versioning
because the are not necessarily bo
On Tue, Jan 23, 2018 at 10:32:49AM +0100, Pierre-Yves Chibon wrote:
> We just sent an announcement about this, sorry for being late on this.
>
> Basically, you can "waive" test results using waiverdb-cli (dnf install
> waiverdb-cli) which will allow the update to go through despite of the failing
On Tue, Jan 23, 2018 at 02:04:26PM +0100, Florian Weimer wrote:
> On 01/23/2018 01:49 PM, Daniel P. Berrange wrote:
> > On Mon, Jan 22, 2018 at 04:24:31PM +0100, Florian Weimer wrote:
> > > I updated redhat-rpm-config to instruct ld to reject linking shared
> > > objects
> > > with undefined symbo
On Tue, 2018-01-23 at 10:32 +0100, Pierre-Yves Chibon wrote:
>
> We just sent an announcement about this, sorry for being late on this.
>
> Basically, you can "waive" test results using waiverdb-cli (dnf install
> waiverdb-cli) which will allow the update to go through despite of the failing
> te
2018-01-22 0:38 GMT+01:00 Tao Zhao :
> Hi Mamoru,
>
> Thanks for the information! I've pinged his gmail. Let's see how it goes.
Hi Alick,
sorry, I missed that mail. I have given up looking after individual
packages, so make sure to use a meaningful subject if you want to
catch my attention. ;-)
2018-01-22 1:23 GMT+01:00 Greg Evenden :
> you might even be better to catch him over on the SUSE IRC channels, it might
> be worth a shot to see if anyone in SUSE Packages those packages an are up to
> date an Grab the Source RPM's from there
Good idea, but this shouldn't be necessary.
I'm wor
On Tue, Jan 23, 2018 at 07:36:08AM +0100, Igor Gnatenko wrote:
> > I'd really like to see us tend towards coming up with macros that
> > provide elegant fallbacks on EPEL. (The %license macro is a good
> > example.)
> There is no fallback for rich dependencies. There is no fallback for
> filetrigge
2018-01-22 20:21 GMT+01:00 Matthew Miller :
>
> I saw him mention that he'll be at DevConf.cz, so maybe someone can
> catch him there.
That must have been last year. :-) Unfortunately I can't make it this
time and only came last year to find new maintainers for my packages
and meet with old friend
On Tue, 2018-01-23 at 07:36 +0100, Igor Gnatenko wrote:
> On Mon, 2018-01-22 at 14:33 -0500, Matthew Miller wrote:
> > On Sat, Jan 20, 2018 at 02:23:16PM +0100, Igor Gnatenko wrote:
> > > What I'm trying to say here is that each time we want to
> > > implement
> > > some feature in Fedora, we eithe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496fd75a07
ea749cb
- --
- -Igor Gnatenko
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlpnPSEACgkQaVcUvRu8
X0zgYBAAqfV6lP/OHdB/tsCsojIw/xjjSt+1jhQzuBO
- Mail original -
De: "Neal Gompa"
>> 2. if your concern is that the *forge* macros are defective somewhere I'd
>> be curious where as you'd be the
>> first to report an actual technical problem. I've used them intensively in
>> rawhide and el7 with many different
>>rpm tools and the
On Tue, Jan 23, 2018 at 8:54 AM, wrote:
>
>
> - Mail original -
> De: "Neal Gompa"
>
>>> 2. if your concern is that the *forge* macros are defective somewhere I'd
>>> be curious where as you'd be the
>>> first to report an actual technical problem. I've used them intensively in
>>> raw
- Mail original -
De: "Neal Gompa"
> As long as I can do Obsoletes/Provides for the old name for the devel,
> unit-test,
BTW is anyone using the unit-test packages? Right now I do not generate them, I
don't need them, and making them work with autodeps would be hairy (deploying
with
On Tue, Jan 23, 2018 at 9:00 AM, wrote:
>
>
> - Mail original -
> De: "Neal Gompa"
>
>> As long as I can do Obsoletes/Provides for the old name for the devel,
>> unit-test,
>
> BTW is anyone using the unit-test packages? Right now I do not generate them,
> I don't need them, and making t
On Tue, Jan 23, 2018 at 2:48 PM, Igor Gnatenko
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496fd75a07
> ea749cb
This was announced to all package owners depending on tinyxml2 right
after the build succeed on f
On Tue, 2018-01-23 at 08:13 -0500, Matthew Miller wrote:
> On Tue, Jan 23, 2018 at 10:32:49AM +0100, Pierre-Yves Chibon wrote:
> > We just sent an announcement about this, sorry for being late on this.
> >
> > Basically, you can "waive" test results using waiverdb-cli (dnf install
> > waiverdb-cli
- Mail original -
De: "Fabio Valentini"
> So, if I understand correctly, both the forge stuff and the new macros for
> go packaging are completely opt-in?
> If that's correct, this looks like the best solution to me - as old
> packages can then be converted one at a time (which I am loo
On 01/23/2018 12:26 PM, Mamoru TASAKA wrote:
Florian Weimer wrote on 01/23/2018 12:24 AM:
In some cases (such as when a DSO is
loaded as a plugin and is expected to bind to symbols in the main
executable), undefined symbols are expected. In this case, you can
add
%undefine _strict_symbol
> - Mail original -
> De: "Neal Gompa"
>> I'm curious, what are you missing in the preamble ? As far as I can see it's
>> all there (even though some values
>> set to variables %gometa precomputes). I had it's right autogenerated some
>> parts of it in the past but it's all
>> converted
On Tue, Jan 23, 2018 at 9:40 AM, wrote:
>
>> - Mail original -
>> De: "Neal Gompa"
>
>>> I'm curious, what are you missing in the preamble ? As far as I can see
>>> it's all there (even though some values
>>> set to variables %gometa precomputes). I had it's right autogenerated some
>>>
On 16 January 2018 at 18:01, Tomasz Kłoczko wrote:
[..]
> >> https://bugzilla.redhat.com/show_bug.cgi?id=1529121
> >
> > I think you should find a new maintainer for libxml2, and libxslt, and
> > xmlsec1
> > because right now I have little time, and since Fedora changes the rules for
> > spec fi
On 12/17/2017 01:11 AM, nicolas.mail...@laposte.net wrote:
Hi,
I am proposing for inclusion a set of rpm technical files aimed at automating
the packaging of forge-hosted projects.
- Packaging draft: https://fedoraproject.org/wiki/More_Go_packaging
- https://pagure.io/packaging-committee/issue
As happens for most releases, I'm updating Boost in rawhide and
rebuilding the affected packages in a side tag (f28-boost).
https://fedoraproject.org/wiki/Changes/F28Boost166
If you maintain a package that depends on Boost please coordinate any
updates with me, so that any changes you make in th
Hello World!
My name is Christian Glombek (or simply Chris :) and I'd like to join the
Fedora Packagers Group. I'm currently a student of Electrical Engineering
and Business Management at RWTH University in Aachen, Germany.
My FAS and IRC handle is `lorbus` and on GitHub and Twitter I'm
`LorbusChr
On Tue, Jan 23, 2018 at 2:28 AM, Pierre-Yves Chibon wrote:
> Finally, if it turns out you need to push an update through despite of the
> test
> results, you can do so using waiver-cli (dnf install waiverdb-cli). We are
> working on integrating this into Bodhi itself, making this easier.
Good!
On Tue, Jan 23, 2018 at 9:07 AM, Tomasz Kłoczko
wrote:
If it will be no new actions to the end of this week I'm going to
raise FESCo ticket to takeover at least libxml2.
Yes, libxml2 is security-critical; we can't wait this long to apply
security patches. The Fedora package maintainer needs t
On Tue, 2018-01-23 at 08:42 -0700, Jerry James wrote:
>
> There are no instructions on how to use it on this wiki page. Okay,
> we'll try using --help:
>
> $ waiverdb-cli --help
> Usage: waiverdb-cli [OPTIONS]
>
> Creates new waivers against test results.
>
> Examples:
>
> waiverdb-
On 23 January 2018 at 15:59, wrote:
[..]
> That said... has the patch been proposed for inclusion upstream? It looks
> like Nick Wellnhofer is taking care of libxml2 upstream these days, so it
> shouldn't need to wait for Daniel. I see you only included a link to a
> Chromium bug report with the
On Tue, Jan 23, 2018 at 03:21:56PM +0100, Adam Williamson wrote:
> It's a bit off-topic, but...when this happens, what do we do about
> links? There are probably many links to this page. This applies to
> anything being 'converted' from the wiki to docs, I guess...can we make
> wiki URLs redirect t
On Sat, Jan 13, 2018 at 11:50:44PM +0100, Michael Schwendt wrote:
> On Fri, 12 Jan 2018 16:13:24 +0100, Pierre-Yves Chibon wrote:
>
> > I believe the script runs at least daily so if you see something wrong then
> > do
> > report it :)
>
> Here's a recently opened ticket about package "aide":
>
On 23/01/18 16:18, Adam Williamson wrote:
On Tue, 2018-01-23 at 08:42 -0700, Jerry James wrote:
Where are the instructions? Why is informing packagers, the group
most affected by this change, an afterthought? We should have been
told about all of this, in detail, prior to the thing being turn
(Resending with correct docs list cc. Sorry about that.)
On Tue, Jan 23, 2018 at 11:30:46AM -0500, Matthew Miller wrote:
> On Tue, Jan 23, 2018 at 03:21:56PM +0100, Adam Williamson wrote:
> > It's a bit off-topic, but...when this happens, what do we do about
> > links? There are probably many lin
On Tue, 2018-01-23 at 08:00 +0100, Florian Weimer wrote:
> On 01/22/2018 10:15 PM, Adam Jackson wrote:
> > On Mon, 2018-01-22 at 19:19 +0100, Florian Weimer wrote:
> > > Redeclarations in system headers are expected. Do you compile with
> > > -Wsystem-headers? Or do you something else which is un
On 23 January 2018 at 16:24, Tomasz Kłoczko wrote:
> On 23 January 2018 at 15:59, wrote:
> [..]
>> That said... has the patch been proposed for inclusion upstream? It looks
>> like Nick Wellnhofer is taking care of libxml2 upstream these days, so it
>> shouldn't need to wait for Daniel. I see yo
I wish this message wasn't crossposted everywhere, but I don't want to
lose any discussion by trimming the CC list. Sorry if replies generate
bounces for some.
> "nm" == nicolas mailhot writes:
nm> And the forge macros are now available since
nm> redhat-rpm-config-73-1.fc28 (I had missed th
On Tue, Jan 23, 2018 at 10:45 AM, Tomasz Kłoczko
wrote:
Strange only is that looks like this bug already is known more than
year!
Looks like two years... I followed the chain of links in the Red Hat
bugs, which claim this is already reported as
https://bugzilla.gnome.org/show_bug.cgi?id=7621
- Mail original -
De: "Neal Gompa"
> For snipping, use "[...]" notation to indicate skipped stuff. It's
> hard to tell otherwise.
Ok, that was easy to fix :)
--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsu
- Mail original -
De: "nicolas mailhot"
> Now that the non-Go part in redhat-rpm-macros is merged in devel I'll try to
> do a clean PR on go-srpm-macros.
> Then once Jan or Jakub accepts it it will be possible to play with the
> automation in devel and I'll be able to share my specs s
On Tue, Jan 23, 2018 at 10:32:49AM +0100, Pierre-Yves Chibon wrote:
> On Mon, Jan 22, 2018 at 01:57:34PM -0700, Jerry James wrote:
> > Here's something I didn't expect from the new ABI gate. Which, before
> > I go further, I think will be a great idea nearly all of the time. I
> > think avoiding
On Tue, Jan 23, 2018 at 02:21:02PM +0100, Adam Williamson wrote:
> On Tue, 2018-01-23 at 10:32 +0100, Pierre-Yves Chibon wrote:
> >
> > We just sent an announcement about this, sorry for being late on this.
> >
> > Basically, you can "waive" test results using waiverdb-cli (dnf install
> > waiverdb
I get this error after clicking the authorization link:
[16450:16491:0123/182437.407698:ERROR:browser_gpu_channel_host_factory.cc(120)]
Failed to launch GPU process.
Created new window in existing browser session.
127.0.0.1 - - [23/Jan/2018 18:24:37] "GET
/?error_description=Unknown+client+ID&erro
On 23 January 2018 at 18:20, Ralph Bean wrote:
I've removed the abicheck requirement from the greenwave policies for
> now until we know more:
> https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=
> 465f155d140a9fbe34f0f51dbfc2137b2900a6f8
>
Do we have to do anything to proceed
On 01/23/2018 01:28 AM, Pierre-Yves Chibon wrote:
> There are three tests that must pass in order for updates to go to stable:
>
> 0. dist.depcheck - to make sure the update's dependencies are available.
> 1. dist.abicheck - to make sure the update's ABI remains stable in a
>given Fedora relea
On 23/01/18 15:38 +0100, Florian Weimer wrote:
We could deactivate -z defs for F28 and reactivate it after the branch
for F29, giving packagers more time to fix issues.
I think that might be a good idea (given how late in the F28 process
we are) but for many packages it will just mean we have t
On Tue, Jan 23, 2018 at 05:56:47PM +, Jonathan Wakely wrote:
> On 23/01/18 15:38 +0100, Florian Weimer wrote:
> > We could deactivate -z defs for F28 and reactivate it after the branch
> > for F29, giving packagers more time to fix issues.
>
> I think that might be a good idea (given how late
On Tue, Jan 23, 2018 at 05:18:42PM +0100, Adam Williamson wrote:
> On Tue, 2018-01-23 at 08:42 -0700, Jerry James wrote:
> > Where are the instructions? Why is informing packagers, the group
> > most affected by this change, an afterthought? We should have been
> > told about all of this, in deta
On Tue, Jan 23, 2018 at 08:13:02AM -0500, Matthew Miller wrote:
> On Tue, Jan 23, 2018 at 10:32:49AM +0100, Pierre-Yves Chibon wrote:
> > We just sent an announcement about this, sorry for being late on this.
> >
> > Basically, you can "waive" test results using waiverdb-cli (dnf install
> > waiver
On Tue, Jan 23, 2018 at 06:37:56PM +0100, Rafael dos Santos wrote:
> On 23 January 2018 at 18:20, Ralph Bean wrote:
>
> I've removed the abicheck requirement from the greenwave policies for
> > now until we know more:
> > https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=
> > 46
On Tue, Jan 23, 2018 at 06:35:45PM +0100, Rafael dos Santos wrote:
> I get this error after clicking the authorization link:
>
> [16450:16491:0123/182437.407698:ERROR:browser_gpu_channel_host_factory.cc(120)]
> Failed to launch GPU process.
> Created new window in existing browser session.
> 127.0.
Pierre-Yves Chibon wrote:
> On Thursday, a new version of Bodhi was deployed that enabled Bodhi to
> gate updates based on test results. You may notice a "Test Gating
> Status" message in the right have side of the page.
...
> There are three tests that must pass in order for updates to go to stab
On 23 January 2018 at 19:22, Ralph Bean wrote:
> On Tue, Jan 23, 2018 at 06:35:45PM +0100, Rafael dos Santos wrote:
> > I get this error after clicking the authorization link:
> >
> > [16450:16491:0123/182437.407698:ERROR:browser_gpu_
> channel_host_factory.cc(120)]
> > Failed to launch GPU proce
François Cami wrote:
> On Tue, Jan 23, 2018 at 2:48 PM, Igor Gnatenko
> wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA256
>>
>>
https://src.fedoraproject.org/rpms/tinyxml2/c/3600750a8f1b0eaa6cab346496fd75a07
>> ea749cb
>
> This was announced to all package owners depending on tinyxml
On 23 January 2018 at 17:04, wrote:
[..]
>> Strange only is that looks like this bug already is known more than year!
>
>
> Looks like two years... I followed the chain of links in the Red Hat bugs,
> which claim this is already reported as
> https://bugzilla.gnome.org/show_bug.cgi?id=762100 and
- Mail original -
De: "Mátyás Selmeci"
Hi,
> This looks pretty cool!
Thanks for the feedback!
> One thing I notice in the limitations section of
> your draft is a lot of "we can't do XXX due to lack of release
> discipline..."
> Do you have any recommendations for Go programmers o
1 - 100 of 146 matches
Mail list logo
