> announcement should be made here too
+
> Rule of thumb: more communication is better.
Ack.
Change proposal for
https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master
"A week in advance, notify maintainers who depend on their package to rebuild
when there are abi/api chan
On 01/23/2018 05:12 PM, Adam Williamson wrote:
> The initial thought we - we being Tim, Kamil, Josef, Ralph and I - had
> is to simply invert the policy, if we can, so it becomes "the update
> passes *unless* we can find a 'fail' for any of the required tests". So
> all updates would be push-able (
On Wed, Jan 24, 2018 at 08:21:30AM -, François Cami wrote:
> > announcement should be made here too
> +
> > Rule of thumb: more communication is better.
>
> Ack.
>
> Change proposal for
> https://fedoraproject.org/wiki/Updates_Policy#Rawhide_.2F_devel_.2F_master
>
> "A week in advance, not
On Wed, Jan 24, 2018 at 03:25:48AM -0500, Randy Barlow wrote:
> On 01/23/2018 05:12 PM, Adam Williamson wrote:
> > The initial thought we - we being Tim, Kamil, Josef, Ralph and I - had
> > is to simply invert the policy, if we can, so it becomes "the update
> > passes *unless* we can find a 'fail'
On Jan 24, 2018 08:55, "Miroslav Suchý" wrote:
Dne 20.1.2018 v 12:27 Igor Gnatenko napsal(a):
> Why I'm writing this? I want to hear from you if you think it would be
good to
> prohibit (or advise, or whatever mechanism would work) usage if
conditionals in
> (at least) master branch to allow us t
24.01.2018 07:10 Florian Weimer wrote:
>
> On 01/22/2018 11:58 PM, Rafal Luzynski wrote:
> > I'd like to notify you that today I've finished my works on date
> > formatting in glibc, that means upstream. These changes are already
> > arriving to Fedora Rawhide (they should be there tomorrow) and w
2018-01-19 9:15 GMT+01:00 Adrian Reber :
> On Fri, Jan 19, 2018 at 06:50:16AM +0100, Nicolas Chauvet wrote:
>> 2018-01-18 22:25 GMT+01:00 Adrian Reber :
>> > libcdio upstream released the 2.0 version a few weeks ago and I will
>> > updated rawhide to the latest libcdio version. It comes with a new
On Tue, Jan 23, 2018 at 10:33:01PM +0100, Dominik 'Rathann' Mierzejewski wrote:
> On Tuesday, 23 January 2018 at 20:16, Matthew Miller wrote:
> > On Tue, Jan 23, 2018 at 12:25:56PM -0600, Rex Dieter wrote:
> > > > There are three tests that must pass in order for updates to go to
> > > > stable:
>
On Wed, 2018-01-24 at 09:34 +0100, Pierre-Yves Chibon wrote:
> On Wed, Jan 24, 2018 at 08:21:30AM -, François Cami wrote:
> > > announcement should be made here too
> >
> > +
> > > Rule of thumb: more communication is better.
> >
> > Ack.
> >
> > Change proposal for
> > https://fedoraproje
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
is anybody against of removal of libxml2-static package? It is not used by any
Fedora package.
- --
- -Igor Gnatenko
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEhLFO09aHZVqO+CM6aVcUvRu8X0wFAlpoTCQACgkQaVcUvRu8
X0yCbhAAku+w8JAHVpftAeDXmTIU
On 24.01.2018 07:02, Florian Weimer wrote:
On 01/24/2018 12:10 AM, Sandro Mani wrote:
I've proposed a change to update to giflib-5.x for F28+ [1] (which is
an incompatible update from the current giflib-4.x). I did some
initial testing in this COPR repo [1], and have hit a problem with
java-
On Wed, 24 Jan 2018 09:57:03 +0100
Adam Williamson wrote:
> On Wed, 2018-01-24 at 09:34 +0100, Pierre-Yves Chibon wrote:
> > On Wed, Jan 24, 2018 at 08:21:30AM -, François Cami wrote:
> > > > announcement should be made here too
> > >
> > > +
> > > > Rule of thumb: more communication is bet
Just a quick note if you've been seeing strange errors this morning,
like dnf crashing when doing something like a 'groupinstall' or a
'group update': it seems there was a storage issue during
synchronization of repodata for the most recent update push, and that's
causing problems like this. releng
Hi Rafal
Does that mean it is finally possible for a user to set its default date format
to ISO 8601 without switching its language to Danish English? Windows has been
allowing that for ages (which is only sensible, since iso 8601 is an
international standard, and numeric date representation s
Missing expected images:
Server dvd i386
Workstation live i386
Server boot i386
Kde live i386
Failed openQA tests: 14/129 (x86_64), 1/2 (arm)
New failures (same test did not fail in Rawhide-20180117.n.1):
ID: 187574 Test: x86_64 Server-dvd-iso install_repository_nfs_variation
URL: https://
On 01/24/2018 10:08 AM, nicolas.mail...@laposte.net wrote:
Does that mean it is finally possible for a user to set its default date format
to ISO 8601 without switching its language to Danish English? Windows has been
allowing that for ages (which is only sensible, since iso 8601 is an
interna
24.01.2018 10:08 nicolas.mail...@laposte.net wrote:
>
>
> Hi Rafal
>
>
> Does that mean it is finally possible for a user to set its default
> date format to ISO 8601 without switching its language to Danish English?
> [...]
No, this was not a part of my work. I was working only on how the
month n
- Original Message -
> From: "nicolas mailhot"
> To: "Jason L Tibbitts III"
> Cc: gol...@lists.fedoraproject.org, "Development discussions related to
> Fedora" ,
> "Discussion of RPM packaging standards and practices for Fedora"
>
> Sent: Tuesday, January 23, 2018 9:28:15 PM
> Subj
- Original Message -
> From: "Jason L Tibbitts III"
> To: "nicolas mailhot"
> Cc: gol...@lists.fedoraproject.org, "Development discussions related to
> Fedora" ,
> "Discussion of RPM packaging standards and practices for Fedora"
>
> Sent: Tuesday, January 23, 2018 6:00:24 PM
> Subj
- Mail original -
De: "Rafal Luzynski"
> Hi Rafal
>
>
> > Does that mean it is finally possible for a user to set its default
> > date format to ISO 8601 without switching its language to Danish English?
> > [...]
> No, this was not a part of my work. I was working only on how the
> mon
- Original Message -
> From: "nicolas mailhot"
> To: "Development discussions related to Fedora"
>
> Sent: Tuesday, January 23, 2018 7:45:06 PM
> Subject: Re: Re: Proposed Fedora packaging guideline: More Go packaging
>
>
>
> - Mail original -
> De: "Mátyás Selmeci"
>
>
On Tue, Jan 23, 2018 at 02:06:15PM -0500, R P Herrold wrote:
> On Tue, 23 Jan 2018, Daniel P. Berrange wrote:
>
> > What needs to be done for this ? I see my package "libvirt" present
> > in its UI
> >
> > https://apps.fedoraproject.org/koschei/package/libvirt
> >
> > but it says
> >
> > "
Rex Dieter wrote:
> Pierre-Yves Chibon wrote:
>> 1. dist.abicheck - to make sure the update's ABI remains stable in a
>>given Fedora release.
>
> I think it unwise to make item 1 a mandatory item at this point. I'd
> argue a large number of packages do not provide public api/abi that's
> wort
Jerry James wrote:
> Here's something I didn't expect from the new ABI gate.
Why did you not expect it? I pointed out this exact issue on January 13,
right after this change was announced, and ~5 days before it was implemented
without anybody responding to my objection:
https://pagure.io/fesco/
Dne 23.1.2018 v 19:03 Daniel P. Berrange napsal(a):
> 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
On 24 January 2018 at 09:04, Igor Gnatenko
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello,
>
> is anybody against of removal of libxml2-static package? It is not used by any
> Fedora package.
It is easy to (simple) check ..
[tkloczko@domek SPECS.fedora]$ egrep -e 'BuildRequ
On 24 January 2018 at 11:21, Tomasz Kłoczko wrote:
[..]
> It is easy to (simple) check ..
>
> [tkloczko@domek SPECS.fedora]$ egrep -e 'BuildRequires:.*libxml-static' *
> [tkloczko@domek SPECS.fedora]$
Really sorry.
Typo in regexp (s/libxml/libxml2/) but result still is the same:
[tkloczko@domek
> Just FTR: above we have "I think" vs "in practice, it looks not like you
> may think".
> Real engineering is about 1) testing, 2) testing, 3) testing.
> "Assumption" like, "I think" is/should be the real enemy of each
> engineer.
>
> Stricter use of branching will have yet another effects that f
> Oh it definitely does.
>
> I am handling mass rebuilds of Ruby packages or updates of Ruby on
> Rails. This is complex task requiring touching plenty of packages. Due
> to update of Rails in master, I simply cannot contact maintainers of all
> packages and assuring their branches still works. I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2018-01-24 at 11:21 +, Tomasz Kłoczko wrote:
> On 24 January 2018 at 09:04, Igor Gnatenko
> wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Hello,
> >
> > is anybody against of removal of libxml2-static package?
Hi folks!
So, I just wrote a note updating the status of the update gating
situation, in the FESCo ticket where turning the gating on was
approved. If you want all the details (that I know, anyway) of where
we stand and what's going on to try and sort things out, here it is:
https://pagure.io/fe
Fabio Valentini wrote:
> My reasoning:
>
> There are many reasons why .spec files have to diverge between branches,
> including for:
> - mass rebuilds after branching a new fedora release,
That is a limitation in rel-eng tooling: If a mass rebuild is needed after
branching, it is surely needed i
Sérgio Basto wrote:
> %if 0%{?fedora}
> BuildRequires: python2-six
> %else
> BuildRequires: python-six
> %endif
BuildRequires: python%{!?rhel:2}-six
Kevin Kofler
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an emai
Igor Gnatenko wrote:
> Why I'm writing this? I want to hear from you if you think it would be
> good to prohibit (or advise, or whatever mechanism would work) usage if
> conditionals in (at least) master branch to allow us to develop features
> faster. Thoughts? Suggestions?
While I would not pers
On Wed, Jan 24, 2018 at 4:04 AM, Igor Gnatenko
wrote:
>
> Hello,
>
> is anybody against of removal of libxml2-static package? It is not used by any
> Fedora package.
I would appreciate it if it wasn't removed. I'm using the
libxml2-static (along with a number of other static libraries) in
experim
- Mail original -
De: "Jakub Cajka"
Hi Jakub,
>> For my part I doubt I'll ever use it in EL6 since I did it
>> for Go and the EL6 Go stack is really too old for a merge to be interesting.
>> Anyway I'll certainly let you know when I feel the time is right (but do not
>> block on me!)
>
On 24 January 2018 at 11:41, Igor Gnatenko wrote:
[..]
> > Other changes discarded from my set of changes:
>
> Please, don't mix issues / suggestions. I was asking ONLY about
> libxml2-static.
>
And I'm only using your email to show which other changes your radar does
not detected :P
I'm using
On 24/01/18 13:15 +, Tomasz Kłoczko wrote:
On 24 January 2018 at 11:41, Igor Gnatenko
wrote:
[..]
> Other changes discarded from my set of changes:
Please, don't mix issues / suggestions. I was asking ONLY about
libxml2-static.
And I'm only using your email to show which other changes
On 09/27/2017 03:11 PM, Chris Adams wrote:
One thing that is not mentioned: how much information is stored in the
binaries? How much larger will the resulting binaries be?
We currently see a size increase of about 1% per actually annotated
executable or DSO in Fedora rawhide.
(But not every
On 23/01/18 21:13 +, James Hogarth wrote:
On 23 Jan 2018 15:39, "Jonathan Wakely" wrote:
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
On 24/01/18 13:51 +, Jonathan Wakely wrote:
On 23/01/18 21:13 +, James Hogarth wrote:
On 23 Jan 2018 15:39, "Jonathan Wakely" wrote:
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/wi
On 24 January 2018 at 11:21, Tomasz Kłoczko
wrote:
[..]
> Fact that those libraries are listed in:
>
> Libs.private: -lz -llzma -lm
>
> does not mean that some devel packages are needed. Libs.private is
> used on STATIC linking!!! Use static linking in Fedora is highly
> REDUCED
> So far
On Tuesday, 23 January 2018 at 07:36, 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 either n
I have a package which indirectly calls qmake (from Qt5). Is there a
way to inject the standard build flags using environment variables, or
do I have to patch the invocation of the qmake command itself to pass
the flags, similar to what %{qmake_qt5} does?
Would it make to add rpmbuild-qmake o
I've tried to mostly stay out of this discussion because I to *NOT*
consider myself an expert.
I've been a Fedora package maintainer for several years now and have
learned more than I ever thought I would but I am not:
- a programmer
- an expert git user
- a *nix guru
>From my simplistic point of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2018-01-24 at 14:35 +, Tomasz Kłoczko wrote:
> On 24 January 2018 at 11:21, Tomasz Kłoczko
> wrote:
> [..]
> > Fact that those libraries are listed in:
> >
> > Libs.private: -lz -llzma -lm
> >
> > does not mean that some devel
De: "Jakub Cajka"
> Very nice list, it would be nice to have it as sub-wiki page of guidelines. I
> have took liberty to add
> few points.
Ok, I put it here so people have a place to work on it
https://fedoraproject.org/wiki/More_Go_packaging#Go_developer_guidance:_making_your_software_third-
On Tue, 2018-01-23 at 09:17 +0100, Florian Weimer wrote:
> 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/i
On Wed, Jan 24, 2018 at 10:05:56AM +0100, Dan Horák wrote:
> > +1 - I'd say a mail to the list *and* directly to each affected
> > maintainer. devel@ is a firehose and some maintainers may not keep up
> > with it.
> isn't devel-announce better fit than devel? Because its description [1]
> lists "-
Florian Weimer wrote:
> I have a package which indirectly calls qmake (from Qt5). Is there a
> way to inject the standard build flags using environment variables, or
> do I have to patch the invocation of the qmake command itself to pass
> the flags, similar to what %{qmake_qt5} does?
%{qmake_qt
Rex Dieter wrote:
> Florian Weimer wrote:
>
>> I have a package which indirectly calls qmake (from Qt5). Is there a
>> way to inject the standard build flags using environment variables, or
>> do I have to patch the invocation of the qmake command itself to pass
>> the flags, similar to what %{q
Intel has pulled the 20180108 microcode due to some CPUs crashing
(uncommanded reboots are a crash), and they have reverted latest
recommended to 20171117. And they appear to be recommending no longer
deploying the 20180108 microcode, but I can't tell if they are
directing this to firmware oems or
Rex Dieter wrote:
> Rex Dieter wrote:
>
>> Florian Weimer wrote:
>>
>>> I have a package which indirectly calls qmake (from Qt5). Is there a
>>> way to inject the standard build flags using environment variables, or
>>> do I have to patch the invocation of the qmake command itself to pass
>>> t
On 01/24/2018 07:18 PM, Rex Dieter wrote:
Rex Dieter wrote:
Rex Dieter wrote:
Florian Weimer wrote:
I have a package which indirectly calls qmake (from Qt5). Is there a
way to inject the standard build flags using environment variables, or
do I have to patch the invocation of the qmake com
Florian Weimer wrote:
> On 01/24/2018 07:18 PM, Rex Dieter wrote:
>> Rex Dieter wrote:
>>
>>> Rex Dieter wrote:
>>>
Florian Weimer wrote:
> I have a package which indirectly calls qmake (from Qt5). Is there a
> way to inject the standard build flags using environment variables,
On Wed, Jan 24, 2018 at 10:04:36AM +0100, Igor Gnatenko wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hello,
>
> is anybody against of removal of libxml2-static package? It is not used by any
> Fedora package.
Static libraries are useful occasionally, especially as Neal said for
On Tue, 2018-01-23 at 19:52 -0500, Jared K. Smith wrote:
> On Tue, Jan 23, 2018 at 6:56 PM, Howard Howell
> wrote:
> > Due to that last line, issued su and password and ran it again:
> >
> > # lshw
> >
> > Segmentation fault (core dumped)
> >
> > #
>
> Due to the fact that you're having segfau
Hi,
On 01/20/2018 01:15 AM, Patrick Monnerat wrote:
> On 01/19/2018 11:07 PM, Alois Mahdal wrote:
>> Hi Fedora!
>>
>> TL;DR: What do experienced C/C++ packagers think about this PR,
>> considering potential future appearance in Fedora?
>>
>> https://github.com/naelstrof/slop/pull/94
>>
> Usin
On 01/23/2018 06:56 PM, Howard Howell wrote:
Due to that last line, issued su and password and ran it again:
# lshw
Segmentation fault (core dumped)
ok, great---so now do 'gdb lshw', type 'r' in gdb, and see where it crashes.
You may need to debuginfo-install few packages if gdb says it can't
On 01/21/2018 07:23 AM, Tom Hughes wrote:
Not really. It's a grab bag of different things that may or not be
related to Wayland.
I think this problem is compounded by the fact that Wayland and several
other system features such as Gnome session setup are very integrated,
and it's hard to debu
On Wed, Jan 24, 2018 at 1:37 PM, Przemek Klosowski
wrote:
Can anyone suggest ways of debugging this?
Run coredumpctl to see what processes crashed. There should be at least
a gnome-shell crash, maybe also a gnome-session crash, maybe also an
XWayland crash. Usually only the gnome-shell and g
On 24 January 2018 at 11:32, Samuel Rakitničan <
srakitni...@fedoraproject.org> wrote:
> > 1) easier to test upgrades between Fedora versions
> >
> > As each Fedora major release may have in updates only security and
> critical
> > fixes and ABI (libraries SONAME changes) will be completely locked
Rex Dieter wrote:
> Florian Weimer wrote:
Oh, *indirectly* calls qmake, that may be trickier. Which package?
>> pcp: https://bugzilla.redhat.com/show_bug.cgi?id=1538187
> ...
>> I don't want to copy this solution in the dozen or so packages which
>> need this (and I probably would have mis
On 01/24/2018 10:05 PM, Rex Dieter wrote:
Rex Dieter wrote:
Florian Weimer wrote:
Oh, *indirectly* calls qmake, that may be trickier. Which package?
pcp: https://bugzilla.redhat.com/show_bug.cgi?id=1538187
...
I don't want to copy this solution in the dozen or so packages which
need th
On Wed, 24 Jan 2018 14:37:30 -0500
Przemek Klosowski wrote:
> For instance, I observed a reliable desktop session crash on exiting
> Pan newsreader. I don't know how to debug it because it crashes the
> session and I get logged out.
I think this is because the C++ used in Pan is incompatible wit
Florian Weimer wrote:
> On 01/24/2018 10:05 PM, Rex Dieter wrote:
>> Rex Dieter wrote:
>>
>>> Florian Weimer wrote:
>>
>> Oh, *indirectly* calls qmake, that may be trickier. Which package?
>>
pcp: https://bugzilla.redhat.com/show_bug.cgi?id=1538187
>>> ...
I don't want to copy th
Florian Weimer wrote:
>> * Adapt packages to use the wrapper. this can take the form of explicitly
>> setting QMAKE (or equivalent), adjusting PATH to prefer the qt5 wrapper
>> dir, or patching, or some combination of the above.
>>
>> In the specific case of pcp, it supports QMAKE, so it's a one
On Wed, Jan 24, 2018 at 12:13 PM, Chris Murphy wrote:
> Intel has pulled the 20180108 microcode due to some CPUs crashing
> (uncommanded reboots are a crash), and they have reverted latest
> recommended to 20171117. And they appear to be recommending no longer
> deploying the 20180108 microcode, b
Greetings, all!
The elections for Council - January 2018 have concluded, and
the results are shown below.
Council is electing 2 seats this time.
A total of 142 ballots were cast, meaning a candidate
could accumulate up to 710 votes (142 * 5).
The results for the elections are as follows:
# vo
Greetings, all!
The elections for Mindshare - January 2018 have concluded, and
the results are shown below.
Mindshare is electing 2 seats this time.
A total of 124 ballots were cast, meaning a candidate
could accumulate up to 620 votes (124 * 5).
The results for the elections are as follows:
Greetings, all!
The elections for FESCo - January 2018 have concluded, and
the results are shown below.
FESCo is electing 5 seats this time.
A total of 143 ballots were cast, meaning a candidate
could accumulate up to 1001 votes (143 * 7).
The results for the elections are as follows:
# votes
On Thu, Jan 25, 2018 at 01:47:13AM +0100, Jan Kurik wrote:
> The results for the elections are as follows:
>
> # votes | name
> - +--
> 703 | Kevin Fenzi (nirik)
> 579 | Adam Miller (maxamillion)
> 512 | Jared Smith (jsmith)
> 503 | Josh Boyer
On Wed, Jan 24, 2018 at 11:15 AM, Matthew Miller
wrote:
> On Wed, Jan 24, 2018 at 10:05:56AM +0100, Dan Horák wrote:
>> > +1 - I'd say a mail to the list *and* directly to each affected
>> > maintainer. devel@ is a firehose and some maintainers may not keep up
>> > with it.
>> isn't devel-announce
Le 22/01/2018 à 16:24, Florian Weimer a écrit :
> 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#1535422
74 matches
Mail list logo
