Hi,
To paraphrase Captain Tsubasa "the CI is your friend". If there was a
merge request, the build would have failed and you still would have
sent a mail here to ask how to add the dependency :). Even for smaller
changes, it's always interesting to have the CI run because it's quite
quick and can
On Wednesday, 10 July 2024 01:51:16 CEST, David Jarvie wrote:
On Tuesday, 9 July 2024 23:47:30 BST Albert Astals Cid wrote:
El dimarts, 9 de juliol del 2024, a les 22:12:40 (CEST), David Jarvie va
escriure: ...
If I'd created a merge request, it would presumably have just sat there
unmergeab
On Tuesday, 9 July 2024 23:57:09 BST Albert Astals Cid wrote:
> Please work on fixing them, otherwise i will remove the failing CI jobs on
> their 4th failing week, it is very important that CI is passing for multiple
> reasons.
>
> Good news: 4 repositories have been fixed
>
>
> Bad news: 1 rep
On Tuesday, 9 July 2024 23:47:30 BST Albert Astals Cid wrote:
> El dimarts, 9 de juliol del 2024, a les 22:12:40 (CEST), David Jarvie va
>
> escriure:
> > I have just changed the dependencies for KAlarm (removed Canberra, added
> > libvlc and libvlccore), but after committing the changes, the buil
Please work on fixing them, otherwise i will remove the failing CI jobs on
their 4th failing week, it is very important that CI is passing for multiple
reasons.
Good news: 4 repositories have been fixed
Bad news: 1 repository is still failing, 3+ repositories have started failing
kio-extras
El dimarts, 9 de juliol del 2024, a les 22:12:40 (CEST), David Jarvie va
escriure:
> I have just changed the dependencies for KAlarm (removed Canberra, added
> libvlc and libvlccore), but after committing the changes, the build fails on
> invent.kde.org.
In the future probably helps if you do si
> Thoughts on my proposal?
+1000
Do you have a branch where you're testing this along with the qdoc patch?
David
I have just changed the dependencies for KAlarm (removed Canberra, added
libvlc and libvlccore), but after committing the changes, the build fails on
invent.kde.org. I've changed everything I can find in the KAlarm repository
relating to the dependencies, so is there something else I need to do
On Wed, Jul 10, 2024 at 4:37 AM Nicolas Fella wrote:
> Hi,
>
Hi Nicolas,
>
> while reviewing our API documentation I noticed an increasing amount of
> brokenness in it. Not even in the content, but the way it is presented.
>
> Doxygen seems to struggle to properly parse and document some new-i
These 19 packages are missing from my KDE Plasma 5.23 Slackware 15.0_64
system.
kactivitymanagerd-pluginsrc, krunnerrc, kuriikwsfiltersrc, baloofilerc,
plasmaanotifyrc, kaccessrc, plasmaUserFeedback, touchpadxlibinputrc,
kgammarc, device_automounter-kcmrc, kgammarc, device_automounter_kcmrc,
kded_
Hi Nicolas,
I couldn't find according tickets in Doxygen's issue tracker. I looked
for Q_SIGNAL, QML_ELEMENT, QML_NAMED_ELEMENT, and QML_SINGLETON.
I know they have 1,7k open issues and it might not be their highest
priority. I still would prefer to let Doxygen know what we as their
users would
El dimarts, 9 de juliol del 2024, a les 18:37:16 (CEST), Nicolas Fella va
escriure:
> Hi,
>
> while reviewing our API documentation I noticed an increasing amount of
> brokenness in it. Not even in the content, but the way it is presented.
>
> Doxygen seems to struggle to properly parse and docu
Hi,
while reviewing our API documentation I noticed an increasing amount of
brokenness in it. Not even in the content, but the way it is presented.
Doxygen seems to struggle to properly parse and document some new-ish Qt
features:
- It doesn't parse signals declared with Q_SIGNAL (as opposed to
13 matches
Mail list logo
