Hi,
Kaleb S. KEITHLEY wrote on Thu, Jan 18, 2018 at 01:16:35PM -0500:
> The LizardFS FSAL is GPLv3. NFS-Ganesha is LGPLv3+.
>
> From a Fedora packaging standpoint is it acceptable to build a GPLv3
> plug-in for an otherwise LGPLv3+ binary?
>
> If the licenses were reversed, I'd be reasonably co
On Fri, Jan 19, 2018 at 8:51 AM, Igor Gnatenko
wrote:
> On Fri, 2018-01-19 at 07:53 +0100, Alexander Ploumistos wrote:
>> Should the scriptlets be removed only in rawhide, or can I apply the
>> changes in F26 and F27?
>
> They can be removed for all supported Fedora.
Thanks, the recent thread on
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
> > soname and I will also rebuild all depende
Dominique Martinet wrote on Fri, Jan 19, 2018 at 09:04:46AM +0100:
> In principle this should be fine, VLC does that too -- libvlc (the core)
> is LGPL and vlc itself with the gui is GPL.
(It occured to me that VLC isn't in fedora so that doesn't help much
with regards to packaging, but I guess th
On Fri, 2018-01-19 at 07:59 +0100, Thomas Haller wrote:
> the message doesn't give much motivation beside "can be avoided in
> many
> cases". I would be intrested in your exact criticism.
>
Hello,
Don't take this personally (I feel you thought some offense). I never
said NetworkManager sucks and
On Friday, 19 January 2018 at 04:16, Michael Schwendt wrote:
> On Thu, 18 Jan 2018 20:07:27 -0600, Rex Dieter wrote:
>
> > I can
> > dnf install .i686
> >
> > and I see no 64bit packages pulled in.
>
> With F27,
>
> dnf install wine.i686
>
> really pulls in various x86_64 alongside their i6
19.01.2018 04:54 Michael Cronenworth wrote:
> [...]
> Yes. Yes. There are cases where the 64-bit binary doesn't run and the 32-bit
> one
> does. There are cases where the software is 32-bit only and no longer
> supported but
> still needed to export data.
>
> Until Microsoft decides to abandon 32-
On Fri, 2018-01-19 at 10:02 +0100, David Demelier wrote:
> On Fri, 2018-01-19 at 07:59 +0100, Thomas Haller wrote:
> > the message doesn't give much motivation beside "can be avoided in
> > many
> > cases". I would be intrested in your exact criticism.
> >
>
> Hello,
>
> Don't take this personal
Michael Cronenworth wrote:
> Yes. Yes. There are cases where the 64-bit binary doesn't run and the
> 32-bit one does. There are cases where the software is 32-bit only and no
> longer supported but still needed to export data.
>
> Until Microsoft decides to abandon 32-bit we will still need it.
I
On 01/18/2018 11:50 PM, Igor Gnatenko wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello,
Does anybody know why we are still using %{?_isa} thing?
DNF/libsolv forcefully install 64bit package for any 32bit package in
transaction. So it is not possible to get 32bit package without 64b
David Demelier wrote:
> I just think there are many network possibilities on Linux and
> therefore I was proposing to not add a mandatory default in Core.
> Especially for people creating extremely minimal appliance (raspberry
> pi, firewall) where both network script and systemd-networkd may
> alr
On Fri, Jan 19, 2018 at 11:48:52AM +0100, Thomas Haller wrote:
> When you say "Core" group, what are the practical effects of removing
> it? You can uninstall NetworkManager on Fedora today. Do you mean, it
> should not be installed by default? But you need a way to connect to
> the network on a ne
On 19 January 2018 at 11:44, Miroslav Lichvar wrote:
> On Fri, Jan 19, 2018 at 11:48:52AM +0100, Thomas Haller wrote:
>> When you say "Core" group, what are the practical effects of removing
>> it? You can uninstall NetworkManager on Fedora today. Do you mean, it
>> should not be installed by defa
On 17 January 2018 at 17:13, Matthew Miller wrote:
> On Tue, Jan 16, 2018 at 08:18:42AM -0500, Josh Boyer wrote:
>> - Better Git frontend for CentOS
>> - Possibility to submit PRs against RHEL branches
>> - Easy to see changes from RHEL and Fedora (and CentOS).
>> What are some others?
>
> I'd lik
Hello guys!
I wanted to let you know I have decided to create additional subpackage
'ghostscript-tools-dvipdf' after some discusssions. It is because the
'dvipdf' tool requires 'dvips' utility to work correctly, which is provided
in 'texlive-dvips' subpackage. This resulted in lot of texlive packa
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 Fri, Jan 19, 2018 at 7:34 AM, James Hogarth wrote:
> On 19 January 2018 at 11:44, Miroslav Lichvar wrote:
>> On Fri, Jan 19, 2018 at 11:48:52AM +0100, Thomas Haller wrote:
>>> When you say "Core" group, what are the practical effects of removing
>>> it? You can uninstall NetworkManager on Fedo
*William Moreno Reyes*
Colaborador Proyecto Fedora | Nicaragua
IRC: williamjmorenor Canales: #fedora-latam ; #fedora-ni
https://fedoraproject.org/wiki/User:Williamjmorenor
2018-01-18 12:24 GMT-06:00 Brian Exelbierd :
> We are looking for interested people who are willing to write docs in
> perso
On 18/01/18 19:45, Sérgio Basto wrote:
> On Thu, 2018-01-18 at 20:17 +0100, Igor Gnatenko wrote:
>> Hello,
>>
>> I'm working on removing all this cruft from all our packages (and
>> creating
>> conditionals for all packages which have epel branch).
>
>> Unfortunately some maintainers adding them b
On Fri, Jan 19, 2018 at 9:01 AM, J. Randall Owens
wrote:
> On 18/01/18 19:45, Sérgio Basto wrote:
>> On Thu, 2018-01-18 at 20:17 +0100, Igor Gnatenko wrote:
>>> Hello,
>>>
>>> I'm working on removing all this cruft from all our packages (and
>>> creating
>>> conditionals for all packages which hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2018-01-19 at 14:01 +, J. Randall Owens wrote:
> On 18/01/18 19:45, Sérgio Basto wrote:
> > On Thu, 2018-01-18 at 20:17 +0100, Igor Gnatenko wrote:
> > > Hello,
> > >
> > > I'm working on removing all this cruft from all our packages (an
Michael Schwendt wrote:
> On Thu, 18 Jan 2018 20:07:27 -0600, Rex Dieter wrote:
>
>> I can
>> dnf install .i686
>>
>> and I see no 64bit packages pulled in.
>
> With F27,
>
> dnf install wine.i686
>
> really pulls in various x86_64 alongside their i686 builds.
wine is an exception, it does
On jeudi 18 janvier 2018 23:08:50 CET Dominik 'Rathann' Mierzejewski wrote:
>
> Please add me as co-maintainer, they're dependencies of one of my
> packages, too.
>
> Regards,
> Dominik
Hi Dominik,
I've just added you as a co-admin on both packages as you requested. I intend
to do an update on
On 01/19/2018 05:22 AM, Kevin Kofler wrote:
I'm not saying that 32-bit WINE should go away nor that the 64-bit
repository should not include it as a multilib package. I'm saying that
installing WINE on an x86_64 system should not force you to install the 32-
bit multilib version.
You can use 64
On 19 January 2018 at 03:16, Michael Schwendt wrote:
> On Thu, 18 Jan 2018 20:07:27 -0600, Rex Dieter wrote:
>
>> I can
>> dnf install .i686
>>
>> and I see no 64bit packages pulled in.
>
> With F27,
>
> dnf install wine.i686
wine is completely brain damaged example.
Doesn't matter wine.i686 or
On 01/19/2018 09:32 AM, Tomasz Kłoczko wrote:
IMHO wine as the package is broken by design. Maintainer of the wine
just over complicated almost everything what was possible to over
complicate.
It's not broken. It's just the nature of Windows binaries. Users expect "dnf install
wine" to install
On Fri, Jan 12, 2018 at 04:51:20PM +0100, Tomasz Torcz 👁️ wrote:
> Taking the advantage of the fact that developers of both (fedora and
> systemd) attend
> this list, let me ask: will we get systemd v237 in Fedora 28?
> We have a bit over a month until branching. As WireGuard support got
> m
Hello all,
My name is Anderson Sasaki and I recently joined the Red Hat crypto team.
I have been working with cryptography and HSM's (Hardware Security Modules) for
a while (8 years or so).
My objective here will be to help the maintenance of PKCS#11 related packages
and to contribute to related
On Fri, Jan 19, 2018 at 11:02 AM, Tomasz Torcz 👁️ wrote:
> On Fri, Jan 12, 2018 at 04:51:20PM +0100, Tomasz Torcz 👁️ wrote:
>> Taking the advantage of the fact that developers of both (fedora and
>> systemd) attend
>> this list, let me ask: will we get systemd v237 in Fedora 28?
>> We have a
I think that problem is somewhere else and it is IMO fundamental problem.
Everything hangs on one simple fact that master branch of the Fedora
packages is used now to build packages from the other Fedora-based
distributions.
It would be b*dy easy remove all icons caches updates if other
distributi
On 19 January 2018 at 15:48, Michael Cronenworth wrote:
> On 01/19/2018 09:32 AM, Tomasz Kłoczko wrote:
>>
>> IMHO wine as the package is broken by design. Maintainer of the wine
>> just over complicated almost everything what was possible to over
>> complicate.
>
>
> It's not broken. It's just th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2018-01-19 at 16:37 +, Tomasz Kłoczko wrote:
> I think that problem is somewhere else and it is IMO fundamental problem.
>
> Everything hangs on one simple fact that master branch of the Fedora
> packages is used now to build packages fr
On Fri, Jan 19, 2018 at 11:15 AM, Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:
> I think real problem here is that people want same spec to build
> everywhere.
> And we are not able to teach people to not do this. Only way how we can
> teach
> them is to make it impossible (e.g. deny p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2018-01-19 at 11:22 -0600, Richard Shaw wrote:
> On Fri, Jan 19, 2018 at 11:15 AM, Igor Gnatenko <
> ignatenkobr...@fedoraproject.org> wrote:
>
> > I think real problem here is that people want same spec to build
> > everywhere.
> > And we a
On Fri, Jan 19, 2018 at 12:22 PM, Richard Shaw wrote:
> On Fri, Jan 19, 2018 at 11:15 AM, Igor Gnatenko
> wrote:
>>
>> I think real problem here is that people want same spec to build
>> everywhere.
>> And we are not able to teach people to not do this. Only way how we can
>> teach
>> them is to
===
#fedora-meeting: FESCO (2018-01-19)
===
Meeting started by maxamillion at 16:00:33 UTC. The full logs are
available at
https://meetbot.fedoraproject.org/fedora-meeting/2018-01-19/fesco.2018-01-19-16.00.log.html
.
Meeting summa
Would have been nice to get some more background information than just the git
commit message. Then one needs to do research to find this thread and the
related ticket. I don't have time to follow all the discussions/tickets on
devel or anywhere else, but this is even more time consuming. Especi
On Fri, Jan 19, 2018 at 06:37:09PM +0100, Igor Gnatenko wrote:
> Within Fedora, those conditionals are not happening that often.. But
> I would really love to see better separation of Fedora and EPEL.
> Because EPEL **slows down improvements of Fedora**.
As you know, I want to go the other way. I
On 19 January 2018 at 18:42, Johannes Lips wrote:
> Would have been nice to get some more background information than just the
> git commit message. Then one needs to do research to find this thread and
> the related ticket. I don't have time to follow all the discussions/tickets
> on devel or an
On Fri, 19 Jan 2018 15:32:13 +, Tomasz Kłoczko wrote:
> > dnf install wine.i686
>
> wine is completely brain damaged example.
Maybe. Something on x86_64 is broken nevertheless.
If memory serves correctly, Yum could handle it, but dnf seems to run into
non-arch-specific explicit dependenc
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
Background: I'm packaging `slop` in my COPR, as "experimental" builds.
Some day I'd like to propose it to Fedora, but it's n
On Fri, Jan 19, 2018 at 11:36:36AM -0500, Neal Gompa wrote:
> On Fri, Jan 19, 2018 at 11:02 AM, Tomasz Torcz 👁️
> wrote:
> > On Fri, Jan 12, 2018 at 04:51:20PM +0100, Tomasz Torcz 👁️ wrote:
> >> Taking the advantage of the fact that developers of both (fedora and
> >> systemd) attend
> >> thi
Hi folks! I'm proposing we cancel the blocker review meeting for
Monday. There are only two proposed blockers, which doesn't seem worth
running a meeting for. HOWEVER, I do suggest that folks take a look at
the proposed blockers and vote in-bug, so we can move forward on them.
Thanks!
--
Adam Will
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 discussion,
and at the time of the meeting I'm likely to be trying to take a shower
after 16 hours of traveling from the West Coast to Czechia, so possibly
not in shap
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
Using the project version for soname is usually a bad idea, because
soname i
On Fri, 2018-01-19 at 18:37 +0100, Igor Gnatenko wrote:
> On Fri, 2018-01-19 at 11:22 -0600, Richard Shaw wrote:
> > On Fri, Jan 19, 2018 at 11:15 AM, Igor Gnatenko <
> > ignatenkobr...@fedoraproject.org> wrote:
> >
> > > I think real problem here is that people want same spec to build
> > > every
On Thu, 2018-01-18 at 20:07 -0600, Rex Dieter wrote:
> Igor Gnatenko wrote:
>
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA256
> >
> > Does anybody know why we are still using %{?_isa} thing?
>
> To ensure arch's match between subpkgs.
>
> > DNF/libsolv forcefully install 64bit package f
On Thu, 2018-01-18 at 20:17 +0100, Igor Gnatenko wrote:
> Hello,
>
> I'm working on removing all this cruft from all our packages (and
> creating
> conditionals for all packages which have epel branch).
First many thanks, if we have an wiki page is that info (conditionals
for all packages which h
Igor Gnatenko wrote:
> […]
>> I was not fully aware of this and I've personally hit this difficulty
>> not on my proposal of the remove hicolor icon caches but on proposing,
>> for example, OpenIPMI or readline changes.
>> Most of my changes were by those packages maintainers simple discarded
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I often build an rpm in koji to make sure it builds but in order to
consume that rpm using our tools most of the time it needs to be in
a yum repo somewhere. I could create a repo locally and serve it locally
or even push it to somehwere to fedorapeo
-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$releasever-build/latest/$basearch/
> enabled=0
> skip_if_unavailabl
Hi All,
As per
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers, I
am posting here to see if anyone know how to contact Christoph Wickert
(cwickert).
The bug report is at https://bugzilla.redhat.com/show_bug.cgi?id=1530114
Regards,
Alick
Hi,
I've just pushed LLVM 6.0.0-rc1 builds to rawhide. If your package depends
on LLVM no action is required at this time, because dnf should automatically
pull in the compatibility package llvm5.0 as a dependency. The next time you
rebuild your package, if you still want to link against llvm 5.
On Fri, Jan 19, 2018 at 9:01 AM, J. Randall Owens
wrote:
> I'm not even the best at bash, much less the scripting in spec files,
> but is it possible this would be a problem because e.g. Fedora 26 would
> be evaluated as 026, which would evaluate as octal, and therefore the
> conditional evaluate
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 octal Here are a few common scripting
lan
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 are obsolete, which is not a lot to be honest. I would h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2018-01-20 at 00:39 +, Sérgio Basto wrote:
> On Fri, 2018-01-19 at 18:37 +0100, Igor Gnatenko wrote:
> > On Fri, 2018-01-19 at 11:22 -0600, Richard Shaw wrote:
> > > On Fri, Jan 19, 2018 at 11:15 AM, Igor Gnatenko <
> > > ignatenkobr...@f
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, 2018-01-19 at 13:51 -0500, Matthew Miller wrote:
> On Fri, Jan 19, 2018 at 06:37:09PM +0100, Igor Gnatenko wrote:
> > Within Fedora, those conditionals are not happening that often.. But
> > I would really love to see better separation of Fed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Sat, 2018-01-20 at 00:51 +, Tim Landscheidt wrote:
> Igor Gnatenko wrote:
>
> > […]
> > > I was not fully aware of this and I've personally hit this difficulty
> > > not on my proposal of the remove hicolor icon caches but on proposing,
> >
Hello,
alick9...@gmail.com wrote on 01/20/2018 12:59 PM:
Hi All,
As per
https://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers, I
am posting here to see if anyone know how to contact Christoph Wickert
(cwickert).
The bug report is at https://bugzilla.redhat.com/show_bug
60 matches
Mail list logo
