On Jan 11, 2016 22:23, "Martin Gieseking" wrote:
>
> Am 11.01.2016 um 20:53 schrieb Erik Schilling:
> > After a short discussion with upstream they told me that they ship the
> > branding for tmw inside of the manaplus sources. So it would probably be
> > the easiest to simply create a tmw package
On 01/13/2016 08:24 AM, Luya Tshimbalanga wrote:
> In general, leading whitespace is only allowed when making conditional
> statement or using backslash like these following examples:
>
> --- Example #1 ---
> %if (0%{?fedora} && 0%{?fedora} < 19) || (0%{?rhel} && 0%{?rhel} < 7)
> --vendor="fe
On 12/01/16 10:18 PM, Andrew Toskin wrote:
> I'm new to RPM packaging. I've recently forked a repository, and one of the
> first things I tried to do was clean up formatting of the .spec file.
> Particularly the %if blocks were hard to follow because the previous author
> did not use any indenta
Missing expected images:
Kde disk raw armhfp
No images in this compose but not Rawhide 20160111
No images in Rawhide 20160111 but not this.
Failed openQA tests: 4 of 66
ID: 2985Test: i386 kde_live default_install
URL: https://openqa.fedoraproject.org/tests/2985
ID: 2983Test: x8
I'm new to RPM packaging. I've recently forked a repository, and one of the
first things I tried to do was clean up formatting of the .spec file.
Particularly the %if blocks were hard to follow because the previous author did
not use any indentation at all. However, it seems like maybe indentati
On Tue, Jan 12, 2016 at 7:25 PM, Nico Kadel-Garcia wrote:
> On Fri, Jan 8, 2016 at 10:37 AM, Sérgio Basto wrote:
>> On Sex, 2016-01-08 at 08:54 -0500, Jaroslav Mracek wrote:
>>> Hi everybody,
>>>
>>> I would like to set following packages as Orphan due to that upstream
>>> is dead or maintainers
On 12/01/16 22:59 +, Jonathan Wakely wrote:
The old version could be added as keepassx1, or just via COPR, for
those who still want it.
I've created a COPR with keepassx 0.4.4 builds for F22 and F23:
https://copr.fedoraproject.org/coprs/jwakely/keepassx1/build/153188/
--
devel mailing list
On Fri, Jan 8, 2016 at 10:37 AM, Sérgio Basto wrote:
> On Sex, 2016-01-08 at 08:54 -0500, Jaroslav Mracek wrote:
>> Hi everybody,
>>
>> I would like to set following packages as Orphan due to that upstream
>> is dead or maintainers do not respond:
>>
>> repoview
>
> have we a replace for repoview
On Tue, Jan 12, 2016 at 5:30 PM, Matthew Miller
wrote:
> On Tue, Jan 12, 2016 at 01:31:30AM +, Peter Robinson wrote:
>> Will there be an ABI guaranteed beta or RC so that this can be
>> complete before branching as per the schedule [1]? All major rebases
>> should be complete prior to branchin
So how should the maintainer proceed?
The policy was violated, but it's done now. F23 has already been
updated, F22 has an update in testing now (with negative karma).
The old version could be added as keepassx1, or just via COPR, for
those who still want it.
Since some people will already hav
On 01/08/2016 11:27 AM, bugzi...@redhat.com wrote:
> https://bugzilla.redhat.com/show_bug.cgi?id=1294904
>
> Antonio Trande changed:
>
>What|Removed |Added
>
> Flags|fed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 01/12/2016 03:38 PM, Martin Ueding wrote:
> I was rather surprised by this too. When the UI changed I was
> already a bit sceptical as KeePassX has not changed in like five
> years. When it did not open the old database I knew that I was
> served
I was rather surprised by this too. When the UI changed I was already a
bit sceptical as KeePassX has not changed in like five years. When it
did not open the old database I knew that I was served version 2. A
short look in the dnf automatic update emails confirmed that.
The mid-release break was
On Tue, Jan 12, 2016 at 2:08 PM, Mattia Verga wrote:
> Il 07/01/2016 20:30, Tomasz Torcz ha scritto:
>>
>> On Thu, Jan 07, 2016 at 01:33:22PM -0500, Josh Boyer wrote:
>>>
>>> Hello,
>>>
>>> The 4.3.3 kernel has been pushed to updates-testing for F23. As of
>>> right now, it has a +12 karma score.
Should we split the discussion about socket activation in another thread.
And discuss zookeeper service specifically here.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Il 07/01/2016 20:30, Tomasz Torcz ha scritto:
On Thu, Jan 07, 2016 at 01:33:22PM -0500, Josh Boyer wrote:
Hello,
The 4.3.3 kernel has been pushed to updates-testing for F23. As of
right now, it has a +12 karma score. Given that it is a major release
rebase, we're going to wait at least a few
On Tue, 12 Jan 2016 16:27:03 +0100, Sven Lankes wrote:
> As I understand it, your sponsor is supposed to look after your commits.
Not forever, though. Sponsorship is not a life-time duty, and monitoring
git commits isn't either. It's not even mentioned as a responsibility.
There are sponsors who
Am 12.01.2016 um 19:50 schrieb Lennart Poettering:
On Tue, 12.01.16 19:48, Reindl Harald (h.rei...@thelounge.net) wrote:
Am 12.01.2016 um 19:44 schrieb Lennart Poettering:
On Tue, 12.01.16 19:37, Reindl Harald (h.rei...@thelounge.net) wrote:
That said, of course, this is not obvious at f
>
> Please don't top-post [1]
>
Sorry I was on mobile gmail client.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
On Tue, 12.01.16 19:48, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>
> Am 12.01.2016 um 19:44 schrieb Lennart Poettering:
> >On Tue, 12.01.16 19:37, Reindl Harald (h.rei...@thelounge.net) wrote:
> >
> >>>That said, of course, this is not obvious at first, hence since quite
> >>>some time "s
Am 12.01.2016 um 19:44 schrieb Lennart Poettering:
On Tue, 12.01.16 19:37, Reindl Harald (h.rei...@thelounge.net) wrote:
That said, of course, this is not obvious at first, hence since quite
some time "systemctl stop" will actually explain this to you: if you
stop a daemon, but leave its sock
On Tue, 12.01.16 19:37, Reindl Harald (h.rei...@thelounge.net) wrote:
> >That said, of course, this is not obvious at first, hence since quite
> >some time "systemctl stop" will actually explain this to you: if you
> >stop a daemon, but leave its socket running, then you'll get a
> >friendly messa
Am 12.01.2016 um 19:30 schrieb Lennart Poettering:
On Tue, 12.01.16 18:54, Reindl Harald (h.rei...@thelounge.net) wrote:
Also, what happens if the daemon is configured to listen on some
different port? Or on multiple ports? Are you parsing the daemon's
config file too to figure out what to wa
On 12/01/16 19:33, Muayyad AlSadi wrote:
Will I do agree it's a hack.
But it's better than forking in bash.
And usually I don't care about the exact time socket/port is active
because zookeeper is supposed to handle fail over.
[ the rest below..]
Please don't top-post [1]
Cheers!
--alec
[
Will I do agree it's a hack.
But it's better than forking in bash.
And usually I don't care about the exact time socket/port is active because
zookeeper is supposed to handle fail over.
On Jan 12, 2016 7:54 PM, "Reindl Harald" wrote:
>
>
> Am 12.01.2016 um 17:41 schrieb Lennart Poettering:
>
>>
On Tue, 12.01.16 18:54, Reindl Harald (h.rei...@thelounge.net) wrote:
> >Also, what happens if the daemon is configured to listen on some
> >different port? Or on multiple ports? Are you parsing the daemon's
> >config file too to figure out what to watch for? YUCK!
>
> the Fedora myqld unit does,
On Tue, Jan 12, 2016 at 07:22:46PM +0100, Jan Kurik wrote:
> > Jan, previously when we've updated the schedule, the previous dates for
> > each milestone are retained with a strikethrough (see
> > https://fedoraproject.org/wiki/Releases/23/Schedule). Are we not doing
> > that intentionally this tim
On Tue, Jan 12, 2016 at 6:33 PM, Matthew Miller
wrote:
> On Tue, Jan 12, 2016 at 03:23:55AM +0100, Jan Kurik wrote:
>> schedule for 2 weeks. Please check the updated schedule at
>> https://fedoraproject.org/wiki/Releases/24/Schedule#Key_Milestones .
>> Dates for the most important milestones follo
On 12/01/16 12:54 -0500, Chuck Anderson wrote:
Given that people have already had their databases upgraded to .kdbx
(but the v1 .kdb file is still there), instead of downgrading keepassx
which is now at v2, you could inroduce a new keepassx1 package. It
might be cleaner that way now that the v2
On 01/12/2016 11:54 AM, Orion Poplawski wrote:
On 01/12/2016 08:28 AM, Johnny Hughes wrote:
'LibRaw-0.17.1-3.el7.x86_64 (epel-testing)' and
'LibRaw-0.14.8-5.el7.20120830git98d925.x86_64 (@base/$releasever)' are
conflicting
I think there is some confusion around this. It seems that it may hav
On 12/01/16 18:50 +0100, Jens Lody wrote:
keepassx 2 uses kdbx file-ending, while keepassx 0.4 uses kdb.
I have updated and converted, but the old file is still present and
untouched.
Oh good!
So then there's even less reason not to support parallel installations
of both versions.
The only qu
On Tue, Jan 12, 2016 at 10:41:24AM +, Jonathan Wakely wrote:
> I'm concerned by this update too.
>
> The latest post in Bugzilla says:
>
> (In reply to Francesco Frassinelli (frafra) from comment #35)
> >(In reply to Ed Marshall from comment #33)
> >> (and, obviously, send email to the mailin
Am 12.01.2016 um 17:41 schrieb Lennart Poettering:
On Tue, 12.01.16 17:16, Muayyad AlSadi (als...@gmail.com) wrote:
well. But if you can double fork() in Java you should be fine and can
it seems that zookeeper is doing the fork in the bash script using nohub
not in java
when it finished s
Am Tue, 12 Jan 2016 10:41:24 +
schrieb Jonathan Wakely :
> On 12/01/16 01:47 -0800, Ed Marshall wrote:
> >Bringing this discussion to the mailing list, since it's all
> >apparently happened in bugzilla until now (and I only found out when
> >I updated this evening).
> >
> >For reference: https
On Tue, Jan 12, 2016 at 03:23:55AM +0100, Jan Kurik wrote:
> schedule for 2 weeks. Please check the updated schedule at
> https://fedoraproject.org/wiki/Releases/24/Schedule#Key_Milestones .
> Dates for the most important milestones follows:
Jan, previously when we've updated the schedule, the pre
On Tue, Jan 12, 2016 at 01:31:30AM +, Peter Robinson wrote:
> Will there be an ABI guaranteed beta or RC so that this can be
> complete before branching as per the schedule [1]? All major rebases
> should be complete prior to branching.
> [1] https://fedoraproject.org/wiki/Releases/24/Schedule
On Tue, 12.01.16 17:16, Muayyad AlSadi (als...@gmail.com) wrote:
> > well. But if you can double fork() in Java you should be fine and can
>
> it seems that zookeeper is doing the fork in the bash script using nohub
> not in java
>
> > when it finished setting up its listening socket. You cannot
On Tue, 2016-01-12 at 15:22 +, Fedora compose checker wrote:
> Missing expected images:
>
> Kde disk raw armhfp
>
> No images in this compose but not Rawhide 20160111
>
> No images in Rawhide 20160111 but not this.
>
> Failed openQA tests: 56 of 64
Looks like either a font rendering change
On Tue, Jan 12, 2016 at 10:06:40AM -0500, Nico Kadel-Garcia wrote:
>> Could we adjust the tooling so that a request for commit access is
>> automatically granted if it isn't answered within three months?
> That's a potential security problem. If I, for example, can get
> commit access to any id
> Polling around a 1s sleep loop. That's a gross hack
that's 0.1s
On Tue, Jan 12, 2016 at 5:15 PM, Reindl Harald
wrote:
>
>
> Am 12.01.2016 um 16:09 schrieb Lennart Poettering:
>
>> On Tue, 12.01.16 15:57, Reindl Harald (h.rei...@thelounge.net) wrote:
>>
>>
>>> Am 12.01.2016 um 15:45 schrieb Le
Missing expected images:
Kde disk raw armhfp
No images in this compose but not Rawhide 20160111
No images in Rawhide 20160111 but not this.
Failed openQA tests: 56 of 64
ID: 2920Test: i386 workstation_live default_install
URL: https://openqa.fedoraproject.org/tests/2920
ID: 2919
> well. But if you can double fork() in Java you should be fine and can
it seems that zookeeper is doing the fork in the bash script using nohub
not in java
> when it finished setting up its listening socket. You cannot script
typically I loop using "lsof" or "nc"
> Polling around a 1s sleep lo
Am 12.01.2016 um 16:09 schrieb Lennart Poettering:
On Tue, 12.01.16 15:57, Reindl Harald (h.rei...@thelounge.net) wrote:
Am 12.01.2016 um 15:45 schrieb Lennart Poettering:
On Tue, 12.01.16 10:22, Muayyad AlSadi (als...@gmail.com) wrote:
@Lennart Poettering is there a way to use something
On Tue, 12.01.16 15:57, Reindl Harald (h.rei...@thelounge.net) wrote:
>
>
> Am 12.01.2016 um 15:45 schrieb Lennart Poettering:
> >On Tue, 12.01.16 10:22, Muayyad AlSadi (als...@gmail.com) wrote:
> >
> >>
> >>@Lennart Poettering is there a way to use something like "ExecStartPost="
> >>do the the
On Tue, Jan 12, 2016 at 9:31 AM, Sven Lankes wrote:
> On Tue, Jan 12, 2016 at 01:30:27PM +0100, Michael Schwendt wrote:
>
>> Isn't that tedious, inefficient and a waste of time?
>
> As all of the unresponsive maintainer procedure.
>
> Could we adjust the tooling so that a request for commit access
Am 12.01.2016 um 15:45 schrieb Lennart Poettering:
On Tue, 12.01.16 10:22, Muayyad AlSadi (als...@gmail.com) wrote:
@Lennart Poettering is there a way to use something like "ExecStartPost="
do the the notify with type=simple?
When would you even call that? Somehow your Java app needs to re
On Tue, 12.01.16 10:22, Muayyad AlSadi (als...@gmail.com) wrote:
>
> @Lennart Poettering is there a way to use something like "ExecStartPost="
> do the the notify with type=simple?
When would you even call that? Somehow your Java app needs to report
when it finished setting up its listening sock
On Mon, 11.01.16 20:19, Christopher (ctubbsii-fed...@apache.org) wrote:
> Hi,
>
> I'm a co-maintainer for ZooKeeper, and I'd like to help get this right, if
> possible. More importantly, I'm interested in setting a precedent for Java
> system services in systemd. So, forgive my ignorance, but wha
https://bugzilla.redhat.com/show_bug.cgi?id=1297769
Petr Pisar changed:
What|Removed |Added
Status|ASSIGNED|CLOSED
Fixed In Version|
On Tue, Jan 12, 2016 at 01:30:27PM +0100, Michael Schwendt wrote:
> Isn't that tedious, inefficient and a waste of time?
As all of the unresponsive maintainer procedure.
Could we adjust the tooling so that a request for commit access is
automatically granted if it isn't answered within three mon
On Tue, Jan 12, 2016 at 09:02:08AM -0500, Josh Boyer wrote:
> On Tue, Jan 12, 2016 at 8:58 AM, David Howells wrote:
> > Jan Kurik wrote:
> >
> >> let me inform you about changes in Fedora 24 schedule.
> >>
> >> There is a will to accommodate GCC6 compiler in F24 and use it to
> >> compile all the
Announcing the creation of a new nightly release validation test event
for Fedora 24 Rawhide 20160112. Please help run some tests for this
nightly compose if you have time. For more information on nightly
release validation testing, see:
https://fedoraproject.org/wiki
On Tue, Jan 12, 2016 at 9:02 AM, Josh Boyer
wrote:
> On Tue, Jan 12, 2016 at 8:58 AM, David Howells
> wrote:
> > Jan Kurik wrote:
> >
> >> let me inform you about changes in Fedora 24 schedule.
> >>
> >> There is a will to accommodate GCC6 compiler in F24 and use it to
> >> compile all the bina
Dne 18.8.2015 v 16:26 Vít Ondruch napsal(a):
> Hi all,
>
> Today, I noticed that mock build root prepared by DNF is significantly
> larger then prepared by YUM (see attached logs). Owners of packages
> installed into minimal buildroot probably wants to review their
> dependency chain.
>
> I also re
On Tue, Jan 12, 2016 at 8:58 AM, David Howells wrote:
> Jan Kurik wrote:
>
>> let me inform you about changes in Fedora 24 schedule.
>>
>> There is a will to accommodate GCC6 compiler in F24 and use it to
>> compile all the binaries delivered in this release [1].
>
> Do the cross-gcc packages als
Jan Kurik wrote:
> let me inform you about changes in Fedora 24 schedule.
>
> There is a will to accommodate GCC6 compiler in F24 and use it to
> compile all the binaries delivered in this release [1].
Do the cross-gcc packages also need moving to GCC6 immediately as I believe
they're used to c
upstream issue < https://issues.apache.org/jira/browse/ZOOKEEPER-2095
suggests the following
ExecStart=/usr/bin/java \
-Dzookeeper.log.dir=/var/log/zookeeper \
-Dzookeeper.root.logger=INFO,ROLLINGFILE \
-cp /usr/share/java/zookeeper/* \
-Dlog4j.configuration=file:/etc/zookeeper/log4j.prop
On Tue, 2016-01-12 at 10:42 +, Jonathan Wakely wrote:
> P.S. the people who want version 2 already had *several* COPRs to
> choose from that provide version 2. Pushing it to the stable releases
> was really not necessary.
Seems to be hitting users too:
https://ask.fedoraproject.org/en/questio
> - If the socket availability doesn't matter, remove the nohup,
redirection, fork stuff and use a "Type = simple" service. Presuming that
the java process runs in foreground this should be fine.
passing -f to solr or start-foreground to zookeeper would short-circuit the
"nohup" as it would use "
On Tue, 12 Jan 2016 00:26:14 +, Andrew Clayton wrote:
> Interesting. In Claws Mail for this message I'm seeing
>
> From:
> To:
> Subject:
> Date:
> X-Mailer:
> Organization:
> Message-ID:
>
> (true, they may not all be shown by default)
Preferences > Message View > Text Options > Headers
Cl
On Tue, 12 Jan 2016 11:17:37 +0100, Christian Dersch wrote:
> > The same procedure has been started a few times, at least
> >
> > https://bugzilla.redhat.com/736874
> > https://bugzilla.redhat.com/963890
> >
> > Requesting co-maintainer access would be a way to solve such
> > isues.
> >
> I
On 12/24/2015 10:01 PM, Jason L Tibbitts III wrote:
To satisfy my curiosity, I grepped the convenient tarball of specfiles
(http://pkgs.fedoraproject.org/repo/rpm-specs-latest.tar.xz) for lines
matching "(?After fixing %define -> %global in my spec file, my vim is having
several problems:
* F
On 12/01/16 10:54, Muayyad AlSadi wrote:
the problem here is the bash script wrapped around
in the good old days of solr there used a param passed to solr.jar to
make the fork magic in java (maybe it was --daemon)
but now it's done in bash with "nohup" followed by "while true lsof
-PniTCP:
Hi,
the 3.19.4 release of evolution-data-server changes soname version for
camel, due to some API changes.
I will rebuild packages for which I have commit rights, the same as I
can help with the API change fixes, thus feel free to ping me or drop
an e-mail. I do not think that other than E
Compose started at Tue Jan 12 05:15:02 UTC 2016
Broken deps for i386
--
[IQmol]
IQmol-2.3.0-9.fc24.i686 requires libboost_serialization.so.1.58.0
IQmol-2.3.0-9.fc24.i686 requires libboost_iostreams.so.1.58.0
IQmol-2.3.0
On 01/12/2016 09:58 AM, Mikolaj Izdebski wrote:
On 01/11/2016 11:48 PM, Orion Poplawski wrote:
The julia language loads libraries at run time by using the .so filename. We
work around this in the julia package by symlinking the needed sonames into
%{_libdir}/julia/, e.g.:
for lib in arpack cho
On 12/01/16 10:41 +, Jonathan Wakely wrote:
On 12/01/16 01:47 -0800, Ed Marshall wrote:
Bringing this discussion to the mailing list, since it's all apparently
happened in bugzilla until now (and I only found out when I updated this
evening).
For reference: https://bugzilla.redhat.com/show_
On 12/01/16 01:47 -0800, Ed Marshall wrote:
Bringing this discussion to the mailing list, since it's all apparently
happened in bugzilla until now (and I only found out when I updated this
evening).
For reference: https://bugzilla.redhat.com/show_bug.cgi?id=1282825
This update (0.4.3 to 2.0.0)
On 01/12/2016 10:00 AM, Michael Schwendt wrote:
> The same procedure has been started a few times, at least
>
> https://bugzilla.redhat.com/736874
> https://bugzilla.redhat.com/963890
>
> Requesting co-maintainer access would be a way to solve such
> isues.
> --
>
I requested it in pkgdb some
- Original Message -
>
>
> - Original Message -
> > On Fri, 8 Jan 2016 11:12:37 -0500 (EST)
> > Jaroslav Skarvada wrote:
> >
> > > $ git push -v
> > > Pushing to ssh://jskar...@pkgs.fedoraproject.org/memtest86+
> > > WARNING: 'memtest86+' is an alias for 'rpms/memtest86+'
> >
> the problem here is the bash script wrapped around
in the good old days of solr there used a param passed to solr.jar to make
the fork magic in java (maybe it was --daemon)
but now it's done in bash with "nohup" followed by "while true lsof
-PniTCP:$SOLR_PORT -sTCP:LISTEN" to detect if it's
Bringing this discussion to the mailing list, since it's all apparently
happened in bugzilla until now (and I only found out when I updated this
evening).
For reference: https://bugzilla.redhat.com/show_bug.cgi?id=1282825
This update (0.4.3 to 2.0.0) went out today, for both F22 and F23. It
remov
> the problem here is the bash script wrapped around
just pass "start-foreground" and it will be short-circuit
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
Am 12.01.2016 um 09:22 schrieb Muayyad AlSadi:
nohup "$JAVA" "-Dzookeeper.log.dir=${ZOO_LOG_DIR}"
"-Dzookeeper.root.logger=${ZOO_LOG4J_PROP}" \
-cp "$CLASSPATH" $JVMFLAGS $ZOOMAIN "$ZOOCFG" > "$_ZOO_DAEMON_OUT"
2>&1 < /dev/null &
if [ $? -eq 0 ]
...
/bin/echo -n $! > "$Z
On Mon, 11 Jan 2016 21:48:25 +0100, Christian Dersch wrote:
> Hi all,
>
> I tried to contact tuxbrewr some weeks ago (due to quassel bug fixes and
> maintainance), without any response. Does anybody know how to contact
> him? I already tried smparr...@gmail.com without success.
>
> Info: https:/
>> my point is that having a child double forked does not mean Zookeeper TCP
>> port is ready which is as bad as simple which is also does not indicate
>> when it's ready
> Well, then Zookeeper is simply broken.
sorry it's just me. I forget that the classic UNIX double fork do listen
before the d
On Sat, 2016-01-09 at 23:36 -0600, Bruno Wolff III wrote:
> On Mon, Jan 04, 2016 at 10:33:01 +0100,
> Jiří Konečný wrote:
> > On Fri, 2015-12-11 at 10:44 +0100, Jiří Konečný wrote:
> > > Hello all,
> > >
> > > it was some time but I finally made it to the Fedora review
> > >
> > > https://bug
77 matches
Mail list logo
