Bug#1067245: minder: please provide /usr/bin/minder
Package: minder Version: 1.16.2-1 Severity: minor Hi maintainer, I've installed minder but seems typing "minder" in the terminal doesn't launch the program. Had to dpkg -L the package to find it's installed as "/usr/bin/com.github.phase1geo.minder", which is not very intuitive. Would be nice if the binary could be simple renamed to "minder" upon install, or, if that's not possible, at least a /usr/bin/minder symbolic link pointing to the long name. Thanks in advance! -- System Information: Debian Release: trixie/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 6.6.15-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages minder depends on: ii dconf-gsettings-backend [gsettings-backend] 0.40.0-4+b1 ii libarchive13 3.7.2-1 ii libc62.37-15 ii libcairo21.18.0-1+b1 ii libgdk-pixbuf-2.0-0 2.42.10+dfsg-3+b1 ii libgee-0.8-2 0.20.6-1 ii libglib2.0-0 2.78.4-1 ii libgranite6 6.2.0-3+b1 ii libgtk-3-0 3.24.41-1 ii libgtksourceview-4-0 4.8.4-5+b1 ii libhandy-1-0 1.8.3-1 ii libjson-glib-1.0-0 1.8.0-2 ii libmarkdown2 2.2.7-2+b1 ii libpango-1.0-0 1.52.0+ds-1 ii libpangocairo-1.0-0 1.52.0+ds-1 ii libxml2 2.9.14+dfsg-1.3+b2 minder recommends no packages. minder suggests no packages. -- no debconf information
Bug#1029068: vcswatch: fails to run due to full file system.
Package: qa.debian.org Followup-For: Bug #1029068 Hi, Just noticed at least one of my packages¹ got also hit by this one: Error: fatal: Unable to create temporary file '/srv/scratch/qa.debian.org/vcswatch/c/claws-mail/objects/pack/tmp_idx_XX': No space left on device fatal: index-pack failed Is this fixable or just a temporary server issue? In case of the former, can I help to fix this somehow? best regards, ¹ https://qa.debian.org/cgi-bin/vcswatch?package=claws-mail -- Ricardo Mones http://people.debian.org/~mones «Not responsible for typographical errors.»
Bug#967764: sylpheed: depends on deprecated GTK 2
Hi, On Wed, 1 Nov 2023 23:47:17 +0100 Alexandre Detiste wrote: > Hi, > > I had been using sylpheed before & clawsmail > more recently. I do think it's time to drop the ball: > > i.e: > 1) RM src:sylpheed > 2) let src:claws-mail provide a "sylpheed" transitional package, > 3) maybe with a config migration script, but this step is not mandatory > to get 1 & 2 done. For this route I think is mandatory the existing configurations of sylpheed do still work after being replaced by claws-mail. IMO better than leaving users with a migrated configuration that doesn't work is preferable to let the users to configure claws-mail from scratch. Note that claws-mail has migration code for sylpheed configurations since the early days, but with the years passed since they forked this could be easily missing some change. > Conveniently the version number of claws-mail is higher than sylpheed's > one, so no need for extra debhelper wizardy. > > (I did somethink like "3" for residualvm -> scummvm but MR was rejected... > it's better to discuss first) > > Greetings > > > From: Bastian Germann > > Date: Wed, 25 Oct 2023 20:15:53 +0200 > > > > With claws-mail, there is a sylpheed fork available in Debian that has > > the porting to GTK 3 done. sylpheed upstream development seems to have > > stalled. Please consider to have a good migration story for users and > > get rid of sylpheed for trixie. My feeling, from the decades I've been subscribed to upstream ML, is that for most of Sylpheed users migration to Claws Mail is not an option. Of course I could be wrong, and not having it in Debian could also lean the scale for some of those users, but, although the core function is still the same, this is not a trivial change from the users' point of view IMO. To summarize: I think is better to some slightly annoyed users who had to install claws-mail by hand than a bunch of angry users because they got claws-mail installed when they simply requested to upgrade sylpheed. Said that, we're still at the beginning of the cycle and there's still a lot of time before trixie is released, no need to make a rushed decision now. best regards, -- Ricardo Mones http://people.debian.org/~mones «Whistler's Law: You never know who is right, but you always know who is in charge.» pgpA6XDGGV9lF.pgp Description: Firma digital OpenPGP
Bug#1053397: ytree: new upstream version available
Source: ytree Version: 1.99pl1-2.1 Severity: wishlist X-Debbugs-Cc: mo...@debian.org Dear Maintainer, On ytree's homepage a new upstream version is listed (2.05 at the moment of writting this message). As usually, would be nice to have it packaged for Debian. best regards and thanks in advance, -- System Information: Debian Release: 12.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 6.1.0-10-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#853231: Please update xsensor to newer fork
Hi Bastian, Wasn't aware you were interested in xsensors, glad to know! On Sat, 23 Sep 2023 15:49:56 +0200 Bastian Germann wrote: > I am uploading a LowNMU to DELAYED/10 to fix this. > The GitHub generated tarball is used because autoreconf is run anyway. > The debdiff is attached. Mmm... Does it work? Last time I tried that fork it wasn't working very well (compared to current version in Debian, that is). regards, -- Ricardo Mones http://people.debian.org/~mones «You teach best what you most need to learn.»
Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12
control: severity -1 important Hi José Luis, On Sun, 23 Jul 2023 14:22:34 +0200 José Luis González wrote: > control: severity -1 grave > > Hi Ricardo, > > > Right, but that doesn't deserve a 'grave' severity as only gsmtp > > users are affected and no data is lost or security hole is > > introduced. I've adjusted this accordingly. > > The definition of grave severity is: > > grave > makes the package in question unusable or mostly so, or > causes data loss, or introduces a security hole allowing access to the > accounts of users who use the package. > > This bug renders sylpheed unusuable or mostly so for me, so it is > indeed a grave bug. I am restoring severity accordingly. No, it's not. That "for me" you added is the part that is not mentioned in the definition and that's a quite important difference: that the package is unusable for _you_ doesn't make it unusable for _everybody_, and that's what the definition mean when it says the package is unusable. Anybody not using Gmail can use Sylpheed without problems, for example, so even if it makes unusable it for you, please keep severity as it should be. > > That has been reported on the list that downgrading to 3.7.0 fixes > > the problem: > > https://www.sraoss.jp/pipermail/sylpheed/2023-May/007129.html > > > Can you check if downgrading fixes it? > > I wish I could check it but so far the only way I have to do so is > installing from source. What I can confirm is the bug appeared when > upgrading from version 3.7.0 to version 3.8.0~beta1-1. Building Sylpheed 3.7.0 from source in Debian 12 is pretty simple, go to some empty dir and run: $ sudo apt install build-essential devscripts $ sudo apt build-dep sylpheed $ dget http://deb.debian.org/debian/pool/main/s/sylpheed/sylpheed_3.7.0-8.dsc $ cd sylpheed-3.7.0/ $ dpkg-buildpackage -us -uc $ cd .. $ sudo dpkg -i sylpheed_3.7.0-8_amd64.deb > I hope you understand this bug is preventing me from using sylpheed > and so from reading and writing email, unless from gmail's web > interface. I find of great concern that the bug is in Debian's new > stable distribution: bookworm. If you know the bug is in version > 3.8.0~beta1-1 I would suggest downgrading stable to 3.7.0 if you can > manage to do so. Yeah, I understand the situation is not funny for you. Fact is upstream has still not dealt with this bug despite the time passed (months), so there's no patch I can apply to current version. This fact joined with the increased slowness of upstream development during the past years makes me wonder if it's still worth to maintain Sylpheed within Debian. regards, -- Ricardo Mones http://people.debian.org/~mones «Bank error in your favor. Collect $200.»
Bug#1036407: sylpheed: compose mail shortcut doesn't work in compose window
control: severity -1 wishlist control: tags -1 upstream control: forwarded -1 https://github.com/sylpheed-mail/sylpheed/issues/16 Hi José Luis, On Sat, 20 May 2023 16:14:57 +0200 José Luis González wrote: > Package: sylpheed > Version: 3.7.0-8 > Severity: important > Tags: upstream > > Control + M shortcut doesn't work in compose windows, effectively > preventing from opening a new compose message window while composing a > current one. This is something that happens often so such a > restriction only makes it difficult and tiresome to use Sylpheed, as > it forces you to open Sylpheed's window to be able to create it, and > locate the existing compose window afterwards, as Sylpheed window is > likely to have concealed the already existing compose window. I think this is intentional, anyway forwarding upstream. regards, -- Ricardo Mones ~ Fichier introuvable Erreur 404
Bug#1036392: sylpheed: check new mail features should be an account preference, not a general
control: severity -1 wishlist control: tags -1 upstream control: forwarded -1 https://github.com/sylpheed-mail/sylpheed/issues/15 Hi José Luis, On Sat, 20 May 2023 12:18:21 +0200 José Luis González wrote: > Package: sylpheed > Version: 3.7.0-8 > Severity: normal > > "Check new mail every X minutes" and "Check new mail on start" are > preferences that make sense and may be necessary to be account > options, not just common to all accounts, as it currently stands. Thanks for your report, forwarded upstream. -- Ricardo Mones http://people.debian.org/~mones «The whole world is a tuxedo and you are a pair of brown shoes. -- George Gobel»
Bug#1036389: sylpheed: notification window displayed as system dialog, not actually not displayed
control: severity -1 wishlist control: tags -1 moreinfo On Sat, 20 May 2023 13:46:21 +0200 José Luis González wrote: > The problem seems to be that it's not displayed as a window, as the > setting claims, but as a system dialog. Either an additional setting is > added to choose a system dialog/notification or the behaviour is > changed to a window, as the name implies. I would suggest a separate > tickbox for both if retaining the sytem dialog is wanted. I'm pretty sure a "system dialog" is also a window... care to explain why do you make such difference between them? are you perhaps expecting a different behaviour just because the label says "window"? regards, -- Ricardo Mones http://people.debian.org/~mones «Sattinger's Law: It works better if you plug it in.» pgpPROtKEYjVS.pgp Description: Firma digital OpenPGP
Bug#1036799: sylpheed: unable to send or read email after upgrading to Debian 12
control: severity -1 important control: tags -1 confirmed control: forwarded -1 https://www.sraoss.jp/pipermail/sylpheed/2023-May/007127.html Hi José Luis, On Fri, 26 May 2023 17:46:44 +0200 José Luis González wrote: > Package: sylpheed > Version: 3.8.0~beta1-1 > Severity: grave > > After upgrading to Debian 12 and booting again the computer I am > unable to use sylpheed to neither send email with both accounts I > have set up, nor read new messages, just with the IMAP one in this > case. > > Both accounts are from Gmail. > > The error message I get trying to send with the POP3 is > > Error > > Hubo un error enviando el mensaje: > 501 5.5.2 Cannot Decode response > r11-20020a5d494b00b00300aee6c9cesm5425569wrs.20 - gsmtp > > while with the IMAP one is > > Hubo un error enviando el mensaje: > 501 5.5.2 Cannot Decode response > j13-20020a5d604d00b00306344eaebfsm5456150wrt.28 - gsmtp > > Whereas, trying to open the inbox of the IMAP one, or any other > folder, gets this: > > Error > > No se pudo establecer una conexión con el servidor. > > making it impossible to read or query new mail. Right, but that doesn't deserve a 'grave' severity as only gsmtp users are affected and no data is lost or security hole is introduced. I've adjusted this accordingly. That has been reported on the list that downgrading to 3.7.0 fixes the problem: https://www.sraoss.jp/pipermail/sylpheed/2023-May/007129.html Can you check if downgrading fixes it? best regards, -- Ricardo Mones http://people.debian.org/~mones «Tempt not a desperate man. -- William Shakespeare, "Romeo and Juliet"»
Bug#1005840: claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)
On Sat, 3 Dec 2022 18:38:20 +0100 Francesco Poli wrote: > Control: fixed -1 claws-mail-themes/20221017+dfsg.1-1 > > > [it seems to me that control directives in messages sent to -done > addresses are not processed... I am repeating the directive for this > reason] Umm, how inconvenient, but thanks anyway! :) > > On Sat, 3 Dec 2022 18:08:55 +0100 Ricardo Mones wrote: > > > control: fixed -1 claws-mail-themes/20221017+dfsg.1-1 > > > > On Sun, 27 Feb 2022 17:55:23 +0100 > > Francesco Poli wrote: > > […] > > > > Yeah, agreed, but given I doubt that can be possible at this > > > > point to make upstream release a new tarball just to fix those > > > > bits, specially without a contact address. Will try to ask > > > > upstream if somebody has his contact, otherwise I'm afraid the > > > > only solution will be the removal. > > > > > > Thanks for willing to attempt this. > > > Let's see how it goes... > > > > Despite the time passed, efforts were worth it and it went well :-) > > > [...] > > This is great news, indeed! > Thanks for your efforts. > > > Now, if only the licensing status of Fugue/* were also ironed out... > See the original bug report! ;-) Oh, the joys of reporting two problems on one bug… had lost track of this one! The original web from where the theme icons are being reused (http://www.pinvoke.com/) still works and points to the licence so I tend to agree this is CC-BY-3.0, furthermore the theme includes the full text in the LICENSE.txt, so I've updated the copyright file¹. Presumably this can be improved if #884224 is fixed at some point ;-) Regarding persuading authors to switch licenses, well, my feeling is that you have the same power than me to do that. As you rightly said, the license is accepted by Debian currently, and that, very likely, outweighs any other argument you can give to them. best regards, ¹ https://salsa.debian.org/claws-mail-team/claws-mail-themes/-/commit/84ce4ff4d7141d5a95c57fec67556d8350f9ad81 -- Ricardo Mones http://people.debian.org/~mones «Alimony and bribes will engage a large share of your wealth.»
Bug#1024412: claws-mail: reproducible builds: Embeds timezone-dependent build date in manpages
Hi Vagrant! On Fri, 18 Nov 2022 13:32:24 -0800 Vagrant Cascadian wrote: > The attached patch to debian/rules fixes this by setting ISO_DATE > using the UTC timezone. Applied, thanks! > According to my local tests, With this patch applied claws-mail should > build reproducibly on tests.reproducible-builds.org! > > Thanks for maintaining claws-mail! Thank you for your work at reproducible builds! :) -- Ricardo Mones http://people.debian.org/~mones «Your true value depends entirely on what you are compared with.» pgpSL4TaXtHnV.pgp Description: OpenPGP digital signature
Bug#1019604: Any plans to fix this?
Hi maintainers, Just wondering, after Claws Mail being removed from testing because of this bug… is there any ongoing plan to fix this bug before freeze starts or should I play safer and remove the bsfilter plugin from Claws Mail to allow migration again? thanks in advance for any response, -- Ricardo Mones http://people.debian.org/~mones «Don't look now, but there is a multi-legged creature on your shoulder.» pgpt8ehG1_HyJ.pgp Description: OpenPGP digital signature
Bug#1018749: claws-mail: Size of Dropdown and Clear-Button to large.
control: tags -1 confirmed Hi Christopher, On Tue, 30 Aug 2022 07:43:12 +0200 Christopher Bock wrote: > Package: claws-mail > Version: 4.1.0-2 > Severity: minor > > Dear Maintainer, > >* What led up to the situation? > > I guess some Update from the gtk-libraries. The origin seems to be packaging changes in the adwaita theme which have migrated to testing recently, this one to be precise: https://salsa.debian.org/gnome-team/adwaita-icon-theme/-/commit/b5022c4f854d08af064dab7f25df7b38d83df0b5 I've been also able to reproduce it with a fresh VM from the debian testing ISO, but keep reading... :) >* What exactly did you do (or not do) that was effective (or > ineffective)? > Nothing of the following was effective. > > - Starting Claws-Mail with different Themes via > - GTK_THEME=Adwaita claws-mail > - GTK_THEME=Breeze claws-mail Just guessing, but perhaps Breeze suffered the same process. […] >* What was the outcome of this action? > > The Size of the Drop-Down-Field and Clear-Button for Searching > Mails is about 3 times thicker than it should be. > And now that i loaded the report in Claws-Mail to send it > over i can see that the Size of TO/CC/BCC/.. is also broken. > >* What outcome did you expect instead? > >A clean look like in the past. Yeah, that would be nice. Anyway seems also strange that the automatic-resizing mentioned on the above commit's comment is not happening at all, despite the code is requesting to create the button¹ with an icon of 16x16 pixels² and nothing is mentioned on the code of that function about the size parameter being ignored or deprecated³. Hence I'm not reassigning to adwaita-icon-theme because I think more investigation is required. I'm also CCing adwaita developer in case I've overlooked something and he can shed some light here, hi Simon! :) best regards, ¹ https://git.claws-mail.org/?p=claws.git;a=blob;f=src/compose.c;h=60443a8aad69a1c750cd885365a6048c2211efab;hb=3674865761a7d909ac4bff505a624b175d842c41#l7246 ² https://docs.gtk.org/gtk3/enum.IconSize.html ³ https://docs.gtk.org/gtk3/ctor.Button.new_from_icon_name.html -- Ricardo Mones http://people.debian.org/~mones «Q: What is purple and commutes? A: An Abelian grape.»
Bug#1015345: manuskript: new upstream version available
Source: manuskript Version: 0.12.0-1 Severity: wishlist Tags: upstream Dear Miriam, Long time no see! I hope you're well ^_^ Seems there's a new upstream version of this package (0.14¹). Haven't reviewed the changes, but perhaps it would be nice to have it in Debian. thanks in advance and best regards, ¹ http://www.theologeek.ch/manuskript/download/ -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1014080: zutty: crashes on startup
Hi David,
On Thu, 07 Jul 2022 08:47:45 -0300
David Bremner wrote:
> Ricardo Mones writes:
>
> >
> > Indeed, seems something specific, had never seen a similar error. A list
> > of questions which I think would be useful to know before forwarding this
> > upstream:
[…]
> > • Are compute shaders supported? (glxinfo | grep ARB_compute_shader)
>
> That seems to be the problem, nothing found. According to the xorg page
>
> https://www.x.org/wiki/RadeonFeature/
>
> the hardware does not support compute shaders? Or at least they write
> "N/A".
>
> I'm not sure you'll get much sympathy upstream, but IMHO the error
> message could be improved in any case.
Agreed, as currently is pretty obscure, IMHO.
Could you build zutty on your system with the attached patch and check if it
improves somehow?
thanks in advance,
--
Ricardo Mones
http://people.debian.org/~mones
«You think Oedipus had a problem -- Adam was Eve's mother.»
diff --git a/src/charvdev.cc b/src/charvdev.cc
index 7eb1979..4620292 100644
--- a/src/charvdev.cc
+++ b/src/charvdev.cc
@@ -396,6 +396,7 @@ namespace zutty
: px (fontpk->getPx ())
, py (fontpk->getPy ())
{
+ checkExtensions ();
createShaders ();
/*
@@ -638,6 +639,20 @@ namespace zutty
// private methods
+ void
+ CharVdev::checkExtensions ()
+ {
+const GLubyte* what = glGetString(GL_EXTENSIONS);
+char* p = strtok ((char *) what, " ");
+while (p) {
+if (strstr (p, "compute") != NULL)
+return;
+p = strtok (nullptr, " ");
+}
+logE << "sorry, your OpenGL doesn't have compute shaders\n" << std::endl;
+exit (1);
+ }
+
void
CharVdev::createShaders ()
{
diff --git a/src/charvdev.h b/src/charvdev.h
index ae94fc4..2135407 100644
--- a/src/charvdev.h
+++ b/src/charvdev.h
@@ -133,6 +133,7 @@ namespace zutty
Cell * cells = nullptr; // valid pointer if mapped, else nullptr
+ void checkExtensions ();
void createShaders ();
};
pgplV_ENWgvga.pgp
Description: Firma digital OpenPGP
Bug#1014080: zutty: crashes on startup
Hi David, On Wed, 29 Jun 2022 21:14:48 -0300 David Bremner wrote: > Package: zutty > Version: 0.12.2.20220528.131633+dfsg1-1 > Severity: important > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > This might be specific to my configuration (amd64 GPU, free drivers), > but zutty doesn't work at all on my machine. > > ╭─ convex:~ > ╰─% zutty > E [charvdev.cc:277] Error: Compiling compute shader: > > terminate called after throwing an instance of 'std::system_error' > what(): Resource deadlock avoided > zsh: IOT instruction zutty Indeed, seems something specific, had never seen a similar error. A list of questions which I think would be useful to know before forwarding this upstream: • What GPU and drivers are you using? • What OpenGL version? (glxinfo | grep "OpenGL version") • Are compute shaders supported? (glxinfo | grep ARB_compute_shader) regards, -- Ricardo Mones http://people.debian.org/~mones «What about WRITING it first and rationalizing it afterwords? :-) -- Larry Wall in <8...@jpl-devvax.jpl.nasa.gov>» pgpqez0JtotaQ.pgp Description: Firma digital OpenPGP
Bug#1013412: edgar: a real homepage exists
Package: edgar Severity: minor X-Debbugs-Cc: Matt Barry Hi, Just noticed the control' Homepage field is set to a github URL but there's a real homepage at https://www.parallelrealities.co.uk/games/edgar/ Would be nice to update this field. thanks in advance and best regards, -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.18.0-1-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_WARN Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#1011985: claws-mail: [backport request] for compatibility with gmail
On Wed, 22 Jun 2022 00:56:09 +0200 Andreas Rönnquist wrote: > I have prepared a backport of claws-mail, and have uploaded it - It's > in the backports NEW queue, so I don't know how long it will take > before getting through (It is out of my control). Thanks a lot Andreas! -- Ricardo Mones http://people.debian.org/~mones «We cannot command nature except by obeying her. -- Sir Francis Bacon» pgpjaA59YHbXe.pgp Description: Firma digital OpenPGP
Bug#1009473: claws-mail: FTBFS: perl.h:736:25: error: expected expression before ‘do’
control: tags -1 confirmed fixed pending
control: affects 1009149 claws-mail
Hi Lucas,
On Tue, Apr 12, 2022 at 07:45:18PM +0200, Lucas Nussbaum wrote:
> Source: claws-mail
> Version: 4.0.0-3
> Severity: serious
> Justification: FTBFS
> Tags: bookworm sid ftbfs
> User: lu...@debian.org
> Usertags: ftbfs-20220412 ftbfs-bookworm
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
>
>
> Relevant part (hopefully):
> > In file included from perl_plugin.c:51:
> > perl_plugin.c: In function ‘XS_ClawsMail_filter_init’:
> > /usr/lib/x86_64-linux-gnu/perl/5.34/CORE/perl.h:736:25: error: expected
> > expression before ‘do’
> > 736 | # define STMT_START do
> > | ^~
> > /usr/lib/x86_64-linux-gnu/perl/5.34/CORE/XSUB.h:333:24: note: in expansion
> > of macro ‘STMT_START’
> > 333 | #define XSRETURN_UV(v) STMT_START { XST_mUV(0,v); XSRETURN(1); }
> > STMT_END
> > |^~
> > perl_plugin.c:576:27: note: in expansion of macro ‘XSRETURN_UV’
> > 576 | msginfo->size ? XSRETURN_UV(msginfo->size) :
> > XSRETURN_UNDEF;
> > | ^~~
[…]
Already fixed in salsa:
https://salsa.debian.org/claws-mail-team/claws-mail/-/blob/master/debian/patches/20cope_with_fix_for_1009149.patch
> If you reassign this bug to another package, please marking it as
> 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
This is caused by the fix of #1009149¹, which invalidates the usage of
XSRETURN macros within expressions just because clang "warns a lot" and
because it has "little value", oh well.
Nevertheless I wonder why the above fix is not updating some doc to
reflect this new behaviour, but perhaps that's been done in other patch.
regards,
¹
https://salsa.debian.org/perl-team/interpreter/perl/-/commit/c949a3d4176ec66493af1aa87c1dc64fc6127bb6
--
Ricardo Mones
~
Absence of evidence is not evidence of absence. Carl Sagan
signature.asc
Description: PGP signature
Bug#1008765: claws-mail: build-depends on unavailable package libltdl3-dev
Package: claws-mail Version: 4.0.0-3 Severity: grave Tags: ftbfs Justification: renders package unusable X-Debbugs-Cc: mo...@debian.org Just noticed claws-mail is also affected by 2.4.7-2 upload of libtool, like detailed in bugs #1008470 and #1008698. This is a remainder to my future self to fix it next week, taking advantage of the next upstream release this weekend. -- System Information: Debian Release: 11.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64)
Bug#1007259: closed by Debian FTP Masters (reply to Ricardo Mones ) (Bug#1007259: fixed in claws-mail 4.0.0-3)
On Wed, Mar 23, 2022 at 01:05:17AM +0200, Shai Berger wrote: > Yay! Thanks a bunch! My pleasure! -- Ricardo Mones ~ Absence of evidence is not evidence of absence. Carl Sagan
Bug#1005840: claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)
On Sun, 27 Feb 2022 12:21:47 +0100 Francesco Poli wrote: > On Sat, 26 Feb 2022 22:08:17 +0100 Ricardo Mones wrote: > > > On Tue, 15 Feb 2022 22:12:54 +0100 > > "Francesco Poli (wintermute)" wrote: > [...] > > > Files: UltimateClawsMail0.5.1/* > [...] > > > License: CC-BY-NC-SA-3.0 > [...] > > > > > > This is non-free, since it's non-commercial. > > > Please persuade its upstream copyright holder to re-license it > > > under DFSG-free terms (such as the GNU GPL) or drop the theme > > > from the package. > > > > Curiously enough, upstream site¹ says it's licensed under GPL: > > > > > The author of the Ultimate Gnome theme has graciously allowed me to > > > publish Ultimate Claws Mail under the GPL rather than Creative Commons. > > > UCM is now licensed under the GPL v3. > > That's encouraging! Thanks for investigating. > > > > > But the themeinfo metadata included in the tarball still says CC... > > Very awkward... > > > not sure > > if the above is enough to update the license on Debian's copyright and > > themeinfo or not though. What do you think? > [...] > > I think the best way forward is to get in touch with upstream copyright > holders and seek clarification. That can be difficult, since I'm unable to find any address of the Author within the upstream website or tarball. Furthermore seems that discussion already happened: https://code.google.com/archive/p/ultimate-claws-mail/issues/1 > Ideally, the metadata included in the upstream distribution tar archive > should be consistent with the statement on the upstream website. > > I would be great, if that theme were clearly and explicitly licensed > under the terms of the GNU GPL. Yeah, agreed, but given I doubt that can be possible at this point to make upstream release a new tarball just to fix those bits, specially without a contact address. Will try to ask upstream if somebody has his contact, otherwise I'm afraid the only solution will be the removal. regards, -- Ricardo Mones http://people.debian.org/~mones «Try to divide your time evenly to keep others happy.» pgpfLsMCZGSAg.pgp Description: Firma digital OpenPGP
Bug#1005840: claws-mail-themes: includes non-free content (CC-by-nc-sa-v3.0)
On Tue, 15 Feb 2022 22:12:54 +0100 "Francesco Poli (wintermute)" wrote: > Package: claws-mail-themes > Version: 20140629+dfsg2-1 > Severity: serious > Justification: Policy 2.2.1 > > Hello and thanks for maintaining claws-mail. > > I noticed that one of the themes shipped in package 'claws-mail-themes' > is non-free and should not be included in a package in Debian main: > > Files: UltimateClawsMail0.5.1/* > Copyright: >Daniel LaGesse > License: CC-BY-NC-SA-3.0 > Comment: >http://creativecommons.org/licenses/by-nc-sa/3.0/ > > This is non-free, since it's non-commercial. > Please persuade its upstream copyright holder to re-license it > under DFSG-free terms (such as the GNU GPL) or drop the theme > from the package. Curiously enough, upstream site¹ says it's licensed under GPL: > The author of the Ultimate Gnome theme has graciously allowed me to > publish Ultimate Claws Mail under the GPL rather than Creative Commons. > UCM is now licensed under the GPL v3. But the themeinfo metadata included in the tarball still says CC... not sure if the above is enough to update the license on Debian's copyright and themeinfo or not though. What do you think? regards, ¹ https://code.google.com/archive/p/ultimate-claws-mail/ -- Ricardo Mones http://people.debian.org/~mones «This fortune intentionally says nothing.» pgpcq5trQxcxd.pgp Description: Firma digital OpenPGP
Bug#853231: Please update xsensor to newer fork
Hi Jeremy, On Mon, Jan 30, 2017 at 01:20:37PM -0500, Jeremy Newton wrote: > Package: xsensors > Version: 0.70 > Severity: wishlist > > I forked xsensors a while ago due to upstream no longer being active. > > Please consider changing the xsensors debian package to my fork, as it has > some bug fixes and new features, including GTK3 support, preferences and > appdata: > https://github.com/Mystro256/xsensors I've tried that fork and while ./autogen.sh succeeds, "make dist" fails, so no tarball can be generated: $ make dist make dist-gzip am__post_remove_distdir='@:' make[1]: Entering directory '<...>/upstream/raw/xsensors' make[1]: *** No rule to make target 'compile', needed by 'distdir'. Stop. make[1]: Leaving directory '<...>/upstream/raw/xsensors' make: *** [Makefile:572: dist] Error 2 Perhaps you can update the autotools machinery to be able to get a distribution tarball which can be used for packaging. regards, -- Ricardo Mones ~ RTFM - "Read The Manual" (The 'F' is silent). Usually a very good idea. Bjarne Stroustrup signature.asc Description: PGP signature
Bug#993743: xdemorse: autopkgtest regression: warning on stderr
control: tags -1 confirmed pending Hi Paul, On Sun, Sep 05, 2021 at 09:57:18PM +0200, Paul Gevers wrote: > Source: xdemorse > Version: 3.6.4-1 > X-Debbugs-CC: debian...@lists.debian.org, mo...@debian.org > Severity: serious > User: debian...@lists.debian.org > Usertags: regression > > Dear maintainer(s), > > With a recent upload of xdemorse the autopkgtest of xdemorse fails in > testing when that autopkgtest is run with the binary packages of > xdemorse from unstable. It passes when run with only packages from > testing. In tabular form: > >passfail > xdemorse from testing3.6.4-1 > all others from testingfrom testing > > I copied some of the output at the bottom of this report. Looking at the > actual test, I wonder how useful it is. There was a discussion somewhere > recently about xvfb and maybe also about ending with "&", but I forgot > the details. It may be that the test can't fail (apart from output to > stderr, which is exactly what's happening here). [...] It's caused by another component's output, and it's already fixed in git: https://salsa.debian.org/debian/xdemorse/-/commit/61863d48adc8fee43f76e9d97b1fc75009415a69 Will be included in upload of new upstream version, probably during this week, but feel free to do so if you have plenty free time, no problem. Thanks for reporting! :-) -- Ricardo Mones ~ I'm sorry, my responses are limited. You must ask the right questions. A hologram signature.asc Description: PGP signature
Bug#991723: claws-mail: CVE-2021-37746
Hi Kentaro, On Tue, Aug 03, 2021 at 11:46:50PM +0900, Kentaro Hayashi wrote: > On Fri, 30 Jul 2021 22:31:07 +0200 Salvatore Bonaccorso > wrote: > > [1] > > https://git.claws-mail.org/?p=claws.git;a=commit;h=ac286a71ed78429e16c612161251b9ea90ccd431 > > I'm not an expert, so feedback are welcome. > I think that [1] maybe incomplete. > > [1] commit fixes two parts, checking by is_uri_string [2] and new comparison > with uri->uri. [3] > > [2] > if (is_uri_string(uri->uri) == FALSE) > - return TRUE; > + return FALSE; > > > It seems ok, if it is not valid string, it should return FALSE. > > > [3] > > + if (strlen(uri->uri) > get_uri_len(uri->uri)) > + retval = FALSE; > > Before this check, there are "if (retval == FALSE)" block, > thus the above code must be put before "if (retval == FALSE)" block, > so this fix is wrong. (at least it doesn't work as expected) The "if (retval == FALSE)" block before [3] you mention is allowing the user to inspect the URL in a dialog and override the decission computed by the function so far. Moving the strlen/get_url_len check before that block would mean the user could also override that check. Therefore it has to be determined first if that difference in URL lengths can be also easily detected by user eyes. I suspect is not that easy, and allowing users to override that would make it easier for phishers to introduce dangerous URLs. But I may be wrong, of course. As currently, even if the used has decided to display the URL, the function will deny if the lenghts differ, so I think that's safer, but, as you say, some users may not expect that. Perhaps this unexpected behaviour requires some more info in the UI, better than opening the door to unsafe URLs. regards, -- Ricardo Mones ~ I'm sorry, my responses are limited. You must ask the right questions. A hologram signature.asc Description: PGP signature
Bug#989319: Sylpheed: inbox messages missing
control: severity -1 normal control: tags -1 = unreproducible moreinfo Hi José, On Tue, Jun 01, 2021 at 04:01:01AM +0200, José Luis González wrote: > Package: sylpheed > Version: 3.7.0-4 > Severity: critical > Tags: upstream > > Since about a month or two Sylpheed isn't showing me my inbox > messages. However it's printed 0/n total, with n > 0. Sorry, but don't really understand what you mean here. Firstly, what type of account are you using? Can you please also detail the steps you're taking since opening the application up to the point you call "show my inbox", what would you expect and what you currently see? (feel free to send some screenshot) regards, -- Ricardo Mones ~ Don't take the name of root in vain. /usr/src/linux/README signature.asc Description: PGP signature
Bug#987541: ukopp: consider packaging upstream maintained successor
Source: ukopp Severity: wishlist Tags: upstream Dear future maintainer, Considering adopting¹ ukopp? That's good, but note it has been discontinued upstream under this name. Instead, please consider packaging the sucessor of this program, named Backwild². Thanks in advance for your contribution to Debian! ¹ https://bugs.debian.org/987092 ² https://kornelix.net/backwild/backwild.html -- System Information: Debian Release: 10.9 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-16-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#987224: claws-mail: Hangs on attempt to view certain emails
control: tags -1 moreinfo Hi Paul, On Mon, 19 Apr 2021 22:25:43 +0100 "Paul \"LeoNerd\" Evans" wrote: > Package: claws-mail > Version: 3.17.8-1+b1 > Severity: normal > > A few emails I receive will cause claws-mail to hang in a CPU spin when > attempting to preview it (by selecting it in the message list for > preview in the third pane). This CPU spin consumes 100% of one core, > with nothing visible to strace. The program does not respond to regular > SIGINT/TERM and requires SIGKILL to quit it. > > These cases are entirely repeatable, and all occur on github issue > notifications from one particular author. Most notifications from that > author do not hang, and work as expected. But occasionally one > notification will cause a hang, and I have noticed the coincidence that > it is always the same author. > > I shall attach a file directly from my Maildir containing such a case. Since is not specified I've tried to view your message without plugins, with litehtml plugin and with dillo plugin. Didn't find any problem viewing the message in the three cases, so I guess is something particular on your configuration or machine. To narrow a bit the problem, which other plugins have you loaded? Does removing any of them (try one at a time) improve the situation? Also, since it's reproducible in your machine, and before experimenting with the plugin list, can you run claws-mail with --debug flag in a terminal and see if something interesting is printed? thanks in advance! -- Ricardo Mones http://people.debian.org/~mones «Alas, I am dying beyond my means. -- Oscar Wilde [as he sipped champagne on his deathbed]» pgp8RkN_zn_Ht.pgp Description: Firma digital OpenPGP
Bug#982047: wordwarvi
control: tags -1 confirmed Hi Joe, On Sun, Jan 31, 2021 at 07:10:46PM -0500, Joe Nahmias wrote: > > Indeed, fortuitous timing! He just tagged and closed your issue.Yes, > I'm familiar with packaging and at one point was the maintainer for > this package, so I should be okay ;)--Joe Well, for the next time I'd suggest you to push your changes to salsa *before* uploading or at least *immediately after* uploading ;-) If you don't have the time or willingness to do it, just please push your pending git commits, I'd like to fix #982047 ASAP. Thanks in advance, -- Ricardo Mones http://people.debian.org/~mones «Everything will be just tickety-boo today.» signature.asc Description: PGP signature
Bug#981249: duff: homepage is not homepage
Package: duff Severity: minor Hi maintainer, The current homepage field redirects to an advertisement page which is not related to the project. I'd suggest changing it to SF project page instead: https://sourceforge.net/projects/duff/ thanks in advance, -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages duff depends on: ii libc6 2.31-9 duff recommends no packages. duff suggests no packages.
Bug#979088: plasma-applet-redshift-control: redshift
Package: plasma-applet-redshift-control Version: 1.0.18+phabricator~2019080100-1 Followup-For: Bug #979088 Hi, Just found that redshift is not running twice as original submitter said, but up to 3 instances (just first session after reboot): $ pgrep -a redshift 2318 /usr/bin/redshift 2402 /usr/bin/redshift -l 43.5357 -5.6615 -t 6500 4000 -b 1 1 -g 1 1 1 2403 /usr/bin/redshift -l 50 7 -t 6500 4000 -b 1 1 -g 1 1 1 -r Apliying the suggested workaround just removes the first, but there's still two of them: $ systemctl stop redshift.service --user && systemctl disable redshift.service --user $ pgrep -a redshift 2402 /usr/bin/redshift -l 43.5357 -5.6615 -t 6500 4000 -b 1 1 -g 1 1 1 2403 /usr/bin/redshift -l 50 7 -t 6500 4000 -b 1 1 -g 1 1 1 -r Fortunately these two don't fight for changing the screen gamma and the flicker is not noticeable. regards, -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-1-amd64 (SMP w/4 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-applet-redshift-control depends on: ii fonts-font-awesome 5.0.10+really4.7.0~dfsg-4 ii redshift1.12-4 plasma-applet-redshift-control recommends no packages. plasma-applet-redshift-control suggests no packages. -- no debconf information
Bug#979541: sylpheed: [regression] spell check no longer recognizes some correct Italian words
control: tags -1 moreinfo Hi Francesco, On Thu, Jan 07, 2021 at 11:49:04PM +0100, Francesco Poli wrote: > On Thu, 07 Jan 2021 23:33:09 +0100 Francesco Poli (wintermute) wrote: > > [...] > > For example, if I compose a message with the following text: > > > > """ > > Questa è una prova che mi interessa poiché c'è qualcosa che non va. > > """ > > > > and select "it" spell language, I see the following red-underlined > > words or expressions: "è", "poiché", "c'è". > > I forgot to add that even "mi" is red-underlined, despite being pure > ASCII. > > [...] > > Hence, I do not understand what exactly broke during the last days > > of package upgrades. > > Maybe the way Sylpheed communicates the text to aspell? > > I tried to downgrade the following packages: > > libaspell15:amd64 from 0.60.8-2 to 0.60.8-1 > aspell from 0.60.8-2 to 0.60.8-1 > aspell-it from 2.4-20070901-0-3.1 to 2.4-20070901-0-3 > > but this didn't help. > > I am more and more puzzled... Current version was not a very fortunate upload, though in theory should not have side effects like the ones you're describing here. Anyway, can you try to downgrade sylpheed itself to 3.7.0-7 and check? thanks in advance, -- Ricardo Mones ~ Physics is like sex: sure, it may give some practical results, but that's not why we do it.Richard Feynman signature.asc Description: PGP signature
Bug#972928: claws-mail: Crash when attempted to enter IMAP folder
control: tags -1 moreinfo On Mon, Oct 26, 2020 at 10:33:35AM +, curious_debian wrote: > Package: claws-mail > Version: 3.17.3-2 > Severity: normal > > When attempted to enter IMAP folder, window instantly dissapeared (crash) > > dmesg: > > [Mon Oct 26 10:23:55 2020] claws-mail[1879911]: segfault at 1f ip > 004a35bd sp 7ffe5872a4e0 error 4 in claws-mail[442000+23] > [Mon Oct 26 10:23:55 2020] Code: 30 85 c0 0f 84 a4 02 00 00 c7 05 3e f6 2e 00 > 00 00 00 00 31 f6 48 89 df e8 c0 fc ff ff 49 8b 84 24 88 00 00 00 48 85 c0 74 > 19 <48> 8b 00 31 f6 83 38 04 48 8b 43 50 40 0f 94 c6 48 8b 78 30 e8 5a > > Context: Folder I was entering to was just downloaded via "Check for new > folders" option. > > Using Debian Stable AMD64. Is that reproducible? I've seen similar sporadic segfaults in the past and is unlikely is Claws Mail fault only. You can try translate the faulting address into some more meaningful, see [1]. Also, if it's reproducible you'll have to install debugging packages and get a proper backtrace [2]. regards, [1] https://stackoverflow.com/a/2549363 [2] https://wiki.debian.org/HowToGetABacktrace -- Ricardo Mones ~ 00:45 < hammar> cool.. have you used rssyl? 00:46 <@Ticho> um, yesSeen on #sylpheed signature.asc Description: PGP signature
Bug#969055: purpose: wrong homepage
Source: purpose Severity: minor Tags: newcomer Hi maintainer, Current homepage field gives 404, but the current git(lab) of Purpose seems to be https://invent.kde.org/frameworks/purpose Perhaps somebody can update the field in control ;-) best regards, -- System Information: Debian Release: bullseye/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-2-amd64 (SMP w/4 CPU threads) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#925056: adopting this poor lil' orphan
Hi Ivan, On Sun, Apr 26, 2020 at 02:46:44PM -0700, Ivan Kohler wrote: > retitle 925056 ITA: ssmtp -- extremely simple MTA to get mail off the system > to a mail hub > thanks > > I have this in production on a number of machines, so at the very least > worth conservatively applying things that would seem to do more good > than harm, while considering future options (migrate to something else, > or get ssmtp into shape?). Also have this in at least one machine, so I thought the same some months ago :-) Moments ago I just did a QA upload with commits that were pending. The git repo is under salsa's debian group, so feel free to continue from there. > Co-maintainers welcome. Feel free to add me as well. > Looks like there is no particular active current "upstream" either > AFAICT. You're right, unfortunately that's another point to be addressed, any ideas? regards, -- Ricardo Mones http://people.debian.org/~mones «You will stop at nothing to reach your objective, but only because your brakes are defective.» signature.asc Description: PGP signature
Bug#954833: libcss-minifier-perl: typo in POD
Package: libcss-minifier-perl Severity: minor Tags: patch upstream Hi maintainers, Just fixing a typo found while reading the package documentation, patch attached. best regards, -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libcss-minifier-perl depends on: ii perl 5.28.1-6 libcss-minifier-perl recommends no packages. libcss-minifier-perl suggests no packages. >From 97923375fd48b895f48523ccd5a5ea0b803840e9 Mon Sep 17 00:00:00 2001 From: Ricardo Mones Date: Tue, 24 Mar 2020 00:32:12 +0100 Subject: [PATCH] Add patch to fix typo in POD --- debian/patches/fix-typo.patch | 16 debian/patches/series | 1 + 2 files changed, 17 insertions(+) create mode 100644 debian/patches/fix-typo.patch create mode 100644 debian/patches/series diff --git a/debian/patches/fix-typo.patch b/debian/patches/fix-typo.patch new file mode 100644 index 000..9727eaa --- /dev/null +++ b/debian/patches/fix-typo.patch @@ -0,0 +1,16 @@ +Subject: Fix typo in exported name +From: Ricardo Mones + +diff --git a/lib/CSS/Minifier.pm b/lib/CSS/Minifier.pm +index b0742a4..42bef3e 100644 +--- a/lib/CSS/Minifier.pm b/lib/CSS/Minifier.pm +@@ -308,7 +308,7 @@ For static CSS files, it is recommended that you minify during the build stage o + + None by default. + +-Exportable on demand: minifiy() ++Exportable on demand: minify() + + + =head1 SEE ALSO diff --git a/debian/patches/series b/debian/patches/series new file mode 100644 index 000..60dbe30 --- /dev/null +++ b/debian/patches/series @@ -0,0 +1 @@ +fix-typo.patch -- 2.20.1
Bug#953896: psensor: new upstream version 1.2.0
Source: psensor Severity: wishlist Hi, Seems there's a new upstream version of psensor, would be nice to have it packaged for Debian. Since you seem to be also the upstream author, I wonder if you're still interested on Debian packaging of psensor, are you? best regards and thanks for your work so far! -- System Information: Debian Release: 10.3 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#953517: Updating the node-util Uploaders list
Source: node-util Version: 0.10.3-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953514: Updating the loganalyzer Uploaders list
Source: loganalyzer Version: 4.1.5+dfsg-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953509: Updating the node-is-typedarray Uploaders list
Source: node-is-typedarray Version: 1.0.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953515: Updating the node-bowser Uploaders list
Source: node-bowser Version: 0.7.3-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953513: Updating the node-sdp-transform Uploaders list
Source: node-sdp-transform Version: 1.4.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953510: Updating the ganglia-nagios-bridge Uploaders list
Source: ganglia-nagios-bridge Version: 1.2.1-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953511: Updating the jquery-i18n-properties Uploaders list
Source: jquery-i18n-properties Version: 1.1.0-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953508: Updating the node-websocket Uploaders list
Source: node-websocket Version: 1.0.28-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953512: Updating the node-merge Uploaders list
Source: node-merge Version: 1.2.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953516: Updating the pegjs Uploaders list
Source: pegjs Version: 0.7.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953507: Updating the node-typedarray-to-buffer Uploaders list
Source: node-typedarray-to-buffer Version: 3.0.3-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953497: Updating the loganalyzer Uploaders list
Source: loganalyzer Version: 4.1.5+dfsg-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953501: Updating the node-sdp-transform Uploaders list
Source: node-sdp-transform Version: 1.4.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953498: Updating the node-bowser Uploaders list
Source: node-bowser Version: 0.7.3-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953503: Updating the node-util Uploaders list
Source: node-util Version: 0.10.3-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953499: Updating the node-is-typedarray Uploaders list
Source: node-is-typedarray Version: 1.0.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953502: Updating the node-typedarray-to-buffer Uploaders list
Source: node-typedarray-to-buffer Version: 3.0.3-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953504: Updating the node-websocket Uploaders list
Source: node-websocket Version: 1.0.28-3 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953496: Updating the jquery-i18n-properties Uploaders list
Source: jquery-i18n-properties Version: 1.1.0-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953505: Updating the pegjs Uploaders list
Source: pegjs Version: 0.7.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953500: Updating the node-merge Uploaders list
Source: node-merge Version: 1.2.0-2 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#953495: Updating the ganglia-nagios-bridge Uploaders list
Source: ganglia-nagios-bridge Version: 1.2.1-1 Severity: minor User: m...@qa.debian.org Usertags: mia-teammaint Daniel Pocock is not a member of the Project anymore (see https://bugs.debian.org/953378#12) We are tracking their status in the MIA team and would like to ask you to remove them from the Uploaders list of the package so we can close that part of the file. (If the person is listed as Maintainer, what we are asking is to please step in as a new maintainer.) Thanks. signature.asc Description: PGP signature
Bug#822726: dclock: blink/seconds issues
control: tags -1 moreinfo Hi J meritt, On Thu, May 05, 2016 at 12:49:22AM -0400, J meritt wrote: > Attached are patches for the changes described below. Not sure which version of the code you used to generate it but unfortunately the patches doesn't apply to current upstream branch¹ neither to master branch in package's git repo. Can you provide a working patch against any of these branches? Preferably in unified format, separated by the bug fixed on each patch. > Features added: Can you provide these as a separate per-feature patches? Mixing features with fixes makes it harder to track problems if they arise. Thanks in advance and best regards, ¹ https://salsa.debian.org/debian/dclock/-/tree/upstream -- Ricardo Mones ~ Never send a human to do a machine's job. Agent Smith signature.asc Description: PGP signature
Bug#948532: closed by Debian FTP Masters (reply to Ricardo Mones ) (Bug#948532: fixed in claws-mail 3.17.5-1)
Hi Laurent, On Tue, Feb 25, 2020 at 12:38:42AM +0100, Laurent Bigonville wrote: > found 948532 3.17.5-1 > thanks > > Hello, > > Le 24/02/20 à 20:51, Debian Bug Tracking System a écrit : > > > * Switch to libenchant-2-dev (Closes: #948532) > > Looks like libclaws-mail-dev still depends against libenchant-dev, so > it's not fully fixed My bad, thanks for noticing! fixed on salsa now ;-) best regards, -- Ricardo Mones ~ The world will end in 5 minutes. Please log out.Unknown signature.asc Description: PGP signature
Bug#944424: cairo-dock-plug-ins: libetpan 1.9.4 uses now pkg-config
control: severity 944424 serious control: severity 944456 serious On Tue, Dec 24, 2019 at 08:55:10AM +0100, Ricardo Mones wrote: > Hi, > > On Sat, Nov 09, 2019 at 09:30:07PM +0100, Ricardo Mones wrote: > > I've just uploaded the new version to experimental, so you can test > > building with it. > > > > In a month or so will raise the severity of this bug when uploading to > > unstable. Please, let me know if you need more time to solve this. > > The version of libetpan currently in experimental will be uploaded to > unstable on 1st week of 2020, unless somebody objects to. Finally it has been uploaded today, sorry for the delay. regards, -- Ricardo Mones ~ Don't take the name of root in vain. /usr/src/linux/README signature.asc Description: PGP signature
Bug#950623: claws-mail-litehtml-viewer: crashes when opening a folder (plugin litehtml-viewer)
control: forwarded -1 https://www.claws-mail.org/bug/4300 control: tags -1 confirmed fixed-upstream Hi François, On Tue, Feb 04, 2020 at 11:30:16AM +0100, François Gannaz wrote: > Package: claws-mail-litehtml-viewer > Version: 3.17.4-3 > Severity: important > > Dear Maintainer, > > when opening my "junk" IMAP folder, claws-mail crashes every time. > Here is the truncated gdb back trace: > > Thread 1 "claws-mail" received signal SIGSEGV, Segmentation fault. > 0x7675ee76 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 > (gdb) bt > #0 0x7675ee76 in () at /lib/x86_64-linux-gnu/libc.so.6 > #1 0x71d29c53 in lh_widget::set_base_url(char const*) () at > /usr/lib/x86_64-linux-gnu/claws-mail/plugins/litehtml_viewer.so […] > If I uncheck the setting "Preferences > Message View > Text Options > > Render HTML-only messages with plugin if possible", then claws-mail > does not crash anymore. > > I have redacted the offending spam email in order to remove my > professional address from it, please let me know if you need the > unredacted email. Thanks for the report, unfortunately seems it's very common to send spam with bad tags, but fortunately this has been already fixed in upstream git (see the upstream bug above). > Thank you for maintaining claws-email. You're welcome! Best regards, -- Ricardo Mones ~ RTFM - "Read The Manual" (The 'F' is silent). Usually a very good idea. Bjarne Stroustrup signature.asc Description: PGP signature
Bug#949720: sylpheed: diff for NMU version 3.7.0-5.1
On Sat, Jan 25, 2020 at 01:00:16PM +0100, Laurent Bigonville wrote: > Le 25/01/20 à 12:26, Ricardo Mones a écrit : > > On Fri, Jan 24, 2020 at 01:04:08PM +0100, Laurent Bigonville wrote: > > > Le 24/01/20 à 12:13, Ricardo Mones a écrit : > > > > Hi Laurent, > > > > > > > > On Fri, Jan 24, 2020 at 10:50:51AM +0100, Laurent Bigonville wrote: > > > > > Control: tags 949720 + patch > > > > > Control: tags 949720 + pending > > > > > > > > > > > > > > > Dear maintainer, > > > > > > > > > > I've prepared an NMU for sylpheed (versioned as 3.7.0-5.1) and > > > > > uploaded it to DELAYED/3. Please feel free to tell me if I > > > > > should delay it longer. > > > > Thanks for the patch! Given it's not even a RC bug I don't understand > > > > such a hurry, am I missing something? > > > sylpheed is marked as lowNMU I believe > > Indeed, but if you really think lowNMU means you can do NMUs like this > > one I'd suggest you to read again what lowNMU means. > https://wiki.debian.org/LowThresholdNmu describes what it is: > > > > The maintainers and maintainer groups listed below declare that their > > packages (all, or the ones listed specifically below) may be fixed and > > uploaded without delay, at any time, as long as the NMU procedure > > <http://www.debian.org/doc/developers-reference/pkgs.html#nmu> in the > > Debian Developer's Reference is otherwise followed. You don't need to > > contact the maintainers beforehand, and you don't need to use a delayed > > upload queue. If the package maintainer or maintainer group is active, > > it is polite to let them have a stab at fixing the problem first. > > > > Every change should be to fix a reported bug. Changes should not be > > frivolous. For example, don't change from debhelper to cdbs just because > > you prefer it that way; if you really want to make such big changes to > > the package, talk with the maintainer or maintainer group first, and > > maybe offer to adopt the package. > > The NMU procedure describes: > > > Unless you have an excellent reason not to do so, you must then give > > some time to the maintainer to react (for example, by uploading to the > > |DELAYED| queue). Here are some recommended values to use for delays: > > > > * Upload fixing only release-critical bugs older than 7 days, with > > no maintainer activity on the bug for 7 days and no indication > > that a fix is in progress: 0 days > > * Upload fixing only release-critical bugs older than 7 days: 2 days > > * Upload fixing only release-critical and important bugs: 5 days > > * Other NMUs: 10 days > > > Ergo any bugs (including important bugs and "Other NMU") can be uploaded > without delay if the package is marked as LowThresholdNmu > > Well this is at least my understanding. You must be using some more info because given the examples cited in the NMU procedure I fail to conclude that in a package which is actively maintained, an important bug which is just a few _hours_ old can be NMUed to the 3 day queue. > > > > > and I'm not sure about the real consequences of having the 2 libraries > > > loaded at the same time, so I prefer to see this fixed rapidly. > > I don't think that could eat your homework, but I agree it's better to > > have this fixed soon :) > > I've canceled my NMU Thanks, just uploaded the packages. Unfortunately had to leave the town yesterday because a late-notified funeral and could not do it earlier. regards, -- Ricardo Mones ~ Quantity derives from measurement, figures from quantities, comparisons from figures, and victories from comparisons. Sun Tzu signature.asc Description: PGP signature
Bug#949720: sylpheed: diff for NMU version 3.7.0-5.1
On Fri, Jan 24, 2020 at 01:04:08PM +0100, Laurent Bigonville wrote: > Le 24/01/20 à 12:13, Ricardo Mones a écrit : > > Hi Laurent, > > > > On Fri, Jan 24, 2020 at 10:50:51AM +0100, Laurent Bigonville wrote: > > > Control: tags 949720 + patch > > > Control: tags 949720 + pending > > > > > > > > > Dear maintainer, > > > > > > I've prepared an NMU for sylpheed (versioned as 3.7.0-5.1) and > > > uploaded it to DELAYED/3. Please feel free to tell me if I > > > should delay it longer. > > Thanks for the patch! Given it's not even a RC bug I don't understand > > such a hurry, am I missing something? > sylpheed is marked as lowNMU I believe Indeed, but if you really think lowNMU means you can do NMUs like this one I'd suggest you to read again what lowNMU means. > and I'm not sure about the real consequences of having the 2 libraries > loaded at the same time, so I prefer to see this fixed rapidly. I don't think that could eat your homework, but I agree it's better to have this fixed soon :) regards, -- Ricardo Mones ~ Datei nicht gefunden Fehler 404 signature.asc Description: PGP signature
Bug#949720: sylpheed: diff for NMU version 3.7.0-5.1
Hi Laurent, On Fri, Jan 24, 2020 at 10:50:51AM +0100, Laurent Bigonville wrote: > Control: tags 949720 + patch > Control: tags 949720 + pending > > > Dear maintainer, > > I've prepared an NMU for sylpheed (versioned as 3.7.0-5.1) and > uploaded it to DELAYED/3. Please feel free to tell me if I > should delay it longer. Thanks for the patch! Given it's not even a RC bug I don't understand such a hurry, am I missing something? Anyway, I'll try to make an upload during the weekend. best regards, -- Ricardo Mones ~ Absence of evidence is not evidence of absence. Carl Sagan signature.asc Description: PGP signature
Bug#948025: tint: infinite loop after Ctrl+D on level prompt
Package: tint Version: 0.05 Severity: normal Tags: upstream Dear Maintainer, * What led up to the situation? When program is started without arguments it prompts for a starting level and suggests a number between 1 and 9. If you do not enter a valid number the prompt is printed again waiting for a valid input. * What exactly did you do (or not do) that was effective (or ineffective)? I entered Ctrl+D. * What was the outcome of this action? The prompt started to be rinted continuously, without waiting. Fortunately pressing Ctrl+C aborted the program. * What outcome did you expect instead? The prompt to be printed once and waiting for input. -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64)
Bug#944424: cairo-dock-plug-ins: libetpan 1.9.4 uses now pkg-config
Hi, On Sat, Nov 09, 2019 at 09:30:07PM +0100, Ricardo Mones wrote: > I've just uploaded the new version to experimental, so you can test > building with it. > > In a month or so will raise the severity of this bug when uploading to > unstable. Please, let me know if you need more time to solve this. The version of libetpan currently in experimental will be uploaded to unstable on 1st week of 2020, unless somebody objects to. regards, -- Ricardo Mones ~ The world will end in 5 minutes. Please log out.Unknown signature.asc Description: PGP signature
Bug#944903: plasma-discover: ignores user selection and updates everything
Package: plasma-discover Version: 5.14.5.1-1 Severity: normal Dear Maintainer, There was a lot of updates, firefox was listed first on the list. Unchecked firefox. The interface was updated saying 1 package not to be updated. Just pressed upgrade button, it asked me for root password, and then everything, including firefox, was updated. Of course I was expecting that firefox was left without updating. Thanks in advance, -- System Information: Debian Release: 10.2 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages plasma-discover depends on: ii appstream0.12.5-1 ii apt-config-icons 0.12.5-1 ii kio 5.54.1-1 ii libappstreamqt2 0.12.5-1 ii libc62.28-10 ii libkf5attica55.54.0-1 ii libkf5configcore55.54.0-1+deb10u1 ii libkf5configwidgets5 5.54.0-1 ii libkf5coreaddons55.54.0-1 ii libkf5crash5 5.54.0-1 ii libkf5dbusaddons55.54.0-1 ii libkf5i18n5 5.54.0-1 ii libkf5itemmodels55.54.0-1 ii libkf5kiocore5 5.54.1-1 ii libkf5kiowidgets55.54.1-1 ii libkf5newstuffcore5 5.54.0-2 ii libkf5notifications5 5.54.0-1 ii libkf5service-bin5.54.0-1 ii libkf5service5 5.54.0-1 ii libkf5widgetsaddons5 5.54.0-1 ii libkf5xmlgui55.54.0-1 ii libpackagekitqt5-1 1.0.1-1 ii libqt5core5a 5.11.3+dfsg1-1+deb10u1 ii libqt5dbus5 5.11.3+dfsg1-1+deb10u1 ii libqt5gui5 5.11.3+dfsg1-1+deb10u1 ii libqt5network5 5.11.3+dfsg1-1+deb10u1 ii libqt5qml5 5.11.3-4 ii libqt5quick5 5.11.3-4 ii libqt5widgets5 5.11.3+dfsg1-1+deb10u1 ii libqt5xml5 5.11.3+dfsg1-1+deb10u1 ii libstdc++6 8.3.0-6 ii packagekit 1.1.12-5 ii plasma-discover-common 5.14.5.1-1 ii qml-module-org-kde-kcoreaddons 5.54.0-1 ii qml-module-org-kde-kirigami2 5.54.0-1 ii qml-module-org-kde-kquickcontrols5.54.0-1 ii qml-module-org-kde-kquickcontrolsaddons 5.54.0-1 ii qml-module-org-kde-qqc2desktopstyle 5.54.0-1 ii qml-module-qtquick-dialogs 5.11.3-2 Versions of packages plasma-discover recommends: ii apt-config-icons-large 0.12.5-1 ii software-properties-kde 0.96.20.2-2 Versions of packages plasma-discover suggests: pn apt-config-icons-hidpi pn plasma-discover-backend-flatpak -- no debconf information
Bug#944424: cairo-dock-plug-ins: libetpan 1.9.4 uses now pkg-config
Source: cairo-dock-plug-ins Severity: important Tags: upstream Dear Maintainers, The new release of libetpan has switched from the custom libetpan-config script to use a pkg-config file. This means that current configuration tests for detecting libetpan library will fail and the package will FTBFS. I've just uploaded the new version to experimental, so you can test building with it. In a month or so will raise the severity of this bug when uploading to unstable. Please, let me know if you need more time to solve this. best regards, -- Ricardo Mones http://people.debian.org/~mones «You had some happiness once, but your parents moved away, and you had to leave it behind.»
Bug#938735: txt2tags: Python2 removal in sid/bullseye
Source: txt2tags Followup-For: Bug #938735 Hi, Seems somebody has ported this to Python 3: https://github.com/jendrikseipp/txt2tags This could be a better alternative to removal of the package in case current upstream doesn't provide an updated version. HTH, -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#943771: linux-ftpd: Homepage URL fails name resolution
Package: linux-ftpd Severity: minor Dear Maintainer, Trying to open current homepage gives a DNS failure. Seems this one works though: http://ftp.linux.org.uk/pub/linux/Networking/netkit/ Thanks in advance and best regards, -- System Information: Debian Release: 10.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_WARN Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#943469: nudoku: new upstream version
Package: nudoku Severity: wishlist Dear Maintainer, Seems a new upstream version, namely 2.0.0, is available since some time ago¹. Would be nice to have it packaged for Debian ;-) Thanks in advance and best regards, ¹ https://tracker.debian.org/pkg/nudoku -- Ricardo Mones ~ Absence of evidence is not evidence of absence. Carl Sagan
Bug#943308: RM: claws-mail-python-plugin -- ROM; Is blocking migration of claws-mail/3.17.4-2 to testing
Package: ftp.debian.org Severity: normal Hi ftpmasters! I'd like claws-mail-python-plugin to be removed from sid because it's apparently blocking the migration of latest upload (which has this plugin removed) to testing. Thanks in advance and best regards, -- Ricardo Mones http://people.debian.org/~mones «Don't relax! It's only your tension that's holding you together.»
Bug#942057: claws-mail: shows wrong sha256 certificate fingerprint
control: tags -1 confirmed pending fixed-upstream Hi, On Wed, Oct 09, 2019 at 06:44:28PM +0200, koniu wrote: > Package: claws-mail > Version: 3.17.3-2 > Severity: normal > > Hi, > > Just a headsup- current claws in stable/testing (3.17.3-2) shows wrong sha256 > certificate fingerprints. > > This was fixed in 3.17.4, in sid since August. Is there a block to > upgrade in testing/stable? No, there isn't, just matter of time. Thanks for reporting anyway. regards, -- Ricardo Mones ~ I'm sorry, my responses are limited. You must ask the right questions. A hologram signature.asc Description: PGP signature
Bug#940536: dhex: hangs on keyboard config screen
Package: dhex Version: 0.69-1 Severity: important Hi, As described the program hangs on what it looks like some keyboard configuration screen, which only can be exited by Ctrl-C. I tried also pressing ESC as advertised, but is ignored: Please press the following keys (Press ESC if your keyboard does not have them) Config file:/home/mones/.dhexrc KEYESC: The standard cancel key Nothing else can be done with it, so this is completely useless. Looking also at #889956 makes me wonder if this stuff wouldn't be better removed from the archive. regards, -- System Information: Debian Release: 10.1 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-6-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dhex depends on: ii libc62.28-10 ii libncurses6 6.1+20181013-2+deb10u1 ii libtinfo66.1+20181013-2+deb10u1 dhex recommends no packages. dhex suggests no packages. -- no debconf information
Bug#939834: claws-mail: Does not respond to `can_change_accels`
control: tags -1 moreinfo
Hi Paul,
On Mon, Sep 09, 2019 at 12:32:31PM +0100, Paul "LeoNerd" Evans wrote:
> Package: claws-mail
> Version: 3.17.4-1
> Severity: normal
>
> GTK applications ought to allow users to customise the keyboard
> shortcuts ("accelerators") if enabled globally, by users highlighting a
> menu option and pressing a new key.
>
> I have it enabled globally:
>
> $ gconftool --get /desktop/gnome/interface/can_change_accels
> true
>
> but yet doing this has no effect in claws-mail.
Claws Mail it's not a GNOME application, no surprise here.
> Additionally I've even tried manually editing `.claws-mail/menurc` but
> the file seems to be ignored and rewritten on startup.
Because you don't have customisable keyboard shortcuts enabled, try
Configuration → Preferences → Other → Miscellaneous → Keyboard
shortchuts frame → Enable customisable keyboard shortcuts checkbox.
BTW, you can also edit menurc with clawsker instead of manually :)
> It may be significant that I am running xfce rather than gnome.
Should work on any desktop enviroment, even on non GTK+-based ones.
regards,
--
Ricardo Mones
~
I'm sorry, my responses are limited. You must ask the right
questions. A hologram
signature.asc
Description: PGP signature
Bug#927904: claws-mail: filtering option does not work as excepted
control: tags -1 moreinfo Hi Pierre, On Wed, Apr 24, 2019 at 10:23:55PM +0200, Pierre wrote: > Package: claws-mail > Version: 3.17.1-1~bpo9+1 > Severity: normal > > Dear Maintainer, > I am using Claws-Mail with a POP account with two differents > computers, with a setup in order to have sent mail on both computers. > The first computer runs Debian, the second OpenIndiana (with > Claws-Mail 3.16). > > When I am sending a mail, Claws-Mail automatically adds my email > address in the Bcc field, Thank to the option given in "Account > preferences" -> "Compose". > > Then, I use two filters (1 and 2) to move automatically these sent > mails : > Condition 1: > header "X-Mailer" matchcase "linux" & from matchcase "X@X.X" > Action 1: > mark_as_read move "#mh/Mail-XXX/Trash" > > Condition 2: > header "X-Mailer" matchcase "solaris" & from matchcase "X@X.X" > Action 2: > move "#mh/Mail-XXX/sent" > > For the OpenIndiana computer, "solaris" and "linux" are just reversed. > > The Debian computer is ignoring these rules, and the OpenIndiana > machine is running fine. For example, if I send a mail from this > address to another mail address, the Debian machine will ignore the > filtering action and the mail will stay in the inbox folder. > > I tried to change the configuration files and mails, the Debian > computer still have this issue, but not the OpenIndiana computer. > > Could you help me please ? Is this already solved? Have you enabled filtering rules¹ loggging and spotted what's different between both systems? regards, ¹ As indicated in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927904#10 -- Ricardo Mones ~ Never send a human to do a machine's job. Agent Smith signature.asc Description: PGP signature
Bug#934696: eb: Broken homepage link (404)
Source: eb Severity: minor Hi Tatsuya, Seems the homepage link of your eb package is now broken and the 404 page of the main site is now displayed. I've checked and the user page¹ where it was hosted is also missing, so it's very likely the user is not working for the owner of the main site anymore. Perhaps you can contact him/her and see if there's a new homepage. Thanks in advance and best regards, ¹ http://www.sra.co.jp/people/m-kasahr/ -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
Bug#932563: sylpheed: Don't build against flex-old
control: tags -1 pending - patch On Sat, Jul 20, 2019 at 07:38:25PM +0300, Tommi Vainikainen wrote: > Source: sylpheed > Severity: normal > Tags: patch > > Hi, as a maintainer of flex-old package I'm considering requesting > removing it as obsolete and unmaintained version of flex. sylpheed > Build-Depends on flex-old as alternative to current flex. Please build > the package only against current flex by removing references to > flex-old package such as changed in the following patch. Thanks, fixed in git. -- Ricardo Mones ~ RTFM - "Read The Manual" (The 'F' is silent). Usually a very good idea. Bjarne Stroustrup signature.asc Description: PGP signature
Bug#932511: claws-mail: Don't build against flex-old
control: tags -1 pending - patch On Sat, Jul 20, 2019 at 12:02:32PM +0300, Tommi Vainikainen wrote: > Source: claws-mail > Severity: normal > Tags: patch > > Hi, as a maintainer of flex-old package I'm considering requesting > removing it as obsolete and unmaintained version of flex. The > claws-mail Build-Depends on flex-old optionally. Please build the > package only against current flex by removing references to flex-old > package such as changed in the following patch. Thanks, fixed in git. -- Ricardo Mones ~ Never send a human to do a machine's job. Agent Smith signature.asc Description: PGP signature
Bug#932041: liquidprompt: loses color when average load greater than 100%
Package: liquidprompt Version: 1.11-3 Severity: normal Hi, As subject says seems liquidprompt does not keep "warning" color when average load goes beyond 100%, attached screenshot. Upstream screenshot¹ shows different colors, so not sure it's a Debian problem, an upstream regression or something else :) thanks in advance and best regards, ¹ https://github.com/nojhan/liquidprompt -- System Information: Debian Release: 10.0 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-5-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled liquidprompt depends on no packages. liquidprompt recommends no packages. Versions of packages liquidprompt suggests: ii acpi1.7-1.1 ii lm-sensors 1:3.5.0-3 -- no debconf information
Bug#812609: tracker.debian.org: wrong versioned links for security versions
On Mon, Jun 10, 2019 at 08:09:23AM -0300, zaza wrote: > On Fri, 26 Apr 2019 16:17:15 +0200 Salman Mohammadi wrote: > > On Mon, 25 Jan 2016 16:43:38 +0100 Ricardo Mones wrote: > > > > > > The links to .dsc file wich appear on versioned links panel for security > > > versions are using httpredir.d.o, which always gives 40x errors for those > > > package versions. Example: https://tracker.debian.org/pkg/claws-mail > > > (3.8.1-2+deb7u1 and 3.11.1-3+deb8u1 dsc links) > > > > > > > Dear Recardo, > > > > I couldn't reproduce this bug in the package that you have mentioned. > > > Neither do I. FWIW the link labeled 'old-sec' in today's claws-mail tracker page still fails. Not with a 404 though, it just says: ,--- | Error | | two or more packages specified (claws-mail updates) `--- regards, -- Ricardo Mones ~ bash: ./signature: No such file or directory /bin/bash signature.asc Description: PGP signature
Bug#928548: unblock: libetpan/1.9.3-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package libetpan
The upload just adds an upstream patch to fix serious bug #927709.
Full debdiff attached, thanks in advance!
unblock libetpan/1.9.3-2
-- System Information:
Debian Release: 9.8
APT prefers stable-debug
APT policy: (500, 'stable-debug'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores)
Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
diff -Nru libetpan-1.9.3/debian/changelog libetpan-1.9.3/debian/changelog
--- libetpan-1.9.3/debian/changelog 2019-01-26 20:49:11.0 +0100
+++ libetpan-1.9.3/debian/changelog 2019-05-06 23:27:54.0 +0200
@@ -1,3 +1,11 @@
+libetpan (1.9.3-2) unstable; urgency=high
+
+ * debian/patches/90_fix_tls_timeout.diff
+ - Add upstream patch to fix TLS timeout (Closes: #927709)
+ * Raised changelog urgency because of serious bug
+
+ -- Ricardo Mones Mon, 06 May 2019 23:27:54 +0200
+
libetpan (1.9.3-1) unstable; urgency=medium
* New upstream version 1.9.3
diff -Nru libetpan-1.9.3/debian/patches/90_fix_tls_timeout.diff
libetpan-1.9.3/debian/patches/90_fix_tls_timeout.diff
--- libetpan-1.9.3/debian/patches/90_fix_tls_timeout.diff 1970-01-01
01:00:00.0 +0100
+++ libetpan-1.9.3/debian/patches/90_fix_tls_timeout.diff 2019-05-06
23:27:54.0 +0200
@@ -0,0 +1,19 @@
+Origin:
https://github.com/dinhviethoa/libetpan/commit/4aee22436809af67f23170fe15106b91ff2971e6
+Subject: Fix TLS timeouts with recent versions of GnuTLS
+ gnutls_handshake_set_timeout takes a timeout value in ms, but we were
+ providing a value in seconds. This means that on new-enough platforms
+ that use GnuTLS (e.g., Debian Buster), we would accidentally configure
+ a timeout 1,000 times shorter than requested.
+Bug-Debian: https://bugs.debian.org/927709
+
+--- a/src/data-types/mailstream_ssl.c
b/src/data-types/mailstream_ssl.c
+@@ -636,7 +636,7 @@ static struct mailstream_ssl_data * ssl_data_new(int fd,
time_t timeout,
+ timeout_value = mailstream_network_delay.tv_sec * 1000 +
mailstream_network_delay.tv_usec / 1000;
+ }
+ else {
+- timeout_value = timeout;
++ timeout_value = timeout * 1000;
+ }
+ #if GNUTLS_VERSION_NUMBER >= 0x030100
+ gnutls_handshake_set_timeout(session, timeout_value);
diff -Nru libetpan-1.9.3/debian/patches/series
libetpan-1.9.3/debian/patches/series
--- libetpan-1.9.3/debian/patches/series2019-01-26 20:49:11.0
+0100
+++ libetpan-1.9.3/debian/patches/series2019-05-06 23:27:54.0
+0200
@@ -1,3 +1,4 @@
# 10_unnecessary_linkage.diff
11_use_openjade.diff
12_add_dummy_readme.diff
+90_fix_tls_timeout.diff
Bug#927709: libetpan: GnuTLS timeouts are 1000 times shorter than configured
On Sun, Apr 21, 2019 at 09:10:26PM +0100, Chris Boot wrote: > Control: severity -1 serious > Control: tags -1 patch > > Dear Maintainer, > > I think this bug should be RC given that it appears to make some > important (to some people at least) software potentially unusable on > Buster. Please feel free to downgrade if you particularly disagree, though. Isn't that basically the definition of 'important' severity level? :-) Anyway, haven't looked at the bug or the fix, just arriving from a short trip, so if you feel serious is more appropriate, so be it. thanks, -- Ricardo Mones ~ I'm sorry, my responses are limited. You must ask the right questions. A hologram signature.asc Description: PGP signature
Bug#923980: claws-mail-gdata-plugin: gdata plugin crashes after update to 3.17.3-1
control: reopen -1 control: notfixed -1 claws-mail/3.17.3-2 control: tags -1 help Hi Christian, On Wed, Apr 10, 2019 at 06:31:49PM +0200, Christian Beier wrote: > > Hi Ricardo, > > I just upgraded to 3.17.3-2, but unfortunately still get the segfault: […] > I checked with 3.17.3-2's source package and there is a de.gmo file in > there which still contains the %s. Might this be the reason? Yes, the added patch fixes the source file, but does not fix the binaries already there, which come from upstream. I hadn't time to do much tests, just tried to remove the gmo files from master and rebuild, but the result is still the same. The only idea left is to repackage upstream tarball, but since that's an idea I don't like much I'm Cc-ing the release list for advice on how to deal with this (thanks in advance! :) best regards, -- Ricardo Mones ~ Absence of evidence is not evidence of absence. Carl Sagan signature.asc Description: PGP signature
Bug#926705: claws-mail: CVE-2019-10735
control: forwarded -1 https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4159 control: tags -1 confirmed upstream On Tue, Apr 09, 2019 at 01:24:21PM +0200, Sylvain Beucler wrote: > Package: claws-mail > Version: 3.17.3-2 > X-Debbugs-CC: t...@security.debian.org > Severity: important > Tags: security > > Hi, > > The following vulnerability was published for claws-mail. > > CVE-2019-10735[0]: > | In Claws Mail 3.14.1, an attacker in possession of S/MIME or PGP > | encrypted emails can wrap them as sub-parts within a crafted multipart > | email. The encrypted part(s) can further be hidden using HTML/CSS or > | ASCII newline characters. This modified multipart email can be re-sent > | by the attacker to the intended receiver. If the receiver replies to > | this (benign looking) email, they unknowingly leak the plaintext of > | the encrypted message part(s) back to the attacker. > > > If you fix the vulnerability please also make sure to include the > CVE (Common Vulnerabilities & Exposures) id in your changelog entry. > > For further information see: > > [0] https://security-tracker.debian.org/tracker/CVE-2019-10735 > https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-10735 > https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4159 > > Cheers! > Sylvain Alright, thanks. -- Ricardo Mones ~ Physics is like sex: sure, it may give some practical results, but that's not why we do it.Richard Feynman signature.asc Description: PGP signature
Bug#926357: unblock: claws-mail/3.17.3-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package claws-mail Just added a patch from upstream to fix a segfault when using gdata plugin with German locales, caused by an unnecessary %s in a msgstr. Debdiff attached, thanks in advance! unblock claws-mail/3.17.3-2 -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE= (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled diff -Nru claws-mail-3.17.3/debian/changelog claws-mail-3.17.3/debian/changelog --- claws-mail-3.17.3/debian/changelog 2018-12-29 18:10:15.0 +0100 +++ claws-mail-3.17.3/debian/changelog 2019-04-03 20:11:50.0 +0200 @@ -1,3 +1,10 @@ +claws-mail (3.17.3-2) unstable; urgency=medium + + * debian/patches/90fix_segfault_gdata_german.patch + - Add patch fixing segfault in gdata plugin (Closes: #923980) + + -- Ricardo Mones Wed, 03 Apr 2019 20:11:50 +0200 + claws-mail (3.17.3-1) unstable; urgency=medium * New upstream release diff -Nru claws-mail-3.17.3/debian/patches/90fix_segfault_gdata_german.patch claws-mail-3.17.3/debian/patches/90fix_segfault_gdata_german.patch --- claws-mail-3.17.3/debian/patches/90fix_segfault_gdata_german.patch 1970-01-01 01:00:00.0 +0100 +++ claws-mail-3.17.3/debian/patches/90fix_segfault_gdata_german.patch 2019-04-03 20:11:50.0 +0200 @@ -0,0 +1,17 @@ +Description: Fix segfault using gdata plugin in German locales +Origin: https://git.claws-mail.org/?p=claws.git;a=commit;h=0ffa910327b3476aafec74013d69af98dd9fb5e2 +Bug-Debian: https://bugs.debian.org/923980 + +diff --git a/po/de.po b/po/de.po +index 979095871..7332704c9 100644 +--- a/po/de.po b/po/de.po +@@ -10502,7 +10502,7 @@ msgstr "GData-Plugin: Fehler beim Erneuern der Autorisierung: %s\n" + + #: src/plugins/gdata/cm_gdata_contacts.c:535 + msgid "GData plugin: Authorization refresh successful\n" +-msgstr "GData-Plugin: Erneuern der Autorisierung erfolgreich: %s\n" ++msgstr "GData-Plugin: Erneuern der Autorisierung erfolgreich\n" + + #: src/plugins/gdata/cm_gdata_contacts.c:595 + #, c-format diff -Nru claws-mail-3.17.3/debian/patches/series claws-mail-3.17.3/debian/patches/series --- claws-mail-3.17.3/debian/patches/series 2018-12-29 18:10:15.0 +0100 +++ claws-mail-3.17.3/debian/patches/series 2019-04-03 20:11:50.0 +0200 @@ -1,2 +1,3 @@ 11mark_trashed_as_read.patch 12fix_manpage_header.patch +90fix_segfault_gdata_german.patch
Bug#926147: ERROR: Connection to mail.myhost.lt:995 failed.
control: tags -1 moreinfo Hi Giedrius, On Mon, Apr 01, 2019 at 09:48:10AM +0300, Giedrius wrote: > Package: sylpheed > Version: 3.7.0-4 > Severity: normal > > After upgrading from strech to buster doesn't send and > does not receive emails. Written by ERROR: Connection to mail.am.lt:995 > failed. > I can't find anything that might be bad in the settings. With Debian strech, > the same settings work well. > Terminal writes: > .comments: unlink: Folders > > (sylpheed: 12851): LibSylph-WARNING **: 09: 39: 06.590: SSL_connect () failed > with error 1, ret = -1 (error: 1425F102: SSL routines: > ssl_choose_client_version: unsupported protocol) > > > (sylpheed: 12851): LibSylph-WARNING **: 09: 39: 06.590: can't initialize SSL. > > (sylpheed: 12851): LibSylph-WARNING **: 09: 39: 06.590: [09:39:06] Couldn't > connect. > > gmail.com account is working well. > > Maybe you can advise what's wrong here. The server probably doesn't support TLS v1.2 protocol, which has been added as minimum requirement in buster. You can workaround this by downgrading MinProtocol and/or CipherString in the system_default_sect section of your /etc/ssl/openssl.cnf file, and see if it works, but: ! Notice that such changes will make *all* your SSL connections less ! secure. Upgrading the server to support TLS v1.2 is the right fix. regards, -- Ricardo Mones ~ Quantity derives from measurement, figures from quantities, comparisons from figures, and victories from comparisons. Sun Tzu signature.asc Description: PGP signature
Bug#925446: arpalert: Please fix homepage
Package: arpalert Severity: minor Dear Maintainer, Seems homepage of arpalert seems to have moved to: http://www.arpalert.org/arpalert.html while the root site remains now as author's homepage. This also affects watch file, because src dir is forbidden and versions have to be parsed from download section in homepage :-( thanks in advance, -- System Information: Debian Release: 9.8 APT prefers stable-debug APT policy: (500, 'stable-debug'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-8-amd64 (SMP w/4 CPU cores) Locale: LANG=es_ES.UTF-8, LC_CTYPE=es_ES.UTF-8 (charmap=UTF-8), LANGUAGE=es_ES.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages arpalert depends on: ii adduser 3.115 ii ieee-data 20160613.1 ii libc6 2.24-11+deb9u4 ii libpcap0.8 1.8.1-3 arpalert recommends no packages. arpalert suggests no packages.
Bug#923980: claws-mail-gdata-plugin: gdata plugin crashes after update to 3.17.3-1
control: severity -1 important control: tags -1 confirmed fixed-upstream Hi Christian, On Thu, 07 Mar 2019 22:10:53 +0100 Christian Beier wrote: > Package: claws-mail-gdata-plugin > Version: 3.17.3-1 > Severity: normal > > Dear Maintainer, > > I recently upgraded from stretch to buster, now claws-mail with gdata > plugin enabled segfaults. > > Runs fine without gdata plugin enabled. > > Also runs fine with `LANG=C claws-mail` > > It seems the locale makes a difference, please see attached backtrace for > the default de_DE.UTF-8 Thanks for reporting! I've fixed this upstream¹, but hopefully will provide an updated package soon. best regards, ¹ https://git.claws-mail.org/?p=claws.git;a=commitdiff;h=0ffa910327b3476aafec74013d69af98dd9fb5e2 -- Ricardo Mones http://people.debian.org/~mones «Conscious is when you are aware of something and conscience is when you wish you weren't.» pgpSjRWPmOD9J.pgp Description: Firma digital OpenPGP
Bug#921945: sylpheed: Sylpheed uses the wrong application for opening pdf files
control: forwarded -1 https://sylpheed.sraoss.jp/redmine/issues/312 control: severity -1 wishlist Hi Jean-Marc, On Sun, Feb 10, 2019 at 01:57:28PM +0100, Jean-Marc wrote: > Package: sylpheed > Version: 3.7.0-4 > Severity: normal > > Dear Maintainer, > > > Sylpheed does not take into account the XDG default application the > desktop environment should use for opening files of a specific > MIME/Filetype. > > Example: . when I tried to open a PDF file, Sylpheed uses gimp to open > the file. > > Gimp is the first application in the > /usr/share/applications/mimeinfo.cache entry defining which > application(s) can read/open/associate with pdf files. > > $ grep application/pdf /usr/share/applications/mimeinfo.cache > application/pdf=gimp.desktop;inkscape.desktop;org.gnome.Evince.desktop;libreoffice-draw.desktop; > > It should use my desktop's default application from Debian Gnome > default spec in /usr/share/applications/gnome-mimeapps.list to open > PDF files. AFAIK Sylpheed is not a GNOME application, is just a GTK+2 application. Anyway I'm forwarding this upstream, just in case they may consider worth to implement it for a better user experience. thanks for reporting, -- Ricardo Mones ~ Never send a human to do a machine's job. Agent Smith signature.asc Description: PGP signature
Bug#869297: O: wordwarvi -- retro-styled side-scrolling shoot'em up arcade game
control: retitle -1 ITA: wordwarvi -- retro-styled side-scrolling shoot'em up arcade game control: owner -1 ! On Sat, 22 Jul 2017 14:56:17 +0200 Tobias Frost wrote: > Package: wnpp > > The current maintainer of wordwarvi, Joe Nahmias , > is apparently not active anymore. Therefore, I orphan this package now. May the force be with me, I'll move this to Games Team planet… -- Ricardo Mones http://people.debian.org/~mones «Paranoia doesn't mean the whole world isn't out to get you.» pgplPWt87vW7_.pgp Description: Firma digital OpenPGP
Bug#840874: O: tint -- TINT Is Not Tetris(tm) ...at least the name isn't
control: retitle -1 ITA: tint -- TINT Is Not Tetris(tm) ...at least the name isn't control: owner -1 ! On Sat, 15 Oct 2016 19:23:49 +0200 Tobias Frost wrote: > Package: wnpp > Severity: normal > > The current maintainer of tint, Mario Lang , > has retired. Therefore, I orphan this package now. Hopefully I'll maintain this package within the Games Team. regards, -- Ricardo Mones http://people.debian.org/~mones «All generalisations are dangerous, including this one.» pgpFCpMrzc8aK.pgp Description: Firma digital OpenPGP
Bug#717648: claws-mail: False positive filtering.
Control: tags -1 moreinfo Hi Sthu, First, sorry for the very very late response, this has been neglected for long time. On Tue, 23 Jul 2013 14:39:13 +0700 Sthu wrote: > Package: claws-mail > Version: 3.9.2-1 > Severity: normal > > Dear Maintainer, > > > I have huge number of filters on subjects of letters: there a lot of > > subject match "qweqwe" | subject match "asdasd" | ... > > And i see several false positives: i use caseless, non-regular expression > filtering therefore the words in the filtered out subjects should be as it > is specified in the filters - i.e. no modification of symbols while > filtering -- but it is bot the case: letters are filtered out that contain > not those, specified in the filters. Is this still reproducible with current Claws Mail version? > Please pass along my message to developers. Thank you. I'd like to be able to reproduce it first before forwarding. Thanks in advance, -- Ricardo Mones http://people.debian.org/~mones «Reading is thinking with someone else's head instead of one's own.» pgpZxdxfOfm5Z.pgp Description: Firma digital OpenPGP
Bug#906807: Can't send reply to encrypted message
control: tags -1 moreinfo Hi Jeffrey, On Tue, Aug 21, 2018 at 11:53:20AM +0200, Jeffrey Ratcliffe wrote: > Package: claws-mail > Version: 3.16.0-2 > Severity: normal > > When replying to an encrypted message, on hitting "send", I get the error: > "Could not queue message for sending. Couldn't get recipient encryption key" > > However, Privacy System=None is selected in Options. > > On selecting a different privacy system, I can send the message. I think this is fixed in the release in testing, so, can you check if 3.17.2-1 behaves better in this situation? Thanks in advance and happy holidays, -- Ricardo Mones ~ I'm sorry, my responses are limited. You must ask the right questions. A hologram signature.asc Description: PGP signature
Bug#912872: clawsker: Depends on libgtk2-perl, that won't be part of Bullseye
control: forwarded -1 https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4117 control: tags -1 upstream Hi, On Sun, Nov 04, 2018 at 06:37:46PM +0100, intrig...@debian.org wrote: > Source: clawsker > Severity: normal > User: debian-p...@lists.debian.org > Usertags: gtk2-removal > > Hi! > > This package depends on libgtk2-perl, that I intend to remove > from testing soon after the Buster release, and then from sid at > some later point during the Bullseye development cycle: > >https://bugs.debian.org/912860 > > Please get in touch with the upstream project and suggest they > port this application to libgtk3-perl. I've personally ported > a couple Perl GTK+ apps from 2.x to 3.x and it's rather > straightforward. Upstream for the GTK+ 3 and GObject > Introspection Perl bindings is responsive and happy to add > missing bits to the bindings. Can we have pointers to these migrations patches/commits/repos? I think having working examples can help upstream here. > I see that upstream is active so I expect this port should be totally > doable in this timeframe. Don't understand what do you want to mean here. Porting it to C would also be doable, and probably more future-proof, since the C library is probably the last piece to be removed. What's the expected removal date for the libgtk3-perl bindings? regards, -- Ricardo Mones ~ Absence of evidence is not evidence of absence. Carl Sagan signature.asc Description: PGP signature
Bug#874024: the attachment
Hi, On Sat, Sep 02, 2017 at 09:20:50AM +0200, c.bu...@posteo.jp wrote: > Here is the file causing the problem in the parser A new version of libytnef has been uploaded to unstable¹. Can you try upgrading that library and checking if this is completely fixed? Thanks in advance, ¹ https://tracker.debian.org/news/997146/accepted-libytnef-193-1-source-amd64-into-unstable/ -- Ricardo Mones ~ You have the capacity to learn from mistakes. You'll learn a lot today. /usr/games/fortune signature.asc Description: PGP signature
