No missing expected images.
Compose FAILS proposed Rawhide gating check!
4 of 47 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING**
below
Failed openQA tests: 13/131 (x86_64), 1/24 (i386), 1/2 (arm)
New failures (same test not failed in Rawhide-201
On Thu, Dec 20, 2018 at 07:38:29AM +0100, Igor Gnatenko wrote:
> So what process should I use? Pull Requests or just removing obsolete
> stuff? I'm ready to do either way. Should I leave this to FESCo?
The choice of implementation details is yours. You can always ask
FESCo for opinion, but I don't
On 12/19/18 4:31 PM, John Harris wrote:
On Wednesday, December 19, 2018 5:10:21 AM EST Bruno Wolff III wrote:
gnupg2 is now obsoleting gnupg and the previous gpg command is not
available.
The change page said gpg would be renamed gpg1, but this was
not done. Unfortunately gpg2 will not read my e
So what process should I use? Pull Requests or just removing obsolete
stuff? I'm ready to do either way. Should I leave this to FESCo?
On Wed, Dec 19, 2018 at 8:00 PM Jason L Tibbitts III wrote:
>
> > "KL" == Kalev Lember writes:
>
> KL> I agree with Zbyszek, I think it would be best to push
On 12/19/18 5:38 AM, Cătălin George Feștilă wrote:
Read all error (Problem: conflicting requests) and my dnf search (not
xchat) is reported like :
I don't like flame.
I'm not quite sure what you're trying to say here, but the "conflicting
requests" is because the package you want to install (g
On Wed, Dec 19, 2018 at 12:49:51PM -0600, Jason L Tibbitts III wrote:
> > "KL" == Kalev Lember writes:
>
> KL> I agree with Zbyszek, I think it would be best to push the changes
> KL> directly to git.
>
> But then we're back to the same problem: Do you remove the ldconfig
> calls entirely or
At the time yaml-cpp 0.6 was released several packages still needed the 0.3
API so the yaml-cpp03 package was created.
Currently no package requires the library on F28 through Rawhide and it has
a couple of CVE's attached to it that will not get fixed.
My intention since there are no dependencies
https://fedoraproject.org/wiki/Changes/DeepinDE
== Summary ==
Package the Deepin Desktop Environment for Fedora.
== Owner ==
* Name: [[User:Zsun|Zamir SUN]] - main coordinator, packager
* Email: zsun#AT#fedoraproject.org
* [[User:Mosquito|Bowen Li]] - main packager
* Email: mosquito#AT#fedorapro
As a reminder, several Change proposal deadlines for Fedora 30 are approaching:
* 2019-01-02 — Changes requiring infrastructure changes
* 2019-01-08 — Changes requiring mass rebuild
* 2019-01-08 — System-Wide changes
* 2019-01-29 — Self-Contained changes
For more information on Changes, see the C
> "KL" == Kalev Lember writes:
KL> I agree with Zbyszek, I think it would be best to push the changes
KL> directly to git.
But then we're back to the same problem: Do you remove the ldconfig
calls entirely or do you add the macros? Prepare for flames if you get
it wrong, even though it's no
On Wednesday, December 19, 2018 5:10:21 AM EST Bruno Wolff III wrote:
> gnupg2 is now obsoleting gnupg and the previous gpg command is not
> available.
> The change page said gpg would be renamed gpg1, but this was
> not done. Unfortunately gpg2 will not read my existing secret keys. (They
> are p
Bruno Wolff III wrote:
> In my case it would have helped if gnupg1 had obsoleted gnupg
IMO, that is a better and safer approach ^^
-- Rex
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
On 19. 12. 18 15:03, Kevin Kofler wrote:
Unfortunately, this list still contains many packages that were already
retired eons ago. (The information that the packages are retired must have
been lost for some reason during the migration to Pagure or during a Pagure
upgrade.) E.g., kdelibs4 was rena
On Wed, Dec 19, 2018, 15:09 Zbigniew Jędrzejewski-Szmek On Wed, Dec 19, 2018 at 11:22:21AM +0100, Igor Gnatenko wrote:
> > I've updated change which is explicitly mentions that I'm going to
> > send Pull Requests to packages, so it should not make anyone unhappy.
>
> Are you sure this is a viable
On Wed, Dec 19, 2018 at 11:22:21AM +0100, Igor Gnatenko wrote:
> On Wed, Dec 19, 2018 at 2:20 AM Jason L Tibbitts III
> wrote:
> >
> > > "ZJ" == Zbigniew Jędrzejewski-Szmek writes:
> >
> > ZJ> I think it's pretty clear: all the standard invocations of
> > ZJ> scriptlets that have by replaced
Unfortunately, this list still contains many packages that were already
retired eons ago. (The information that the packages are retired must have
been lost for some reason during the migration to Pagure or during a Pagure
upgrade.) E.g., kdelibs4 was renamed to kdelibs years ago. (It might make
Read all error (Problem: conflicting requests) and my dnf search (not
xchat) is reported like :
I don't like flame.
On Wed, Dec 19, 2018 at 3:30 PM Dominik 'Rathann' Mierzejewski
wrote:
>
> On Wednesday, 19 December 2018 at 14:25, Cătălin George Feștilă wrote:
> > Can the problem of packet depend
=
#fedora-meeting-3: Weekly Meeting of the Modularity Working Group
=
Meeting started by nils at 15:00:00 UTC.
Minutes:
https://meetbot.fedoraproject.org/fedora-meetin
On Wednesday, 19 December 2018 at 14:25, Cătălin George Feștilă wrote:
> Can the problem of packet dependencies create such results? I do not
> see X-chat software.
Try hexchat:
$ rpm -q hexchat
hexchat-2.14.2-1.fc29.x86_64
Also, this is a user question, not a developer one, so please ask such
q
On Sat, Dec 15, 2018 at 7:39 AM Bruno Wolff III wrote:
>
> On Wed, Dec 12, 2018 at 12:37:24 -0600,
> Bruno Wolff III wrote:
> >On Thu, Dec 06, 2018 at 14:29:15 +,
> > "Richard W.M. Jones" wrote:
> >>
> >>Anyway it seems like Rawhide isn't getting new nodebug kernels.
> >>
> >>- Latest node
Can the problem of packet dependencies create such results? I do not
see X-chat software.
[root@desk mythcat]# dnf search chat
Last metadata expiration check: 0:18:23 ago on Tue 18 Dec 2018 07:53:20 PM EET.
...
On Tue, Dec 18, 2018 at 9:00 PM Scott Talbert wrote:
>
> On Tue, 18 Dec 2018, Cătălin
On Wed, Dec 19, 2018 at 11:28:16 +0100,
Igor Gnatenko wrote:
Seems that I missed writing announcement, but there is a package
called `gnupg1` which provides `gpg1` binary.
So you should be fine with that I hope. And sorry for this trouble.
Thanks for the help.
I'm not sure why I didn't find
Seems that I missed writing announcement, but there is a package
called `gnupg1` which provides `gpg1` binary.
So you should be fine with that I hope. And sorry for this trouble.
On Wed, Dec 19, 2018 at 11:25 AM Bruno Wolff III wrote:
>
> gnupg2 is now obsoleting gnupg and the previous gpg comma
On Wed, Dec 19, 2018 at 2:20 AM Jason L Tibbitts III wrote:
>
> > "ZJ" == Zbigniew Jędrzejewski-Szmek writes:
>
> ZJ> I think it's pretty clear: all the standard invocations of
> ZJ> scriptlets that have by replaced by transfiletriggers will be
> ZJ> removed, along with the whole %post/%postu
gnupg2 is now obsoleting gnupg and the previous gpg command is not available.
The change page said gpg would be renamed gpg1, but this was not done.
Unfortunately gpg2 will not read my existing secret keys. (They are pretty
old and probably should be replaced.) For now using rpm --nodeps allowed
Hey folks,
since 18.3.1-2 mesa is built using meson. Please let me know if it
breaks anything.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://get
On Wed, Dec 19, 2018 at 09:54:07AM +0100, Michal Novotny wrote:
> Hello Fedora devels!
>
> TL;DR: let's use rpm DistTag (DistTag, not the %dist macro) to denote
> stream names
>
> As we all know, modularity was created to provide
> parallel-availability, that is providing the same package in its
> Hi list,
>
> I have discovered a very weird problem with the package bear on
> apps.fedoraproject.org: it got somehow mixed with the (completely
> unrelated) packages erlang-bear, bear-devel and bear-factory.
> My actual question: what is going on? How do I get out of this mess?
>
>
> Thanks
Hello Fedora devels!
TL;DR: let's use rpm DistTag (DistTag, not the %dist macro) to denote
stream names
As we all know, modularity was created to provide
parallel-availability, that is providing the same package in its
different major versions from the same rpm repository.
The first question to
29 matches
Mail list logo
