Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "diodon":
* Package name: diodon
Version : 1.13.0-1
Upstream Author : Oliver Sauder
* URL : https://launchpad.net/diodon
* License : LGPL
Diodon is a desktop utility and not a command line tool. So far the only
two things you can do from the command line is to open diodon or to open
it in debug mode by setting `G_MESSAGES_DEBUG` to `all`. Both those
options are documented in the man page.
It would be great to have more
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "diodon":
* Package name: diodon
Version : 1.12.0-1
Upstream Author : Oliver Sauder
* URL : https://launchpad.net/diodon
* License : LGPL
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "diodon":
* Package name: diodon
Version : 1.11.2-1
Upstream Author : Oliver Sauder
* URL : https://launchpad.net/diodon
* License : LGPL
Never mind. Because of custom-library-search-path error [0] there needs
to be a new upstream version anyway and with that new release this build
error can then be fixed as well.
Oliver
[0] https://lintian.debian.org/tags/custom-library-search-path
Lucas,
Thanks for reporting. This issue has actually been resolved upstream but
it seems that I uploaded an invalid orig tarball for version 1.11.1 for
the Debian package. Instead of the new upstream tarball 1.11.1, 1.11.0
was still used (when opening the tarball from [0] the folder name is
still
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "diodon":
* Package name: diodon
Version : 1.11.1-1
Upstream Author : Oliver Sauder
* URL : https://launchpad.net/diodon
* License : LGP
On 13.07.21 22:19, Adrian Bunk wrote:
> Package: gir1.2-diodon-1.0
> Version: 1.8.0-1
> Severity: serious
>
> ${gir:Depends} needs "dh --with gir" in debian/rules.
> The manual dependency on gir1.2-glib-2.0 is no longer necessary
> when this is fixed.
>
> Something still seems to go wrong
Hi Chris,
Thanks for reporting this. This file is actually obsolete and was only
needed when Diodon was only available on Launchpad before publishing it
to Debian and synced to Ubuntu from there. See here [0] for more
information.
This file should indeed be removed from the Debian package.
Hi Chris
Thanks for your report.
Actually this was an unnoticed rename of
/etc/xdg/autostart/diodon.desktop to
/etc/xdg/autostart/diodon-autostart.desktop when Diodon moved to the
Meson Build system.
I guess using the `dh_installdeb` with a `diodon.mainscript` file will
be the easiest as per
Thanks Sam for reporting this.
This is actually not fully related to the original report of this issue
as it is a bug that `Clear` method does not completely remove clipboard
content from the Zeitgeist database as I agree it really should.
As discussed on the upstream issue [0] I will look into
I assume the sqlite database got corrupted or is too big. There is an
article here [0] which describes why this could happen. Diodon uses
Zeitgeist to store clipboard items and zeitgeist manages the sqlite
database itself.
So you find the database at ~/.local/share/zeitgeist/.
Best have a look
What desktop environment do you use?
Oliver
On 17.10.20 17:23, Jörg Frings-Fürst wrote:
> Package: diodon
> Version: 1.11.0-1
> Severity: important
>
> Hello,
>
> Diodon has no icon in the Notification Area.
>
> It is running:
>
> [quote]
> $ ps -Af | grep diodon
> jff 153136 12932 0
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "diodon":
* Package name: diodon
Version : 1.11.0-1
Upstream Author : Oliver Sauder
* URL : https://launchpad.net/diodon
* License : LGPL-2.
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "diodon"
* Package name: diodon
Version : 1.10.0-1
Upstream Author : Oliver Sauder
* URL : https://launchpad.net/diodon
* License : GPL
This is a known issue see https://bugs.launchpad.net/diodon/+bug/1435033
Unfortunately so far it is not quite clear what causes this. Any
comments are welcome.
Oliver
On 26.05.20 16:58, Christoph Berg wrote:
> Package: diodon
> Version: 1.9.0-1
> Severity: normal
>
> Hi,
>
> I just started
I am working on this upstream.
See https://github.com/diodon-dev/diodon/pull/20
Oliver
On 15.04.20 12:20, Simon McVittie wrote:
> Source: diodon
> Version: 1.9.0-1
> Tags: sid bullseye
> Severity: important
> Control: block 895037 by -1
> User: pkg-ayatana-de...@lists.alioth.debian.org
>
Link to corresponding upstream bug tracker issue
https://bugs.launchpad.net/diodon/+bug/1871008
Cheers,
Oliver
On 06.04.20 05:05, Christoph Anton Mitterer wrote:
> Package: diodon
> Version: 1.9.0-1
> Severity: important
>
>
>
> Hi.
>
> Just noted that, even though not used, diodon eats up
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "diodon"
* Package name: diodon
Version : 1.9.0-1
Upstream Author : Oliver Sauder
* URL : https://launchpad.net/diodon
* License : GPL
Just an update on the current progress of this issue.
Updating of waf seems to be more complicated and breaks the current build.
Instead of trying to fix those errors an upstream PR is work in progress
to move to meson build system as many GNOME projects do as well.
See
: error: fakeroot debian/rules clean subprocess returned exit
status 2
I don't know anything about waf, so that's not something I can troubleshoot.
Not going to NMU.
Scott K
On Tuesday, September 17, 2019 1:46:07 PM EDT Oliver Sauder wrote:
I currently do not have a lot of time at hand. So if you cou
I currently do not have a lot of time at hand. So if you could follow up
releasing your NMU debdiff that would be great (diff looks good to me).
Oliver
On 01.09.19 09:18, Scott Kitterman wrote:
On Fri, 30 Aug 2019 07:15:05 + Matthias Klose wrote:
Package: src:diodon
Version: 1.8.0-1
I have addressed this issue and uploaded a new package to mentors.
See sponsorship request at
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=892660
Oliver
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "diodon"
* Package name: diodon
Version : 1.8.0-1
Upstream Author : Oliver Sauder <o...@esite.ch>
* URL : https://launchpad.net/di
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "diodon"
* Package name: diodon
Version : 1.6.0-1
Upstream Author : Oliver Sauder <o...@esite.ch>
* URL : https://launchpad.net/di
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "diodon"
* Package name: diodon
Version : 1.6.0-1
Upstream Author : Oliver Sauder <o...@esite.ch>
* URL : https://launchpad.net/di
I have updated Diodon package so it doesn't depend on dbus-launch anymore.
Uploaded to mentors:
https://mentors.debian.net/package/diodon
https://mentors.debian.net/debian/pool/main/d/diodon/diodon_1.6.0-1.dsc
Looking for a sponsor...
signature.asc
Description: OpenPGP digital signature
Does this error still occur?
If yes could you run following commands:
G_MESSAGES_DEBUG=all diodon > diodon_debug.txt
and attach diodon_debug.txt to this bug report?
Thanks.
Oliver
Severity: important
Reverting severity to important as it has been marked by mistake (Diodon
doesn't use Qt).
Also a package updating to 1.5.0 is available
https://mentors.debian.net/package/diodon
Looking for a sponsor.
Regards,
Oliver
I have fixed this issue with the update to the newest upstream version
1.5.0.
It is uploaded to https://mentors.debian.net/package/diodon and needs
sponsorship.
Thanks,
Oliver
Package: diodon
Version: 1.3.0-1
Severity: important
Hey.
There is a new upstream version 1.5.0 diodon would need to be updated
too: https://launchpad.net/diodon/+milestone/1.5.0
I will follow up with this update but creating this issue as reference.
Regards,
Oliver
AFAICS you're also upstream, right?
yes
1) Well as you say, it works quite nicely with other DEs, at least
those close to GNOME (like Cinnamon).
Depending on Zeitgeist more or less excludes these users - maybe not
from a technical PoV, but rather because such people typically don't
use
Tags: wontfix
I can understand your concerns, let me outline a couple of things here
though:
1. Diodon does work on other DEs but is mainly targeted to integrate
well into GNOME and Unity [0]
2. It is true (unfortunately) that Zeitgeist is not actively developed
anymore but it is still
On 21.05.2015 21:58, Emilio Pozuelo Monfort wrote:
Control: severity -1 serious
We want to remove libgee2 from unstable RSN, and there are only a few rdeps
now,
so I'm bumping the severity of the bugs.
If you have questions don't hesitate to ask.
Emilio
Hey Emilio,
I actually
+1,11 @@
+ding (1.7-3) unstable; urgency=low
+
+ * debian/patches/08_adjust_ding_desktop_file.patch:
+Fixed installation of ding.desktop file.
+ * Update to Standards-Version 3.9.4
+
+ -- Oliver Sauder o...@esite.ch Sat, 12 Apr 2014 12:28:37 +0300
+
ding (1.7-2) unstable; urgency=low
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package diodon:
* Package name: diodon
Version : 1.0.3
Upstream Author : Oliver Sauder o...@esite.ch
* URL : https://launchpad.net/diodon
* License : GPL-2
According to the discussion here [0] won't there be any waf package
available, but all packages using waf have to include its source code.
So therefore it would be still great to get the waf supported integrated
into debhelper.
Oliver
[0]
Package: wnpp
Severity: wishlist
Owner: Oliver Sauder o...@esite.ch
* Package name: diodon
Version : 1.0.0
Upstream Author : Oliver Sauder o...@esite.ch
* URL : https://launchpad.net/diodon
* License : GPL2+
Programming Lang: Vala
Description : diodon
diff.
So I want to suggest that the waf.mk class clean phase is also cleaning
up those?
I have attached a patch which does so.
Thanks,
Oliver
[0] http://wiki.debian.org/UnpackWaf
From 53f0386d083f43bf69d6a0fc2852a95f754774e7 Mon Sep 17 00:00:00 2001
From: Oliver Sauder o...@esite.ch
Date: Fri, 11
Hello Beren,
I am a bit confused that you started the packaging of gemrb all over
again even though there has been many proposal for sponsorship of a
gemrb package.
I have tried to find a sponsor a couple of times through many different
ways. Unfortunately, I have not been successful so far. Due
Package: libpeas
Version: 1.1.1-2
Severity: normal
Tags: patch
Vala itself now ships a vapi for libpeas.
I bumped into an issue where the debain vapi file overwrote
the behavior of the vapi file of vala itself.
See gnome bug https://bugzilla.gnome.org/show_bug.cgi?id=660361
In this bug the
Package: libpeas
Version: 1.1.1-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch
*** /tmp/tmpREqeaE
In Ubuntu, the attached patch was applied to achieve the following:
There is a gir file PeasGtk-1.0.gir available for
Package: libpeas
Version: 1.1.1-1
Followup-For: Bug #642015
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu oneiric ubuntu-patch
*** /tmp/tmpksSqZL
So now with a complete patch (installing it with dev package was missing)
-- System Information:
Debian Release: wheezy/sid
APT
Package: libpeas-1.0-0
Version: 1.1.1-1
Severity: normal
The vapi file needs to be the same name as the pkgconfig file. See
http://live.gnome.org/Vala/Bindings for details.
Currently the vapi file is named peas-1.0.vapi however it should be
libpeas-1.0.vapi.
This has been fixed in Ubuntu see
44 matches
Mail list logo
