ok. I have pushed 6.9.9-3 to rawhide.
Hopefully I got all the CVE's right in the changelog.
If someone wants to check over and make sure I didn't miss any that were
fixed in the 6.x branch that would be great.
I'd like to let it run a few days in rawhide before updating stable
branches, just in c
On Wed, 2017-07-26 at 16:27 -0700, Adam Williamson wrote:
> On Wed, 2017-07-26 at 16:17 -0700, Adam Williamson wrote:
> > Hi, folks! This is just a heads-up for anyone who's been watching the
> > openQA test results for an update, or something, and been confused.
> >
> > A few days ago we added a
On 07/27/2017 10:11 AM, Michael Catanzaro wrote:
> Ouch.
>
> Since the unresponsive maintainer process takes some time, could a
> provenpackager please update ImageMagick while we wait for this to go
> through?
I can try and update to the latest 6.x version... but looks like 7.x
changes api and w
Thanks. Looks like the old one was already closed for being old.
New review is here: https://bugzilla.redhat.com/show_bug.cgi?id=1476014
I'm happy to swap with someone.
Thanks,
Michael
On Thu, 27 Jul 2017, at 07:55 PM, Jason L Tibbitts III wrote:
> > "MC" == Michael Cullen writes:
>
> MC>
On Thu, 2017-07-27 at 13:32 -0400, Josh Boyer wrote:
> On Thu, Jul 27, 2017 at 12:02 PM, Adam Williamson
> wrote:
> > On Thu, 2017-07-27 at 06:09 -0400, Josh Boyer wrote:
> > > On Wed, Jul 26, 2017 at 7:17 PM, Adam Williamson
> > > wrote:
> > > > Hi, folks! This is just a heads-up for anyone who'
> "MC" == Michael Cullen writes:
MC> - would it be better to create a new review ticket or take over the
MC> existing one?
Please create a new ticket and close the old one as a duplicate. That
way the original submitter can remove their address from the CC list if
they're not interested, an
Hi,
I noticed there's an old review for icemon [1] which I'd like to revive
- would it be better to create a new review ticket or take over the
existing one?
Thanks,
Michael
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1311959
___
devel mailing lis
On 27 July 2017 at 13:37, Stephen John Smoogen wrote:
>
>
> On 27 July 2017 at 13:11, Michael Catanzaro
> wrote:
>
>> Ouch.
>>
>> Since the unresponsive maintainer process takes some time, could a
>> provenpackager please update ImageMagick while we wait for this to go
>> through?
>>
>> It is a
On 27 July 2017 at 13:11, Michael Catanzaro
wrote:
> Ouch.
>
> Since the unresponsive maintainer process takes some time, could a
> provenpackager please update ImageMagick while we wait for this to go
> through?
>
> It is a serious oversight that our security process can fail like this for
> suc
On Thu, Jul 27, 2017 at 12:02 PM, Adam Williamson
wrote:
> On Thu, 2017-07-27 at 06:09 -0400, Josh Boyer wrote:
>> On Wed, Jul 26, 2017 at 7:17 PM, Adam Williamson
>> wrote:
>> > Hi, folks! This is just a heads-up for anyone who's been watching the
>> > openQA test results for an update, or somet
Do you think it'd be possible to script the python-foo to python2-foo
renaming? If yes, then maybe it'd make sense to just get some pps to
do it in rawhide now and get the "easy" part done with? That should
significantly cut down on the number of misnamed packages and let
packagers spend their time
Ouch.
Since the unresponsive maintainer process takes some time, could a
provenpackager please update ImageMagick while we wait for this to go
through?
It is a serious oversight that our security process can fail like this
for such a major package when the maintainer is not watching Bugzilla
Hi
Upstream notified me that the way qbs is currently packaged (as part of
qt-creator) is wrong, and that it should live in a separate package with
the correct version (instead of using the qt-creator version). The
review request for the split-off qbs package is here:
https://bugzilla.redhat
Online-Apotheke, Garantierte Qualitat!
E-Mails in Ihrem Browser anzeigen
Online-Apotheke, Garantierte Qualitat!
Sparen Sie Ihr Geld, Zeit, Bemuhunge
The workaround recommended by binutils upstream (--no-plt-localentry)
does not work, and a glibc built with that still has the problem.
I have not rebuilt dependent packages (cmake, curl) with the flag. If
*those* are mislinked, we really have a problem. There's no word on the
root cause yet.
T
Hello fellow Fedora contributors,
We've created a page on Fedora wiki [1] that's something like a Change
proposal*.
The document is called "Finalizing Fedora's Switch to Python 3" and it
describes steps needed in order to:
* Switch /usr/bin/python to Python 3 in cooperation with Python ups
On Thu, 2017-07-27 at 06:09 -0400, Josh Boyer wrote:
> On Wed, Jul 26, 2017 at 7:17 PM, Adam Williamson
> wrote:
> > Hi, folks! This is just a heads-up for anyone who's been watching the
> > openQA test results for an update, or something, and been confused.
> >
> > A few days ago we added a new
On Thu, Jul 27, 2017 at 11:04 AM, Vít Ondruch wrote:
>
> This was related to rubygem-bson and I switched the rubygem-bson from noarch
> to arch in this commit:
>
> http://pkgs.fedoraproject.org/cgit/rpms/rubygem-bson.git/commit/?id=f507fa3ee0e8b29e60ef6164c28733691332dea4
>
> I don't think there
Il giorno gio, 27/07/2017 alle 15.16 +0200, Dario Lesca ha scritto:
> Il giorno gio, 06/07/2017 alle 15.44 +0300, Alexander Bokovoy ha
> .
> But when I start bind with:
>
> # systemctl start named
>
> I get this error:
>
> lug 27 14:39:53 server-addc.dom.loc named[2418]: samba_dlz: Failed to
On 07/26/2017 06:25 PM, Al Stone wrote:
I've been experimenting in a slightly different environment (RHEL vs Fedora) but have been seeing oddly
similar results. The use or not of the "-pipe" in GCC didn't seem to help. If I forced the make
in the %build step to be just "make" (aka, "make -j1"
On Tue, 2017-07-25 at 01:49 -0400, David Airlie wrote:
> > So, should this package be added to base-x ? Should something depend on
> > it? Should X actually start up without libEGL.so.1, and I should file
> > *that* as a bug? Thanks!
>
> Hans might answer this better, but X should start fine with
Dne 27.7.2017 v 16:56 Martin Langhoff napsal(a):
> Turns out that Elixir should not be noarch, as some of its code is
> endianness specific. What's best practice to switch away from noarch
> for packages in current Fedora? How about EPEL?
>
> I see this outdated and unresolved Packaging Comittee
Turns out that Elixir should not be noarch, as some of its code is
endianness specific. What's best practice to switch away from noarch for
packages in current Fedora? How about EPEL?
I see this outdated and unresolved Packaging Comittee issue...
https://pagure.io/packaging-committee/issue/117
an
On Thu, Jul 27, 2017 at 10:05:40AM +0200, Pierre-Yves Chibon wrote:
> The activity log hasn't been filled, we could try doing it but that
> will take a really long time as it would have to run through each
> commits in all the repos. However, new activity should show up just
> fine.
This is not ur
On Thu, Jul 27, 2017 at 3:10 AM, Richard W.M. Jones wrote:
> Unfortunately once I started to look at the code it seems to be some
> kind of generated C which is almost impossible to follow, eg:
Yes, it is Scheme code compiled to C. Lots of fun to dig through. :-)
> You can ask for access to a m
Hello Fedora people,
please let me remind you of the running Nomination period.
For FESCo we have opened 4 seats:
https://fedoraproject.org/wiki/Development/SteeringCommittee/Nominations
For Council we have opened 1 seat:
https://fedoraproject.org/wiki/Council/Nominations
For FAmSCo we have ope
Il giorno gio, 27/07/2017 alle 15.39 +0200, Zdenek Sedlak ha scritto:
> How does the unit file look like?
Do you mean that:
> # cat /usr/lib/systemd/system/named.service
> [Unit]
> Description=Berkeley Internet Name Domain (DNS)
> Wants=nss-lookup.target
> Wants=named-setup-rndc.service
> Before=
Il giorno gio, 27/07/2017 alle 15.39 +0200, Zdenek Sedlak ha scritto:
> How does the unit file look like?
where or how to I can see that?
--
Dario Lesca
(inviato dal mio Linux Fedora 26 Workstation)
___
devel mailing list -- devel@lists.fedoraproject.o
On 2017-07-27 15:16, Dario Lesca wrote:
> Il giorno gio, 06/07/2017 alle 15.44 +0300, Alexander Bokovoy ha
> scritto:
>> So, we pushed 4.7.0-RC1 to Rawhide. Also, asn/samba_ad_dc COPR repo
>> contains a rebuild for F25 and F26. Feel free to test that.
> Today I have start to try f27+samba4.7.
>
> D
Il giorno gio, 06/07/2017 alle 15.44 +0300, Alexander Bokovoy ha
scritto:
> So, we pushed 4.7.0-RC1 to Rawhide. Also, asn/samba_ad_dc COPR repo
> contains a rebuild for F25 and F26. Feel free to test that.
Today I have start to try f27+samba4.7.
Download and install Fedora 27 server rawhide
https
> "FW" == Florian Weimer writes:
FW> I'm doing scratch builds, and I think they are kind of difficult to
FW> see in Koji.
Yeah, you can see them in the task list when they're active. I see the
one you're running now.
Still, if you are running into problems and need me or anyone else to
kic
On 07/27/2017 02:31 PM, Jason L Tibbitts III wrote:
> I don't see any recent koji jobs submitted by you, nor any recent glibc
> build besides the mass rebuild one (which I believe failed due to
> debuginfo generation issues) so just let me know if you need me to kick
> off a glibc build or a build
> "FW" == Florian Weimer writes:
FW> I think I have a workaround, but I'm blocked by this koji CLI bug:
You can always ask someone else to do a build for you; just let me know
if you need that done.
I don't see any recent koji jobs submitted by you, nor any recent glibc
build besides the ma
On 07/26/2017 08:22 AM, Björn 'besser82' Esser wrote:
It looks like the whole parallelized make-process is hitting the 4
Gbytes limit per process / task on 32 Bit arches…
Have you tried this?
%build
export CFLAGS="echo %{optflags} | sed -e 's!-pipe!!g'"
export CXXFLAGS="$CFLAGS"
…
Sometimes
On 07/27/2017 12:39 PM, Tom Hughes wrote:
> On 27/07/17 11:16, Florian Weimer wrote:
>
>> I think I have a workaround, but I'm blocked by this koji CLI bug:
>>
>>https://bugzilla.redhat.com/show_bug.cgi?id=1472106
>>
>> It seems I can't do any builds through the koji CLI.
>
> I think on IRC y
On 27/07/17 11:16, Florian Weimer wrote:
I think I have a workaround, but I'm blocked by this koji CLI bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1472106
It seems I can't do any builds through the koji CLI.
I think on IRC yesterday it was decided that message was code for "your
ker
I think I have a workaround, but I'm blocked by this koji CLI bug:
https://bugzilla.redhat.com/show_bug.cgi?id=1472106
It seems I can't do any builds through the koji CLI.
Thanks,
Florian
___
devel mailing list -- devel@lists.fedoraproject.org
To uns
On Wed, Jul 26, 2017 at 7:17 PM, Adam Williamson
wrote:
> Hi, folks! This is just a heads-up for anyone who's been watching the
> openQA test results for an update, or something, and been confused.
>
> A few days ago we added a new ppc64 openQA worker host box; ultimately
Out of curiosity, do you
On 07/27/2017 01:21 AM, Jason L Tibbitts III wrote:
> I noticed one of my packages failed to build because the test suite
> failed, but only on ppc64le.
>
> builddir/build/BUILD/cyrus-imapd-3.0.2/cunit/.libs/lt-unit: error while
> loading shared libraries:
> /builddir/build/BUILD/cyrus-imapd-3.0.2
On Wed, Jul 26, 2017 at 08:14:14AM -0600, Jerry James wrote:
> Failing that, does anybody with access
> to an s390x instance have time to help me? The latest bigloo release
> built successfully on all arches but s390x:
>
> https://koji.fedoraproject.org/koji/taskinfo?taskID=20740401
>
> The fail
On Thu, Jul 27, 2017 at 10:36:29AM +0200, Vít Ondruch wrote:
> Dne 27.7.2017 v 10:05 Pierre-Yves Chibon napsal(a):
> >> 2) The "contributors" list does not appear to be correct. Looking at
> >> "ruby", there is listed "tagoh" user, who is in pkgdb "Obsolete" on all
> >> branches. Is it old data on
Dne 27.7.2017 v 10:29 Pierre-Yves Chibon napsal(a):
> On Thu, Jul 27, 2017 at 10:05:40AM +0200, Pierre-Yves Chibon wrote:
>> On Thu, Jul 27, 2017 at 07:35:46AM +0200, Vít Ondruch wrote:
>>>
>>> Dne 26.7.2017 v 19:41 Pierre-Yves Chibon napsal(a):
On Wed, Jul 26, 2017 at 07:20:38PM +0200, Vít
Dne 27.7.2017 v 10:05 Pierre-Yves Chibon napsal(a):
> On Thu, Jul 27, 2017 at 07:35:46AM +0200, Vít Ondruch wrote:
>>
>> Dne 26.7.2017 v 19:41 Pierre-Yves Chibon napsal(a):
>>> On Wed, Jul 26, 2017 at 07:20:38PM +0200, Vít Ondruch wrote:
Dne 24.7.2017 v 22:49 Pierre-Yves Chibon napsal(a):
>>
On Thu, Jul 27, 2017 at 10:05:40AM +0200, Pierre-Yves Chibon wrote:
> On Thu, Jul 27, 2017 at 07:35:46AM +0200, Vít Ondruch wrote:
> >
> >
> > Dne 26.7.2017 v 19:41 Pierre-Yves Chibon napsal(a):
> > > On Wed, Jul 26, 2017 at 07:20:38PM +0200, Vít Ondruch wrote:
> > >>
> > >> Dne 24.7.2017 v 22:49
On Thu, Jul 27, 2017 at 07:35:46AM +0200, Vít Ondruch wrote:
>
>
> Dne 26.7.2017 v 19:41 Pierre-Yves Chibon napsal(a):
> > On Wed, Jul 26, 2017 at 07:20:38PM +0200, Vít Ondruch wrote:
> >>
> >> Dne 24.7.2017 v 22:49 Pierre-Yves Chibon napsal(a):
> >>> On Mon, Jul 10, 2017 at 11:23:35AM +0200, Pie
Hello,
On Thu, Jul 27, 2017 at 6:07 AM, Josh Stone wrote:
> On 07/26/2017 06:23 PM, Josh Stone wrote:
> >> I did some other random checks and found a few other packages with
> >> ppc64le-only build failures: freeipa, gammu, gap-pkg-float, gambas3,
> >> getdp (and I stopped looking after that).
46 matches
Mail list logo
