On 03/06/2018 03:40 PM, Kevin Kofler wrote:
> Michal Ruprich wrote:
>> the plan to drop the GTK+ GUI [1] was approved by FESCO, so I will be
>> dropping the wireshark-gtk package in rawhide(currently F29). Also I
>> would like to propose that we change the name of wireshark-qt. There are
>> three
On 7 March 2018 at 04:12, Nathaniel McCallum wrote:
>
> https://bodhi.fedoraproject.org/updates/grubby-8.40-10.fc28
>
> We've built grubby with support for /boot on btrfs. We're trying to
> land this in F28. But we need testers. That's where you come in! If
> you ever interact with grubby and espe
On Thu, Mar 08, 2018 at 08:26:30PM -0800, Kevin Fenzi wrote:
> On 03/08/2018 07:53 PM, Kevin Kofler wrote:
> > Randy Barlow wrote:
> >> It may be possible to automate the process a bit to make it less heavy
> >> for developers, though there is some complication for multi-package
> >> updates
> >
>
On Fri, 2018-03-09 at 10:06 +0100, Pierre-Yves Chibon wrote:
> On Thu, Mar 08, 2018 at 08:26:30PM -0800, Kevin Fenzi wrote:
> > On 03/08/2018 07:53 PM, Kevin Kofler wrote:
> > > Randy Barlow wrote:
> > > > It may be possible to automate the process a bit to make it
> > > > less heavy
> > > > for de
On Thu, Mar 08, 2018 at 01:00:32PM -0500, Randy Barlow wrote:
> I would like to kick off a general discussion about how we might gate
> packages in Rawhide. I think it would be nice to get something in place
> for the Fedora 29 timeframe.
I was waiting to have some more time to work on it to kick
On Fri, Mar 09, 2018 at 10:12:37AM +0100, Mathieu Bridon wrote:
> We could take a hint from how we make software upstream these days:
>
> 1. submit a pull request for the package in src.fp.o on the master
>branch
> 2. a CI automatically builds this package in Koji
> 3. merge the pull request i
Thanks for starting this discussion and I really want to thank you for
offering Bodhi to handle the Rawhide. It would be really sad I some
other system was used for Rawhide then for stable versions.
Dne 9.3.2018 v 10:20 Pierre-Yves Chibon napsal(a):
> On Thu, Mar 08, 2018 at 01:00:32PM -0500, Ran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have built RPM with backported with/without/unless rich deps for F26.
https://copr.fedorainfracloud.org/coprs/ignatenkobrain/rpm-4.13.x-richd
eps/
Just update from this repo before doing distro-sync/system-upgrade and
you should be good.
- --
-
Dne 8.3.2018 v 10:13 Vít Ondruch napsal(a):
>
>
> Dne 8.3.2018 v 09:19 Igor Gnatenko napsal(a):
>> On Wed, 2018-03-07 at 16:39 +0100, Vít Ondruch wrote:
>>
>> > Dne 7.3.2018 v 15:08 Jerry James napsal(a):
>> >> On Wed, Mar 7, 2018 at 12:43 AM, Igor Gnatenko
>> >> wrote:
>> >>> This is the second
On Fri, Mar 09, 2018 at 10:52:27AM +0100, Vít Ondruch wrote:
> I had a different idea in mind, basically try to keep the experience as
> close as
> what it is now.
> for single package:
>- packager commit
>- packager build
>- build is tagged into a specfic koji tag
>- test are r
Dne 9.3.2018 v 11:24 Pierre-Yves Chibon napsal(a):
> On Fri, Mar 09, 2018 at 10:52:27AM +0100, Vít Ondruch wrote:
>> I had a different idea in mind, basically try to keep the experience as
>> close as
>> what it is now.
>> for single package:
>>- packager commit
>>- packager build
>>
Hello,
Gating is failed for some weird reason:
# Test died: command 'dnf -y install bodhi-client git createrepo koji'
failed at /var/lib/openqa/share/tests/fedora/lib/utils.pm line 383.
https://bodhi.fedoraproject.org/updates/FEDORA-2018-fda9fed6fd
I suppose it's known issue. Is there any way to
The goal I have in mind for such a SIG would be to:
* Maintain the Node.js packages (npm/nodejs)
* Promote Node.js usage in Fedora!
* Establish a community of JavaScript devs to share code, fixes, etc.
I noticed that there wasn't a SIG already for this, so I hope that this
isn't inconvenient.
I'
On 09/03/18 11:56, Elliott Pardee wrote:
The goal I have in mind for such a SIG would be to:
* Maintain the Node.js packages (npm/nodejs)
* Promote Node.js usage in Fedora!
* Establish a community of JavaScript devs to share code, fixes, etc.
I noticed that there wasn't a SIG already for this,
= Proposed Self Contained Change: OpenLDAP: Drop MozNSS Compatibility Layer =
https://fedoraproject.org/wiki/Changes/OpenLDAPdropMozNSSCompatibilityLayer
Owner(s):
* Matus Honek
Since Fedora 28, OpenLDAP is compiled with OpenSSL instead of NSS and
includes MozNSS Compatiblity Layer (i.e. TLS
Hi,
I don't really know how I got to this list. I do have my new email
address in FAS and I haven't gotten any questions about the AADG recently.
Regards,
Vratislav
On 03/05/2018 09:10 PM, Kevin Fenzi wrote:
> Greetings, we've been told that the email addresses for these package
> maintainers
On Fri, Mar 9, 2018 at 7:06 AM Tom Hughes wrote:
> On 09/03/18 11:56, Elliott Pardee wrote:
> > The goal I have in mind for such a SIG would be to:
> >
> > * Maintain the Node.js packages (npm/nodejs)
> > * Promote Node.js usage in Fedora!
> > * Establish a community of JavaScript devs to share c
On Thu, 2018-03-08 at 11:24 -0800, Kevin Fenzi wrote:
> On 03/08/2018 11:11 AM, Richard Shaw wrote:
> > What about making side tags easily available to packagers directly? I could
> > build my package that includes an ABI breaking update and rebuild the
> > dependencies within that side tag and the
Some x86_64 packages need a 32-bit glibc during build time. Koji does
not provide it.
Unfortunately, there is no way to permanently block glibc32 from
entering composes. We have repeatedly asked for it. It simply does not
happen. If end users install glibc32, there system may be irrevocabl
On Fri, Mar 9, 2018 at 8:07 AM, Florian Weimer wrote:
> Some x86_64 packages need a 32-bit glibc during build time. Koji does not
> provide it.
>
> Unfortunately, there is no way to permanently block glibc32 from entering
> composes. We have repeatedly asked for it. It simply does not happen.
Martin Kolman wrote:
> That would be really nice! There are often cases where a fix or
> enhancement needs to land in at least two components at once (in our cases
> usually pykickstart & anaconda and/or blivet & anaconda) and the only
> "atomic" way of doing that is doing a chainbuild, which, fran
Milan Crha wrote:
> so it looks like you are going to remove chain-build from fedpkg,
> right? It's kind of pain it doesn't work for stable, but if you want to
> get rid of it for rawhide too, or add some unnecessary obstacles for
> its usage, then it's a downgrade like the kerberos usage (it's a p
On 03/09/2018 02:21 PM, Josh Boyer wrote:
So as a stop-gap measure, I'd like to add this:
Conflicts: kernel
That's a metapackage now, which isn't actually required for installs.
Better to do it on kernel-core, however..
Noted.
to the glibc32 package, to make it very unlikely that end user
Kevin Fenzi wrote:
> To be fair, there was a suggestion that we show results in
> pagure/src.fedoraproject.org, but to me, that definitely sounds like the
> wrong place for such things.
I think they should be displayed in Koji on the build info page for the
particular build that was tested. That
Pierre-Yves Chibon wrote:
> I had a different idea in mind, basically try to keep the experience as
> close as what it is now.
Your proposal makes sense, it sounds like how I would do it too. If we want
gating at all, it should be done that way.
Kevin Kofler
_
On Fri, Mar 9, 2018 at 8:44 AM, Florian Weimer wrote:
> On 03/09/2018 02:21 PM, Josh Boyer wrote:
>
>>> So as a stop-gap measure, I'd like to add this:
>>>
>>> Conflicts: kernel
>>
>>
>> That's a metapackage now, which isn't actually required for installs.
>> Better to do it on kernel-core, howeve
On 03/09/2018 02:52 PM, Josh Boyer wrote:
Stepping back a bit, I'm curious why glibc32 would land in the
composes. It shouldn't... it should only be tagged in the fNN-build
tags, which the composes should not pull from. Where do we have
recent issues of it getting pulled into a compose?
It
El vie, 09-03-2018 a las 14:55 +0100, Florian Weimer escribió:
> On 03/09/2018 02:52 PM, Josh Boyer wrote:
>
> > Stepping back a bit, I'm curious why glibc32 would land in the
> > composes. It shouldn't... it should only be tagged in the fNN-
> > build
> > tags, which the composes should not pul
On 03/09/2018 03:01 PM, Dennis Gilmore wrote:
El vie, 09-03-2018 a las 14:55 +0100, Florian Weimer escribió:
On 03/09/2018 02:52 PM, Josh Boyer wrote:
Stepping back a bit, I'm curious why glibc32 would land in the
composes. It shouldn't... it should only be tagged in the fNN-
build
tags, whi
A more modern architecture would be something closer to pull requests on
dist-git;
tests report into the PR the same way github works today.
This would work *particularly* well if it was easy to make a pull request across
multiple packages, which would be obvious and easy if we just one git repo
On Fri, Mar 9, 2018, at 9:23 AM, Colin Walters wrote:
> A more modern architecture would be something closer to pull requests on
> dist-git;
> tests report into the PR the same way github works today.
>
> This would work *particularly* well if it was easy to make a pull request
> across
> mult
> On Do, 08.03.18 16:51, Zbigniew Jędrzejewski-Szmek (zbyszek(a)in.waw.pl)
> wrote:
>
>
> Urks. That form doesn't support searching by real name. Adam, what's
> you fedora user name?
>
My FAS name is "agoode".
Thanks!
___
devel mailing list -- deve
Dne 9.3.2018 v 15:23 Colin Walters napsal(a):
> A more modern architecture would be something closer to pull requests on
> dist-git;
> tests report into the PR the same way github works today.
May be if we had all .spec files in single repository .
V.
>
> This would work *particularly* w
On Mon, 29 Jan 2018 15:38:00 +0100, Michael Schwendt wrote:
> On Tue, 9 Jan 2018 18:46:06 +0100, Jan Kurik wrote:
>
> > = System Wide Change: Replace glibc's libcrypt with libxcrypt =
> > https://fedoraproject.org/wiki/Changes/Replace_glibc_libcrypt_with_libxcrypt
> >
> > Change owner(s):
> > *
On 01/29/2018 03:38 PM, Michael Schwendt wrote:
The reason why I ask is that Claws Mail still uses encrypt() with the sole
purpose of being able to decrypt old passwords. It doesn't convert them to
different encryption algorithms automatically, unless the user changes the
password, and it doesn't
On Fri, 9 Mar 2018 16:14:39 +0100, Florian Weimer wrote:
> On 01/29/2018 03:38 PM, Michael Schwendt wrote:
> > The reason why I ask is that Claws Mail still uses encrypt() with the sole
> > purpose of being able to decrypt old passwords. It doesn't convert them to
> > different encryption algorith
On 03/09/2018 04:26 PM, Michael Schwendt wrote:
On Fri, 9 Mar 2018 16:14:39 +0100, Florian Weimer wrote:
On 01/29/2018 03:38 PM, Michael Schwendt wrote:
The reason why I ask is that Claws Mail still uses encrypt() with the sole
purpose of being able to decrypt old passwords. It doesn't convert
On 03/08/2018 03:54 PM, Kevin Kofler wrote:
> I wrote:
>> Fedora:
>>> Beta and Final freezes are in effect from 00:00 UTC of the freeze day.
>>
>> KDE:
>>> All deadlines are due 23:59 UTC, but if you need a few more hours, notify
>>> someone from the release team.
>
> PS: The deadlines I encount
On 8 March 2018 at 14:37, Tony Nelson wrote:
> On 18-03-07 14:14:38, Nicolas Mailhot wrote:
>>
>> Le mercredi 07 mars 2018 à 12:18 -0500, Josh Boyer a écrit :
>> > On Wed, Mar 7, 2018 at 12:11 PM, Nicolas Mailhot
>> > wrote:
>> > > Le mercredi 07 mars 2018 à 11:31 -0500, Stephen John Smoogen a éc
On 03/06/2018 05:55 PM, Sérgio Basto wrote:
Again, IMHO, wiki page should be updated (add something like: -z defs
was postponed ... ) and still it should be added a link to
buildflags.md .
Okay, I made some edits.
BTW "%define _strict_symbol_defs_build 1" will enable -z defs ?
Yes.
Thanks,
I'm trying this, on a relatively up-to-date Fedora 27 machine
(mock-1.4.9-1.fc27.noarch):
mock -r fedora-28-x86_64 --init
and get:
Start: dnf install
Error: Failed to synchronize cache for repo 'updates'
WARNING: Machine 00b000ffcd4543ddbe52926cee6d50d5 still running. Killing...
ERROR: Command
On Fri, 2018-03-09 at 17:47 +0100, Florian Weimer wrote:
> I'm trying this, on a relatively up-to-date Fedora 27 machine
> (mock-1.4.9-1.fc27.noarch):
>
> mock -r fedora-28-x86_64 --init
>
> and get:
>
> Start: dnf install
> Error: Failed to synchronize cache for repo 'updates'
> WARNING: Machi
On 03/09/2018 06:03 PM, Sérgio Basto wrote:
On Fri, 2018-03-09 at 17:47 +0100, Florian Weimer wrote:
I'm trying this, on a relatively up-to-date Fedora 27 machine
(mock-1.4.9-1.fc27.noarch):
mock -r fedora-28-x86_64 --init
and get:
Start: dnf install
Error: Failed to synchronize cache for rep
Hi list,
latest F28 mame build [1] has failed at the linking stage on x86_64 only
with the following error:
`_ZSt20__replacement_assertPKciS0_S0__end' referenced in section
`.gnu.build.attributes' of
../../../../linux_gcc/bin/x64/Release/mame_mame/libsega.a(model1.o):
defined in discarded section
Minutes:
https://meetbot.fedoraproject.org/fedora-meeting/2018-03-09/fesco.2018-03-09-15.00.html
Minutes (text):
https://meetbot.fedoraproject.org/fedora-meeting/2018-03-09/fesco.2018-03-09-15.00.txt
Log:
https://meetbot.fedoraproject.org/fedora-meeting/2018-03-09/fesco.2018-03-09-15.00.log.html
On Fri, 2018-03-09 at 10:38 +0100, Pierre-Yves Chibon wrote:
> On Fri, Mar 09, 2018 at 10:12:37AM +0100, Mathieu Bridon wrote:
> > We could take a hint from how we make software upstream these days:
> >
> > 1. submit a pull request for the package in src.fp.o on the master
> >branch
> > 2. a C
On 03/08/2018 11:10 PM, Milan Crha wrote:
> On Thu, 2018-03-08 at 11:24 -0800, Kevin Fenzi wrote:
>> * CI/automated tests run on it, and if all is ok goes out in the next
>> rawhide compose.
>> * If not ok, you could wave the results or build more things/edit the
>> update until it passes.
>
>
Thomasz, could you please leave karma on the bodhi update?
https://bodhi.fedoraproject.org/updates/grubby-8.40-10.fc28
I already have a patch against anaconda.
https://github.com/rhinstaller/anaconda/pull/1375
On Fri, Mar 9, 2018 at 4:04 AM, Tomasz Kłoczko
wrote:
> On 7 March 2018 at 04:12, N
On 03/09/2018 03:02 AM, Pavel Zhukov wrote:
> Hello,
> Gating is failed for some weird reason:
>
> # Test died: command 'dnf -y install bodhi-client git createrepo koji'
> failed at /var/lib/openqa/share/tests/fedora/lib/utils.pm line 383.
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2018-f
On 03/09/2018 04:08 AM, Vratislav Podzimek wrote:
> Hi,
>
> I don't really know how I got to this list. I do have my new email
> address in FAS and I haven't gotten any questions about the AADG recently.
As long as your email address is up to date in fas you should be fine. :)
kevin
--
>
>
> R
On 03/09/2018 05:42 AM, Kevin Kofler wrote:
> Broken dependency notifications are disabled because the scripts are broken:
> they still use yum, which does not support the boolean dependencies. It is
> sad that this was still not fixed after months. Instead of wasting their
> time on annoyances
On 03/09/2018 09:12 AM, Florian Weimer wrote:
> On 03/09/2018 06:03 PM, Sérgio Basto wrote:
>> On Fri, 2018-03-09 at 17:47 +0100, Florian Weimer wrote:
>>> I'm trying this, on a relatively up-to-date Fedora 27 machine
>>> (mock-1.4.9-1.fc27.noarch):
>>>
>>> mock -r fedora-28-x86_64 --init
>>>
>>> a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/08/2018 11:18 PM, Adam Williamson wrote:
> On Thu, 2018-03-08 at 22:25 -0500, Dusty Mabe wrote:
>>
>> On 03/08/2018 08:17 PM, Fedora compose checker wrote:
>>> Missing expected images:
>>>
>>> Atomichost qcow2 x86_64
>>> Atomichost raw-xz x86
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 03/09/2018 09:33 PM, Dusty Mabe wrote:
>
> I honestly think we should
>
> - #1 - make Cloud an empty variant (It's useless, and we build repos for no
> reason)
> - #2 - Cloud base images get built from Everything and put in Cloud/ director
On Fri, 2018-03-09 at 21:42 -0500, Dusty Mabe wrote:
>
> On 03/09/2018 09:33 PM, Dusty Mabe wrote:
> >
>
>
> > I honestly think we should
> >
> > - #1 - make Cloud an empty variant (It's useless, and we build repos for no
> > reason)
> > - #2 - Cloud base images get built from Everything an
Kevin Fenzi wrote:
> On 03/09/2018 05:42 AM, Kevin Kofler wrote:
>
>> Because a broken dependency in ANY package included on ANY
>> release-critical deliverable now fails the ENTIRE compose process. It is
>> clear that this does not scale.
>
> That is not what is causing the broken composes. See
Kevin Fenzi wrote:
> yeah, but you would have even better workflow with a side tag.
The problem with a workflow relying entirely on side tags is that it is
going to increase the risk of conflicts with concurrent changes (a
phenomenon already somewhat present where side tags are used, but using s
On Fri, 2018-03-09 at 12:02 +0100, Pavel Zhukov wrote:
> Hello,
> Gating is failed for some weird reason:
>
> # Test died: command 'dnf -y install bodhi-client git createrepo koji'
> failed at /var/lib/openqa/share/tests/fedora/lib/utils.pm line 383.
>
> https://bodhi.fedoraproject.org/updates/FE
No missing expected images.
Passed openQA tests: 2/2 (x86_64)
--
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedorap
59 matches
Mail list logo
