tomboy fails with : ----------------- Missing method .ctor in assembly /usr/lib/tomboy/Tomboy.exe, type Mono.Addins.AddinEventHandler Missing method .ctor in assembly /usr/lib/tomboy/Tomboy.exe, type Mono.Addins.AddinEventHandler Exception in Gtk# callback delegate Note: Applications can use GLib.ExceptionManager.UnhandledException to handle the exception. System.IO.FileNotFoundException: Could not load file or assembly 'Mono.Addins, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' or one of its dependencies. File name: 'Mono.Addins, Version=1.0.0.0, Culture=neutral, PublicKeyToken=0738eb9f132ed756' at Tomboy.AddinManager..ctor (System.String tomboy_conf_dir, System.String old_tomboy_conf_dir) [0x00000] in <filename unknown>:0 at Tomboy.NoteManager.Initialize () [0x00000] in <filename unknown>:0 at Tomboy.Tomboy+<Main>c__AnonStorey1.<>m__0 () [0x00000] in <filename unknown>:0 at GLib.Timeout+TimeoutProxy.Handler () [0x00000] in <filename unknown>:0 at GLib.ExceptionManager.RaiseUnhandledException(System.Exception e, Boolean is_terminal) at GLib.Timeout+TimeoutProxy.Handler() at Gtk.Application.gtk_main() at Gtk.Application.Run() at Tomboy.GnomeApplication.StartMainLoop() at Tomboy.Application.StartMainLoop() at Tomboy.Tomboy.StartTrayIcon() at Tomboy.Tomboy.Main(System.String[] args) ----------------------------------- To solve this problem, one has to install mono-addins package. So mono-addins should belong to tomboy dependencies. Reproducible: Steps to Reproduce:
Keywords: (none) => TriagedAssignee: bugsquad => mageia
It's already a build dependency: BuildRequires: pkgconfig(mono-addins) On my laptop: [root@maximus dams]# LC_ALL=C urpmi tomboy In order to satisfy the 'mono(Mono.Addins)[== 1.0.0.0]' dependency, one of the following packages is needed: 1- monodevelop-4.0.12-2.mga4.noarch: Full-featured IDE for mono and Gtk# (to install) 2- mono-addins-1.0-2.mga4.noarch: Mono Addins (to install) What is your choice? (1-2) It's cauldron but nothing changed in specfile between 4 and cauldron and new tomboy is just for translations.
Can you give me more informations please? Like: $ rpm -qa | grep mono (before installing 'mono-addins' yourself).
Status: NEW => ASSIGNED
Hardware: i586 => All
[denis@localhost ~]$ rpm -qa | grep mono libmono2.0_1-3.2.3-5.mga4 gnu-free-mono-fonts-20120503-5.mga4 mono-data-sqlite-3.2.3-5.mga4 mono-extras-3.2.3-5.mga4 mono-data-3.2.3-5.mga4 mono-data-oracle-3.2.3-5.mga4 mono-nunit-3.2.3-5.mga4 mono-wcf-3.2.3-5.mga4 monodevelop-4.0.12-2.mga4 mono-winforms-3.2.3-5.mga4 libmono0-3.2.3-5.mga4 mono-3.2.3-5.mga4 mono-locale-extras-3.2.3-5.mga4 mono-ibm-data-db2-3.2.3-5.mga4 monodoc-core-3.2.3-5.mga4 mono-winfxcore-3.2.3-5.mga4 mono-web-3.2.3-5.mga4 mono-data-postgresql-3.2.3-5.mga4 mono-basic-2.10-5.mga4 libmono-devel-3.2.3-5.mga4
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version. Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't able to fix it before Mageia 4's end of life. If you are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. If it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates. This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version) If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED" 2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release. Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO. 3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page: https://wiki.mageia.org/en/How_to_report_a_bug_properly If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). If you would like to help fixing bugs in the future, don't hesitate to join the packager team via our mentoring program [1] or join the teams that fit you most [2]. [1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager [2] http://www.mageia.org/contribute/
Status: ASSIGNED => RESOLVEDResolution: (none) => OLD
Bug always present in Mageia 5
Status: RESOLVED => REOPENEDCC: (none) => contactResolution: OLD => (none)
Is it present in cauldron too?
Version: 4 => 5
Assigning to packagers collectively since the former maintainer has dropped maintainership for this package.
Assignee: mageia => pkg-bugs
Hi, i have commited the correction, but now it install also the devel package which is not nedded.
Fixed by modifying the requires in spec file
Status: REOPENED => RESOLVEDResolution: (none) => FIXED