10 Jun
2012
10 Jun
'12
11:56 a.m.
propertiespage.cpp in this plugin references one of the UIC headers in
filesharesamba, so filesharesamba must be compiled first.
---
filesharing/advanced/propsdlgplugin/CMakeLists.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/filesharing/advanced/propsdlgplugin/CMakeLists.txt
b/filesharing/advanced/propsdlgplugin/CMakeLists.txt
index f6477d1..26d94f5 100644
--- a/filesharing/advanced/propsdlgplugin/CMakeLists.txt
+++ b/filesharing/advanced/propsdlgplugin/CMakeLists.txt
@@ -32,6 +32,7 @@ install( FILES
tde_add_library( propsdlgplugin_common STATIC_PIC AUTOMOC
SOURCES propertiespage.cpp propertiespagegui.ui
+ DEPENDENCIES filesharesamba
)
--
1.7.10.4.153.g8c399cf
10 Jun
10 Jun
9:07 p.m.
New subject: [trinity-devel] [PATCH tdenetwork 4/4] The propsdlgplugin must depend on filesharesamba.
propertiespage.cpp in this plugin references one of
the UIC headers in
filesharesamba, so filesharesamba must be compiled first.
---
filesharing/advanced/propsdlgplugin/CMakeLists.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/filesharing/advanced/propsdlgplugin/CMakeLists.txt
b/filesharing/advanced/propsdlgplugin/CMakeLists.txt
index f6477d1..26d94f5 100644
--- a/filesharing/advanced/propsdlgplugin/CMakeLists.txt
+++ b/filesharing/advanced/propsdlgplugin/CMakeLists.txt
@@ -32,6 +32,7 @@ install( FILES
tde_add_library( propsdlgplugin_common STATIC_PIC AUTOMOC
SOURCES propertiespage.cpp propertiespagegui.ui
+ DEPENDENCIES filesharesamba
)
--
1.7.10.4.153.g8c399cf
Is there any chance that you could create a series of bug reports (e.g.
one for tdebase problems, another for tdenetwork problems, etc.) with the
patches attached? With the volume of mail on this list I am concerned
that I (and the other developers) may not remember to evaluate/apply all
of the patches you are sending in.
Thanks!
Tim
9:48 p.m.
New subject: [trinity-devel] [PATCH tdenetwork 4/4] The propsdlgplugin must depend on filesharesamba.
On 10 Jun 2012, Timothy Pearson said:
Is there any chance that you could create a series of
bug reports (e.g.
one for tdebase problems, another for tdenetwork problems, etc.) with the
patches attached? With the volume of mail on this list I am concerned
that I (and the other developers) may not remember to evaluate/apply all
of the patches you are sending in.
I could do that if I remembered where the bug report page was :)
(Or I can just ping occasionally if it doesn't get applied. I suspect
that some of the problems I'm seeing are something or other to do with
my configuration -- e.g. Akregator is now complaining that it can't find
the archiving plugin and refusing to start, which I'm fairly sure must
be something that works for other people. And kded just blocked forever
on... something, a symptom I knew from KDE3 but vaguely hoped that
Trinity had solved. Bah. :/ :/ )
--
NULL && (void)
9:51 p.m.
New subject: [trinity-devel] [PATCH tdenetwork 4/4] The propsdlgplugin must depend on filesharesamba.
On 10 Jun 2012, Timothy Pearson said:
http://bugs.trinitydesktop.org/buglist.cgi?quicksearch=ALL
:)
If the kded hang bug is not reported yet please do so! We can't fix bugs
we don't experience and are not reported...
Thanks!
Tim
Is there any chance that you could create a
series of bug reports (e.g.
one for tdebase problems, another for tdenetwork problems, etc.) with
the
patches attached? With the volume of mail on this list I am concerned
that I (and the other developers) may not remember to evaluate/apply all
of the patches you are sending in.
I could do that if I remembered where the bug report page was :)
11 Jun
11 Jun
9:19 a.m.
New subject: [trinity-devel] [PATCH tdenetwork 4/4] The propsdlgplugin must depend on filesharesamba.
On 10 Jun 2012, Timothy Pearson outgrape:
If the kded hang bug is not reported yet please do so!
We can't fix bugs
we don't experience and are not reported...
Next time it happens -- and it happens a lot -- I'll get a backtrace and
report it. (Killing kded brings it back to life, working -- unlike in
KDE3, where it caused kdeinit to segfault. So an improvement there.)
Now trying to get kdeaccessibility to build. At all... :/
--
NULL && (void)
10:17 a.m.
New subject: [trinity-devel] [PATCH tdenetwork 4/4] The propsdlgplugin must depend on filesharesamba.
On 10 Jun 2012, Timothy Pearson outgrape:
Bugs 1025 to 1027 created (though bug 1026 took three attempts because
'attachment creation failed' for no obvious reason. Bugzilla is a really
bad patch tracking system...)
--
NULL && (void)
On 10 Jun
2012, Timothy Pearson said:
http://bugs.trinitydesktop.org/buglist.cgi?quicksearch=ALL
:) Is there any chance that you could create a
series of bug reports (e.g.
one for tdebase problems, another for tdenetwork problems, etc.) with
the
patches attached? With the volume of mail on this list I am concerned
that I (and the other developers) may not remember to evaluate/apply all
of the patches you are sending in.
I could do that if I remembered where the bug report page was :) 
4 p.m.
New subject: [trinity-devel] [PATCH tdenetwork 4/4] The propsdlgplugin must depend on filesharesamba.
On 11 June 2012 06:17, Nix <nix(a)esperi.org.uk> wrote:
On 10 Jun 2012, Timothy Pearson outgrape:
Bugs 1025 to 1027 created (though bug 1026 took three attempts because
'attachment creation failed' for no obvious reason. Bugzilla is a really
bad patch tracking system...)
It's really not so bad :P. It's easier for our project size to keep
everything in one source, one searchable resource to use. (Though I do
like commits via email because it allows users to do code review by
simply responding)
Calvin
On 10 Jun
2012, Timothy Pearson said:
http://bugs.trinitydesktop.org/buglist.cgi?quicksearch=ALL
:) Is there any chance that you could create a
series of bug reports (e.g.
one for tdebase problems, another for tdenetwork problems, etc.) with
the
patches attached? With the volume of mail on this list I am concerned
that I (and the other developers) may not remember to evaluate/apply all
of the patches you are sending in.
I could do that if I remembered where the bug report page was :)
5:05 p.m.
New subject: [trinity-devel] [PATCH tdenetwork 4/4] The propsdlgplugin must depend on filesharesamba.
On 11 Jun 2012, Calvin Morrison stated:
It's really not so bad :P. It's easier for our
project size to keep
everything in one source, one searchable resource to use. (Though I do
like commits via email because it allows users to do code review by
simply responding)
That's where patchwork is nice: it collects such responses as well, and
collates them all into a great big webpage. http://patchwork.ozlabs.org/
is the largest installation I'm aware of, and gives a fairly good
flavour of its capabilities.
--
NULL && (void)
10 a.m.
New subject: [trinity-devel] [PATCH tdenetwork 4/4] The propsdlgplugin must depend on filesharesamba.
On 10 Jun 2012, Timothy Pearson verbalised:
Is there any chance that you could create a series of
bug reports (e.g.
one for tdebase problems, another for tdenetwork problems, etc.) with the
patches attached?
Just attach the patches one after the other?
I'm stunned that you find that more convenient than, well, anything
really, it seems terribly baroque (for you, not me). But if you prefer
it, so shall it be.
(btw, it seems what you really need is to have
<http://ozlabs.org/~jk/projects/patchwork/> monitoring this mailing
list. It snarfs the patches automatically, snarfs replies to them, and
sticks them in a searchable web framework.)
--
NULL && (void)
4580
days inactive
4581
days old
8 comments
3 participants
participants (3)
-
Calvin Morrison -
Nix -
Timothy Pearson