Re: Orphaned packages to be retired

[Ernestas Kulik]

On Mon, Jan 28, 2019 at 8:51 PM Jason L Tibbitts III 
wrote:

> > "RG" == Raphael Groner  writes:
>
> RG> Hi Miro, winetricks should get assigned to ekulik as he's the new
> RG> main admin.
>
> I've made ekulik the main admin of the winetricks repository.  It's not
> blocked in koji so everything should be OK now.
>

Thank you!


-- 
Ernestas Kulik
Associate Software Engineer - Base Operating Systems (Core Services/ABRT)
Red Hat Czech, s.r.o.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaned packages to be retired

[Ernestas Kulik]

On Mon, Jan 28, 2019 at 8:44 PM Björn 'besser82' Esser <
besse...@fedoraproject.org> wrote:

> Am Montag, den 28.01.2019, 20:31 +0100 schrieb Raphael Groner:
> > Hi Miro,
> >
> > winetricks should get assigned to ekulik as he's the new main admin.
> >
> > I've added him with admin ACL but orphaned the package badly.
> >
> > Can someone fix this?
> >
> > Regards, Raphael
>
>
> He needs to claim the package with a releng-ticket on pagure.
>

I’ve opened a ticket a while ago, but, since this has already been
resolved, I’ll just close it.


-- 
Ernestas Kulik
Associate Software Engineer - Base Operating Systems (Core Services/ABRT)
Red Hat Czech, s.r.o.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Bash 5.0

[Siteshwar Vashisht]

- Original Message -
> From: "Adam Williamson" 
> To: "Development discussions related to Fedora" 
> 
> Sent: Monday, January 28, 2019 11:38:58 PM
> Subject: Re: F30 Self-Contained Change proposal: Bash 5.0
> 
> It's not the "only" issue, because it was submitted over two weeks
> *after* the deadline for system-wide changes.
> 
> I am somewhat concerned about dropping in a major new bash version
> quite late in the cycle and just before the mass rebuild, particularly
> when there are bits like this in the announcement:
> 
> "There are a number of changes to the
> expansion of $@ and $* in various contexts where word splitting is not
> performed to conform to a Posix standard interpretation, and additional
> changes to resolve corner cases for Posix conformance." (are you *sure*
> all our corner cases are expecting Posix-conformant behaviour? I'm not)
> 
> "The `globasciiranges' shell option
> is now enabled by default; it can be set to off by default at
> configuration time." (OK, so we can turn it off again if necessary, but
> still, could be interesting)
> 
> "There are a few incompatible changes between bash-4.4 and bash-5.0"
> (sure, these are in 'rarely used' things, but we have an awful *lot* of
> shell scripts in us. We're a Linux distribution, it comes with the
> territory. I'm pretty sure we use those 'rarely used' thing at least
> somewhere)
> 
> that *plus* the required readline version bump *plus* the suggestion
> that some significant bugs were already discovered in the .0 release
> makes me a little hesitant about this. I'm not saying "no!", but...it
> certainly strikes me as a potentially disruptive change that needs some
> kind of justification to go in late beyond "NEW SHINY".

I agree that it would be much safer to target it for Fedora 31. I have no 
objection if we change target release.

> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
> http://www.happyassassin.net
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> 

-- 
--
Siteshwar Vashisht
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Retire YUM 3

[Lubomír Sedlář]

Igor Gnatenko píše v Po 28. 01. 2019 v 19:14 +0100:
> Which includes:
> * koji -- our buildsystem
> * pungi -- our compose tool

Not really. The only affected part is pungi-legacy subpackage, which
provides /usr/bin/pungi command. While it still has some users, it is
not part of any official release process.

> * sigul -- our signing tool for RPMs
> 
> On Mon, Jan 28, 2019 at 6:52 PM Miro Hrončok 
> wrote:
> > 
> > On 28. 01. 19 18:35, Igor Gnatenko wrote:
> > > This feels more like system-wide change…
> > > 
> > > Especially since you say that some extra packages will be
> > > retired.
> > 
> > A very limited set. The distro as a whole should not be impacted by
> > this.
> > 
> > The retired packages are legacy cruft. And the important stuff that
> > needs to be
> > updated needs some motivation like this.
> > 
> > > 
> > > On Mon, Jan 28, 2019 at 6:33 PM Ben Cotton 
> > > wrote:
> > > > 
> > > > (Note this change was previously submitted for Fedora 29:
> > > > https://pagure.io/fesco/issue/2064)
> > > > 
> > > > https://fedoraproject.org/wiki/Changes/Retire_YUM_3
> > 
> >  >> (snip)
> > 
> > --
> > Miro Hrončok
> > --
> > Phone: +420777974800
> > IRC: mhroncok
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: 
> > https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives: 
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> 
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Ibus-typing-booster default for Indian languages

[Mike FABIAN]

Owen Taylor  さんはかきました:

>> Currently, ibus-m17n is the default input method for Indian languages
>> in Fedora.  ibus-typing-booster uses the same libm17n used by
>> ibus-m17n to support input for Indian languages and thus it can do
>> everything ibus-m17n can do. But on top of that, ibus-typing-booster
>> supports predictive input by remembering user input and by using words
>> from dictionaries.  Therefore, ibus-typing-booster is a more useful input 
>> method
>> for these languages.
>>
>> == Benefit to Fedora ==
>> A better input experience for users of Indian languages.
>
> How would I try this out in Fedora 29?
>
> I see that I have ibus-typing-booster installed, but I don't see any
> sign of it in the GNOME "Region & Language" panel input source
> selection. Does ibus-typing-booster look like one input support for
> each supported language, or does it look like a single input source?

It looks like a single input source. Here are some
screen shots how to add it using the GNOME "Region & Language" panel:

http://mike-fabian.github.io/ibus-typing-booster/documentation.html#adding-gnome

It is listed under “Other” in the GNOME "Region & Language" panel input
source selection.

That is because it use “t” here:

$ /usr/libexec/ibus-engine-typing-booster --xml


typing-booster
Typing Booster
t
GPL
Mike FABIAN , Anish Patil 


/usr/share/ibus-typing-booster/icons/ibus-typing-booster.svg
default
A completion input method to speedup 
typing.
🚀
/usr/libexec/ibus-setup-typing-booster
InputMode



At the moment, ibus supports only one language in the
“t” tag. And as ibus-typing-booster supports many
languages, “en” does not seem right, it would look
like it supports only English. So only “t” for “Other” seems appropriate
at the moment. But it is a bit hard to find in “Other” in the GNOME
"Region & Language" panel.

When ibus-typing-booster is first used, it defaults to dictionaries
and m17n-input-methods appropriate to the locale it is first started in.

/usr/share/ibus-typing-booster/engine/itb_util.py contains the defaults,
for example for Marathi it has:

LOCALE_DEFAULTS = {
...
'mr_IN': {'inputmethods': ['mr-inscript2', 'NoIme'], 'dictionaries': 
['mr_IN', 'en_GB']},
...

So when the locale is mr_IN.UTF-8 while ibus-typing-booster is first
started, it defaults to the two input methods 'mr-inscript2' (a Marathi
input method) and 'NoIme' (that is direct keyboard input, useful for
English) and the dictionaries for mr_IN and for en_GB.

This can be changed in the setup tool of ibus-typing-booster, one can
choose up to 10 input methods and 10 dictionaries at the same time. 

> Thanks!
> Owen
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

-- 
Mike FABIAN 
睡眠不足はいい仕事の敵だ。
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Attempt to update ispc

[Luya Tshimbalanga]

I managed to resolve some issue but now the problem is related to the
hardened part:

https://koji.fedoraproject.org/koji/taskinfo?taskID=32324093

Here is the following lines for the failure:

BUILDSTDERR: /usr/bin/ld: kernels_ispc_sse2.o: relocation R_X86_64_32
against symbol
`RenderTile___uniuniREFs_5B_unInputHeader_5D_REFs_5B_unInputDataArrays_5D_uniun_3C_unT_3E_un_3C_unT_3E_un_3C_unT_3E_sse2'
can not be used when making a PIE object; recompile with -fPIC
BUILDSTDERR: /usr/bin/ld: kernels_ispc_sse4.o: relocation R_X86_64_32S
against `.rodata.cst16' can not be used when making a PIE object;
recompile with -fPIC
BUILDSTDERR: /usr/bin/ld: kernels_ispc_avx.o: relocation R_X86_64_32
against symbol
`RenderTile___uniuniREFs_5B_unInputHeader_5D_REFs_5B_unInputDataArrays_5D_uniun_3C_unT_3E_un_3C_unT_3E_un_3C_unT_3E_avx'
can not be used when making a PIE object; recompile with -fPIC
BUILDSTDERR: /usr/bin/ld: kernels_ispc_avx2.o: relocation R_X86_64_32S
against `.rodata.cst32' can not be used when making a PIE object;
recompile with -fPIC
BUILDSTDERR: /usr/bin/ld: kernels_ispc_avx512knl.o: relocation
R_X86_64_32 against symbol
`RenderTile___uniuniREFs_5B_unInputHeader_5D_REFs_5B_unInputDataArrays_5D_uniun_3C_unT_3E_un_3C_unT_3E_un_3C_unT_3E_avx512knl'
can not be used when making a PIE object; recompile with -fPIC
BUILDSTDERR: /usr/bin/ld: kernels_ispc_avx512skx.o: relocation
R_X86_64_32 against symbol
`RenderTile___uniuniREFs_5B_unInputHeader_5D_REFs_5B_unInputDataArrays_5D_uniun_3C_unT_3E_un_3C_unT_3E_un_3C_unT_3E_avx512skx'
can not be used when making a PIE object; recompile with -fPIC
BUILDSTDERR: /usr/bin/ld: final link failed: nonrepresentable section on
output
BUILDSTDERR: collect2: error: ld returned 1 exit status
BUILDSTDERR: make[2]: ***
[examples/deferred/CMakeFiles/deferred_shading.dir/build.make:204:
bin/deferred_shading] Error 1
BUILDSTDERR: make[1]: *** [CMakeFiles/Makefile2:370:
examples/deferred/CMakeFiles/deferred_shading.dir/all] Error 2
BUILDSTDERR: make: *** [Makefile:133: all] Error 2



Luya
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

python-pep8 is orphaned

[iliana weller]

Hello,

I've orphaned python-pep8. pep8 was renamed to pycodestyle in 2016; it
received its last release in 2017. It should be removed from Fedora in a
future release.

I unfortunately don't have time to proceed with the full retirement
process myself. If somebody would like to pick it up:
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_an_Orphaned_Package

$ dnf repoquery --whatrequires python2-pep8
python2-autopep8-0:1.2.4-9.fc29.noarch
python2-pytest-pep8-0:1.0.6-15.fc29.noarch
python2-spyder-0:3.3.1-3.fc29.noarch
$ dnf repoquery --whatrequires python3-pep8
python3-autopep8-0:1.2.4-9.fc29.noarch
python3-hacking-0:1.1.0-3.fc29.noarch
python3-pytest-pep8-0:1.0.6-15.fc29.noarch
python3-spyder-0:3.3.1-3.fc29.noarch

See also https://bugzilla.redhat.com/show_bug.cgi?id=1667200's dependent
bugs.

(Please CC me on replies that need my attention.)

-- 
iliana weller 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

[Fedocal] Reminder meeting : Modularity WG (weekly)

[nils]

Dear all,

You are kindly invited to the meeting:
   Modularity WG (weekly) on 2019-01-29 from 15:00:00 to 16:00:00 UTC
   At fedora-meetin...@irc.freenode.net

The meeting will be about:
Meeting of the Modularity Working Group.

More information available at: [Modularity Working Group wiki 
page](https://fedoraproject.org/wiki/Modularity_Working_Group)

The agenda for the meeting is available as flagged tickets [in the Modularity 
repository](https://pagure.io/modularity/issues?status=Open&tags=Meeting).



Source: https://apps.fedoraproject.org/calendar/meeting/9443/

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaning: llvm5.0, clang5.0, llvm6.0, clang6.0

[Luya Tshimbalanga]

We are in a process updating ISPs. We need a hand fixing the -fPIC issue on the 
build.

Luya

Sent from Samsung Galaxy 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaning: llvm5.0, clang5.0, llvm6.0, clang6.0

[Tom Stellard]

On 01/28/2019 02:47 PM, Igor Gnatenko wrote:
> It would be great if you would include list of dependent packages +
> their maintainers.
> 

Here is the list of dependent packages:

Maintainers by package:
beignet  ignatenkobrain
ghdl sailer
ispc luya slaanesh
iwyu daveisfera
ldc  bioinfornatics cicku kalev
rtagsgicmo

Packages by maintainer:
bioinfornatics ldc
cicku  ldc
daveisfera iwyu
gicmo  rtags
ignatenkobrain beignet
kalev  ldc
luya   ispc
sailer ghdl
slaanesh   ispc

-Tom

> You can use 
> https://pagure.io/fedora-misc-package-utilities/blob/master/f/find-package-maintainers
> for finding maintainers.
> 
> On Mon, Jan 28, 2019 at 11:42 PM Tom Stellard  wrote:
>>
>> Hi,
>>
>> I am orphaning the llvm and clang compatibility packages for versions 5.0 
>> and 6.0.
>> We are about to push LLVM 8.0 into rawhide, so I will no longer maintain 
>> these
>> older versions.  There are still a few users of these packages, so the 
>> package
>> owners can either rebuild their packages for LLVM 7/8 or take over ownership
>> of the compatibility package they need.
>>
>> -Tom
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
>> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
>> List Archives: 
>> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
> 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Retiring perl-perlmenu

[Emmanuel Seyman]

[ perl-devel is in cc: ]

Hello, all.

I maintain perl-perlmenu in Fedora and I will be retiring it at the end
of the week unless someone offers to maintain it instead. For the record,
I would advise against this since upstream no longer exists and nothing
depends on the particular package.

Emmanuel
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Bash 5.0

[Adam Williamson]

On Mon, 2019-01-28 at 22:24 +0100, Dominik 'Rathann' Mierzejewski
wrote:
> On Monday, 28 January 2019 at 03:57, Neal Gompa wrote:
> [...]
> > My understanding is that generally script breakage is considered a bug
> > and would have priority for fixing in bash anyway, so I *really* don't
> > think there's any harm in doing this. GCC is an order of magnitude
> > worse than bash, and we do fine with that *every year*. Something that
> > straight up says it's not intending to break scripts that just happens
> > to say it's a 5.0 release should not be as much of a cause for
> > concern.
> 
> We do (upgrade GCC), but it's always a System Wide Change, and that
> is the only issue with this proposal (which was submitted as a
> Self-contained Change).

It's not the "only" issue, because it was submitted over two weeks
*after* the deadline for system-wide changes.

I am somewhat concerned about dropping in a major new bash version
quite late in the cycle and just before the mass rebuild, particularly
when there are bits like this in the announcement:

"There are a number of changes to the
expansion of $@ and $* in various contexts where word splitting is not
performed to conform to a Posix standard interpretation, and additional
changes to resolve corner cases for Posix conformance." (are you *sure*
all our corner cases are expecting Posix-conformant behaviour? I'm not)

"The `globasciiranges' shell option
is now enabled by default; it can be set to off by default at
configuration time." (OK, so we can turn it off again if necessary, but
still, could be interesting)

"There are a few incompatible changes between bash-4.4 and bash-5.0"
(sure, these are in 'rarely used' things, but we have an awful *lot* of
shell scripts in us. We're a Linux distribution, it comes with the
territory. I'm pretty sure we use those 'rarely used' thing at least
somewhere)

that *plus* the required readline version bump *plus* the suggestion
that some significant bugs were already discovered in the .0 release
makes me a little hesitant about this. I'm not saying "no!", but...it
certainly strikes me as a potentially disruptive change that needs some
kind of justification to go in late beyond "NEW SHINY".
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaning: llvm5.0, clang5.0, llvm6.0, clang6.0

[Igor Gnatenko]

It would be great if you would include list of dependent packages +
their maintainers.

You can use 
https://pagure.io/fedora-misc-package-utilities/blob/master/f/find-package-maintainers
for finding maintainers.

On Mon, Jan 28, 2019 at 11:42 PM Tom Stellard  wrote:
>
> Hi,
>
> I am orphaning the llvm and clang compatibility packages for versions 5.0 and 
> 6.0.
> We are about to push LLVM 8.0 into rawhide, so I will no longer maintain these
> older versions.  There are still a few users of these packages, so the package
> owners can either rebuild their packages for LLVM 7/8 or take over ownership
> of the compatibility package they need.
>
> -Tom
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Orphaning: llvm5.0, clang5.0, llvm6.0, clang6.0

[Tom Stellard]

Hi,

I am orphaning the llvm and clang compatibility packages for versions 5.0 and 
6.0.
We are about to push LLVM 8.0 into rawhide, so I will no longer maintain these
older versions.  There are still a few users of these packages, so the package
owners can either rebuild their packages for LLVM 7/8 or take over ownership
of the compatibility package they need.

-Tom
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Retire YUM 3

[Sérgio Basto]

On Mon, 2019-01-28 at 12:27 -0500, Ben Cotton wrote:
> (Note this change was previously submitted for Fedora 29:
> https://pagure.io/fesco/issue/2064)
> 
> https://fedoraproject.org/wiki/Changes/Retire_YUM_3
> 
> == Summary ==
> Remove yum (v3) and all related packages from Fedora.
> 
> == Owner ==
> * Name: [[User:mdomonko|Michal Domonkos]]
> * Email: mdomo...@redhat.com
> 
> == Detailed Description ==
> Remove packages from the distribution:
> * createrepo
> * yum
> * yum-langpacks
> * yum-utils
> * yum-metadata-parser
> * yum-updatesd
> * python-urlgrabber
> 
> All these packages should no longer be used and all software using
> them should be migrated to DNF.
> 
> Compatibility:
> * Important packages such as yum, createrepo or yum-utils will be
> provided/obsoleted by relevant packages from the dnf stack
> * Important executables such yum, repoquery, createrepo, etc. will be
> provided either as new executables or via symlinks
> 
> == Benefit to Fedora ==
> Drop an old package manager that has no active upstream development.
> Move existing users to DNF which that has active development.
> Secondary benefit is reducing number of packages in Fedora that still
> depend on Python 2.
> 
> == Scope ==
> * Proposal owners: Remove packages from the distribution: createrepo,
> yum, yum-langpacks, yum-utils, yum-metadata-parser, yum-updatesd,
> python-urlgrabber
> * Other developers: Either remove packages from the distribution or
> switch them to DNF
> * Release engineering: [https://pagure.io/releng/issue/7588 #7588]
> * Policies and guidelines: N/A
> * Trademark approval: N/A (not needed for this Change)

koji-builder, mash and repoview are ready to work without yum ?


== Upgrade/compatibility impact ==
> Any tool based on YUM 3 Python API will stop working. This applies on
> any 3rd party software which won't be changed in Fedora as part of
> this change.
> CLI compatibility will be provided by DNF.
> 
> == How To Test ==
> Repoclosure passes after dropping the packages.
> 
> == User Experience ==
> There shouldn't be any impact on YUM users because the functionality
> is provided by DNF already.
> Users of tools listed in the Dependencies section shouldn't see any
> difference if the migration to DNF is done properly.
> 
> == Dependencies ==
> The list of source packages (SRPMs) that still depend on some of the
> yum-related packages to be removed:
> (see wiki page)
> 
> == Contingency Plan ==
> * Contingency mechanism: Do not remove the packages in the current
> release.
> * Contingency deadline: Beta Freeze
> * Blocks release? No
> * Blocks product? No
> 
> == Documentation ==
> N/A
> 
> == Release Notes ==
> Inform end-users about removing the YUM 3 stack and definitive
> migration to DNF.
> 
> -- 
> Ben Cotton
> Fedora Program Manager
> TZ=America/Indiana/Indianapolis
> ___
> devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
> To unsubscribe send an email to 
> devel-announce-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: 
> https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Bash 5.0

[Dominik 'Rathann' Mierzejewski]

On Monday, 28 January 2019 at 03:57, Neal Gompa wrote:
[...]
> My understanding is that generally script breakage is considered a bug
> and would have priority for fixing in bash anyway, so I *really* don't
> think there's any harm in doing this. GCC is an order of magnitude
> worse than bash, and we do fine with that *every year*. Something that
> straight up says it's not intending to break scripts that just happens
> to say it's a 5.0 release should not be as much of a cause for
> concern.

We do (upgrade GCC), but it's always a System Wide Change, and that
is the only issue with this proposal (which was submitted as a
Self-contained Change).

Regards,
Dominik
-- 
Fedora   https://getfedora.org  |  RPM Fusion  http://rpmfusion.org
There should be a science of discontent. People need hard times and
oppression to develop psychic muscles.
-- from "Collected Sayings of Muad'Dib" by the Princess Irulan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: [HEADS UP] Rebasing to Readline-8.0 in rawhide

[Jason L Tibbitts III]

> "SV" == Siteshwar Vashisht  writes:

SV> I would do that.

Thanks.

SV> I will also provide a compatibility package for readline 7.

That does help, but then you have to know that it's the magic package
you need to install in order to restore the command line editing
capability.  Nothing about the libss setup makes that obvious, since it
only tries to load a list of libraries by name at runtime and doesn't
link against them at all.  There's no packaging dependency between it
and any of the various libraries it will use.

 - J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaned packages to be retired

[Raphael Groner]

Thanks!


Am 28.01.19 um 20:41 schrieb Jason L Tibbitts III:

"RG" == Raphael Groner  writes:


RG> Hi Miro, winetricks should get assigned to ekulik as he's the new
RG> main admin.

I've made ekulik the main admin of the winetricks repository.  It's not
blocked in koji so everything should be OK now.

  - J<


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaned packages to be retired

[Jason L Tibbitts III]

> "RG" == Raphael Groner  writes:

RG> Hi Miro, winetricks should get assigned to ekulik as he's the new
RG> main admin.

I've made ekulik the main admin of the winetricks repository.  It's not
blocked in koji so everything should be OK now.

 - J<
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaned packages to be retired

[Björn 'besser82' Esser]

Am Montag, den 28.01.2019, 20:31 +0100 schrieb Raphael Groner:
> Hi Miro,
> 
> winetricks should get assigned to ekulik as he's the new main admin.
> 
> I've added him with admin ACL but orphaned the package badly.
> 
> Can someone fix this?
> 
> Regards, Raphael


He needs to claim the package with a releng-ticket on pagure.


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Orphaned packages to be retired

[Raphael Groner]

Hi Miro,

winetricks should get assigned to ekulik as he's the new main admin.

I've added him with admin ACL but orphaned the package badly.

Can someone fix this?

Regards, Raphael
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Retire YUM 3

[Neal Gompa]

On Mon, Jan 28, 2019 at 12:29 PM Ben Cotton  wrote:
>
> == Detailed Description ==
> Remove packages from the distribution:
> [...]
> * python-urlgrabber
>

We don't actually have to drop this one. One of the SUSE guys
submitted a pull request to port it to Python 3:
https://github.com/rpm-software-management/urlgrabber/pull/8

If someone could take a look at reviewing that so it can be merged, we
can keep this package around.



--
真実はいつも一つ！/ Always, there's only one truth!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Retire YUM 3

[Igor Gnatenko]

Which includes:
* koji -- our buildsystem
* pungi -- our compose tool
* sigul -- our signing tool for RPMs

On Mon, Jan 28, 2019 at 6:52 PM Miro Hrončok  wrote:
>
> On 28. 01. 19 18:35, Igor Gnatenko wrote:
> > This feels more like system-wide change…
> >
> > Especially since you say that some extra packages will be retired.
>
> A very limited set. The distro as a whole should not be impacted by this.
>
> The retired packages are legacy cruft. And the important stuff that needs to 
> be
> updated needs some motivation like this.
>
> >
> > On Mon, Jan 28, 2019 at 6:33 PM Ben Cotton  wrote:
> >>
> >> (Note this change was previously submitted for Fedora 29:
> >> https://pagure.io/fesco/issue/2064)
> >>
> >> https://fedoraproject.org/wiki/Changes/Retire_YUM_3
>  >> (snip)
>
> --
> Miro Hrončok
> --
> Phone: +420777974800
> IRC: mhroncok
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Orphaned packages to be retired

[Miro Hrončok]

The following packages are orphaned and will be retired when they
are orphaned for six weeks, unless someone adopts them. If you know for sure
that the package should be retired, please do so now with a proper reason:
https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

I plan to retire packages that were already announced 3 times next Monday.

Unorphan/unretire packages at https://pagure.io/releng/issues

(I still cannot unorphan packages, but rest assured that I monitor the tracker
and I'm not retiring packages that have open request for unorphaning.)

Note: If you received this mail directly you (co)maintain one of the affected
packages or a package that depends on one. Please adopt the affected package or
retire your depending package to avoid broken dependencies, otherwise your
package will be retired when the affected package gets retired.

Remarks: Some packages are falsely reported as orphaned for 60+ weeks.
The issue was reported and I won't retire them sooner than after real 6 weeks.
Sorry about that.

  Package  (co)maintainers Status Change

RunSnakeRun   orphan   2 weeks ago
autotrash frafra, orphan, robyduck 4 weeks ago
bouml orphan   6 weeks ago
bouml-doc orphan   6 weeks ago
catkinorphan, rmattes, robotics-sig,   1 weeks ago
  thofmann
dnsyo codeblock, orphan2 weeks ago
ecryptfs-simple   orphan   6 weeks ago
fasd  orphan   4 weeks ago
hoard orphan   29 weeks ago
jlibrtp   orphan   6 weeks ago
jmake orphan   6 weeks ago
labyrinth orphan   0 weeks ago
memaker   orphan   0 weeks ago
python-ceilometermiddleware   orphan   68 weeks ago
python-cookiesadamwill, orphan 4 weeks ago
python-gencpp orphan, rmattes, robotics-sig,   1 weeks ago
  thofmann
python-genlisporphan, rmattes, robotics-sig,   1 weeks ago
  thofmann
python-genmsg orphan, rmattes, robotics-sig,   1 weeks ago
  thofmann
python-genpy  orphan, rmattes, robotics-sig,   1 weeks ago
  thofmann
python-gnocchiclient  orphan   77 weeks ago
python-kafka  orphan   77 weeks ago
python-pankoclientorphan   77 weeks ago
python-pytimeparseorphan   77 weeks ago
python-ripe-atlas-cousteauorphan   4 weeks ago
python-ripe-atlas-sagan   orphan   4 weeks ago
python-socketIO-clientorphan   4 weeks ago
ripe-atlas-tools  orphan   4 weeks ago
ros-release   orphan, rmattes, robotics-sig,   1 weeks ago
  thofmann
rospack   orphan, rmattes, robotics-sig,   1 weeks ago
  thofmann
scout orphan   0 weeks ago
toothchartorphan   0 weeks ago
tristripper   orphan   6 weeks ago
unp   mstuchli, orphan, python-sig 2 weeks ago
wifi-radarblackfile, orphan4 weeks ago
winetricksekulik, orphan, raphgro, tc011 weeks ago
xword orphan   0 weeks ago

The following packages require above mentioned packages:
Depending on: catkin (4), status change: 2019-01-20 (1 weeks ago)
python-gencpp (maintained by: orphan, rmattes, robotics-sig, thofmann)
		python-gencpp-0.3.4-14.20130623git403d067.fc29.src requires catkin-devel = 
0.4.5-19.gitd4f1f24.fc29


python-genlisp (maintained by: orphan, rmattes, robotics-sig, thofmann)
		python-genlisp-0.3.3-14.20130623git8790a17.fc29.src requires catkin-devel = 
0.4.5-19.gitd4f1f24.fc29


python-genmsg (maintained by: orphan, rmattes, robotics-sig, thofmann)
		python-genmsg-0.3.10-16.20130617git95ca00d.fc28.src requires catkin-devel = 
0.4.5-19.gitd4f

Re: F30 Self-Contained Change proposal: Retire YUM 3

[Miro Hrončok]

On 28. 01. 19 18:35, Igor Gnatenko wrote:

This feels more like system-wide change…

Especially since you say that some extra packages will be retired.


A very limited set. The distro as a whole should not be impacted by this.

The retired packages are legacy cruft. And the important stuff that needs to be 
updated needs some motivation like this.




On Mon, Jan 28, 2019 at 6:33 PM Ben Cotton  wrote:


(Note this change was previously submitted for Fedora 29:
https://pagure.io/fesco/issue/2064)

https://fedoraproject.org/wiki/Changes/Retire_YUM_3

>> (snip)

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Fish 3.0

[Igor Gnatenko]

This change is actually already done, I just wanted to make sure that
it gets more user awareness and gets into release notes.

On Mon, Jan 28, 2019 at 6:33 PM Ben Cotton  wrote:
>
> https://fedoraproject.org/wiki/Changes/Fish_3.0
>
> == Summary ==
> Update [https://fishshell.com/ Fish] to 3.0.
>
> == Owner ==
> * Name: [[User:ignatenkobrain|Igor Gnatenko]]
> * Email: ignatenkobr...@fedoraproject.org
>
> == Detailed Description ==
> Not only update it in F30 but also provide new version as opt-in for
> F28 and F29.
>
> == Benefit to Fedora ==
> The new version of Fish has quite some number of bugfixes, features
> and performance improvements.
>
>
> == Scope ==
> * Proposal owners: Put fish 3.0 into a module (that means it will be
> available for F28 and F29) and mark it as default in Rawhide.
> * Other developers: N/A (not a System Wide Change)
> * Release engineering: [https://pagure.io/releng/issue/8077 #8077]
> * Policies and guidelines: N/A (not a System Wide Change)
> * Trademark approval: N/A (not needed for this Change)
>
> == Upgrade/compatibility impact ==
> * Process and job expansion has largely been removed. %
> will no longer perform these expansions, except for %self
> for the PID of the current shell. Additionally, job management
> commands (disown, wait, bg,
> fg and kill) will expand job specifiers
> starting with %
> ([https://github.com/fish-shell/fish-shell/issues/4230 #4230],
> [https://github.com/fish-shell/fish-shell/issues/1202 #1202]).
> * set x[1] x[2] a b, to set multiple elements of an array
> at once, is no longer valid syntax
> ([https://github.com/fish-shell/fish-shell/issues/4236 #4236]).
> * A literal {} now expands to itself, rather than
> nothing. This makes working with find -exec easier
> ([https://github.com/fish-shell/fish-shell/issues/1109 #1109],
> [https://github.com/fish-shell/fish-shell/pull/4632 #4632]).
> * Literally accessing a zero-index is now illegal syntax and is caught
> by the parser ([https://github.com/fish-shell/fish-shell/issues/4862
> #4862]). (fish indices start at 1)
> * Successive commas in brace expansions are handled in less surprising
> manner. For example, {,,,} expands to four empty strings
> rather than an empty string, a comma and an empty string again
> ([https://github.com/fish-shell/fish-shell/issues/3002 #3002],
> [https://github.com/fish-shell/fish-shell/pull/4632 #4632]).
> * for loop control variables are no longer local to the
> for block
> ([https://github.com/fish-shell/fish-shell/issues/1935 #1935]).
> * Variables set in if and while conditions
> are available outside the block
> ([https://github.com/fish-shell/fish-shell/issues/4820 #4820]).
> * Local exported (set -lx) vars are now visible to
> functions ([https://github.com/fish-shell/fish-shell/issues/1091
> #1091]).
> * The new math builtin (see below) does not support
> logical expressions; test should be used instead
> ([https://github.com/fish-shell/fish-shell/issues/4777 #4777]).
> * Range expansion will now behave sensibly when given a single
> positive and negative index ($foo[5..-1] or
> $foo[-1..5]), clamping to the last valid index without
> changing direction if the list has fewer elements than expected.
> * read now uses -s as short for
> --silent (à la bash); --shell's
> abbreviation (formerly -s) is now -S instead
> ([https://github.com/fish-shell/fish-shell/issues/4490 #4490]).
> * cd no longer resolves symlinks. fish now maintains a
> virtual path, matching other shells
> ([https://github.com/fish-shell/fish-shell/issues/3350 #3350]).
> * source now requires an explicit - as the
> filename to read from the terminal
> ([https://github.com/fish-shell/fish-shell/issues/2633 #2633]).
> * Arguments to end are now errors, instead of being
> silently ignored.
> * The names argparse, read,
> set, status, test and
> [ are now reserved and not allowed as function names.
> This prevents users unintentionally breaking stuff
> ([https://github.com/fish-shell/fish-shell/issues/3000 #3000]).
> * The fish_user_abbreviations variable is no longer used;
> abbreviations will be migrated to the new storage format
> automatically.
> * The FISH_READ_BYTE_LIMIT variable is now called
> fish_byte_limit
> ([https://github.com/fish-shell/fish-shell/issues/4414 #4414]).
> * Environment variables are no longer split into arrays based on the
> record separator character on startup. Instead, variables are not
> split, unless their name ends in PATH, in which case they are split on
> colons ([https://github.com/fish-shell/fish-shell/issues/436 #436]).
> * The history builtin's --with-time option
> has been removed; this has been deprecated in favor of
> --show-time since 2.7.0
> ([https://github.com/fish-shell/fish-shell/pull/4403 #4403]).
> * The internal variables __fish_datadir and
> __fish_sysconfdir are now known as
> __fish_data_dir and __fish_sysconf_dir
> respectively.
>
> == How To Test ==
> 0. Make sure to have modular repositories enabled
> 1. Run dnf module install fish:3
> 2. 

Re: F30 Self-Contained Change proposal: Retire YUM 3

[Igor Gnatenko]

This feels more like system-wide change…

Especially since you say that some extra packages will be retired.

On Mon, Jan 28, 2019 at 6:33 PM Ben Cotton  wrote:
>
> (Note this change was previously submitted for Fedora 29:
> https://pagure.io/fesco/issue/2064)
>
> https://fedoraproject.org/wiki/Changes/Retire_YUM_3
>
> == Summary ==
> Remove yum (v3) and all related packages from Fedora.
>
> == Owner ==
> * Name: [[User:mdomonko|Michal Domonkos]]
> * Email: mdomo...@redhat.com
>
> == Detailed Description ==
> Remove packages from the distribution:
> * createrepo
> * yum
> * yum-langpacks
> * yum-utils
> * yum-metadata-parser
> * yum-updatesd
> * python-urlgrabber
>
> All these packages should no longer be used and all software using
> them should be migrated to DNF.
>
> Compatibility:
> * Important packages such as yum, createrepo or yum-utils will be
> provided/obsoleted by relevant packages from the dnf stack
> * Important executables such yum, repoquery, createrepo, etc. will be
> provided either as new executables or via symlinks
>
> == Benefit to Fedora ==
> Drop an old package manager that has no active upstream development.
> Move existing users to DNF which that has active development.
> Secondary benefit is reducing number of packages in Fedora that still
> depend on Python 2.
>
> == Scope ==
> * Proposal owners: Remove packages from the distribution: createrepo,
> yum, yum-langpacks, yum-utils, yum-metadata-parser, yum-updatesd,
> python-urlgrabber
> * Other developers: Either remove packages from the distribution or
> switch them to DNF
> * Release engineering: [https://pagure.io/releng/issue/7588 #7588]
> * Policies and guidelines: N/A
> * Trademark approval: N/A (not needed for this Change)
>
> == Upgrade/compatibility impact ==
> Any tool based on YUM 3 Python API will stop working. This applies on
> any 3rd party software which won't be changed in Fedora as part of
> this change.
> CLI compatibility will be provided by DNF.
>
> == How To Test ==
> Repoclosure passes after dropping the packages.
>
> == User Experience ==
> There shouldn't be any impact on YUM users because the functionality
> is provided by DNF already.
> Users of tools listed in the Dependencies section shouldn't see any
> difference if the migration to DNF is done properly.
>
> == Dependencies ==
> The list of source packages (SRPMs) that still depend on some of the
> yum-related packages to be removed:
> (see wiki page)
>
> == Contingency Plan ==
> * Contingency mechanism: Do not remove the packages in the current release.
> * Contingency deadline: Beta Freeze
> * Blocks release? No
> * Blocks product? No
>
> == Documentation ==
> N/A
>
> == Release Notes ==
> Inform end-users about removing the YUM 3 stack and definitive migration to 
> DNF.
>
> --
> Ben Cotton
> Fedora Program Manager
> TZ=America/Indiana/Indianapolis
> ___
> devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
> To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

F30 Self-Contained Change proposal: Retire YUM 3

[Ben Cotton]

(Note this change was previously submitted for Fedora 29:
https://pagure.io/fesco/issue/2064)

https://fedoraproject.org/wiki/Changes/Retire_YUM_3

== Summary ==
Remove yum (v3) and all related packages from Fedora.

== Owner ==
* Name: [[User:mdomonko|Michal Domonkos]]
* Email: mdomo...@redhat.com

== Detailed Description ==
Remove packages from the distribution:
* createrepo
* yum
* yum-langpacks
* yum-utils
* yum-metadata-parser
* yum-updatesd
* python-urlgrabber

All these packages should no longer be used and all software using
them should be migrated to DNF.

Compatibility:
* Important packages such as yum, createrepo or yum-utils will be
provided/obsoleted by relevant packages from the dnf stack
* Important executables such yum, repoquery, createrepo, etc. will be
provided either as new executables or via symlinks

== Benefit to Fedora ==
Drop an old package manager that has no active upstream development.
Move existing users to DNF which that has active development.
Secondary benefit is reducing number of packages in Fedora that still
depend on Python 2.

== Scope ==
* Proposal owners: Remove packages from the distribution: createrepo,
yum, yum-langpacks, yum-utils, yum-metadata-parser, yum-updatesd,
python-urlgrabber
* Other developers: Either remove packages from the distribution or
switch them to DNF
* Release engineering: [https://pagure.io/releng/issue/7588 #7588]
* Policies and guidelines: N/A
* Trademark approval: N/A (not needed for this Change)

== Upgrade/compatibility impact ==
Any tool based on YUM 3 Python API will stop working. This applies on
any 3rd party software which won't be changed in Fedora as part of
this change.
CLI compatibility will be provided by DNF.

== How To Test ==
Repoclosure passes after dropping the packages.

== User Experience ==
There shouldn't be any impact on YUM users because the functionality
is provided by DNF already.
Users of tools listed in the Dependencies section shouldn't see any
difference if the migration to DNF is done properly.

== Dependencies ==
The list of source packages (SRPMs) that still depend on some of the
yum-related packages to be removed:
(see wiki page)

== Contingency Plan ==
* Contingency mechanism: Do not remove the packages in the current release.
* Contingency deadline: Beta Freeze
* Blocks release? No
* Blocks product? No

== Documentation ==
N/A

== Release Notes ==
Inform end-users about removing the YUM 3 stack and definitive migration to DNF.

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

F30 Self-Contained Change proposal: Fish 3.0

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/Fish_3.0

== Summary ==
Update [https://fishshell.com/ Fish] to 3.0.

== Owner ==
* Name: [[User:ignatenkobrain|Igor Gnatenko]]
* Email: ignatenkobr...@fedoraproject.org

== Detailed Description ==
Not only update it in F30 but also provide new version as opt-in for
F28 and F29.

== Benefit to Fedora ==
The new version of Fish has quite some number of bugfixes, features
and performance improvements.


== Scope ==
* Proposal owners: Put fish 3.0 into a module (that means it will be
available for F28 and F29) and mark it as default in Rawhide.
* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issue/8077 #8077]
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)

== Upgrade/compatibility impact ==
* Process and job expansion has largely been removed. %
will no longer perform these expansions, except for %self
for the PID of the current shell. Additionally, job management
commands (disown, wait, bg,
fg and kill) will expand job specifiers
starting with %
([https://github.com/fish-shell/fish-shell/issues/4230 #4230],
[https://github.com/fish-shell/fish-shell/issues/1202 #1202]).
* set x[1] x[2] a b, to set multiple elements of an array
at once, is no longer valid syntax
([https://github.com/fish-shell/fish-shell/issues/4236 #4236]).
* A literal {} now expands to itself, rather than
nothing. This makes working with find -exec easier
([https://github.com/fish-shell/fish-shell/issues/1109 #1109],
[https://github.com/fish-shell/fish-shell/pull/4632 #4632]).
* Literally accessing a zero-index is now illegal syntax and is caught
by the parser ([https://github.com/fish-shell/fish-shell/issues/4862
#4862]). (fish indices start at 1)
* Successive commas in brace expansions are handled in less surprising
manner. For example, {,,,} expands to four empty strings
rather than an empty string, a comma and an empty string again
([https://github.com/fish-shell/fish-shell/issues/3002 #3002],
[https://github.com/fish-shell/fish-shell/pull/4632 #4632]).
* for loop control variables are no longer local to the
for block
([https://github.com/fish-shell/fish-shell/issues/1935 #1935]).
* Variables set in if and while conditions
are available outside the block
([https://github.com/fish-shell/fish-shell/issues/4820 #4820]).
* Local exported (set -lx) vars are now visible to
functions ([https://github.com/fish-shell/fish-shell/issues/1091
#1091]).
* The new math builtin (see below) does not support
logical expressions; test should be used instead
([https://github.com/fish-shell/fish-shell/issues/4777 #4777]).
* Range expansion will now behave sensibly when given a single
positive and negative index ($foo[5..-1] or
$foo[-1..5]), clamping to the last valid index without
changing direction if the list has fewer elements than expected.
* read now uses -s as short for
--silent (à la bash); --shell's
abbreviation (formerly -s) is now -S instead
([https://github.com/fish-shell/fish-shell/issues/4490 #4490]).
* cd no longer resolves symlinks. fish now maintains a
virtual path, matching other shells
([https://github.com/fish-shell/fish-shell/issues/3350 #3350]).
* source now requires an explicit - as the
filename to read from the terminal
([https://github.com/fish-shell/fish-shell/issues/2633 #2633]).
* Arguments to end are now errors, instead of being
silently ignored.
* The names argparse, read,
set, status, test and
[ are now reserved and not allowed as function names.
This prevents users unintentionally breaking stuff
([https://github.com/fish-shell/fish-shell/issues/3000 #3000]).
* The fish_user_abbreviations variable is no longer used;
abbreviations will be migrated to the new storage format
automatically.
* The FISH_READ_BYTE_LIMIT variable is now called
fish_byte_limit
([https://github.com/fish-shell/fish-shell/issues/4414 #4414]).
* Environment variables are no longer split into arrays based on the
record separator character on startup. Instead, variables are not
split, unless their name ends in PATH, in which case they are split on
colons ([https://github.com/fish-shell/fish-shell/issues/436 #436]).
* The history builtin's --with-time option
has been removed; this has been deprecated in favor of
--show-time since 2.7.0
([https://github.com/fish-shell/fish-shell/pull/4403 #4403]).
* The internal variables __fish_datadir and
__fish_sysconfdir are now known as
__fish_data_dir and __fish_sysconf_dir
respectively.

== How To Test ==
0. Make sure to have modular repositories enabled
1. Run dnf module install fish:3
2. Try out normal workload in fish

== User Experience ==
* fish now supports && (like and),
|| (like or), and ! (like
not), for better migration from POSIX-compliant shells
([https://github.com/fish-shell/fish-shell/issues/4620 #4620]).
* fish may be started in private mode via fish --private.
Private mode fish sessions do not have access to the history file and
any commands evaluated

F30 Self-Contained Change proposal: Haskell GHC 8.4 and Stackage LTS 12

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/GHC_8.4

== Summary ==
Update the ghc Haskell compiler version from 8.2.2 to 8.4.4 and
Haskell packages to Stackage LTS 12 versions.

== Owner ==
* Name: [[User:Petersen| Jens Petersen]]
* Email: 
* Name: [[Haskell_SIG]]
* Email: 

== Detailed Description ==
The Fedora Haskell packages will be updated to
[https://downloads.haskell.org/~ghc/8.4.4/docs/html/users_guide/8.4.4-notes.html
ghc-8.4.4] and [https://www.stackage.org/lts-12 Stackage LTS 12]
versions.

== Benefit to Fedora ==

This updates Fedora to the latest stable release of GHC 8.4, with a
focus on performance, stability, consolidation, and numerous cleanups
throughout the compiler:
* Further refinement of TypeInType, including significant improvements
in error messages.
* Improvements in code generation resulting in noticable performance
improvements in some types of programs.
* Core library improvements, including phase 2 of the Semigroup/Monoid proposal
* Many improvements to instance deriving
* The resolution of nearly 300 other tickets for the 8.4.1 major
release, and further bugfixes in the subsequent stable minor version
releases

== Scope ==
* Proposal owners:
** Request f30-ghc Koji sidetag for building
([https://pagure.io/releng/issue/8014 done])
** Update the ghc master branch to version 8.4.4 (rebasing to version
from the ghc:8.4 module stream)
** Update Haskell packages to Stackage LTS 12 versions using `cabal-rpm update`
** Rebuild all packages in `rpmbuild-order` locally
** Some old unused libraries no longer in Stackage may be retired from
Rawhide at this time.
** If time permits there may be some packaging changes: to add back
doc subpackages and use explicit files list in .spec files
** Build everything in the Koji f30-ghc sidetag in `rpmbuild-order`
** Request releng to move all the rebuilt packages into Rawhide
** Add Obsoletes needed for any deprecated packages

* Other developers: all required packages will be rebuilt by the
Haskell SIG, though we are open to support from any of the few
packagers outside the SIG
* Release engineering: [https://pagure.io/releng/issue/8014 issue #8014]
** List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)

== Upgrade/compatibility impact ==
Users will need to recompile their Haskell code with the new version
of ghc and libraries.

== How To Test ==
* `dnf install ghc-*-devel`
* `dnf install cabal-install pandoc ShellCheck`
* `cabal update && cabal install some-pkg`
* `ghci`

* `dnf update ghc-*-devel`

== User Experience ==
Users will have the latest really stable Haskell package releases
available to them through the official Fedora repo.

(Note the latest Stackage LTS 13 release is actually with the newer
ghc-8.6 major version but it has some issues including not building on
s390x yet and less packages and maturity, so we are deliberately not
jumping a major release for this change.)

== Dependencies ==
N/A (not a System Wide Change)

== Contingency Plan ==
* Contingency mechanism: (What to do?  Who will do it?): Proposal
owner will revert git master branches to the mass rebuilt F29 versions
package set
* Contingency deadline: Before branching of F30
* Blocks release? N/A (not a System Wide Change)
* Blocks product? N/A

== Documentation ==
* https://ghc.haskell.org/trac/ghc/blog/ghc-8.4.1-released
* https://ghc.haskell.org/trac/ghc/blog/ghc-8.4.2-released
* https://ghc.haskell.org/trac/ghc/blog/ghc-8.4.3-released
* https://ghc.haskell.org/trac/ghc/blog/ghc-8.4.4-released

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

F30 Self-Contained Change proposal: LXQt 0.14.0

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/LXQt_0.14.0

== Summary ==

Update LXQt to 0.14.0 in Fedora.

== Owner ==
* Name: [[User:Zsun|Zamir SUN]]
* Email: zsun#AT#fedoraproject.org 

== Detailed Description ==

LXQt just released with a bunch of bugfixes. It's always good to keep
Fedora users running on most recent software.

Detailed LXQt release note is available
[https://lxqt.org/release/2019/01/25/lxqt-0140/ here].

== Benefit to Fedora ==

This change brings bug fixes and enhancements to LXQt in Fedora.

== Scope ==
* Proposal owners:

1. Update all the LXQt related packages in Fedora.

2. Drop lxqt-l10n from Fedora 30 which is obsoleted since LXQt 0.14.0

3. Fix comps and/or kickstart if needed.

* Other developers: N/A (not a System Wide Change)
* Release engineering: [https://pagure.io/releng/issue/8076 #8076] (a
check of an impact with Release Engineering is needed)
** List of deliverables: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)

== User Experience ==
Users shouldn't feel any difference rather than bug fixes and new features.

== Dependencies ==

The package libqtxdg will be updated. Only Deepin related packages
depends on this. In theory the Deepin change owner will need to be
reminded. In reality I am also the DeepinDE change owner, so there
aren't any risk for this aspect.

== Contingency Plan ==
* Contingency mechanism: Not announcing the update.
* Contingency deadline: Fedora 30 Beta Freeze
* Blocks release? N/A (not a System Wide Change)
* Blocks product? N/A

== Documentation ==
N/A (not a System Wide Change)

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

F30 Self-Contained Change proposal: SWID tag enablement

[Ben Cotton]

https://fedoraproject.org/wiki/Changes/SWID_Tag_Enablement

== Summary ==
Provide tools to allow users and developers to create Software
Identity (SWID) tags for Fedora installs and repositories.

== Owner ==
* Name: [[User:adelton|Jan Pazdziora]]
* Email: jpazdzi...@redhat.com

== Detailed Description ==
SWID (ISO/IEC 19770:2-2015) is a portable standard for identifying
software installed on a system.  We already have SWID tags in
fedora-release to identify the overall release+edition of Fedora. We
will add tools to allow users to
* list installed tags
* create and install individual tags identifying RPMs
* add pre-built tags to repositories
* automatically update local tags as packages are installed, updated and removed
This will involve standalone tools to query and build SWID tags and to
add prebuilt tags to dnf repositories, and plugins for dnf/libdnf to
build and download tags.

== Benefit to Fedora ==
Fedora will be usable to users and developers interested in the SWID
functionality being added to relevant other tools, such as
OpenSCAP-1.3.

== Scope ==
* Proposal owners:
** Add python SWID tools (swidq, rpm2swidtag)
** add SWID metadata awareness to createrepo (but this will not be
used in Fedora, only enabled for user use), agreeing metadata format
with dnf team
** add dnf and libdnf plugins (no core dnf/libdnf changes expected)

* Other developers: N/A (not a System Wide Change)
* Policies and guidelines: N/A (not a System Wide Change)
* Trademark approval: N/A (not needed for this Change)

== Upgrade/compatibility impact ==
N/A (not a System Wide Change)

== How To Test ==
N/A (not a System Wide Change)

== User Experience ==
No change unless users choose to enable SWID tags.
If requested, SWID tags will be either built automatically on demand
for installed RPMs, or downloaded from a repository that the user has
added SWID tags to, at the user’s choice.  swidq will allow the user
to see all installed tags and their relationships.

== Contingency Plan ==
* Contingency mechanism: (What to do?  Who will do it?) N/A (not a
System Wide Change)
* Contingency deadline: N/A (not a System Wide Change)
* Blocks release? N/A (not a System Wide Change), No
* Blocks product? No

== Release Notes ==
Inform users of new capabilities and how they can be used with the
existing tags in fedora-release-*

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Unresponsive maintainer: janfrode

[Björn 'besser82' Esser]

Am Montag, den 28.01.2019, 16:21 + schrieb Mattia Verga:
> Il 1/28/19 12:53 PM, Björn 'besser82' Esser ha scritto:
> > Hello,
> > 
> > does anyone here know how to contact janfrode? I can't get him to
> > answer
> > on rhbz # [1], nor on his email address from FAS.
> > 
> > 
> It seems he has at least a Twitter and a LinkedIn account:
> 
> https://twitter.com/janfrode
> 
> https://www.linkedin.com/in/janfrode


Thanks.  I've tried to contact him on LinkedIn about three weeks ago
without any response.  :/  The Twitter acc. seems to be abandoned since
2015…

On GitHub he uses the same email address as in FAS.  I tried that as
well without any response.


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

FINAL REMINDER: Self-Contained Change deadline is Tuesday

[Ben Cotton]

This is your final reminder that Self-Contained Change proposals for
Fedora 30 must be submitted (i.e. set to the "Change Ready for
Wrangler") category by the end of the day (UTC) on Tuesday, 29
January.

-- 
Ben Cotton
Fedora Program Manager
TZ=America/Indiana/Indianapolis
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Nonresponsive maintainer Matthias Saou

[Miro Hrončok]

https://bugzilla.redhat.com/show_bug.cgi?id=1323249

Anyone knows how to reach Matthias?

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Nonresponsive maintainer David Timms

[Miro Hrončok]

Anyone knows how to reach David?

https://bugzilla.redhat.com/show_bug.cgi?id=1482147

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Bash 5.0

[Adam Williamson]

On Sun, 2019-01-27 at 21:52 -0500, Neal Gompa wrote:
> On Sun, Jan 27, 2019 at 9:49 PM Siteshwar Vashisht  
> wrote:
> > - Original Message -
> > > From: "Nico Kadel-Garcia" 
> > > To: "Development discussions related to Fedora" 
> > > 
> > > Sent: Saturday, January 26, 2019 11:06:39 PM
> > > Subject: Re: F30 Self-Contained Change proposal: Bash 5.0
> > > 
> > > It's also only been released for barely 2 weeks, it's marked as a
> > > major revision number, and it seems a bit late to accept for Fedora
> > > 30. Mark it as a candidate for Fedora 31, and move on?
> > 
> > I am fine with doing that. But we are missing a chance to get some early 
> > testing on the latest release.
> > 
> 
> Is there some way we can (ab)use Koschei to see how things would look
> for bash 5.0 in Rawhide? Personally, I really don't think we'd have as
> many problems as people fear, but if there's a way we could do
> something interesting to prove it, that'd be great too.

Koschei only builds things, so that would only catch issues in bash
scripts used at build time (and only ones that caused a package build
failure, at that). It would not catch any issues that didn't cause a
package build failure, or any runtime issues in the vast swathes of
bash that are used at runtime.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: koji build fails due missing dependencies

[Martin Gansser]

Thanks for your respone MIro, but i can't build GoldenCheetah for now, because 
of
the following error:

BUILDSTDERR:   file /usr/lib64/gstreamer-1.0/libgstcompositor.so conflicts 
between attempted installs of gstreamer1-plugins-bad-free-1.14.4-1.fc30.x86_64 
and gstreamer1-plugins-base-1.15.1-2.fc30.x86_64

[1] https://kojipkgs.fedoraproject.org//work/tasks/4417/32314417/root.log

Regards
Martin
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Unresponsive maintainer: janfrode

[Mattia Verga]

Il 1/28/19 12:53 PM, Björn 'besser82' Esser ha scritto:
> Hello,
>
> does anyone here know how to contact janfrode? I can't get him to answer
> on rhbz # [1], nor on his email address from FAS.
>
>
It seems he has at least a Twitter and a LinkedIn account:

https://twitter.com/janfrode

https://www.linkedin.com/in/janfrode

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Agenda for Tuesday's Modularity Team Meeting (2019-01-29)

[Nils Philippsen]

Find below a list of topics which are planned to be discussed in the
Fedora Modularity Team meeting on Tuesday at 15:00 UTC in
#fedora-meeting-3 on irc.freenode.net.

To find out when this is in your local time zone, check the Fedora
Calendar (if you've set it and are logged in):
  https://apps.fedoraproject.org/calendar/modularity/#m5249

Alternatively, to convert UTC to your local time zone, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d 'Tuesday 15:00 UTC'

Links to all issues below can be found at:
  https://pagure.io/modularity/report/meeting_agenda

= Discussed and Voted =
Modularity WG Charter (contd.)
https://pagure.io/modularity/issue/119
DECISION (+4, 0, -0)

= Followups =

#topic #112 Discussion: Module lifecycles 
#link https://pagure.io/modularity/issue/112
.modularity 112
#link https://pagure.io/fesco/issue/2027

#topic #115 Discussion: Stream branch ownership for packages & modules
#link https://pagure.io/modularity/issue/115
.modularity 115
#link https://pagure.io/fesco/issue/2028

= New business =

N/A

= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/modularity/report/meeting_agenda

If you would like to add something to this agenda, you can file a new
issue at https://pagure.io/modularity/issues, or bring it up at the end
of the meeting during the open floor topic. Note that the meeting is
one hour long and issues we don't get around to discussing may be
deferred until the following meeting.

-- 
Nils Philippsen"Those who would give up Essential Liberty to
Software Engineer   purchase a little Temporary Safety, deserve neither
Red Hat Liberty nor Safety."  --  Benjamin Franklin, 1759
PGP fingerprint:C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: koji build fails due missing dependencies

[Miro Hrončok]

On 28. 01. 19 16:53, Scott Talbert wrote:

On Mon, 28 Jan 2019, Martin Gansser wrote:
the build fails due dependencies [1] although lmfit is present in the rawhide 
repo [2].


[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=32312961
[2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1176846

how can i resolve this ?


lmfit doesn't provide a pkgconfig file it seems so you should probably just 
BuildRequire lmfit-devel instead.


It will provide it in next realese:

https://src.fedoraproject.org/rpms/lmfit/pull-request/3

That is awaiting response. Also from you, Martin.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: koji build fails due missing dependencies

[Scott Talbert]

On Mon, 28 Jan 2019, Martin Gansser wrote:


Hi,

the build fails due dependencies [1] although lmfit is present in the rawhide 
repo [2].

[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=32312961
[2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1176846

how can i resolve this ?


lmfit doesn't provide a pkgconfig file it seems so you should probably 
just BuildRequire lmfit-devel instead.


Scott
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

koji build fails due missing dependencies

[Martin Gansser]

Hi,

the build fails due dependencies [1] although lmfit is present in the rawhide 
repo [2].

[1] https://koji.fedoraproject.org/koji/taskinfo?taskID=32312961
[2] https://koji.fedoraproject.org/koji/buildinfo?buildID=1176846

how can i resolve this ?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: NeuroFedora review swaps

[J. Scheurich]

If you've submitted a review ticket for wdune already, I will be happy
to review it and provide comments.


https://bugzilla.redhat.com/show_bug.cgi?id=1658153

so long
MUFTI
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: NeuroFedora review swaps

[Ankur Sinha]

On Mon, Jan 28, 2019 15:47:00 +0100, J. Scheurich wrote:
> 
> > I'd like to get this package reviewed please:
> > 
> > - python-pyscaffold: https://bugzilla.redhat.com/show_bug.cgi?id=1669913#
> > 
> > Would anyone like to swap reviews?
> 
> I would review it for wdune sponsoring.

Sorry---I'm not current with the wdune scenario. I assumed you meant
that you'd review it unofficially as part of the work to get sponsored
to the packagers group:

https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Show_Your_Expertise_by_Commenting_on_other_Review_Requests

I'm not a sponsor yet so I cannot sponsor you to the group myself, but
once you've done a few reviews, a sponsor will be happy to take a look
at them and guide you through the sponsorship process.

If you've submitted a review ticket for wdune already, I will be happy
to review it and provide comments.

-- 
Thanks,
Regards,

Ankur Sinha
https://ankursinha.in

Time zone: Europe/London


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: NeuroFedora review swaps

[Ankur Sinha]

On Mon, Jan 28, 2019 15:47:00 +0100, J. Scheurich wrote:
> 
> > I'd like to get this package reviewed please:
> > 
> > - python-pyscaffold: https://bugzilla.redhat.com/show_bug.cgi?id=1669913#
> > 
> > Would anyone like to swap reviews?
> >
> I would review it for wdune sponsoring.

Sure. Please feel free to review it unofficially too. All feedback is
welcome.

-- 
Thanks,
Regards,

Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha

Time zone: Europe/London


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Ibus-typing-booster default for Indian languages

[Owen Taylor]

OK, so trying it out, I note the following:

 * The top panel shows a full-color rocket where the current language
would normally be indicated (this needs to be monochromatic, but it
also needs to be meaningful)
 *  There is no I can find to use ibus-typing-booster to type in
something other than the current locale. I'd imagine that typing in
more than one Indian script is a real use case? In any case, the
design is that input sources are per-language and you switch input
source to switch input language.
 * Under wayland (at least), there is severe flashing where the
candidate window disappears and appears for every keystroke.

Presumably we have feedback from native speakers that the
ibus-typing-booster makes things better for them - but I think we need
to address the above issues to make the switch over.

Owen




I don't have any

Owen

On Mon, Jan 28, 2019 at 4:57 AM Jens-Ulrik Petersen  wrote:
>
> On Mon, Jan 28, 2019 at 8:04 AM Owen Taylor  wrote:
>>
>> I see that I have ibus-typing-booster installed, but I don't see any
>> sign of it in the GNOME "Region & Language" panel input source
>> selection. Does ibus-typing-booster look like one input support for
>> each supported language, or does it look like a single input source?
>
>
> ibus Typing Booster used to expose separate Input Sources for each language 
> it supports, but in 2.0 we unified it to a single Input Source under Other 
> languages.
>
> Hope that helps, Jens
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Orphaning: xsel

[Tomas Radej]

Hi,

I am orphaning xsel as I don't have time to maintain it. The recent gcc update 
means xsel no longer compiles.

I am not sure if it is worth maintaining xsel when xclip is packaged as well, 
so if someone think so, please take the package.

Thank you,

-- 
Tomas Radej 
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Spins keepalive deadline approaching

[Matthew Miller]

On Wed, Jan 23, 2019 at 03:29:44PM -0500, John Harris wrote:
> > Future improvements to the release process that will allow for teams to
> > self-publish solutions will eventually remove the need for these
> > keepalives.
> Is that really such a great idea? How would release engineering handle that?

I think it's a great idea.

The idea is to move release engineering from being responsible for turning a
crank that puts out releases to owning a *machine* which creates releases
on demand for the groups actually responsible for that release.

-- 
Matthew Miller

Fedora Project Leader
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Attempt to update ispc

[Florian Weimer]

* Luya Tshimbalanga:

> On 2019-01-27 2:00 p.m., Florian Weimer wrote:
>> * Luya Tshimbalanga:
>>
>>> On 2019-01-26 12:24 a.m., Dominik 'Rathann' Mierzejewski wrote:
 I would try patching out the clang requirement from CMakeLists
 and building with system gcc.

 Regards,
 Dominik
>>> Done. Unfortunately, the build failed as the compiler still remains
>>> clang and finding the cause is beyond my knowledge. Here is the resulted
>>> scratch build:
>>>
>>>
>>> https://koji.fedoraproject.org/koji/taskinfo?taskID=32277096
>> Which sources are you building? Nothing like this is on the master
>> branch on src.fedoraproject.org.
>>
>> Thanks,
>> Florian
> I avoided committing the update as I preferred to do a scratch-build
> hence the link from koji.
> Realizing the change can be seen on the master branch on
> src.fedoraproject.org, I applied the update for view:
> https://src.fedoraproject.org/rpms/ispc/blob/master/f/ispc.spec

Sorry, the rawhide build now fails for me with:

m4 -Ibuiltins/ -DLLVM_VERSION=LLVM_7_0 -DBUILD_OS=UNIX builtins/dispatch.ll | 
python bitcode2cpp.py builtins/dispatch.ll > objs/builtins-dispatch.cpp
BUILDSTDERR: /bin/sh: python: command not found
BUILDSTDERR: make: *** [Makefile:330: objs/builtins-dispatch.cpp] Error
127

This looks completely unrelated to clang.

Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Unresponsive maintainer: janfrode

[Björn 'besser82' Esser]

Hello,

does anyone here know how to contact janfrode? I can't get him to answer
on rhbz # [1], nor on his email address from FAS.


=== Output of `fedora_active_user.py`: ===

```
Last login in FAS:
   janfrode 2014-08-07
Last action on koji:
   Sat, 19 Aug 2017 package list entry revoked: altermime in dist-6E-
epel by pkgdb
Last package update on bodhi:
   2014-06-14 13:13:42 on package mon-1.2.0-11.el6
```

Thanks,
  Björn


[1]  https://bugzilla.redhat.com/show_bug.cgi?id=1666720


signature.asc
Description: This is a digitally signed message part
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Ruby soname bump

[Vít Ondruch]

This landed in Rawhide few minutes ago.


Vít


Dne 22. 01. 19 v 15:19 Vít Ondruch napsal(a):
> Hi,
>
> We have Ruby 2.6 ready in side tag and we are about to merge the changes
> back to Rawhide [1]. Therefore I just want to give heads up that
> although we rebuilt most of the packages due to libruby soname bump,
> there might still be some breakage. You can find the list of packages
> with know issue in ruby-sig ML thread [2] and apologies for the issues.
> Please let us know if you encounter any other issues.
>
> Vít
>
>
> [1] https://pagure.io/releng/issue/8034
>
> [2]
> https://lists.fedoraproject.org/archives/list/ruby-...@lists.fedoraproject.org/message/CTYOIFZ4UNFZYUD74XPG47N3KQ2S7OC7/
>
>
> Dne 28. 11. 18 v 21:07 Ben Cotton napsal(a):
>> https://fedoraproject.org/wiki/Changes/Ruby_2.6
>>
>> == Summary ==
>> Ruby 2.6 is the latest stable version of Ruby. Many new features and
>> improvements are included for the increasingly diverse and expanding
>> demands for Ruby. With this major update from Ruby 2.5 in Fedora 29 to
>> Ruby 2.6 in Fedora 30, Fedora becomes the superior Ruby development
>> platform.
>>
>> == Owner ==
>> * Name: [[User:vondruch| Vít Ondruch]], [[User:pvalena| Pavel Valena]]
>> * Email: vondr...@redhat.com, pval...@redhat.com
>>
>> == Detailed Description ==
>> Ruby 2.6 is upstream's new major release of Ruby. Many new features
>> and improvements are included.
>>
>> === JIT ===
>>
>> Ruby 2.6 introduces an initial implementation of JIT (Just-in-time) compiler.
>>
>> JIT compiler aims to improve performance of any Ruby program
>> execution. Unlike ordinary JIT compilers for other languages, Ruby’s
>> JIT compiler does JIT compilation in a unique way, which prints C code
>> to a disk and spawns common C compiler process to generate native
>> code.
>>
>> The main purpose of this JIT release is to provide a chance to check
>> if it works for your platform and to find out security risks before
>> the 2.6 release. JIT compiler is supported when Ruby is built by GCC,
>> Clang, or Microsoft VC++, which needs to be available on runtime.
>> Otherwise you can’t use it for now.
>>
>> As of Ruby 2.6.0 preview3, we achieved 1.7x faster performance than
>> Ruby 2.5 on CPU-intensive non-trivial benchmark workload called
>> Optcarrot. The performance on memory-intensive workload like Rails
>> application are going to be improved as well.
>>
>> === RubyVM::AST [Experimental] ===
>>
>> Ruby 2.6 introduces `RubyVM::AST` module.
>>
>> This module has `parse` method which parses a given ruby code of
>> string and returns AST (Abstract Syntax Tree) nodes, and `parse_file`
>> method which parses a given ruby code file and returns AST nodes.
>> `RubyVM::AST::Node` class is also introduced. You can get location
>> information and children nodes from `Node` objects. This feature is
>> experimental. Compatibility of the structure of AST nodes are not
>> guaranteed.
>>
>> === New Features ===
>>
>> * Add a new alias `then` to `Kernel#yield_self`.
>> * Add `Random.bytes`.
>> * Add `Binding#source_location`.  This method returns the source
>> location of binding, a 2-element array of __FILE__ and __LINE__.
>> * Add `:exception` option to let `Kernel.#system` raise error instead
>> of returning `false`.
>> * Add a new alias then to `Kernel#yield_self`.
>> * `else` without `rescue` now causes a syntax error. [EXPERIMENTAL]
>> * Constant names may start with a non-ASCII capital letter.
>> * An endless range, (1..), is introduced. It works as it has no end.
>>
>> === Performance improvements ===
>>
>> * Speedup `Proc#call` because we don’t need to care about $SAFE any
>> more. With `lc_fizzbuzz` benchmark it makes x1.4 speed improvement.
>> * Speedup `block.call` where block is passed block parameter. Ruby 2.6
>> improves the performance of passed block calling. There can observed
>> 2.6x improvement with micro-benchmarks.
>> * Transient Heap (theap) is introduced. theap is managed heap for
>> short-living memory objects which are pointed by specific classes. For
>> example, making small and short-living Hash object is x2 faster. With
>> rdoc benchmark, 6-7% performance improvement is observed.
>>
>> === Other notable changes since 2.5 ===
>>
>> * `$SAFE` is a process global state and we can set `0` again.
>> * Passing `safe_level` to `ERB.new` is deprecated. `trim_mode` and
>> `eoutvar` arguments are changed to keyword arguments.
>> * Merged RubyGems 3.0.0.beta2.
>> * Merge Bundler as default gem.
>>
>> == Benefit to Fedora ==
>>
>> With a latest release, Ruby language is supporting the newest language
>> features, which enables even faster and easier development of Ruby
>> applications.
>>
>> == Scope ==
>> * Proposal owners:
>> ** Finish packaging of Ruby 2.6. Current changes available in PR
>> https://src.fedoraproject.org/rpms/ruby/pull-request/32
>> ** Rebuilding of Ruby packages providing native extensions (i.e.
>> packages which depends on libruby).
>> .
>>
>> * Other developers:
>> ** Rebuild of packages wi

Re: NeuroFedora review swaps

[Ankur Sinha]

Hello,

I'd like to get this package reviewed please:

- python-pyscaffold: https://bugzilla.redhat.com/show_bug.cgi?id=1669913#

Would anyone like to swap reviews?

-- 
Thanks,
Regards,

Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha

Time zone: Europe/London


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Attempt to update ispc

[Luya Tshimbalanga]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On 2019-01-27 2:00 p.m., Florian Weimer wrote:
> * Luya Tshimbalanga:
>
>> On 2019-01-26 12:24 a.m., Dominik 'Rathann' Mierzejewski wrote:
>>> I would try patching out the clang requirement from CMakeLists
>>> and building with system gcc.
>>>
>>> Regards,
>>> Dominik
>> Done. Unfortunately, the build failed as the compiler still remains
>> clang and finding the cause is beyond my knowledge. Here is the resulted
>> scratch build:
>>
>>
>> https://koji.fedoraproject.org/koji/taskinfo?taskID=32277096
> Which sources are you building? Nothing like this is on the master
> branch on src.fedoraproject.org.
>
> Thanks,
> Florian
I avoided committing the update as I preferred to do a scratch-build
hence the link from koji.
Realizing the change can be seen on the master branch on
src.fedoraproject.org, I applied the update for view:
https://src.fedoraproject.org/rpms/ispc/blob/master/f/ispc.spec

I figured that gcc parameter was missing on %make_build and the failure
occurred on python line despite the available dependency:
https://koji.fedoraproject.org/koji/taskinfo?taskID=32307602

Luya
-BEGIN PGP SIGNATURE-

iQEzBAEBCAAdFiEEWyB+BQtYiFz4GUNDXlKBdNiiYJoFAlxO1GoACgkQXlKBdNii
YJpvLQgAoqqXkwQwMPwRjO6hQfETtcdU0R/OKJyaHXniTbFPf+stsNPR0YqKMWwD
FuvGNq7S+KscQG9EgFFMnVc19LSWDPoA+9jQF3KkZJFyaI8THx/4ekgVKHz/DkFt
lxL7UR3F++HWNwVfaBnJDOYm9+i8ZYRGMC8qw47i55NsfnuIMj5mNe30o0uvuIqP
xRT077YDisgTE/7dq9dkvWDqLaosqA3hfrtZSmS4EtmCcBvJa++Af72HKkbvC15p
SitFlMLxV46PwFDinxaSO0zyZQy/Su1nYRV6kGlA56ewEyGR6DJvgSd2IehFyo/F
JNP1gM0ssc3EiKGzNd40ugHx7ZlnIw==
=OZJV
-END PGP SIGNATURE-
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30 Self-Contained Change proposal: Ibus-typing-booster default for Indian languages

[Jens-Ulrik Petersen]

On Mon, Jan 28, 2019 at 8:04 AM Owen Taylor  wrote:

> I see that I have ibus-typing-booster installed, but I don't see any
> sign of it in the GNOME "Region & Language" panel input source
> selection. Does ibus-typing-booster look like one input support for
> each supported language, or does it look like a single input source?
>

ibus Typing Booster used to expose separate Input Sources for each language
it supports, but in 2.0 we unified it to a single Input Source under Other
languages.

Hope that helps, Jens
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30: Self-Contained Change proposal: Firefox Wayland By Default On Gnome

[Martin Stransky]

On 1/28/19 9:21 AM, Tom Hughes wrote:

On 25/01/2019 21:55, Tom Hughes wrote:

On 25/01/2019 21:24, Richard W.M. Jones wrote:

On Fri, Jan 25, 2019 at 09:43:32AM -0500, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/Firefox_Wayland_By_Default_On_Gnome 



== Summary ==
Firefox is going to run natively on Gnome Wayland session and won't
use XWayland/X11 Gtk+ backend. This change affects Gnome only and
won't be enabled for other Wayland compositors (KDE Plasma, Sway).


Does this mean it won't work on Xorg?


I was just going to ask whether this means there will now be
one binary that supports both and, if not, what this means for
people still forced into X fallback.


I think I've answered this myself - the current firefox-wayland
in F29 is just a script that sets GDK_BACKEND so there is already
only a single binary that does both. The only change is presumably
that it will prefer the wayland backend.


Yes, that's correct. Also I'm going use a slightly different solution 
[1] in next versions as GDK_BACKEND breaks third party programs launched 
from FF.



That said my testing of the F29 build had strangely variable
results - on one machine it was largely fine and on another it
was completely non-functional for reasons I haven't quite
managed to figure out yet.


Firefox 64 used on Fedora right now has limited Wayland support and 
misses some upstream patches. Please try mozilla nightly [2] with 
GDK_BACKEND=wayland set.


Also the upcoming Firefox 65 carries some new Wayland fixes.

Thanks,
ma.

[1] https://bugzilla.mozilla.org/show_bug.cgi?id=1522780
[2] https://www.mozilla.org/en-US/firefox/channel/desktop/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: F30: Self-Contained Change proposal: Firefox Wayland By Default On Gnome

[Tom Hughes]

On 25/01/2019 21:55, Tom Hughes wrote:

On 25/01/2019 21:24, Richard W.M. Jones wrote:

On Fri, Jan 25, 2019 at 09:43:32AM -0500, Ben Cotton wrote:
https://fedoraproject.org/wiki/Changes/Firefox_Wayland_By_Default_On_Gnome 



== Summary ==
Firefox is going to run natively on Gnome Wayland session and won't
use XWayland/X11 Gtk+ backend. This change affects Gnome only and
won't be enabled for other Wayland compositors (KDE Plasma, Sway).


Does this mean it won't work on Xorg?


I was just going to ask whether this means there will now be
one binary that supports both and, if not, what this means for
people still forced into X fallback.


I think I've answered this myself - the current firefox-wayland
in F29 is just a script that sets GDK_BACKEND so there is already
only a single binary that does both. The only change is presumably
that it will prefer the wayland backend.

That said my testing of the F29 build had strangely variable
results - on one machine it was largely fine and on another it
was completely non-functional for reasons I haven't quite
managed to figure out yet.

Tom

--
Tom Hughes (t...@compton.nu)
http://compton.nu/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org