Re: [Evolution] glib 2.54.1 requierd for 3.31 ?

[Joakim Tjernlund <Joakim Tjernlund infinera com>]

On Wed, 2018-11-14 at 14:11 +0100, Milan Crha via evolution-list wrote:
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments 
> unless you recognize the sender and know the content is safe.
>
>
> On Wed, 2018-11-14 at 12:18 +0000, Joakim Tjernlund wrote:
> > Nice, though I think glib-2.54 would be better.
>
>         Hi,
> that's only a minimum requirement. And the function in question was
> nothing serious.
>
> > That is something else. I do got a gitlab account but Gnome projects
> > like Evo won't let me in anyway, insisting that I should create yet
> > another account.
>
> It depends what you mean with the gitlab account. If an account under
> gitlab.com, then it's not what I'm talking about. GNOME runs its own
> independent instance of the GitLab [1], and as much as it's independent
> also the user accounts are independent. It's like the old bugzilla with
> couple added features.

Oh, I see. I figured you used gitlab's infra. But then why did the migration
not inherit the old accounts ?

> > This is way worse than the previous github hosting.
>
> GNOME was never hosted on github. There had been (and still is) a
> mirror of GNOME projects there, but it was not checked by many
> maintainers, thus it's really only a mirror and nothing else.

Sorry, I misremembered.

> > So I stay with email for now, hoping for the best.
>
> Okay, no problem. Though solving issues by mail is something which will
> probably not happen, because it'll get lost easily. I'd be also afraid
> of other mailing list users not being happy to see any further detailed
> investigation. Just saying.

Thanks for listning anyway. I have the opposite experience though(from the old bugzilla)
There are many reports there that are unfixed and I always had a hard time finding stuff there.

> > 1) Moved meeting still pop up an reminder at the old/initial time.
>
> Needs exact steps, like move by whom and how.

Moved by the Organizer, I get the usual calendar notice in my mbox and I choose
Update. The meeting is moved in my calendar but the reminder fired at the at old time.

> > 2) In Calendar view(see Screenshoot) I see multiple entries for the
> > same person with just Status changed(Needs Attention, Accepted,
> > Tentative etc).
>
> I do not see that here. List of attendees is provided by the server.

I see, but could could this list possibly contain the whole history of changes?
At first i just see Needs Attention for all, then as attendees reply, I see more
entries added to the end.

> >    Scrolling the Attendee window is broken when Theme adds arrows in
> > the scrollbar.
>
> Broken? Does mouse wheel work? Does clicking the scroll up/down button
> work? Can the scrollbar button be dragged? I'm afraid this is lower in
> the stack, like in gtk+, when the place for the scrollbar is too small.
> I'm only guessing.

Mouse wheel usually works but dragging the scrollbar does not, seems the scrollbar is to big now
so one cannot slide it up/down. Could be that there is a minimum scrollbar size and the
window is too small. Maybe if you added say 2 more lines in the window it would go away?

> > 3) Attendee window cannot be resized
>
> True.

Any chance this can be fixed? It is quite difficult to navigate this window when many attendees.

> > 4) Cancelled meetings remains but are prefixed Cancelled in Summary
>
> Edit->Preferences->Calendar and Tasks->View tab->Hide cancelled events.
> Its availability depends on the evolution version:
> https://gitlab.gnome.org/GNOME/evolution/issues/106

I have this fix, will try it.
As I recall(not 100% sure though), I got reminders from these Cancelled events,
will these be "hidden" too?

> > 5) Opening a meeting always generates an error:
> >       "Event cannot be fully edited, because you are not the
> > organiser"
> >    even though I haven't tried to edit anything yet.
>
> Well, you opened an editor, where you can edit event details. Some
> fields are disabled. Rather than cause a confusion "why cannot I edit
> this field, while I can edit that field", user is warned with the
> reason "proactively".

Well I just opened an meeting to look at stuff in it.
Suppose emacs( or your favourite editor) popped up an error window every time you open an readonly file ...

 Jocke