On 20 January 2018 at 07:23, Johannes Lips wrote:
> Well, of course, but the issue is not the change itself or anything. It's
> just the implementation and the lack of information for the maintainer.
> The maintainer just sees a git commit without additional information other
> than the scriplets
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
I know that many of you like to have just one branch which builds everywhere
(starting from el6), but this really slows down development of Fedora for many
years. Let me show some examples:
* File-triggers are not supported by el6/el7 RPM, s
On Jan 20, 2018 12:29, "Igor Gnatenko"
wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
I know that many of you like to have just one branch which builds everywhere
(starting from el6), but this really slows down development of Fedora for
many
years. Let me show some examples:
* F
On Sat, Jan 20, 2018 at 5:27 AM, Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:
>
> * File-triggers are not supported by el6/el7 RPM, so every package which
> has
> icons should have some number of scriptlets conditionalized by %if
> 0%{?rhel}
> && 0%{?rhel} <= 7.
>
Could this be easil
On Sat, Jan 20, 2018 at 7:58 AM, Richard Shaw wrote:
> On Sat, Jan 20, 2018 at 5:27 AM, Igor Gnatenko
> wrote:
>>
>>
>> * File-triggers are not supported by el6/el7 RPM, so every package which
>> has
>> icons should have some number of scriptlets conditionalized by %if
>> 0%{?rhel}
>> && 0%{?rhe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2018-01-20 at 06:58 -0600, Richard Shaw wrote:
> On Sat, Jan 20, 2018 at 5:27 AM, Igor Gnatenko <
> ignatenkobr...@fedoraproject.org> wrote:
>
> >
> > * File-triggers are not supported by el6/el7 RPM, so every package which
> > has
> > icon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2018-01-20 at 13:52 +0100, Fabio Valentini wrote:
> I find it hard to track changes to the Packaging Guidelines, and when those
> changes are made, they sometimes only apply to certain branches (or only to
> rawhide), and it's no longer clear
On 20 January 2018 at 12:58, Richard Shaw wrote:
[..]
> %if 0%{?fedora}
> Recommends: ...
> %else
> Requires: ...
> %endif
>
> does not hurt readability much.
>
> WIth large libraries that are already complicated that's more difficult,
> but in that case major updates are discouraged within a rel
Hi, any progress on this?
Best regards
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
2018-01-20 14:57 GMT+01:00 Reindl Harald :
>
>
> Am 20.01.2018 um 14:47 schrieb Germano Massullo:
>>
>> Hi, any progress on this?
>
>
> you likely gain more when you don't lack the context
>
> there is no single message with subject "Rstudio" in the archive and even if
> - you can't demand others t
Hello Anderson and welcome to Fedora!
- Original Message -
> From: "Anderson Sasaki"
> To: devel@lists.fedoraproject.org
> Sent: Friday, January 19, 2018 5:30:05 PM
> Subject: Self Introduction: Anderson Sasaki
>
> Hello all,
>
> My name is Anderson Sasaki and I recently joined the Red
Just for the record list of things which are now on crash course with
EPEL/RHEL Fedora which are widely used in Fedora specs:
On EPEL/RHEL in spec must be present in spec:
- BuildRoot
- %clean
- %defattr() in %files
NO ONE adds now any %ifings around those parts of the specs (just please do
not pr
On samedi 20 janvier 2018 14:47:20 CET Germano Massullo wrote:
> Hi, any progress on this?
> Best regards
I had a quick look at it, the problem seems t is bndling precompiled binaries
for GWT/Gin/Selenium especially. This is quite a mess to untangle.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2018-01-20 at 15:27 +, Tomasz Kłoczko wrote:
> Just for the record list of things which are now on crash course with
> EPEL/RHEL Fedora which are widely used in Fedora specs:
> On EPEL/RHEL in spec must be present in spec:
> - BuildRoot
>
I have few things but they aren't urgent, so better you take your shower
and rest from your travel.
On 19 January 2018 at 23:22, Adam Williamson
wrote:
> Hi folks! I'm proposing we cancel the QA meeting on Monday. It's been a
> couple of weeks, but I don't have anything super urgent for discuss
Does anyone know how to contact Lameire Alexis? I have tried via bug
https://bugzilla.redhat.com/show_bug.cgi?id=1520562 and alexises on Freenode
IRC without success.
--
Peter Oliver
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscr
On 20/01/18 13:52, Fabio Valentini wrote:
> On Jan 20, 2018 12:29, "Igor Gnatenko" > TL;DR:
>> - We need an authoritative source that tells us packagers which
>> Guidelines apply to which branch (or what has to be done differently -
>> or can be done better - in, for example, f26 when compared to
Hi, guys,
I'm sorry, but wyland is a disaster for me. I do work on lots
of different software platforms, and things are just not working well.
They kind-of-work, which is the really worst condition one can have.
My new video board won't work with wyland, my pixycam software won't
work wi
On Sat, Jan 20, 2018 at 12: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 inte
On 20/01/18 19:14, Howard Howell wrote:
> Hi, guys,
> I'm sorry, but wyland is a disaster for me. I do work on lots
> of different software platforms, and things are just not working well.
> They kind-of-work, which is the really worst condition one can have.
For me, this looks more lik
$ grep . /sys/devices/system/cpu/vulnerabilities/*
/sys/devices/system/cpu/vulnerabilities/meltdown:Mitigation: PTI
/sys/devices/system/cpu/vulnerabilities/spectre_v1:Vulnerable
/sys/devices/system/cpu/vulnerabilities/spectre_v2:Mitigation: Full
generic retpoline
All of my machines show this same
On Fri, 19 Jan 2018 22:53:30 -0500, Dusty Mabe wrote:
> On 01/19/2018 10:39 PM, Reindl Harald wrote:
> Thanks!
> I didn't know about this, but it's not exactly what I'm looking for because
> that seems
> to includ everything that has been built. I'm looking more specifically for
> just a repo
Maybe create a solution based on "koji download-build --help"?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On 20 January 2018 at 06:27, Igor Gnatenko
wrote:
>
> Even if people hope next version of EL will be better in this, it doesn't mean
> that el6/el7 can be fixed easily.
>
>
> Why I'm writing this? I want to hear from you if you think it would be good to
> prohibit (or advise, or whatever mechani
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=Koji Repo
>> baseurl=https://koji.fedoraproject.org/repos/f$releas
On 20/01/18 05:08, 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 numb
On 20 January 2018 at 23:26, Stephen John Smoogen wrote:
[..]
> As EPEL is the only reason I stay in Fedora.. I would like to make
> sure it doesn't cause developers that much problems. As such I would
> be interested in seeing if the macros that Neal said could be better
> implemented throughout
27 matches
Mail list logo