Bug#1074005: newsboat: Please update to 2.35
Hi Martin, Updating newsboat is currently blocked on 2.36 releasing due to https://github.com/newsboat/newsboat/issues/2748 Cheers, Nikos On Fri, 21 Jun 2024, at 17:23, Martin Dosch wrote: > Package: newsboat > Version: 2.32-3 > Severity: wishlist > > Dear Maintainer, > > please update to the newest upstream version 2.35. Currently newsboat is > not in trixie and maybe we are lucky and the build issues will be also > resolved when updating. > > Best regards, > Martin > > -- System Information: > Debian Release: trixie/sid > APT prefers testing > APT policy: (900, 'testing'), (600, 'unstable'), (500, > 'unstable-debug'), (500, 'testing-debug'), (500, 'experimental'), (1, > 'experimental-debug') > Architecture: amd64 (x86_64) > Foreign Architectures: i386 > > Kernel: Linux 6.8.12-amd64 (SMP w/8 CPU threads; PREEMPT) > Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.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 newsboat depends on: > ii libc6 2.38-13 > ii libcurl3t64-gnutls [libcurl3-gnutls] 8.8.0-1 > ii libgcc-s1 14.1.0-2 > ii libjson-c50.17-1+b1 > ii libncursesw6 6.5-2 > ii libsqlite3-0 3.46.0-1 > ii libstdc++614.1.0-2 > ii libstfl0 0.22-3+b8 > ii libtinfo6 6.5-2 > ii libxml2 2.12.7+dfsg-3 > > Versions of packages newsboat recommends: > ii sensible-utils 0.0.23 > > newsboat suggests no packages. > > -- no debconf information > > Attachments: > * signature.asc
Bug#1070170: Generate and include amalgamated header file
Source: catch2 Version: 2.13.10-1 Severity: wishlist X-Debbugs-Cc: ni...@tsipinakis.com Dear Maintainer, I've been depending on the catch2 library package for newsboat which by default vendors the catch library. To be compatible with the Debian policy I have overridden this so that the packaged version is used instead. However with version 3 now there are separate header files for each function and since upstream is relying on the single header/amalgamated version it is not easy to patch to include all the required functionalities. It'd be great to also generate and include the amalgamated header file (generation script can be found here[1]) in order to ease the version 3 transition for amalgamated header users. [1] https://github.com/catchorg/Catch2/blob/fa5a53df17303339eff8fda5cae0b601af207085/tools/scripts/generateAmalgamatedFiles.py Cheers, Nikos
Bug#1069378: picom: FTBFS on arm64: cc: error: unrecognized command-line option '-Wunknown-warning-option'
block -1 by 1069408 thanks Hi, The title of this bug is not a compilation error, it's a feature test. This is actually failing because of 1069408. >> Pkg-config error with 'xcb-present': Could not generate cflags for >> xcb-present: >> Package xcb-dri3 was not found in the pkg-config search path. >> Perhaps you should add the directory containing `xcb-dri3.pc' >> to the PKG_CONFIG_PATH environment variable >> Package 'xcb-dri3', required by 'xcb-present', not found >> >> Dependency lookup for xcb-present with method 'pkgconfig' failed: Could not >> generate cflags for xcb-present: >> Package xcb-dri3 was not found in the pkg-config search path. >> Perhaps you should add the directory containing `xcb-dri3.pc' >> to the PKG_CONFIG_PATH environment variable >> Package 'xcb-dri3', required by 'xcb-present', not found >> >> CMake binary for host machine is cached as not found >> Dependency lookup for xcb-present with method 'cmake' failed: CMake binary >> for machine host machine not found. Giving up. >> Run-time dependency xcb-present found: NO >> >> ../src/meson.build:31:15: ERROR: Dependency lookup for xcb-present with >> method 'pkgconfig' failed: Could not generate cflags for xcb-present: >> Package xcb-dri3 was not found in the pkg-config search path. >> Perhaps you should add the directory containing `xcb-dri3.pc' >> to the PKG_CONFIG_PATH environment variable >> Package 'xcb-dri3', required by 'xcb-present', not found Cheers, Nikos
Bug#1069794: ITP: openbao -- Manage, store and distribute sensitive data.
Package: wnpp Severity: wishlist Owner: Nikos Tsipinakis X-Debbugs-Cc: debian-de...@lists.debian.org, ni...@tsipinakis.com * Package name: openbao Version : v2.0.0-alpha20240329 Upstream Contact: OpenBao Mailing List * URL : https://openbao.org/ * License : MPL-2.0 Programming Lang: Go Description : Manage, store and distribute sensitive data. Fork of Hashicorp Vault after it was relicensed to a non-free license. I intend to give it a shot to package it in the next few weeks in coordination (and hopefully with the guidance of) the Go team.
Bug#1030114: picom: new upstream release
Hi Lev, This has been fixed for a while. Cheers, Nikos
Bug#1038745: dunst: Please package new upstream release 1.9.2
Hi Boyuan, I see you've made a few NM uploads to dunst already, as well as pre-packaged 1.9.2 in salsa, thanks a lot! :) I've now made this a maintainer upload and uploaded 1.9.2. Cheers, Nikos
Bug#1004259: newboat - upcoming rust-rand update.
Hi, On Sun, 23 Jan 2022, at 18:40, Peter Michael Green wrote: > A debdiff is attatched, do you want to handle the upload after > rand is updated in unstable or would you like me to NMU it? I have no preference, since you have the debdiff feel free to NMU it if you're doing a mass-upload already. > rand 0.8 and sufficient related packages to build newsboat > have been uploaded to experimental if you want to test things > in advance of the update in unstable. Thanks! I'll take a look. -- Best Regards, Nikos Tsipinakis
Bug#1000362: newsboat: new usptream version available (2.25)
Hi, Newsboat now requires the rust-cxx crate , which is currently in NEW. (or components of it) It will probably take a while to get it updated. Regards, Nikos On Mon, 22 Nov 2021, at 06:23, Salvatore Bonaccorso wrote: > Source: newsboat > Version: 2.21-1 > Severity: wishlist > X-Debbugs-Cc: car...@debian.org > > Hi > > there is a new upstream version available for newsboat (2.25 at time > of writing). > > https://github.com/newsboat/newsboat/blob/master/CHANGELOG.md#225---2021-09-20 > > Possible to package the new version for unstable? > > Regards, > Salvatore -- Best Regards, Nikos Tsipinakis
Bug#972144: newsboat: segmentation fault at startup
On 15/10, Julien Rabier wrote: > I've compiled newsboat manually from source (commit: > 43a6084c78a1b5f745d3fda219e3dbb43fcb0d1f) and the issue doesn't occur > anymore. > > I think this bug report might be closed by upgrading newsboat in Debian > to 2.21 released 25 days ago. Hi, I've uploaded 2.21 to unstable, please test it when you get the chance to ensure this is indeed fixed and not something else. -- Best Regards, Nikos Tsipinakis
Bug#970858: RFS: dunst/1.5.0-1 -- dmenu-ish notification-daemon
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dunst": * Package name: dunst Version : 1.5.0-1 Upstream Author : Nikos Tsipinakis * URL : https://dunst-project.org/ * License : BSD-3-clause, ISC * Vcs : https://salsa.debian.org/debian/dunst Section : x11 It builds those binary packages: dunst - dmenu-ish notification-daemon To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dunst/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dunst/dunst_1.5.0-1.dsc Changes since the last upload: dunst (1.5.0-1) unstable; urgency=medium . * New upstream version 1.5.0 * d/control: Bump debhelper compat to 13 (no changes) * d/control: Bump standards version to 4.5.0 (no changes) * d/copyright: Update copyright years * d/patches: Refresh patches * d/patches: Fix typo in dunstify error message * d/control: Specify Rules-Requires-Root: no * d/copyright: Add upstream contact info Note: I'm a DM but don't currently have upload rights for this package -- Best Regards, Nikos Tsipinakis
Bug#970859: RFS: picom/8.1-1 -- lightweight compositor for X11
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "picom": * Package name: picom Version : 8.1-1 Upstream Author : Yuxuan Shui * URL : https://github.com/yshui/picom * License : Expat, MPL-2.0, Expat and MPL-2.0 * Vcs : https://salsa.debian.org/nikos/picom Section : x11 It builds those binary packages: picom - lightweight compositor for X11 To access further information about this package, please visit the following URL: https://mentors.debian.net/package/picom/ Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/p/picom/picom_8.1-1.dsc Changes since the last upload: picom (8.1-1) unstable; urgency=medium . * New upstream version 8.1 Note: I'm a DM but don't currently have upload rights for this package -- Best Regards, Nikos Tsipinakis
Bug#966088: mailinglist debian-r...@lists.debian.org
I also support this request. Due to the noise I never look at the messages on pkg-rust-maintainers unless I'm looking for the status of a specific package, so all human messages are lost. -- Best Regards, Nikos Tsipinakis
Bug#963236: newsboat: Failure when receiving data from the peer
On 21/06, Dino Conte wrote: > From another program (Quiterss, RSSOwl etc.) this works without problems, also > the addresses can be pinged. If I install Newsboat from the Snap-Store for > testing purposes, fetching the feeds also works with Newsboat. Looks like the server might be buggy, curl fails as well: $ curl -L http://www.presseportal.de/rss/dienststelle_58451.rss2 curl: (35) error:1414D172:SSL routines:tls12_check_peer_sigalg:wrong signature type I found the following leads in regards to this error message[1][2] [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934453 [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912759
Bug#961432: RFP: picom -- lightweight compositor for X11
On 31/05, Lev Lamberov wrote: > Please, finalize your work, add tags and ping me. I'll upload it to the > Debian archive. Merged, tagged, and pushed. Should ready to be uploaded now. - Nikos
Bug#961432: RFP: picom -- lightweight compositor for X11
On 31/05, Lev Lamberov wrote: > Yep, but as I understand they are in situation where some distributions > picked their fork at the times it was not renamed to picom. Now this > causes troubles. So the rename and migration plan. Since in Debian we > are starting from scratch, I don't think we need these hacks. Anyway, > migrating from compton to picom will require manually installing a new > package, so users are already know that they need to learn about that > new thing and to change their configuration. Alternatively, I'd choose > update-alternatives way, but since there are almost no alternatives in > terms of maintained X11 compositors, I personally don't think it > deserves any time investment. Makes sense, will leave as-is then. > Ouch! And tags are also missing from your repository. Since you use gbp, > then gbp push is to the rescue. That's intentional, since I'm not sure which revision will end up uploaded currently I haven't tagged it yet to avoid force updates. > Will look again at the picom package this evening. Looking forward to it :) - Nikos
Bug#961432: RFP: picom -- lightweight compositor for X11
Hi Lev, On 31/05, Lev Lamberov wrote: > Good. Could you update your Salsa repository too? Whoops, forgot to push, updated with all the recent changes. > Your d/watch needs some tweaks, because currently it detects 7.5 as the > latest upstream version, where there is 8 (which you package). Fixed. > I'd recommend using pristine-tar. > > And I have a question. Why don't you import upstream versions as > archives and not use upstream branch to track upstream master? The > latter could make cherry-picking patches much more easy. This reminds me of the discussion on d-devel about the myriad ways of using git for debian patching. The disappointing answer is "that's the way I've done it this far", however I haven't taken the time to explore all the different workflows, which I do aim on doing soon. > I: picom: spelling-error-in-binary usr/bin/picom everytime every time > I: picom: spelling-error-in-manpage usr/share/man/man1/picom.1.gz everytime > every time Fixed. > P: picom source: file-contains-trailing-whitespace debian/control (line 50) > P: picom source: package-uses-old-debhelper-compat-version 12 > P: picom source: rules-requires-root-missing Fixed. > Also, do we really need to have symlinks (compton and compton-trans) > and corresponding desktop files? Since it is a new Debian package, > probably we can drop these. What do you think? You're right, for now they serve no purpose so I removed them. However, upstream seems to have a full migration plan from compton[1] and it looks like they do intend on keeping backwards compatibility to some degree. So, it might be worth looking into the possibility of going through a migration to picom, given that compton is unmaintained, and will inevitably bitrot. [1] https://github.com/yshui/picom/#migration - Nikos
Bug#961432: RFP: picom -- lightweight compositor for X11
On 26/05, Lev Lamberov wrote: > Then you could compare your packages and somehow merge them, taking best > pieces. I took a look at that package and cherry-picked some improvements from there, also added Fritz to d/copyright. I think it's ready to be uploaded now, I've put it on mentors[1]. Upstream symlinks compton to picom and also installs a compton.desktop file, so rather than override that I opted to set a Conflict/Replaces for compton. [1] https://mentors.debian.net/debian/pool/main/p/picom/picom_8-1.dsc
Bug#961432: RFP: picom -- lightweight compositor for X11
On 26/05, Lev Lamberov wrote: > Would be nice if you could work together on preparing picom for Debian. > I propose Nikos to look at your current work and base on it. Then, > please, let me know when you think it's ready, and I'll take a look. > Please, keep me posted. That reached me a bit too late sadly, I've already used compton as a base to get a workable picom package. What remains now is the copyright file. The complexity here comes from the random spread of the 2 licenses. Some files are MIT from the compton authors, and others are MPL which is the license upstream uses now. Upstream uses 'SPDX-License-Identifier: [MPL-2.0 | MIT]' to specify the license for each file, sadly however licensecheck doesn't appear to recognize it.
Bug#961460: src:newsboat: build depends on librust-xdg-2-dev which doesn't exist (anymore)
Hi, I'm confused here, I just did a test build in a fresh unstable chroot and it seems like newsboat builds just fine. librust-xdg-2-dev is provided by librust-xdg[1]. Is this a false positive of some build script? Or perhaps the rebuild was run in testing rather than unstable (librust-xdg hasn't migrated yet). [1] https://tracker.debian.org/media/packages/r/rust-xdg/control-2.2.0-2 - Nikos On 24/05, Paul Gevers wrote: > Source: newsboat > Version: 2.19-1 > Severity: serious > User: trei...@debian.org > Usertags: -1 edos-uninstallable > > Dear maintainer(s), > > Your package Build-Depends on librust-xdg-2-dev but that package isn't > available in Debian (anymore). You should probably Build-Depends on > librust-xdg-dev instead. > > Paul >
Bug#961432: RFP: picom -- lightweight compositor for X11
retitle -1 ITP: picom -- lightweight compositor for X11 owner -1 thanks My initial thought was that the compton maintainer should be the one to take this over, but it looks like[1] compton was orphaned as its maintainer moved on to wayland. In which case, I'm interested in packaging this. - Nikos [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=960779
Bug#961420: package-sponsorhip-requests search results point to invalid path
Package: lists.debian.org Severity: normal Hi, The search results[1] from the package-sponsorship-requests mailing list appear to 404. On closer inspection it looks like the results point to '/package-sponsorship-requests/%Y/%M/msgid.html' while, looking at the list archives, the correct url appears to be 'package-sponsorship-requests/%Y/package-sponsorship-requests-%Y%m/msgid.html'. [1] https://lists.debian.org/cgi-bin/search?P=xautolock=or=Gpackage-sponsorship-requests==10=rust=Gpackage-sponsorship-requests%7E-%7E%7E4294967295 - Nikos
Bug#927684: dunstify is missing from package
Hi, dunstify wasn't included in the default installation target before, but this has now been changed upstream. The next upload/release will also include dunstify. notify-send indeed can't define actions. On Tue, 12 May 2020, at 15:52, Jakson Alves de Aquino wrote: > I'm using dunstify in scripts to send messages to dunst, > including the definition of actions. Is notify-send capable of > defining actions? I couldn't find this capability in its man page. > So, I believe that other users would benefit from dunstify being > available in a Debian package. > > Thank you! > > -- > Jakson Aquino >
Bug#952507: dunst cannot be disabled and steals notifications
Sorry for the delay, On 03/03, Norbert Preining wrote: > Is there a way to claim that interface/service somehow? I am thinking of > other cinnamon users (since I am one of the maintainers of Cinnamon in > Debian), and how Cinnamon could stop dbus from starting another > notification daemon, when the one from cinnamon is already running. > Is there a way for this? That's already the case, dunst cannot start if another notification daemon is running, you can test it by running dunst and trying to start a second instance of it: ``` $ dunst BadAccess (attempt to access private resource denied) BadAccess (attempt to access private resource denied) Unable to grab key "ctrl+grave" Cannot acquire 'org.freedesktop.Notifications': Name is acquired by PID '1547'. ``` So sadly it's either a race over which daemon gets the address first, or up to dbus to decide which daemon to start. > Or is it anyway too late, because the notification service is started > already before the cinnamon session is started? (during xsession > somewhere)? Unless there are user modifications to the startup scripts dunst is only started by dbus. So if the systemd service is disabled it shouldn't be running at all until a notification comes in and dbus starts it. > Not really anything better than learning how to claim the dbus faster > than dunst? > Is there a way to "shadow"/disable it, similar to shadowing of systemd > units? I'm not aware of anything else, some googling brought me to this bug[1]: > The recommended way to disable a D-Bus service is currently "don't install > it". Another comment in that bug suggests that you could override the service file from `~/.local/share/dbus-1/services` and neutralize it that way, but I'm not sure whether that'll work. [1] https://gitlab.freedesktop.org/dbus/dbus/issues/70
Bug#952507: dunst cannot be disabled and steals notifications
Hello, On 25/02, Norbert Preining wrote: > How am I supposed to disable this program? > And no, I do *not* want to remove it, nor mask the service, because > other uses are using i3 and are using dunst here. The autostart part of dunst is managed by dbus, specifically the auto-activation feature. Unfortunately dbus is not as powerful of a service manager as systemd and it doesn't have a way to prioritise one service over another, or a way to disable one while still keeping it installed. So what can be done now? I don't see a way to solve this other than removing the dbus service file entirely, but for this to work and not break a lot of other systems we have to auto-enable dunst for all desktop users on install This is difficult because i3/X11 in debian doesn't run in systemd so we can't explicitly say to only start dunst after the graphical session has started. So it leaves the only option of having an auto-restart on failure every X seconds (pretty ugly approach IMO, and it's going to spam the error logs if no graphical session is started for a while). Any other suggestions? >From your side you can remove the service file at /usr/share/dbus-1/services/org.knopwob.dunst.service and have the i3 users enable dunst via systemd or enable it globally and disable it for yourself. - Nikos
Bug#949180: newsboat coredumps (with illegal (?) character in existing ~/.newsboat/config)
forwarded -1 https://github.com/newsboat/newsboat/issues/723 thanks On 17/01, gregor herrmann wrote: > Whatever character there was, after removing it, newsboat starts > again. So kind of a "user error"; still this has been working for > years and breaking reading a config file smells like a regression. Indeed a bug, it's a side-effect from Rust having a strict requirement of all strings being valid UTF-8.
Bug#941855: dunst: Daily systemd errors: "Failed to start Dunst notification daemon."
I apologise for the delay in replying but I don't have many clues as to what's happening here or any easy ways to debug it. On 20/10, Francois Marier wrote: > > Perhaps the import-environment fails, could you add `echo DISPLAY=$DISPLAY` > > under that > > and see if it appears in .xsession_errors? > > I added a line to that startup script to email me the value of $DISPLAY when > it runs and I got the following: > > DISPLAY=:1 Curious why it's :1 and not :0, are you running a second X11 session? It could have something to do with that if that's the case. > I looked at the notification log (Ctrl+`) this morning after seeing these > errors in the logs and there was nothing matching that timestamp. Not > surprising since these are complaints about failing to start. > > The only cronjob I have that is set to run specifically at 7am is: > > /etc/cron.d/anacron > > but then maybe the /etc/cron.daily/ jobs also run at around that time. Well, when anacron runs it basically also calls all global crons in the system so that doesn't help much. >From the logs you provided it seems that for your own user session dunst seems to be running normally even when these failure logs appears, so my working hypotheses now is that there's an automated job trying to send a notification as a different user - systemd tries to start dunst which fails as there's no X11 running as that user. Does that sound something that might be happening - do you have any such customizations to your systems? I'm not aware of any packages that use libnotify notifications as part of cron/automated jobs so it's most likely something added later. -- Best Regards, Nikos Tsipinakis
Bug#941855: dunst: Daily systemd errors: "Failed to start Dunst notification daemon."
On 12/10, Francois Marier wrote: > On 2019-10-12 at 09:25:20, Nikos Tsipinakis wrote: > I've got this line in my ~/.config/i3/config: > > exec --no-startup-id /home/francois/devel/remote/user-scripts/startup > > and that corresponds to a script [1] with these lines: > > /usr/bin/systemctl --user import-environment DISPLAY > /usr/bin/systemctl status --user dunst Huh, why `status` and not `start`? Is that a typo? Perhaps the import-environment fails, could you add `echo DISPLAY=$DISPLAY` under that and see if it appears in .xsession_errors? > > However it is weird that systemd reports that dunst is running even though > > it > > obviously fails to start. I'm not sure what is going on there. > > I don't think it fails to start because it works fine and it looks like > this: > > $ systemctl status --user dunst.service > ● dunst.service - Dunst notification daemon > Loaded: loaded (/usr/lib/systemd/user/dunst.service; enabled; vendor > preset: enabled) > Active: active (running) since Fri 2019-10-11 19:21:31 PDT; 15h ago >Docs: man:dunst(1) >Main PID: 5330 (dunst) > Memory: 4.0M > CGroup: /user.slice/user-1000.slice/user@1000.service/dunst.service > └─5330 /usr/bin/dunst > > $ pgrep -a dunst > 5330 /usr/bin/dunst Indeed that looks like it's running - however the error you showed is always fatal and the logs do show dunst service failed a few times, so something happens at that point in time daily that prevents access to X11 and dunst can't start? Bizarre. > The part that confuses me is that once a day (always almost exactly at the > same time) it tries to start or restart (and fails) even though it's already > running in my user session. > > Is there a cron-like job that runs every morning? No, there's nothing that's scheduled to run at a specific time. However, dbus _will_ try to start dunst via systemd if a notification comes through and it detects that it isn't running. Perhaps you have a cron scheduled at that time?
Bug#941855: dunst: Daily systemd errors: "Failed to start Dunst notification daemon."
Hi, This is usually caused by not having exported the DISPLAY variable into the systemd environment, there has been extensive discussion about this in #347[1] upstream. How are you starting X11, are you using a custom xinitrc? However it is weird that systemd reports that dunst is running even though it obviously fails to start. I'm not sure what is going on there. [1] https://github.com/dunst-project/dunst/issues/347
Bug#935165: buster-pu: package newsboat/2.13-1+deb10u1
Package: release.debian.org
Severity: normal
Tags: buster
User: release.debian@packages.debian.org
Usertags: pu
Hi,
I'd like to patch a use-after-free bug in newsboat. It was reported in debian
in #898559[1] and fixed upstream[2]. While I haven't been able to reproduce a
crash with it it's clear that it's there and I have received feedback that it
indeed fixes the linked issue.
Debdiff attached
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898559
[2] https://github.com/newsboat/newsboat/pull/603
diff -Nru newsboat-2.13/debian/changelog newsboat-2.13/debian/changelog
--- newsboat-2.13/debian/changelog 2018-09-23 21:01:29.0 +0300
+++ newsboat-2.13/debian/changelog 2019-08-17 21:10:38.0 +0300
@@ -1,3 +1,10 @@
+newsboat (2.13-1+deb10u1) buster; urgency=medium
+
+ [ Nikos Tsipinakis ]
+ * Patch use after free in itemlist (Closes: #898559)
+
+ -- Nikos Tsipinakis Sat, 17 Aug 2019 21:10:38 +0300
+
newsboat (2.13-1) unstable; urgency=medium
* New upstream release
diff -Nru newsboat-2.13/debian/patches/02-fix-use-after-free.patch
newsboat-2.13/debian/patches/02-fix-use-after-free.patch
--- newsboat-2.13/debian/patches/02-fix-use-after-free.patch1970-01-01
02:00:00.0 +0200
+++ newsboat-2.13/debian/patches/02-fix-use-after-free.patch2019-08-17
21:10:22.0 +0300
@@ -0,0 +1,33 @@
+From a44a72ffa5c66a1de21476d23a8523001eecfc23 Mon Sep 17 00:00:00 2001
+From: Juho Pohjala
+Date: Tue, 13 Aug 2019 16:10:16 +0300
+Subject: [PATCH] Crash when opening a url (#189)
+
+Caused by heap-use-after-free in ItemListFormAction::prepare().
+
+The complete invalidation mode repopulates the listfmt vector, thus it's
+not enough to clear the invalidated_itempos only in case of partial
+invalidation mode. The fix is to clear the invalidated_itempos vector
+also in case of complete invalidation mode.
+---
+ src/itemlistformaction.cpp | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/src/itemlist_formaction.cpp
b/src/itemlist_formaction.cpp
+@@ -930,7 +930,6 @@
+ datetime_format);
+ listfmt.set_line(itempos, line, item.second);
+ }
+- invalidated_itempos.clear();
+ } else {
+ LOG(level::ERROR,
+ "invalidation_mode is neither COMPLETE nor "
+@@ -942,6 +941,7 @@
+ listfmt.format_list(rxman, "articlelist"));
+ }
+
++ invalidated_itempos.clear();
+ invalidated = false;
+
+ set_head(feed->title(),
diff -Nru newsboat-2.13/debian/patches/series
newsboat-2.13/debian/patches/series
--- newsboat-2.13/debian/patches/series 2018-09-23 21:01:29.0 +0300
+++ newsboat-2.13/debian/patches/series 2019-08-17 21:10:22.0 +0300
@@ -1 +1,2 @@
01-use-policy-compliant-perl-hashbang.patch
+02-fix-use-after-free.patch
Bug#935021: newsboat: Error in Russian locale help
Control: tags -1 +fixed-upstream It was fixed upstream with this commit: https://github.com/newsboat/newsboat/commit/662c7c45b48ae08475c1516548d33cca063c9789 It'll get fixed in unstable in the next upload.
Bug#931861: RM: newsbeuter -- RoM; abandoned upstream; actively maintained fork available
Package: ftp.debian.org Severity: normal Hello, Please remove newsbeuter from the archive. It has been abandoned upstream and there is an actively maintained fork (newsboat) already available in Debian. It also currently fails to build with the new json-c version that'll be added in the upcoming transition. Best Regards, Nikos Tsipinakis
Bug#931372: RFS: dunst/1.4.1-1 [ITA] -- dmenu-ish notification-daemon
On 10/07, David Kalnischkies wrote: > As far as I looked I have only some minor nitpick comments because > I like looking at changelogs and get the feeling of understanding what > happened without investigating too deeply. Nitpicks, but very valid points nonetheless. > I think I would prefer "Adopting package" or "Set myself as maintainer" > or something like that as "Update" can basically mean everything like > changing your email address, joining a team or whatever. Fixed. > > * Update Build-Depends > > If there is a good way to summarize what was exactly updated, please say > so. Version bump? Now build-depending on KDE, GNOME and Qt3? I have to admit I wanted to explain a bit more here but given that there were a bunch of small changes in the same file at the same time I got a bit lazy with splitting commits and left it as-is. I've now broken the changes for this and the copyright file down to individual commits, should be much better. > > * Bump standards version > > Which standard? – also there is a new one out by now. Added the version, and updated it to 4.4.0. > > * Bump debhelper compat to 12 > > You could switch to "debhelper-compat (= 12)" in Build-Depends and > remove the debian/compat file. Interesting I didn't know about that, it looks handy. I've updated it to use this format now. > > * Install release notes in docs > > Your are installing them as NEWS: Do you have a deeper reason for doing > that? The policy mentions that release notes should be installed as NEWS[1] "If an upstream release notes file is available, containing a summary of changes between upstream releases intended for end users of the package and often called NEWS, it should be accessible as /usr/share/doc/package/NEWS.gz." > The file contents look like a bit similar to a NEWS.Debian file > in content, but then upstream name and content also suggest it should > contain notes for each (major) release – even if 1.4 is missing – which > would usually be a bit much for NEWS… but yeah, that is really just > personal taste and style I guess. Long story short: mention NEWS. It would be much if it was displayed during installation indeed but from my understanding apt-listchanges only shows NEWS.Debian by default. So in my mind it's fine to have it there for anyone who's interested to read it. > > Thanks again for adopting a package and good luck finding a sponsor now > that unstable is open again! > Thank _you_ for taking a look and reviewing. The new (more descriptive) changelog after this is the following: [ Francois Marier ] * Use sensible-browser instead of Firefox in /etc/xdg/dunst/dunstrc (Closes: #929456) [ Nikos Tsipinakis ] * Adopt package (Closes: #930310) * New upstream version 1.4.1 * Remove cross.patch (applied upstream) * Refresh patches * d/control: - Drop build-dep on libxdg-basedir - Remove glib version constraint (minimum version no longer in archive) - Drop build-dep on gtk in favour of gdk-pixbuf - Add build-dep on dbus daemon and librsvg (required for the test suite) * Bump standards to 4.4.0 * Install release notes as NEWS in docs * Bump debhelper compat to 12 Also switch to using debhelper-compat rather than d/compat * d/copyright: - Update Source URL - Add myself to debian/ attributions - Add missing license for greatest.h [1] https://www.debian.org/doc/debian-policy/ch-docs.html#changelog-files-and-release-notes Best Regards, Nikos Tsipinakis
Bug#915841: newsbeuter FTBFS with json-c 0.13.1
On 03/07, Gianfranco Costamagna wrote: > Hello Nikos,you might want to first upload the fork in new queue, providing > the same binary, so the removal becomes a cruft later > I mean, to not disrupt our userbase: > with moving src:a providing a to src:b providing b > [...] > in case the fork is not a drop-in replacement, probably providing the old > binary name is not worth the effort, in this caseyou can do whatever you > prefer :) The fork is functionally a drop-in equivalent, however given that the name changed this also means that a) the name of the binary changed so everyone will have to swap that out and that b) the name of the configuration directories changed. There's an automated migration on the fork but it only works with the simplest setups and fails in other cases. Newsbeuter has had the fork on its Recommends for a while and I've put out a NEWS entry informing about the change. Overall given that there will need to be some manual migration from the users side I'm not sure it's worth trying to do a proper package rename here. Adding a new "newsbeuter" binary while in reality being newsboat would be a lot more confusing than the alternative IMO.
Bug#931372: RFS: dunst/1.4.1-1 [ITA] -- dmenu-ish notification-daemon
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "dunst" Package name: dunst Version : 1.4.1-1 Upstream Author : Sascha Kruse URL : https://dunst-project.org/ License : BSD 3-clause Section : x11 It builds those binary packages: dunst - dmenu-ish notification-daemon To access further information about this package, please visit the following URL: https://mentors.debian.net/package/dunst Alternatively, one can download the package with dget using this command: dget -x https://mentors.debian.net/debian/pool/main/d/dunst/dunst_1.4.1-1.dsc Changes since the last upload: [ Francois Marier ] * Use sensible-browser instead of Firefox in /etc/xdg/dunst/dunstrc (Closes: #929456) [ Nikos Tsipinakis ] * Update maintainer (Closes: #930310) * New upstream version 1.4.1 * Remove cross.patch (applied upstream) * Refresh patches * Update Build-Depends * Bump standards version * Install release notes in docs * Bump debhelper compat to 12 * Update copyright file Regards, Nikos Tsipinakis
Bug#915841: newsbeuter FTBFS with json-c 0.13.1
On 01/07, Gianfranco Costamagna wrote: > there is an upstream fix in a fork called newsboat > > I'm attaching both patches to this bug report, please apply them! I apologise for ignoring this issue earlier. I initially intended to convert newsbeuter to a stub package pointing to newsboat but missed the buster deadline. Given that upstream is abandoned and there is a functionally identical fork I intend to remove newsbeuter from the archive. It doesn't make sense to become a pseudo-upstream to keep it in Debian. I'll file a removal request for it next week after the Buster release.
Bug#930310: O: dunst -- dmenu-ish notification-daemon
Control: retitle -1 ITA: dunst -- dmenu-ish notification-daemon Control: owner -1 ! I intend to adopt this package, I am not a DM however so I'm going to need someone to sponsor my uploads. Full disclosure: I am also the upstream maintainer
Bug#898559: newsboat crashes when opening url
Control: forwarded -1 https://github.com/newsboat/newsboat/issues/189 Hi, I've forwarded your report to the upstream bug tracker. If you have a github account it'd be beneficial to keep track of the issue and respond to any questions the upstream maintainer may have.
Bug#884893: newsboat: FTBFS: Error opening terminal: unknown.
Control: tags -1 pending fixed-upstream Bug has been fixed upstream, upload pending until I figure out how to handle the other 3 open bugs.
Bug#884893: newsboat: FTBFS: Error opening terminal: unknown.
Control: tags -1 - pending fixed-upstream On 21/12, Nikos Tsipinakis wrote: > Control: tags -1 pending fixed-upstream > > Bug has been fixed upstream, upload pending until I figure out how to handle > the > other 3 open bugs. Accidentally replied to the wrong bug, sorry about that. I'm still unsure about how to fix this one.
Bug#884892: newsboat: FTBFS on arm*: filter/Scanner.cpp: sign-compare errors
Control: tags -1 pending fixed-upstream Bug has been fixed upstream, upload pending until I figure out how to handle the other 3 open bugs.
Bug#884594: default configuration file location not recognised
(Accidentally replied only to the submitter - also sending this to the bug tracker for the record) On 18/12, g l wrote: > > Sent: Monday, December 18, 2017 at 9:02 AM > > From: "Nikos Tsipinakis" <ni...@tsipinakis.com> > > > > I'm not sure what this is about. > > > > > Error: no URLs configured. Please fill the file > > > .../.config/newsbeuter/urls with RSS feed URLs or import an OPML file. > > > > As the error message says, you either need to add feed urls to > > ~/.config/newsbeuter/urls or import an opml file with newsbeuter -i . > > > > This debian system compilation instruction is different from the newsbeuter > manual which states that the default directory is ~/.newsbeuter/ _not_ > ~/.config/newsbeuter. Newsbeuter first checks if ~/.config/newsbeuter and ~/.local/share/newsbeuter exists and if so it uses these directories, if not it falls back to ~/.newsbeuter. Please make sure that the XDG directories don't already exist.
Bug#884594: default configuration file location not recognised
Control: tags -1 + moreinfo Hi, I'm not sure what this is about. > Error: no URLs configured. Please fill the file .../.config/newsbeuter/urls > with RSS feed URLs or import an OPML file. As the error message says, you either need to add feed urls to ~/.config/newsbeuter/urls or import an opml file with newsbeuter -i .
Bug#876370: parse_url: curl_easy_perform returned err 22
For the record, Graham sent the log to me privately. I'm not sure if that was
intentional or not.
If it wasn't, please make sure to preserve the Cc to 876...@bugs.debian.org in
the future to also send the message to the bug tracker.
Can you either apply the attached patch or build from upstream and try again?
(And send the log) It won't fix anything but it'll print the HTTP error code to
the log file, should help understand what's going on.
- Nikos
--- a/rss/parser.cpp
+++ b/rss/parser.cpp
@@ -142,7 +142,7 @@
LOG(LOG_DEBUG, "rsspp::parser::parse_url: ret = %d", ret);
long status;
- curl_easy_getinfo(easyhandle, CURLINFO_HTTP_CONNECTCODE, );
+ curl_easy_getinfo(easyhandle, CURLINFO_HTTP_RESPONSE, );
if (status >= 400) {
LOG(LOG_USERERROR, _("Error: trying to download feed `%s' returned HTTP status code %ld."), url.c_str(), status);
Bug#876370: parse_url: curl_easy_perform returned err 22
Control: tags -1 + unreproducible moreinfo Hi, On 21/09, Debian BTS wrote: >* What led up to the situation? >I am trying to setup the following rss feed which works fine in a >browser. https://www.investegate.co.uk/Rss.aspx?company=KGF Seems to be working fine on my end. Possibly the server was having trouble, try again. If the problem still persists please attach the log file generated by launching newsbeuter with 'newsbeuter -l 6 -d log' and running a refresh on the feed. - Nikos
Bug#876327: ITP: newsboat -- text mode rss feed reader with podcast support
Package: wnpp Severity: wishlist Owner: Nikos Tsipinakis <ni...@tsipinakis.com> * Package name: newsboat Version : 2.10 Upstream Author : Alexander Batischev * URL : https://www.newsboat.org * License : MIT/X Consortium Programming Lang : C++ Description : text mode rss feed reader with podcast support newsboat is an actively maintained for of newsbeuter, an innovative RSS feed reader for the text console. It supports OPML import/exports, HTML rendering, podcast (podboat), offline reading, searching and storing articles to your filesystem, and many more features. Its user interface is coherent, easy to use, and might look common to users of mutt and slrn.
Bug#859453: dunst: Installing dunst does not ensure dbus is running
Package: dunst Version: 1.1.0-2+b1 Severity:normal Dear maintainer, For dunst to work a dbus session needs to be running for the user but currently if Xorg and a simple window manager is installed dbus is not running by default which causes dunst to fail with Name Lost. Is Another notification daemon running? I recommend setting dunst to depend on or to recommend the dbus-x11 package and/or the dbus-session-bus virtual package which among other things sets dbus to launch either when the X11 session starts or when a process tries to use dbus.
Bug#733245: newsbeuter: multiline url autodetection broken
control: forwarded -1 https://github.com/akrennmair/newsbeuter/issues/282 Google Code is dead, issue has been migrated to GitHub. -- Best Regards, Nikos Tsipinakis
Bug#776728: newsbeuter: nasty memory leak in 2.8
On Thu, Mar 31, 2016 at 05:46:32PM +0100, Manuel A. Fernandez Montecelo wrote:
> Uhm, sorry for not being clear. I know that the Debian maintainers
> were busy with other stuff.
>
> What it was not clear to me was why this was present in both 2.8 *and*
> 2.9 upstream, e.g., if the original patch had been reverted because it
> caused other problems.
Oh, I am not really sure. I havent followed the 2.9 development that closely and
I really dont feel like digging into 2 years worth of commits to find out, its
fixed anyway so does it really matter?
--
Best Regards,
Nikos Tsipinakis
Bug#776728: newsbeuter: nasty memory leak in 2.8
On Thu, Mar 31, 2016 at 04:10:06PM +0100, Manuel A. Fernandez Montecelo wrote:
> Was it left out for some particular reason?
>
> I have quite a lot of memory so this is not critical for me in any way
> (but thanks for taking care of this). But I imagine that many of the
> users of newsbeuter can be annoyed by that, so I am curious why this
> memory problem has been going on for so long.
As mentioned above, many users are running newsbeuter in hosts with limited
memory and a 1/2GB memory footprint for a text based RSS reader is simply
ridiculous and since there are no other important bugs open I am releasing a
revision with the patch immediately(its also is a nice excuse to migrate the
package to debhelper :) )
As for why it has been going on for that long, the leak was first observed right
after the release of 2.8 for which a patch was released but was not added to
debian since the previous maintainer was busy, in 2.9 the issue re-appeared for
some reason(either its a new memory leak or a regression of the old one), a
patch was released right after that and unfortunately I didn't notice it before
uploading the new version.
--
Best Regards,
Nikos Tsipinakis
Bug#776728: newsbeuter: nasty memory leak in 2.8
Hello,
On Wed, Mar 30, 2016 at 10:12:35PM +0100, Manuel A. Fernandez Montecelo wrote:
> It seems that 2.9 still uses a lot of memory (at least in my
> use-case), 800MB right now after being restarted a few hours ago.
>
> So re-opening this bug.
Apparently the patch for the memory leak didn't fully make it into 2.9, I'll
upload a patched version later today.
--
Best Regards,
Nikos Tsipinakis
Bug#816919: RFS: newsbeuter/2.9-1 [ITA]
On Sat, Mar 12, 2016 at 02:15:14AM +0100, gregor herrmann wrote: > Thanks for all your work, that's really exciting, and I'm happy to > sponsor this upload. Yay \o/ > The order of the paragraphs is a bit unusual; normally the "Files" > sections come before the "License" sections. Fixed. > Cool. - I just think that the newsbeuter-dbg transition package > should depend on newsbeuter-dbgsym instead of newsbeuter. (Or you can > just drop it; I see the point but so far I haven't seen any other > transition packages for debugging symbols; but it's fine for me to > keep it.) I'm going to keep it for now, fixed the dependency. > And in the future, modernizing d/rules would be nice. I haven't messed around with automatic dh that much yet, I'll try to have that in the next revision. -- Best Regards, Nikos Tsipinakis
Bug#816919: RFS: newsbeuter/2.9-1 [ITA]
On Fri, Mar 11, 2016 at 12:49:38AM +0100, gregor herrmann wrote: > Will take a closer look tomorrow; a first look shows that the package > might profit from some modernization (d/copyright in Copyright Format > 1.0; Done. > dh(1) in debian/rules; migration to new dbgsym packages (cf. > dh_strip(1)'s --dbgsym-migration)), etc.). Done. > lintian and blhc report: > > P: newsbeuter source: no-dep5-copyright Done. > I: newsbeuter: spelling-error-in-binary usr/bin/newsbeuter occured occurred Sneaked this one in the translation-fix patch. > I: newsbeuter: hardening-no-fortify-functions usr/bin/newsbeuter > I: newsbeuter: hardening-no-fortify-functions usr/bin/podbeuter Fixed. > W-dpkg-buildflags-missing|CPPFLAGS 59 (of 59) missing| Fixed. -- Best Regards, Nikos Tsipinakis
Bug#816919: RFS: newsbeuter/2.9-1 [ITA]
On Wed, Mar 09, 2016 at 11:25:01PM +0100, gregor herrmann wrote:
> Thanks for your interest in newsbeuter; I like it and use it daily :)
> And I was looking forward to a version which needs less memory than
> Iceweasel; but for me 2.9 has a massive problem:
>
> The highlighting feature seems to be broken (no idea if this is a
> problem in newsbeuter or ncurses; I haven't retried to rebuild 2.8-2
> to check). Too show what I mean: I have in my ~/.newsbeuter/config
Apparently this issue was already reported and fixed upstream. Added a patch
and it should work as intended now.
--
Best Regards,
Nikos Tsipinakis
Bug#816919: RFS: newsbeuter/2.9-1 [ITA]
On Tue, 8 Mar 2016 17:53:01 +0100 Jakub Wilk <jw...@debian.org> wrote: > You can (and should) forward the bugs upstream. > You can mark the incorrectly translated messages as "fuzzy", so that > the translations won't be used. I forwarded the issue upstream, and patched the erroneous translations. To summarize the last few mails the current changelog is: * New upstream release. (Closes: #776728) * Fix segfault when downloading podcasts * Patch erroneous Portuguese, Ukrainian and Chinese translations. * Bumped standards to 3.9.7 * Updated watch file. * Removed upstream README from docs. * New maintainer. (Closes: #800752) -- Best Regards, Nikos Tsipinakis
Bug#816919: RFS: newsbeuter/2.9-1 [ITA]
Hello Jakub, On Tue, 8 Mar 2016 14:53:58 +0100 Jakub Wilk <jw...@debian.org> wrote: > Speaking of PO files, i18nspector finds some interesting bugs in them: > > E: po/uk.po: c-format-string-missing-arguments msgid "`%s' is not a valid > regular expression: %s": 1 (msgstr) < 2 (msgid) > E: po/zh.po: c-format-string-argument-type-mismatch msgid "Error while > processing command `%s' (%s line %u): %s": int * (msgstr) != unsigned int > (msgid) > E: po/zh.po: c-format-string-missing-arguments msgid "Error: couldn't mark > feed read: %s": 0 (msgstr) < 1 (msgid) > > (plus some other, less severe problems) Unfortunately most of these errors are left for the translators to fix as they are related to the translated message format, nothing I can do since I do not know any of the languages. Best Regards, Nikos Tsipinakis
Bug#816919: RFS: newsbeuter/2.9-1 [ITA]
Hello Dmitry, On Tue, Mar 08, 2016 at 12:01:28PM +0300, Dmitry Bogatov wrote: > [NO DD, can't sponsor] Input is always appreciated :) > There is nice tool `check-all-the-things'. It reveals > > * loads of spelling errors in po/ The 'spelling errors' are mostly ispell trying to correct non-english translations i.e. "./newsbeuter-2.9/po/es.po:438: Autor ==> Author" es.po:436-8 #: src/controller.cpp:1355 src/itemview_formaction.cpp:90 msgid "Author: " msgstr "Autor: " Thats clearly a translation that ispell is trying to parse as english. There are a few minor spelling mistakes in english but very few if any are in user-viewable files(docs) in my opinion not worth making a patch for them, they can easily be patched upstream and pulled down at the next release. > * wrong formatting of your email (email is formatted this way: Name > <em...@bar.com>, >your formatting in patches/podbeuter-segfault-fix misses <> symbols) Author: Nikos Tsipinakis <ni...@tsipinakis.com> Formatting seems correct to me as it is? > * installation instruction (README) should not find way into binary package Agreed, README has been removed from the docs, package re-uploaded. Best Regards, Nikos Tsipinakis
Bug#816919: RFS: newsbeuter/2.9-1 [ITA]
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package "newsbeuter" * Package name: newsbeuter Version : 2.9-1 Upstream Author : Andreas Krennmair <a...@newsbeuter.org> * URL : https://github.com/akrennmair/newsbeuter * License : MIT Section : net It builds those binary packages: newsbeuter - text mode rss feed reader with podcast support newsbeuter-dbg - debugging symbols for newsbeuter To access further information about this package, please visit the following URL: http://mentors.debian.net/package/newsbeuter Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/n/newsbeuter/newsbeuter_2.9-1.dsc Changes since the last upload: * New upstream release. (Closes: #776728) * Fix sefault when downloading podcasts. * Bumped standards to 3.9.7 * Updated watch file. * New maintainer. Best Regards, Nikos Tsipinakis
Bug#800752: RFA: newsbeuter -- text mode rss feed reader with podcast support
retitle 800752 ITA: newsbeuter -- text mode rss feed reader with podcast support owner 800752 ! thanks I have been using newsbeuter on and off for about a year and I'm interested in adopting it. Regards, Nikos Tsipinakis
