On Fri, 2017-08-25 at 14:38 +0200, Kevin Kofler wrote:
> Jan Kurik wrote:
> > * Other developers:
> > Maintainers, should
> > - Verify that their software is linked with the libidn library
> > - Update the software from upstream if it already has been
> > converted to
> > libidn2
> > - Check the li
On Fri, 2017-08-25 at 08:56 -0500, Michael Catanzaro wrote:
> On Fri, Aug 25, 2017 at 1:24 AM, Jan Kurik wrote:
> > The proposed change is about deprecating libidn, which supports
> > IDNA2003, and switch all applications using libidn, to libidn2
> > 2.0.0,
> > which supports IDNA2008.
>
> Any pl
On Monday, August 28, 2017 1:59:42 AM CEST Kevin Kofler wrote:
> Björn Persson wrote:
>
> > To me it looks like an attempt to recruit packagers to help promoting
> > the change _upstream_.
>
>
> There is no upstream for kdelibs3. It is a compatibility package, which is
> 2 major (first digit!) v
I would like to add, that apparently the capitalization of subpackages also
changed. This broke dependencies for me. I don't know if this was intended.
Please see:
https://bugzilla.redhat.com/show_bug.cgi?id=1485703
If it was intended, I am happy to fix this, otherwise please check your script
t
On 28.08.2017 02:03, Kevin Kofler wrote:
Sandro Mani wrote:
Right, I suppose given the smallish audience affected by this, it's
better to violate the update guidelines once than introducing a
permanent epoch bump.
FYI, there are still ongoing plans to upgrade the native qt5-qtbase in F26
to 5
Neal Gompa wrote:
> RPM itself is now sufficiently advanced that it can take on all the
> roles of composition group metadata. They would essentially be transformed
> into metapackages. This has already happened on the SUSE side, where
> their patterns are now just metapackages with Provides that t
On Mon, Aug 28, 2017 at 4:34 AM, Kevin Kofler wrote:
> Neal Gompa wrote:
>> RPM itself is now sufficiently advanced that it can take on all the
>> roles of composition group metadata. They would essentially be transformed
>> into metapackages. This has already happened on the SUSE side, where
>> t
On Tue, Aug 22, 2017 at 05:00:05PM -0700, Kevin Fenzi wrote:
> python-basemap seems wrong...
>
> There's now a python3-basemap and a python2-basemap-examples but no
> python2-basemap. ;(
Oops, sorry for the late reply, I somehow missed this your mail.
My script was confused by the -examples subpa
On 28.08.2017 10:04, Johannes Lips wrote:
I would like to add, that apparently the capitalization of subpackages also
changed. This broke dependencies for me. I don't know if this was intended.
Please see:
https://bugzilla.redhat.com/show_bug.cgi?id=1485703
If it was intended, I am happy to f
On Wed, Aug 23, 2017 at 11:39:20AM +0200, Kalev Lember wrote:
> On 08/23/2017 02:00 AM, Kevin Fenzi wrote:
> > Also, I'd like to very much thank you for doing this work. :)
> > It's great to get done, it's great to do it quickly and I know it's a
> > lot of hard work to script and build things.
>
W dniu 12.08.2017 o 17:15, Zbigniew Jędrzejewski-Szmek pisze:
> atomic-reactor/ ftbfs (AttributeError: module 'docker' has no
> attribute 'Client')
Looks like it uses 'docker-py' rather than 'docker' one which is the one
other projects migrated to.
docker.Client -> docker.APIClient re
On Mon, Aug 28, 2017 at 02:01:19PM +0200, Sandro Mani wrote:
>
>
> On 28.08.2017 10:04, Johannes Lips wrote:
> >I would like to add, that apparently the capitalization of subpackages also
> >changed. This broke dependencies for me. I don't know if this was intended.
This is on purpose: the new
On Mon, Aug 28, 2017 at 02:11:16PM +0200, Marcin Juszkiewicz wrote:
> W dniu 12.08.2017 o 17:15, Zbigniew Jędrzejewski-Szmek pisze:
> > atomic-reactor/ ftbfs (AttributeError: module 'docker' has no
> > attribute 'Client')
>
> Looks like it uses 'docker-py' rather than 'docker' one which
On 08/27/2017 11:11 PM, Honggang LI wrote:
> On Tue, Aug 22, 2017 at 09:29:58AM -0700, Kevin Fenzi wrote:
>> On 08/22/2017 02:30 AM, Petr Pisar wrote:
>>> On 2017-08-22, Honggang LI wrote
...snip...
>
> I will file tickets to retire those packages as "fedpkg retire" can't
> retire them.
No need
On 26 August 2017 at 16:21, Björn Persson wrote:
> Tomasz Kłoczko wrote:
> > This how it IMO should be done:
> [..]
> That looks like a good plan for how large numbers of translators can
> contribute translations to many different languages.
>
> Writing the translations directly in the spec doesn
W dniu 28.08.2017 o 14:31, Zbigniew Jędrzejewski-Szmek pisze:
> On Mon, Aug 28, 2017 at 02:11:16PM +0200, Marcin Juszkiewicz wrote:
>> W dniu 12.08.2017 o 17:15, Zbigniew Jędrzejewski-Szmek pisze:
>>> atomic-reactor/ ftbfs (AttributeError: module 'docker' has no
>>> attribute 'Client')
>
On Wed, Aug 23, 2017 at 9:13 AM, Bruno Wolff III wrote:
> On Wed, Aug 23, 2017 at 08:57:30 -0400,
> Mauricio Tavares wrote:
>
>> I think I read here (or in other mailing list) about an interest in
>> dropping 32bit altogether. But this might be just my imagination.
>>
>
> Certainly there was a
On Wed, Aug 23, 2017 at 10:47 AM, Peter Jones wrote:
> On Wed, Aug 23, 2017 at 07:27:44AM -0500, Bruno Wolff III wrote:
> > Currently grub2 isn't being built for i686 since somewhere between 2.02-8
> > and 2.02-10.
> > I looked through the change log (but not the git log yet) and didn't see
> > a
Hello Robert-André,
Could you please review these three relatively simple packages in return?
* https://bugzilla.redhat.com/1484835 - erlang-stdlib2
* https://bugzilla.redhat.com/1484843 - erlang-chronos
* https://bugzilla.redhat.com/1484846 - erlang-hyper
2017-08-17 18:45 GMT+02:00 Robert-André
On Tue, Jul 11, 2017 at 10:26:03PM +0200, Florian Weimer wrote:
> I ran into this unannounced change:
>
> https://fedoraproject.org/wiki/Changes/Stop_Building_i686_Kernels
>
> If this is accepted, all x86 hardware on which Fedora can run will
> support SSE2, and we should reflect that in the i6
On Fri, Aug 25, 2017 at 07:26:20PM -0400, Ben Rosser wrote:
> I have similar concerns and frustrations as Neal does, I think.
>
> I first want to comment that I appreciate your willingness to engage
> people (like Neal, and like myself) who seem frustrated with the
> future direction of Fedora. An
On Sat, Aug 26, 2017 at 04:04:27AM +0200, Kevin Kofler wrote:
> You could actually just have skipped the October-November release as you did
> during the F21 cycle, leading to a single 9-month cycle, then back to 6
> months. I think a 9-month cycle would be much more realistic than a 3-month
> c
On 08/28/2017 04:11 PM, Tomasz Torcz wrote:
> On Tue, Jul 11, 2017 at 10:26:03PM +0200, Florian Weimer wrote:
>> I ran into this unannounced change:
>>
>> https://fedoraproject.org/wiki/Changes/Stop_Building_i686_Kernels
>>
>> If this is accepted, all x86 hardware on which Fedora can run will
>>
On 2017-08-28, Matthew Miller wrote:
>> > Modularity will allowing *us* at the packaging end to separate source
>> > and spec lifecycle from binary and artifact lifecycle.
>> That, by itself, is not a goal. It is a way to achieve an unspecified goal.
>
> Sure, that's fair. Here's the goal: users
On 07/12/2017 03:44 PM, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jul 12, 2017 at 08:44:02AM -0400, Matthew Miller wrote:
On Wed, Jul 12, 2017 at 01:20:58PM +0200, Ralf Corsepius wrote:
The fact that i686 kernels continue to work in general is basically luck.
You probably will deny this, but
On 08/28/2017 04:35 PM, Florian Weimer wrote:
https://bugzilla.redhat.com/show_bug.cgi?id=1482798
(Bug 1482798 - Illegal instruction in SHA1_Update() when used by chronyd)
That's definitely a bug for F27.
nss-softok is broken in similar ways on fedora-26-i686
Ralf
___
Le lundi 28 août 2017 à 15:49:54 (+0200), Peter Lemenkov a écrit :
> Hello Robert-André,
> Could you please review these three relatively simple packages in return?
>
> * https://bugzilla.redhat.com/1484835 - erlang-stdlib2
> * https://bugzilla.redhat.com/1484843 - erlang-chronos
> * https://bugzi
De: "Kevin Kofler"
Matthew Miller wrote:
>> And, it will also allow those of us working on assembling spins and more
>> options — for example, we can have different streams for Atomic without
>> needing to actually duplicate every package. (And we could do the same for
>> KDE or whatever other a
On 08/26/2017 08:16 PM, Sandro Mani wrote:
Hi
I've got an odd situation with mingw-qt5-qtbase on f26: in git, I have
version 5.7.1, however there is a mingw-qt5-qtbase-5.8.0-3.fc26 in koji
[2] which I cannot understand where it came from, considering also that
other 5.7.1-x versions have been
Hello folks,
I'm planning to update jsoncpp on Rawhide and fc27 during the next
days. After the builds have landed, I'll take care of rebuilding all
consumers against the new so name. Since the API / ABI has no publicly
consumed symbols removed, I don't expect any real problems.
Cheers,
On 28 August 2017 at 11:00, Ralf Corsepius wrote:
> On 07/12/2017 03:44 PM, Zbigniew Jędrzejewski-Szmek wrote:
>>
>> On Wed, Jul 12, 2017 at 08:44:02AM -0400, Matthew Miller wrote:
>>>
>>> On Wed, Jul 12, 2017 at 01:20:58PM +0200, Ralf Corsepius wrote:
>
> The fact that i686 kernels contin
Dear all,
You are kindly invited to the meeting:
Modularity Office Hours on 2017-08-29 from 10:00:00 to 11:00:00 US/Eastern
At https://meet.jit.si/fedora-modularity
The meeting will be about:
This is where you ask the Fedora Modularity Team questions (and we try to
answer them)!
Join us o
Matthew Miller wrote:
> Sure, that's fair. Here's the goal: users will have more options
> without exponentially increasing work for packagers and
> distro-creators.
The exponential number of combinations will still exist, it will just be out
of our, or really anybody's, control. It is impossible
Missing expected images:
Cloud_base qcow2 x86_64
Workstation live i386
Cloud_base raw-xz x86_64
Server boot i386
Kde live i386
Failed openQA tests: 75/137 (x86_64), 16/18 (i386), 1/2 (arm)
New failures (same test did not fail in Rawhide-20170826.n.0):
ID: 135545 Test: x86_64 universal inst
Rebuild status:
* All F25/F26 packages have been rebuilt against ImageMagick 6.9.9.9
* Most of the F27+ packages have been rebuilt with the following exceptions:
- cuneiform
FTBFS since Fedora 23, last upstream release is from 2011
- imageinfo
Requires porting, upstream is alive. I may
Missing expected images:
Cloud_base qcow2 x86_64
Atomic qcow2 x86_64
Workstation live i386
Cloud_base raw-xz x86_64
Server boot i386
Atomic raw-xz x86_64
Kde live i386
Failed openQA tests: 71/126 (x86_64), 16/18 (i386), 1/2 (arm)
Old failures (same test failed in 27-20170827.n.0):
ID: 135607
36 matches
Mail list logo
