Hello, it looks like it was fixed since I've opened the issue.
But the original issue was exactly as I've written: when you opened the last week of the year and went to the previous week, you still saw the last week of the year. (=> The last week of the year was there twice when going through the weeks.) There also was a difference in the events from a different calendar source.
But it doesn't matter now since it's not happening anymore.
Yes. Thanks for your patience!
@davide125 ah, missed the notification... I am really sorry about that.
I see a few successful builds from yesterday in both repositories. Have you changed anything? Does it work as expected now?
I see you use a custom project both for commits and merge-requests.
Maybe, it would be better to build just commit versions in a shared project but use the custom repo as a so-called additional repo.
I've used a very similar setup here (=multiple related projects, main
commits are build in the shared Copr project, but merge-requests/pull-requsts does not influence the shared Copr project).
So, something like this:
- job: copr_build
trigger: commit
owner: dcavalca
project: crosswords
targets:
- fedora-all-aarch64
- job: copr_build
trigger: pull_request
targets:
- fedora-all-aarch64
additional_repos:
- "copr://dcavalca/crosswords"
Hi @jrb, František from the Packit team here.
I've taken a look at what is going on here and it looks like you're mixing our production and staging instances in your setup.
You have two options here:
https://prod.packit.dev/api/webhooks/gitlab
instead of https://stg.packit.dev/api/webhooks/gitlab
).https://stg.packit.dev/api/webhooks/gitlab
. When using stage, you need to set packit_instances
key in your config to specify which instance(s) can react. (It's ["prod"]
by default so you need to use ["stg"]
or ["stg", "prod"]
for the stage to react. Note that this can be defined globally or per job. Take a look at Packit itself for inspiration.)@gnumdk Thank you very much for the quick fix! Do you plan to release a new version or should I manage to install the development one to have it?
Thanks!
Just found it's documented here: https://wiki.gnome.org/Apps/Geary/Plugins (Not sure if the page is linked from somewhere...)
@gnumdk Thank you very much for your response.
I have the Templates
folder (meaning a mail folder, not a folder on a disc).
I am able to create a template, but now I am not sure what to do.
The compose window does not have any confirm button and it looks like Cancel
+ Keep
saves the template.
Oh, now I see the merge button in the template list...;) Thanks! Would you be interested in documenting this? Do you have a place where this can be placed/shown?
Hello!
I am trying to use the mail-merge plugin in Geary but the message sent does not have the placeholder values like {{field}}
replaced.
Here are the steps I use:
"name","mail","content"
"a","lachma...@gmail.com","aaa"
"c","la...@gmail.com","ccc"
Send
button this is the resulting email (geary-message-7P7DR1.txt) in the Outbox
:
As you can see, the mail-merge functionality wasn't applied. Am I doing something wrong? Thank you in advance for any help/tip...
I use flatpaked Geary 40.0
from the Fedora repository and a Google account through Gnome Online Account. (The system is Fedora Linux 36.20220701.0 (Silverblue)
:
(Can you please point me to the instructions on where/how I can get the relevant debug logs? edit: already found https://wiki.gnome.org/Apps/Geary/ReportingABug -- will take a look if I can get more info)
For me, the key was to enable 2FA -- after that, I was able to use the app password directly in Geary and also go through the Gnome Online Accounts setup. (The error mentioning no supported browser disappeared.)