Bug#1004821: libam7xxx: FTBFS with ffmpeg 5.0
On Sat, 25 Jun 2022 13:04:46 +0300 Nicholas Guriev wrote: > This patch should help. Although, call to deprecated av_init_packet() > remains. > It is to be replaced with av_packet_alloc() / av_packet_free() logic. Thank you, Nicholas, this is a good first step. I'll try to find time this week-end to push a new package compatible with FFmpeg 5.0. Take care, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#1004821: libam7xxx: FTBFS with ffmpeg 5.0
On Tue, 1 Feb 2022 23:34:13 +0100 Sebastian Ramacher wrote: > Source: libam7xxx > Version: 0.1.7-1 > Severity: important > X-Debbugs-Cc: sramac...@debian.org > Tags: sid bookworm ftbfs > Usertags: ffmpeg5.0 > > libam7xx FTBFS with ffmpeg 5.0 in experimental: > [...] > > Cheers > -- > Sebastian Ramacher Thank you for the report Sebastian, I'll try to fix this soon, is there a timeline for the ffmpeg 5.0 transition? Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#970426: gtg: New upstream version 5.0 available
On Wed, 16 Sep 2020 11:17:23 +0200 Antonio Ospite wrote: > Package: gtg > Version: 0.3.1-4 > Severity: wishlist > > Dear Maintainer, > > a new upstream version of gtg is available, here is the NEWS file: > https://github.com/getting-things-gnome/gtg/blob/v0.4/NEWS > > This version has been ported to pyhton3 and GTK3 and it would be good to > have it in Debian Unstable. > I am looking into this myself, I have a draft package for the new 5.0 upstream release, however it turns out that the liblarch dependency also needs to be updated and it has been removed from Debian, so that would have to be sorted out first. Related issues: https://github.com/getting-things-gnome/liblarch/issues/31 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1001820 Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#1001820: liblarch: Resurrect package and upload the new available upstream release 0.3.1
Package: liblarch Severity: wishlist Dear Maintainer, I am looking into updating the gtg package in debian, and I noticed that liblarch is a dependency, would you be willing to bring it back to the debian archive? I would volunteer as the maintainer if needed, but I am not a Debian maintainer or developer and I would not be able to upload the new package myself, so I would need a sponsor for that. I opened an upstream issue as well, to see what the upstream thinks about it: https://github.com/getting-things-gnome/liblarch/issues/31 Cc-ing Luca who proposed the removal in #981169 to hear his opinion as well. Thanks, Antonio -- System Information: Debian Release: bookworm/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.15.0-2-amd64 (SMP w/2 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#961365: ITP: jacksum -- Computes checksums, CRCs and message digests
Package: wnpp Followup-For: Bug #961365 Hi Mechtilde, FYI there is a new shiny upstream version of jacksum: https://github.com/jonelo/jacksum/releases/tag/v3.0.0 Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#979641: src:kboot-utils: invalid maintainer address
On Wed, 3 Feb 2021 09:43:30 +0100 Baptiste Beauplat wrote: [...] > > I could open the RM bug on your behalf if you want me to. > Thank you, I would appreciate that. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#979641: src:kboot-utils: invalid maintainer address
On Tue, 2 Feb 2021 20:51:24 +0100 Baptiste Beauplat wrote: > Hi Antonio, > > On 2021/01/25 09:23 AM, Baptiste Beauplat wrote: [..] > > > > Well, installation stats for kboot-utils are close to 0 [1]. A possible > > solution would be to request its removal [2]. If it appears that it was > > actually needed, it could be re-introduced at a later point (not for the > > next stable but I don't think that's a problem). > > > > [1]: https://qa.debian.org/popcon.php?package=kboot-utils > > [2]: > > https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#removing-packages > > Have you decided the course of action for kboot-utils yet? > Hi Baptiste, I would be fine with having it removed, I just haven't had the time to read through your links. Thanks you, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#979641: src:kboot-utils: invalid maintainer address
On Sun, 24 Jan 2021 21:12:54 +0100 Baptiste Beauplat wrote: > Hi Antonio, > > kboot-utils, one of the packages you maintain in Debian has an old, > unreachable > Maitainer address. Could you please update it to prevent it from getting > removed? > > See below the original bug report. > Thank you for reporting this Baptiste. I am actually not sure how useful kboot-utils is nowadays, it was mainly developed to make it easier to boot kernels on the Sony PS3, but I don't think the PS3 is supported by Debian directly anymore. However I would be happy to update the package anyway if there was someone interested to sponsor it, since I cannot upload packages myself and the I doubt my usual sponsor would be interested in it. Ciao, Antonio > Best, > > On 2021/01/09 06:04 PM, Ansgar wrote: > > Source: kboot-utils > > Version: 0.4-1 > > Severity: serious > > Tags: bullseye sid > > X-Debbugs-Cc: Holger Levsen > > > > The maintainer address is invalid, see below. > > > > Ansgar > > > > Start of forwarded message > > From: Mail Delivery System > > Subject: Mail delivery failed: returning message to sender > > Date: Sat, 09 Jan 2021 16:49:56 + > > > > > This message was created automatically by mail delivery software. > > > > A message that you sent could not be delivered to one or more of its > > recipients. This is a permanent error. The following address(es) failed: > > > > osp...@studenti.unina.it > > host fmvip.unina.it [192.132.34.7] > > SMTP error from remote mail server after RCPT > > TO:: > > 550 5.1.1 ... User unknown > > > Reporting-MTA: dns; muffat.debian.org > > > > Action: failed > > Final-Recipient: rfc822;osp...@studenti.unina.it > > Status: 5.0.0 > > Remote-MTA: dns; fmvip.unina.it > > Diagnostic-Code: smtp; 550 5.1.1 ... User unknown > > > > -- > Baptiste Beauplat - lyknode -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#975290: tweeper: report an error when an Instagram/Facebook/etc account doesn't exist
On Fri, 20 Nov 2020 09:12:47 +0100 Antonio Ospite wrote: > On Fri, 20 Nov 2020 14:47:23 +0800 > Paul Wise wrote: > > > Package: tweeper > > Version: 1.4.2-1 > > Severity: important > > When I try to download the RSS for an Instagram account that does not > > exist, tweeper just returns an empty RSS feed and exits with success. > > > > When I try to download the RSS for a Facebook account that does not > > exist, tweeper prints a "Page not found" feed and exits with success. > > > > I assume that there are similar issues with all of supported sites. > > > > Instead it should return an error on stderr and exit with a failure, > > for each of the different websites that are supported. > > > > Thanks for the report Paul, I'll take a look during the weekend. > The issue has been fixed in the upstream master branch: https://git.ao2.it/tweeper.git/commitdiff/ad39a334af38e4a5d37e553e8ad81eac4d2cedaa https://git.ao2.it/tweeper.git/commitdiff/d5cf35e48bf2644118ede9b58f99e200e420b481 And Twitter support has been restored too after it broke because apparently Twitter is not serving the mobile UI anymore. I hope to have a new Debian package uploaded soonish. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#975290: tweeper: report an error when an Instagram/Facebook/etc account doesn't exist
On Fri, 20 Nov 2020 14:47:23 +0800 Paul Wise wrote: > Package: tweeper > Version: 1.4.2-1 > Severity: important > When I try to download the RSS for an Instagram account that does not > exist, tweeper just returns an empty RSS feed and exits with success. > > When I try to download the RSS for a Facebook account that does not > exist, tweeper prints a "Page not found" feed and exits with success. > > I assume that there are similar issues with all of supported sites. > > Instead it should return an error on stderr and exit with a failure, > for each of the different websites that are supported. > Thanks for the report Paul, I'll take a look during the weekend. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#972811: xfonts-utils: New upstream release available, fonttosfnt 1.2.0
Package: xfonts-utils Version: 1:7.7+6 Severity: wishlist Dear Maintainer, as you may know a new upstream release is available for fonttosfnt: https://lists.x.org/archives/xorg/2020-October/060497.html This release includes some fixes that can be useful for people converting bitmap fonts to Open Type bitmaps, which is particularly relevant since pango removed support for older bitmap formats[1,2]. It would be good to have it in Debian. Let me know if you need some help and I'll try to find some time. Thanks a lot, Antonio [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939748 [2] https://gitlab.gnome.org/GNOME/pango/-/issues/386 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.9.0-1-amd64 (SMP w/2 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 xfonts-utils depends on: ii libc6 2.31-4 ii libfontenc1 1:1.1.4-1 ii libfreetype6 2.10.2+dfsg-4 ii x11-common1:7.7+21 ii xfonts-encodings 1:1.0.4-2 ii zlib1g1:1.2.11.dfsg-2 xfonts-utils recommends no packages. xfonts-utils suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#958754: gtg: GTG shows an error when I click on Edit - Preferences
On Fri, 24 Apr 2020 20:10:07 -0300 Leandro Ramos wrote: [...] > File "/usr/share/gtg/GTG/tools/shortcut.py", line 50, in get_saved_binding > list_keys = call_subprocess().splitlines() Hi Leandro, I am not the maintainer but maybe I can help. This error indicates that the CHECK_VERSION command failed and looking at the code we can see that: CHECK_VERSION = "gsettings list-keys " \ "org.gnome.settings-daemon.plugins.media-keys" So maybe you are missing the 'gsettings' binary. $ dpkg -S /usr/bin/gsettings libglib2.0-bin: /usr/bin/gsettings Try installing the libglib2.0-bin package. Probably the package should have depended on it, but with a new upstream version available I don't know if that's worth fixing. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#970426: gtg: New upstream version 4.0 available
Package: gtg Version: 0.3.1-4 Severity: wishlist Dear Maintainer, a new upstream version of gtg is available, here is the NEWS file: https://github.com/getting-things-gnome/gtg/blob/v0.4/NEWS This version has been ported to pyhton3 and GTK3 and it would be good to have it in Debian Unstable. Thanks for your time. Ciao, Antonio -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/2 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 gtg depends on: ii python2.7.17-2 ii python-configobj 5.0.6-3 ii python-dbus 1.2.16-2 ii python-glade2 2.24.0-6 ii python-gtk2 2.24.0-6 ii python-liblarch 2.1.0-4 ii python-notify 0.1.1-4+b2 ii python-xdg0.26-1 Versions of packages gtg recommends: pn python-simplejson ii yelp 3.38.0-1 Versions of packages gtg suggests: pn bugz pn python-appindicator ii python-cairo 1.16.2-3 pn python-cheetah pn python-dateutil pn python-evolution pn python-geoclue pn python-gnomekeyring pn python-launchpadlib pn python-suds -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#969556: closed by Debian FTP Masters (reply to Paul Gevers ) (Bug#969556: fixed in liferea 1.13.2-2)
On Sat, 05 Sep 2020 04:06:02 + "Debian Bug Tracking System" wrote: > This is an automatic notification regarding your Bug report > which was filed against the liferea package: > > #969556: liferea: Feeds with MediaRSS elements fail to render in liferea > 1.13.2 > > It has been closed by Debian FTP Masters > (reply to Paul Gevers ). > Wow, that was really fast, thanks a lot Paul. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#969556: liferea: Feeds with MediaRSS elements fail to render in liferea 1.13.2
Package: liferea Version: 1.13.2-1 Severity: important Tags: upstream patch Dear Maintainer, liferea 1.13.2 has been recently uploaded to Debian, however this version has a regression that breaks rendering for any feed containing MediaRSS elements, like YouTube channel feeds, like for instance: https://www.youtube.com/feeds/videos.xml?channel_id=UC1O0jDlG51N3jGf6_9t-9mw The issue has been fixed upstream and the fix will be available in the next 1.13.3 release. The fix is here: https://github.com/lwindolf/liferea/commit/ff354eee64af0c1229fbde25597d8ccdce1b2353 Maybe the Debian package can cherry-pick the fix while waiting for the new upstream release? Thanks a lot for maintaining liferea. Ciao, Antonio -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-3-amd64 (SMP w/2 CPU threads) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.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 liferea depends on: ii dbus-user-session [default-dbus-session-bus] 1.12.20-1 ii dbus-x11 [dbus-session-bus] 1.12.20-1 ii dconf-gsettings-backend [gsettings-backend] 0.36.0-1 ii gir1.2-freedesktop1.64.1-1 ii gir1.2-gtk-3.03.24.22-1 ii gir1.2-peas-1.0 1.26.0-2 ii libc6 2.31-3 ii libgdk-pixbuf2.0-02.40.0+dfsg-5 ii libgirepository-1.0-1 1.64.1-1 ii libglib2.0-0 2.64.4-1 ii libgtk-3-03.24.22-1 ii libjson-glib-1.0-01.4.4-2 ii libpango-1.0-01.46.1-1 ii libpeas-1.0-0 1.26.0-2 ii libsoup2.4-1 2.70.0-1 ii libsqlite3-0 3.33.0-1 ii libwebkit2gtk-4.0-37 2.28.4-1 ii libxml2 2.9.10+dfsg-5+b1 ii libxslt1.11.1.34-4 ii liferea-data 1.13.2-1 ii python3 3.8.2-3 ii python3-cairo 1.16.2-4 ii python3-gi3.36.1-1 ii python3-notify2 0.3-4 ii python3.8 3.8.5-2 Versions of packages liferea recommends: ii gir1.2-gstreamer-1.0 1.16.2-2 ii gir1.2-notify-0.7 0.7.9-1 Versions of packages liferea suggests: pn kget pn network-manager -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#962074: blender: crash in an assertion and doubt about CMAKE_BUILD_TYPE
On Tue, 30 Jun 2020 14:01:50 +0200 Fabian Greffrath wrote: > Hi there, > > Am 2020-06-30 13:49, schrieb Matteo F. Vescovi: > > I'm spending few days of [VAC] so I'm afk. > > Feel free to provide me a patch to fix the issue and I'll more than > > happy to apply it to the package once I'm back, as already done in the > > past. ;-) > > will adding the line > > export DEB_CPPFLAGS_MAINT_APPEND = -DNDEBUG > > to debian/rules already do the fix? > > - Fabian Thanks Fabian, this is viable as a minimum fix indeed. The intent of my original report was also to ask Matteo if he had an opinion about building with CMAKE_BUILD_TYPE=Release instead, since I may not be familiar with all the implications. But yeah, let's play it safe and go with the -DNDEBUG fix. There is another issue with 2.83.0+dfsg as apparently something changed upstream about fonts installation, I think the following commits break some assumptions in debian/patches/0004-locales_directory_install.patch: https://github.com/blender/blender/commit/68e341e9d59ae917eba992591f4f60660f6c58ff https://github.com/blender/blender/commit/d7514914894e9c96c9eab21fb625a2021aaa71cb I opened an MR which should fix both issues: https://salsa.debian.org/multimedia-team/blender/-/merge_requests/2 Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#963975: blender: Blender crashes on launch (failed assert)
On Mon, 29 Jun 2020 15:34:36 +0100 Ben Morris wrote: > Package: blender > Version: 2.83.1+dfsg-1 > Severity: grave > Justification: renders package unusable > > Blender 2.83.1+dfsg-1 is crashing on launch with the output shown below. I > have > tested this with and without an existing ~/.config/blender/ directory. > > $ blender > blf_load_font_default: 'fonts' data path not found for 'droidsans.ttf', will > not be able to display text > blf_load_font_default: 'fonts' data path not found for 'bmonofont-i18n.ttf', > will not be able to display text > blf_load_font_default: 'fonts' data path not found for 'bmonofont-i18n.ttf', > will not be able to display text This is one bug, probably due to some changes in where blender expects the default fonts, which breaks assumptions in a debian-specific patch, see: https://github.com/blender/blender/commit/68e341e9d59ae917eba992591f4f60660f6c58ff https://github.com/blender/blender/commit/d7514914894e9c96c9eab21fb625a2021aaa71cb > blender(BLI_system_backtrace+0x33) [0x55751863b4b3] > blender(BLF_default+0x1c) [0x55751851eddc] > blender(+0x18262bb) [0x5575168382bb] > blender(ED_time_scrub_draw+0x1af) [0x5575165eab8f] > blender(+0x184943d) [0x55751685b43d] > blender(ED_region_do_draw+0x841) [0x55751656e911] > blender(wm_draw_update+0x4ba) [0x55751620f4ba] > blender(WM_main+0x30) [0x55751620d3c0] > blender(main+0x2b8) [0x557515ee36c8] > /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xeb) [0x7f0c01ea0e0b] > blender(_start+0x2a) [0x557515f303ba] > BLI_assert failed: > /build/blender-l5zyJy/blender-2.83.1+dfsg/source/blender/blenfont/intern/blf.c:185, > BLF_default(), at 'global_font_default != -1' > Aborted > The crash by itself is another issue with asserts, probably similar to what reported in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=962074 I will hopefully have a fix for both soon. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#962074: blender: crash in an assertion and doubt about CMAKE_BUILD_TYPE
Package: blender Version: 2.83.1+dfsg-1 Followup-For: Bug #962074 Dear Maintainer, the crasher is still there in 2.83.1+dfsg-1, could you please consider adjusting the Cmake building flags to avoid it? A couple of alternative solutions are mentioned in the original report, let me know if that report is confusing and if you prefer a summary of the situation. Thanks, Antonio -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.7.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages blender depends on: ii blender-data 2.83.1+dfsg-1 ii fonts-dejavu 2.37-2 ii libavcodec58 7:4.3-2 ii libavdevice58 7:4.3-2 ii libavformat58 7:4.3-2 ii libavutil56 7:4.3-2 ii libboost-locale1.71.0 1.71.0-6+b2 ii libc6 2.30-8 ii libfftw3-double3 3.3.8-2 ii libfreetype6 2.10.1-2 ii libgcc-s1 10.1.0-4 ii libgl11.3.1-1 ii libglew2.12.1.0-4+b1 ii libgomp1 10.1.0-4 ii libilmbase24 2.3.0-6 ii libjack0 [libjack-0.125] 1:0.125.0-3+b1 ii libjemalloc2 5.2.1-1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libopenal11:1.19.1-1+b1 ii libopencolorio1v5 1.1.1~dfsg0-6+b1 ii libopenexr24 2.3.0-6 ii libopenimageio2.1 2.1.16.0~dfsg0-1 ii libopenjp2-7 2.3.1-1 ii libopenvdb7.0 7.0.0-3+b1 ii libosdcpu3.4.33.4.3-3 ii libosdgpu3.4.33.4.3-3 ii libpcre3 2:8.39-13 ii libpng16-16 1.6.37-2 ii libpython3.8 3.8.3-1 ii libsdl2-2.0-0 2.0.12+dfsg1-1 ii libsndfile1 1.0.28-8 ii libspnav0 0.2.3-1+b2 ii libstdc++610.1.0-4 ii libswscale5 7:4.3-2 ii libtbb2 2020.2-2 ii libtiff5 4.1.0+git191117-2 ii libx11-6 2:1.6.9-2+b1 ii libxfixes31:5.0.3-2 ii libxi62:1.7.10-1 ii libxml2 2.9.10+dfsg-5+b1 ii libxrender1 1:0.9.10-1 ii libxxf86vm1 1:1.1.4-1+b2 ii zlib1g1:1.2.11.dfsg-2 blender recommends no packages. blender suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#959842: tweeper: warnings with Facebook: Attribute data-referrer redefined in Entity
On Mon, 11 May 2020 11:14:06 +0800 Paul Wise wrote: > On Mon, 2020-05-11 at 00:26 +0200, Antonio Ospite wrote: > > > these warnings are kind of expected, it's the PHP XML parser which > > tells that the document may not be 100% standard compliant. > > I see, that seems reasonable I guess. > > > If they are too distracting maybe I can add a verbose option and silence > > them by default. I am the upstream too. > > For compatibility with scripts that may be using those warnings in some > way, I would instead add an option to silence the warnings. > I added a '-v <0|1>' option to tweeper that can be used to silence the verbose output, you can pass '-v 0' to disable the ouptut of those XML validation errors. I also restored some support for scraping twitter.com which stopped working after the twitter UI update from June 1st 2020. For now the code is in the master branch on: https://git.ao2.it/tweeper.git/ I still need to fix a couple of issues and then I'll update the Debian package in the next few days. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#962074: blender: crash in an assertion and doubt about CMAKE_BUILD_TYPE
Package: blender Version: 2.82.a+dfsg-1+b2 Severity: normal Tags: upstream Dear Maintainer, I ran into the upstream bug T75822[1] which is caused by an assertion. TBH being able to reproduce that bug with the blender executable shipped in Debian was a little surprising because it is supposed to only happen in debug builds. The assertion is enabled in Debian because dh runs cmake with CMAKE_BUILD_TYPE=None which in particular results in NDEBUG not being defined, which makes asserts() to run. It turns out that having CMAKE_BUILD_TYPE=None by default is on purpose[2] to make sure that cmake does not blindly override global compilation flags if the packager didn't ask that explicitly, some discussion can be found in [3]. My direct concern would be to just have blender not crashing, and upstream is working on a fix[4] for that. However the issue also raised a question about whether a Release build type should be used for the blender Debian executable; or if at least assertions should be disabled by defining NDEBUG. The upstream maintainer for the linux platform would also be interested[5] in this. Do you have an opinion? Thanks, Antonio [1] https://developer.blender.org/T75822 [2] https://sources.debian.org/src/debhelper/13.1/lib/Debian/Debhelper/Buildsystem/cmake.pm/#L16 [3] https://github.com/ros-infrastructure/bloom/issues/327 [4] https://developer.blender.org/D7595 [5] https://developer.blender.org/T75822#942660 -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.6.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages blender depends on: ii blender-data 2.82.a+dfsg-1 ii fonts-dejavu 2.37-2 ii libavcodec58 7:4.2.2-1+b1 ii libavdevice58 7:4.2.2-1+b1 ii libavformat58 7:4.2.2-1+b1 ii libavutil56 7:4.2.2-1+b1 ii libboost-locale1.67.0 1.67.0-18 ii libc6 2.30-8 ii libfftw3-double3 3.3.8-2 ii libfreetype6 2.10.1-2 ii libgcc-s1 10.1.0-3 ii libgl11.3.1-1 ii libglew2.12.1.0-4+b1 ii libgomp1 10.1.0-3 ii libilmbase24 2.3.0-6 ii libjack0 [libjack-0.125] 1:0.125.0-3+b1 ii libjemalloc2 5.2.1-1 ii libjpeg62-turbo 1:1.5.2-2+b1 ii libopenal11:1.19.1-1+b1 ii libopencolorio1v5 1.1.1~dfsg0-6+b1 ii libopenexr24 2.3.0-6 ii libopenimageio2.1 2.1.15.0~dfsg0-1 ii libopenjp2-7 2.3.1-1 ii libopenvdb7.0 7.0.0-3 ii libosdcpu3.4.33.4.3-3 ii libosdgpu3.4.33.4.3-3 ii libpcre3 2:8.39-12+b1 ii libpng16-16 1.6.37-2 ii libpython3.8 3.8.3-1 ii libsdl1.2debian 1.2.15+dfsg2-5 ii libsndfile1 1.0.28-8 ii libspnav0 0.2.3-1+b2 ii libstdc++610.1.0-3 ii libswscale5 7:4.2.2-1+b1 ii libtbb2 2020.2-2 ii libtiff5 4.1.0+git191117-2 ii libx11-6 2:1.6.9-2+b1 ii libxfixes31:5.0.3-2 ii libxi62:1.7.9-1 ii libxml2 2.9.10+dfsg-5 ii libxrender1 1:0.9.10-1 ii libxxf86vm1 1:1.1.4-1+b2 ii zlib1g1:1.2.11.dfsg-2 blender recommends no packages. blender suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#959842: tweeper: warnings with Facebook: Attribute data-referrer redefined in Entity
On Wed, 06 May 2020 11:37:34 +0800 Paul Wise wrote: > Package: tweeper > Version: 1.4.1-1 > Severity: normal > Usertags: warnings > > When I run tweeper against Facebook, I get a number of warnings: > > $ tweeper https://www.facebook.com/facebook > PHP Warning: Error 42: Attribute data-referrer redefined in Entity, line 22 > in /usr/share/php/tweeper/src/Tweeper.php on line 257 Hi, these warnings are kind of expected, it's the PHP XML parser which tells that the document may not be 100% standard compliant. If they are too distracting maybe I can add a verbose option and silence them by default. I am the upstream too. About the empty result, please see below. > > https://facebook.com;> > > Tweeper > Facebook - Home | Facebook > https://www.facebook.com/facebook/ > > > Facebook - Home | Facebook > https://www.facebook.com/facebook/ > > https://scontent-syd2-1.xx.fbcdn.net/v/t1.0-1/p200x200/87284588_124830725745195_9124219877853233152_n.png?_nc_cat=1_nc_sid=dbb9e7_nc_ohc=3tjbRDJdk0sAX8fvvm0_nc_ht=scontent-syd2-1.xxoh=aeac13e958ded89318cbde3c630294ecoe=5ED6584F > > > > IIRC tweeper only supports "posts" on public Facebook pages, for example the following command successfully scrapes the posts: $ tweeper https://www.facebook.com/facebook/posts/ Maybe it would be useful to add support for the home page or for videos and photos pages, but I am not sure I have the motivation to do that. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#939748: Additional information.
On Sat, 11 Apr 2020 12:34:49 + "Gong S." wrote: > The problem with the OTB format is that there are spacing issues. Also > if you do so, the same font would appear twice. > I've seen spacing problems with the TTF version, but the OpenType version converted locally from the original bitmap font seems OK, at least for what I do. Can you elaborate on what spacing issues you observed? Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#939748: Newest version breaks rendering of bitmap fonts in GTK applications.
On Sun, 08 Sep 2019 11:20:28 + "Gong S." wrote: > The newest version in the experimental repo, 1.44.6-1, breaks the > displaying of XLFD bitmap fonts in GTK applications. > Pango 1.44.7-3 has been uploaded to unstable so I expect this will break even more setups. > If you set the UI font to a bitmap font (Fixed) in /etc/gtk2/gtkrc, > all characters are replaced by empty glyphs. > A simpler use case is people using bitmap fonts in gnome-terminal, I for example was using xfonts-terminus. For the discussion on the upstream issue tracker refer to https://gitlab.gnome.org/GNOME/pango/issues/386 One possible solution discussed there is to use OpenType versions of the bitmap font, these are still supported. Fedora has some info about converting bitmap fonts to OpenType: https://fedoraproject.org/wiki/BitmapFontConversion For Terminus I was able to convert it locally and make it work with Pango: https://superuser.com/a/1539389 So the issue could be fixed at the font level, wrt. Terminus I will try to have an otf variant uploaded to Debian. I hope this info is useful for other people missing bitmap fonts. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#930492: marked as pending in mingw-w64
On Sat, 11 Jan 2020 19:33:51 + Stephen Kitt wrote: > Control: tag -1 pending > > Hello, > > Bug #930492 in mingw-w64 reported by you has been fixed in the > Git repository and is awaiting an upload. You can see the commit > message below and you can check the diff of the fix at: > > https://salsa.debian.org/mingw-w64-team/mingw-w64/commit/17f8832bff1d2e6eadfb878f7d5afb056d200364 > Hi, any ETA for an upload with this fix in? Thanks, Antonio > > Ship our own pkg-config-crosswrapper > > Closes: #930492 > > > (this message was generated automatically) > -- > Greetings > > https://bugs.debian.org/930492 > -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#942727: sane-backends: New upstream release 1.0.28 available
Package: src:sane-backends Followup-For: Bug #942727 Hi, I noticed that the maintainer already has some packaging work done for the new upstream release, so I tried building updated packages locally and I think the result is good enough. For those who need the newer code and don't want to wait for the maintainer upload here are some instructions for building updated packages locally. You would need 'git-buildpackage' and 'pbuilder'. I decline any responsibility for any damage. :) Create a pbuilder base: $ DIST=sid ARCH=amd64 BUILDER=pbuilder git pbuilder create --extrapackages "ca-certificates" Check out the latest debian source package and build it. $ mkdir ~/debian-workspace $ cd debian-workspace $ git clone git://jff.email/opt/git/sane-backends.git $ cd sane-backends $ git checkout release/experimental/1.0.28-1_experimental1 $ DIST=sid ARCH=amd64 BUILDER=pbuilder gbp buildpackage --git-debian-branch="release/experimental/1.0.28-1_experimental1" --git-upstream-branch=upstream --git-pbuilder -d You will find the resulting packages in ../build-area/ which can be installed with: $ sudo dpkg -i ../build-area/*.deb Hopefully you can use your scanner now. Dear Maintainer, I noticed there are still some minor lintian warnings here and there, if you need some help addressing them just let me know. Thanks, Antonio -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.4.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#931211: s2s connections are broken after upgrading to buster
Package: ejabberd Followup-For: Bug #931211 Hi, while taking a look at this I run into an interesting discussion here: https://github.com/processone/ejabberd/issues/528 The scenario is different but the log message matches the one in this report. In that case the problem seemed to be related to name resolution in erlang, and not strictly an ejabberd issue. The fact that the issue here started with a buster upgrade might be due to a change in behavior in erlang internals, which might have broken ejabberd assumptions is some corner case. The log message posted by Marco points out to this line in erlang: https://sources.debian.org/src/erlang/1:21.2.6+dfsg-1/lib/kernel/src/inet_dns.erl/#L694 And the "empty" label mentioned in the comment could be the last entry in the log message: ... [<<"_xmpps-server">>,<<"_tcp">>,<<"jabber">>,<<"seeweb">>,<<"it">>,<<>>] In the discussion above, one possible cause is said to be extra trailing dots in FQDNs. Is it possible that the issue Marco is experiencing is caused by something like that? I didn't notice anything strange in posted config, but what about DNS records or entries in /etc/hosts? Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#942727: sane-backends: New upstream release 1.0.28 available
Source: sane-backends Severity: wishlist Dear Maintainer, upstream released SANE-Backends-1.0.28 on 2019-07-31. It supports many new scanners, including mine, it would be great to have the new version packaged. Thank you, Antonio -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#941840: usb.ids: New upstream version available
Package: usb.ids Version: 2019.07.27-1 Severity: wishlist Dear Maintainer, upstream released a new usb.ids file on 2019.10.05 with some ids I contributed. It would be great if we could have it in Debian at some point. Thank you and keep up the good work, Antonio P.S. Would you accept a watch file for the package? Is the source package somewhere in a git repository? -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#939698: [pkg-php-pear] Bug#939698: lintian: warning about pkg-php-tools versioned dependency conflicts with cme suggestion
On Sun, 8 Sep 2019 21:57:49 +0200 Mathieu Parent wrote: > Le dim. 8 sept. 2019 à 02:25, David Prévot a écrit : > > > > Le 07/09/2019 à 11:00, Antonio Ospite a écrit : > > > Package: lintian > > […] > > > one of my packages build-depends on pkg-php-tools, and I used to have > > > that as a versioned dependency, as suggested by this lintian warning: > > > > > > W: tweeper source: pear-package-feature-requires-newer-pkg-php-tools (>= > > > 1.7~) for Composer package support > > > > > > However I found out that running `cme check dpkg` on said package > > > suggests to remove the versioned dependency because it has become > > > unnecessary: > > > > It has become unnecessary since at least oldoldstable, so full ack. I’m > > not the pkg-php-tools maintainer, just a member of the PHP PEAR (and > > Composer) team taking care of ~100 of PHP library packages. > > Acking too as the main author and maintainer of pkg-php-tools. > Thanks David and Mathieu for the prompt reply. And thank you Chris for being awesome: https://salsa.debian.org/lintian/lintian/commit/6cac2636b44942507d5e3fd9085bac40c95f5be8 The warning will be removed from the next lintian release. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#939698: lintian: warning about pkg-php-tools versioned dependency conflicts with cme suggestion
Package: lintian Version: 2.20.0 Severity: wishlist Dear Maintainer, one of my packages build-depends on pkg-php-tools, and I used to have that as a versioned dependency, as suggested by this lintian warning: W: tweeper source: pear-package-feature-requires-newer-pkg-php-tools (>= 1.7~) for Composer package support However I found out that running `cme check dpkg` on said package suggests to remove the versioned dependency because it has become unnecessary: --- Warning in 'control source Build-Depends:1': unnecessary greater-than versioned dependency: pkg-php-tools (>= 1.7~). Debian has oldoldstable -> 1.28; oldstable -> 1.35; stable -> 1.37; unstable -> 1.37; testing -> 1.37; Offending value: 'pkg-php-tools (>= 1.7~)' --- So maybe the lintian warning has become outdated? A comment from the Debian PHP maintainer would be useful to sort this out and decide whether to drop the warning from lintian. CCing: Debian PHP PEAR Maintainers Thanks, Antonio -- System Information: Debian Release: bullseye/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 5.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages lintian depends on: ii binutils 2.32.51.20190821-2 ii bzip21.0.8-2 ii diffstat 1.62-1+b1 ii dpkg 1.19.7 ii dpkg-dev 1.19.7 ii file 1:5.37-5 ii gettext 0.19.8.1-9 ii gpg 2.2.17-3 ii intltool-debian 0.35.0+20060710.5 ii libapt-pkg-perl 0.1.36+b1 ii libarchive-zip-perl 1.64-1 ii libcapture-tiny-perl 0.48-1 ii libcgi-pm-perl 4.44-1 ii libclass-accessor-perl 0.51-1 ii libclone-perl0.41-1+b1 ii libdpkg-perl 1.19.7 ii libemail-valid-perl 1.202-1 ii libfile-basedir-perl 0.08-1 ii libfile-find-rule-perl 0.34-1 ii libio-async-loop-epoll-perl 0.20-1 ii libio-async-perl 0.74-1 ii libipc-run-perl 20180523.0-1 ii liblist-compare-perl 0.53-1 ii liblist-moreutils-perl 0.416-1+b4 ii libmoo-perl 2.003004-2 ii libpath-tiny-perl0.108-1 ii libtext-levenshtein-perl 0.13-1 ii libtimedate-perl 2.3000-2 ii libtry-tiny-perl 0.30-1 ii libtype-tiny-perl1.004004-1 ii liburi-perl 1.76-1 ii libxml-simple-perl 2.25-1 ii libyaml-libyaml-perl 0.80+repack-1 ii man-db 2.8.7-3 ii patchutils 0.3.4-2+b1 ii perl [libdigest-sha-perl]5.28.1-6 ii t1utils 1.41-3 ii xz-utils 5.2.4-1+b1 Versions of packages lintian recommends: ii libperlio-gzip-perl 0.19-1+b5 Versions of packages lintian suggests: pn binutils-multiarch ii libhtml-parser-perl3.72-3+b3 ii libtext-template-perl 1.55-1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#923851: RFP: ghidra -- Ghidra is a software reverse engineering framework
On Thu, 21 Mar 2019 11:22:28 +0800 Yangfl wrote: > I'm willing to package it, as long as they publish its source! > The source code is public now: https://github.com/NationalSecurityAgency/ghidra No idea if it there has been any auditing yet tho. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#826556: please give possibility to not file bootstrapped file as ~/.mrconfig
On Mon, 06 Jun 2016 13:23:08 +0200 Marc Haber wrote: > Package: myrepos > Version: 1.20160123 > Severity: wishlist > > Hi, > Hi Marc, just commenting as I too noticed the same issue. > when I use mr bootstrap to fetch the initial mr configuration, the > downloaded file is put in the local file system as ~/.mrconfig. This > prevents the actual repositories to have a ~/.mrconfig themselves (mr > refuses to overwrite untracked files), which results in ~/.mrconfig to > not be under version control on the actual client. > > Additionally, the bootstrapped file needs to be the final .mrconfig > that is being used in every day use, which causes synchonization > efforts to keep the .mrconfig and other mr configuration (which is > likely to come from a vcsh repo) in sync. And, the bootstrapped > .mrconfig file is likely to need --untrusted since it will most > probably contain include statements, for example. > FWIW the vcsh case can be handled with a pre-merge hook: https://github.com/RichiH/vcsh/issues/190 > mr bootstrap seems to be a rarely used feature (I wasn't able to get a > reply to some of my questions on mailing list and IRC channel), so it > might not be a big issue to change mr bootstrap's behevior in this > regard. For example. mr could be changed to read an .mrbootstrap > config file iff .mrconfig does not exist, and mr bootstrap could > downlaod to .mrbootstrap instead of .mrconfig. > Downloading the bootstrap file to a temporary location could also work. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#924540: xserver-xorg-video-radeon: undefined symbol: glamor_finish when AccelMethod is EXA and TearFree is on
On Fri, 15 Mar 2019 12:54:19 +0100 Michel Dänzer wrote: > On 2019-03-13 11:28 p.m., Antonio Ospite wrote: [...] > > In particular, having both the settngs below in > > /usr/share/X11/xorg.conf.d/10-radeon.conf makes Xorg fail to start when > > using the xserver-xorg-video-radeon driver: > > > > Option "AccelMethod" "EXA" > > Option "TearFree" "on" > > > > Anyway, removing these options fixes the issue for me. > > > > Not sure if this is a regression [...] > > It is, thanks for the report. Fixed by > https://gitlab.freedesktop.org/xorg/driver/xf86-video-ati/commit/79bc0e054f37026377d54cac6cd8127d4aa9baca > . > Great, thanks. > That said, I recommend against forcing EXA, unless there's a good reason > for it. glamor generally works better these days. > > Also, FWIW, TearFree no longer needs to be enabled in xorg.conf but can > be configured dynamically with xrandr. See the radeon manpage on TearFree. > Yeah it was some stale config I had from the past when I was maybe trying to solve some compatibility issue with some program, I don't really remember. I now removed those settings. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#924540: xserver-xorg-video-radeon: undefined symbol: glamor_finish when AccelMethod is EXA and TearFree is on
ut E: PRODUCT=0/0/0/0 E: NAME="HDA ATI HDMI HDMI/DP,pcm=3" E: PHYS="ALSA" E: PROP=0 E: EV=21 E: SW=140 E: MODALIAS=input:bvpe-e0,5,kramlsfw6,8, E: USEC_INITIALIZED=5242410 E: ID_INPUT=1 E: ID_INPUT_SWITCH=1 E: ID_PATH=pci-:05:00.1 E: ID_PATH_TAG=pci-_05_00_1 E: ID_FOR_SEAT=input-pci-_05_00_1 E: TAGS=:seat: P: /devices/pci:00/:00:0e.0/:05:00.1/sound/card1/input5/event5 N: input/event5 L: 0 E: DEVPATH=/devices/pci:00/:00:0e.0/:05:00.1/sound/card1/input5/event5 E: SUBSYSTEM=input E: DEVNAME=/dev/input/event5 E: MAJOR=13 E: MINOR=69 E: USEC_INITIALIZED=5862168 E: ID_INPUT=1 E: ID_INPUT_SWITCH=1 E: ID_PATH=pci-:05:00.1 E: ID_PATH_TAG=pci-_05_00_1 E: LIBINPUT_DEVICE_GROUP=0/0/0:ALSA E: TAGS=:power-switch: P: /devices/platform/i8042/serio0/input/input0 L: 0 E: DEVPATH=/devices/platform/i8042/serio0/input/input0 E: SUBSYSTEM=input E: PRODUCT=11/1/1/ab41 E: NAME="AT Translated Set 2 keyboard" E: PHYS="isa0060/serio0/input0" E: PROP=0 E: EV=120013 E: KEY=40200 3803078f800d001 fedfffef fffe E: MSC=10 E: LED=7 E: MODALIAS=input:b0011v0001p0001eAB41-e0,1,4,11,14,k71,72,73,74,75,76,77,79,7A,7B,7C,7D,7E,7F,80,8C,8E,8F,9B,9C,9D,9E,9F,A3,A4,A5,A6,AC,AD,B7,B8,B9,D9,E2,ram4,l0,1,2,sfw E: USEC_INITIALIZED=1762269 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_BUS=i8042 E: ID_SERIAL=noserial E: ID_PATH=platform-i8042-serio-0 E: ID_PATH_TAG=platform-i8042-serio-0 E: ID_FOR_SEAT=input-platform-i8042-serio-0 E: TAGS=:seat: P: /devices/platform/i8042/serio0/input/input0/event0 N: input/event0 L: 0 S: input/by-path/platform-i8042-serio-0-event-kbd E: DEVPATH=/devices/platform/i8042/serio0/input/input0/event0 E: SUBSYSTEM=input E: DEVNAME=/dev/input/event0 E: MAJOR=13 E: MINOR=64 E: USEC_INITIALIZED=5749110 E: ID_INPUT=1 E: ID_INPUT_KEY=1 E: ID_INPUT_KEYBOARD=1 E: ID_BUS=i8042 E: ID_SERIAL=noserial E: ID_PATH=platform-i8042-serio-0 E: ID_PATH_TAG=platform-i8042-serio-0 E: XKBMODEL=pc105 E: XKBLAYOUT=us E: BACKSPACE=guess E: LIBINPUT_DEVICE_GROUP=11/1/1:isa0060/serio0 E: DEVLINKS=/dev/input/by-path/platform-i8042-serio-0-event-kbd E: TAGS=:power-switch: P: /devices/platform/pcspkr/input/input4 L: 0 E: DEVPATH=/devices/platform/pcspkr/input/input4 E: SUBSYSTEM=input E: PRODUCT=10/1f/1/100 E: NAME="PC Speaker" E: PHYS="isa0061/input0" E: PROP=0 E: EV=40001 E: SND=6 E: MODALIAS=input:b0010v001Fp0001e0100-e0,12,kramls1,2,fw E: USEC_INITIALIZED=5022853 E: ID_INPUT=1 E: ID_SERIAL=noserial E: ID_PATH=platform-pcspkr E: ID_PATH_TAG=platform-pcspkr E: ID_FOR_SEAT=input-platform-pcspkr E: TAGS=:seat: P: /devices/platform/pcspkr/input/input4/event4 N: input/event4 L: 0 S: input/by-path/platform-pcspkr-event-spkr E: DEVPATH=/devices/platform/pcspkr/input/input4/event4 E: SUBSYSTEM=input E: DEVNAME=/dev/input/event4 E: MAJOR=13 E: MINOR=68 E: USEC_INITIALIZED=5639302 E: ID_INPUT=1 E: ID_SERIAL=noserial E: ID_PATH=platform-pcspkr E: ID_PATH_TAG=platform-pcspkr E: LIBINPUT_DEVICE_GROUP=10/1f/1:isa0061 E: DEVLINKS=/dev/input/by-path/platform-pcspkr-event-spkr DRM Information from dmesg: --- -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages xserver-xorg-video-radeon depends on: ii libc6 2.28-8 ii libdrm-radeon1 2.4.97-1 ii libgbm118.3.4-2 ii libudev1 241-1 ii xserver-xorg-core [xorg-video-abi-24] 2:1.20.4-1 xserver-xorg-video-radeon recommends no packages. Versions of packages xserver-xorg-video-radeon suggests: ii firmware-amd-graphics 20190114-1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#919880: gstreamer1.0-pipewire: segfault when pipewire is not installed
Package: gstreamer1.0-pipewire Version: 0.2.5-1 Severity: normal Dear Maintainer, I installed gstreamer1.0-pipewire and tried to inspect piepwiresrc with gst-inspect-1.0 and I got a segfault: --- $ gdb -ex run --args gst-inspect-1.0 pipewiresrc GNU gdb (Debian 8.2-1) 8.2 ... Reading symbols from gst-inspect-1.0...Reading symbols from /usr/lib/debug/.build-id/0f/35e5a3a648136149cd078270645dc16506eb5a.debug...done. done. Starting program: /usr/bin/gst-inspect-1.0 pipewiresrc [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". can't load /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: /usr/lib/x86_64-linux-gnu/spa/support/libspa-support.so: impossibile aprire il file oggetto condiviso: File o directory non esistente Program received signal SIGSEGV, Segmentation fault. 0x7756b006 in pw_thread_loop_new () from /usr/lib/x86_64-linux-gnu/libpipewire-0.2.so.1 (gdb) bt #0 0x7756b006 in pw_thread_loop_new () at /usr/lib/x86_64-linux-gnu/libpipewire-0.2.so.1 #1 0x775cc4fa in () at /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstpipewire.so #2 0x77e340b7 in g_type_create_instance (type=) at ../../../gobject/gtype.c:1864 #3 0x77e16518 in g_object_new_internal (class=class@entry=0x557e8f50, params=params@entry=0x0, n_params=n_params@entry=0) at ../../../gobject/gobject.c:1805 #4 0x77e17c95 in g_object_new_with_properties (object_type=0x557e8140 [GstPipeWireSrc/GstPushSrc/GstBaseSrc/GstElement/GstObject/GInitiallyUnowned], n_properties=0, names=names@entry=0x0, values=values@entry=0x0) at ../../../gobject/gobject.c:1973 #5 0x77e18701 in g_object_new (object_type=, first_property_name=first_property_name@entry=0x0) at ../../../gobject/gobject.c:1645 #6 0x77eb5672 in gst_element_factory_create (factory=0x557decb0 [GstElementFactory], name=0x0) at gstelementfactory.c:372 #7 0xb8e3 in print_element_info (feature=, print_names=0) at gst-inspect.c:1375 #8 0x8ed7 in print_feature_info (print_all=0, feature_name=0x7fffe34d "pipewiresrc") at gst-inspect.c:1338 #9 0x8ed7 in main (argc=, argv=) at gst-inspect.c:1818 (gdb) --- The problem can be easily resolved by installing the "pipewire" package. I am reporting it because in case of a missing library I would have expected a failure but not a segfault. Maybe pipewire should also be a Depend or a Recommend for gstreamer1.0-pipewire or for libpipewire-0.2-1 (the segfault is in libpipewire-0.2.so.1). Not sure if this is an upstream problem too, I have no experience with pipewire. Anyways, thank you for the packages, they are useful to start playing with pipewire. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gstreamer1.0-pipewire depends on: ii libc6 2.28-5 ii libglib2.0-02.58.2-4 ii libgstreamer-plugins-base1.0-0 1.14.4-1 ii libgstreamer1.0-0 1.14.4-1 ii libpipewire-0.2-1 0.2.5-1 gstreamer1.0-pipewire recommends no packages. gstreamer1.0-pipewire suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#919275: kbd: unicode_start and unicode_stop are in different directories
Package: kbd Version: 2.0.4-4 Severity: wishlist Dear Maintainer, I found it weird that unicode_start and unicode_stop are in different directories, since they are symmetric scripts I would have expected to find them in the same directory, either /bin or /usr/bin. Thank you, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages kbd depends on: ii libc6 2.28-5 Versions of packages kbd recommends: ii console-setup 1.188 kbd suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#918994: uscan: --report --dehs does not work with pgpmode=previous
On Fri, 11 Jan 2019 16:30:49 +0100 Antonio Ospite wrote: [...] > P.S. > > I noticed that in the inkscape case signature verification is performed > even if "--no-signature" is passed: > OK, this is by design, and documented in the help text, so ignore this one comment for now. Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#918994: uscan: --report --dehs does not work with pgpmode=previous
5-1 ii patch 2.7.6-3 ii python3-apt 1.7.0 ii python3-debian 0.1.33 ii python3-magic 2:0.4.15-2 ii python3-requests2.20.0-2 ii python3-unidiff 0.5.4-1 ii python3-xdg 0.25-4 ii strace 4.21-1 ii unzip 6.0-21 ii wget1.20.1-1 ii xz-utils5.2.2-1.3 Versions of packages devscripts suggests: ii adequate 0.15.1 pn autopkgtest pn bls-standalone ii build-essential 12.5 pn check-all-the-things pn cvs-buildpackage pn devscripts-el pn diffoscope pn disorderfs pn dose-extra ii duck 0.13 pn faketime ii gnuplot 5.2.6+dfsg1-1 ii gnuplot-qt [gnuplot] 5.2.6+dfsg1-1 pn how-can-i-help ii libauthen-sasl-perl 2.1600-1 pn libdbd-pg-perl ii libfile-desktopentry-perl0.22-1 pn libnet-smtps-perl pn libterm-size-perl ii libtimedate-perl 2.3000-2 pn libyaml-syck-perl ii mailutils [mailx]1:3.5-2 pn mozilla-devscripts pn mutt ii openssh-client [ssh-client] 1:7.9p1-4 ii piuparts 0.95 pn postgresql-client pn quilt pn ratt pn reprotest pn svn-buildpackage pn w3m -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#873341: SBT is uninstallable; depends on nonexistent packages
On Thu, 3 Jan 2019 13:03:42 +0100 Antonio Ospite wrote: > On Thu, 3 Jan 2019 11:45:29 +0100 > Emmanuel Bourg wrote: > [...] > > If someone wants to pick the ball the next steps are to: > > 1. build SBT 1.0 without the embedded libraries > > 2. build Scala 2.12 > > > > I was wondering if downgrading scala to 2.10 might be somewhat useful > and less work. Fedora is also still shipping scala 2.10. > I tried installing scala 2.10.5 from debian snapshot: https://snapshot.debian.org/archive/debian/20150606T044147Z/pool/main/s/scala/ However the sbt from debian was built with scala 2.11 and it will still look for that version at runtime. So if sbt should also be re-compiled to make the combination scala_2.10+sbt_0.13 work it might as well be worth using newer versions as Emmanuel suggested. I think I'll stop my investigations for now. Thank you, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#873341: SBT is uninstallable; depends on nonexistent packages
On Thu, 3 Jan 2019 11:45:29 +0100 Emmanuel Bourg wrote: > Hi Antonio, > > Le 03/01/2019 à 10:59, Antonio Ospite a écrit : > > > Are there any plans to improve the situation? > > We lack contributors to maintain the Scala ecosystem in Debian and some > help would be really welcome. I spent some time updating our scala > package but I'm not a Scala developer and I don't have the time to look > into this anymore. > Thank you Emmanuel, I am not a Scala developer either, I just wanted to build one project written in it, and I was trying to do so using the tools provided in Debian. > If someone wants to pick the ball the next steps are to: > 1. build SBT 1.0 without the embedded libraries > 2. build Scala 2.12 > I was wondering if downgrading scala to 2.10 might be somewhat useful and less work. Fedora is also still shipping scala 2.10. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#915504: sbt: Fails to detect version of java
Package: sbt Version: 0.13.13-2 Followup-For: Bug #915504 Dear Maintainer, the issue has been fixed upstream: https://github.com/sbt/sbt-launcher-package/commit/5a0bde442dec7d9a1bdc35655541902fb873172a#diff-edd0ab5838b2fa424d30f94df800e1f9 Some other fixes are also upstream: https://github.com/sbt/sbt-launcher-package/commit/a638ad49ac484ba87e512f6dfebf8aa83e4b3ad7#diff-edd0ab5838b2fa424d30f94df800e1f9 https://github.com/sbt/sbt-launcher-package/commit/21cf71e384b8d3dba4c56d167837a9236d294c9d#diff-edd0ab5838b2fa424d30f94df800e1f9 Since sbt-launch-lib.bash is a self contained script, creating a patch from the latest upstream version should not be too problematic: $ cd /tmp $ wget https://raw.githubusercontent.com/sbt/sbt-launcher-package/master/src/universal/bin/sbt-launch-lib.bash $ diff -u /usr/share/sbt/bin/sbt-launch-lib.bash sbt-launch-lib.bash Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sbt depends on: ii libsbt-java0.13.13-2 ii openjdk-8-jre [java8-runtime] 8u191-b12-2 sbt recommends no packages. sbt suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#873341: SBT is uninstallable; depends on nonexistent packages
On Fri, 07 Dec 2018 22:57:34 +0100 Antonio Ospite wrote: > Package: sbt > Version: 0.13.13-2 > Followup-For: Bug #873341 > > Dear Maintainer, > > just a curiosity, are you trying to package the latest 0.13.x version or > the newer 1.x version? https://www.scala-sbt.org/download.html > BTW, it looks like sbt is actually installable again in debian unstable, as its dependencies libsbt-test-interface-java and libscala-tools-sbinary-java are readily available. So this bug report could be closed IMHO, and a new one about using a new upstream version may be opened. Anyways from the little I've seen, for sbt to be really usable with the majority of projects, the combination of sbt and scala versions also matters. For instance, some downloadable packages are not available for the combination sbt_0.13 and scala_2.11 which is what we have in debian. The most supported combinations seem to be: - sbt_0.13 + scala_2.10 - sbt_1.0 + scala_2.12 An example of this can be seen by trying to locally build sbt itself, or scala[1], or the kaitai compiler mentioned below. [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845113#22 > JFYI I would use sbt to try to build the Kitai Struct compiler: > https://github.com/kaitai-io/kaitai_struct_compiler > Are there any plans to improve the situation? Thank you, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#845113: scala: Upgrade to 2.12.x
Package: scala Version: 2.11.12-4 Followup-For: Bug #845113 Dear Maintainer, I tried using the 'sbt' from debian to build scala 2.12.x and I get this error: --- ... [warn] module not found: com.eed3si9n#sbt-buildinfo;0.6.1 [warn] typesafe-ivy-releases: tried [warn] https://repo.typesafe.com/typesafe/ivy-releases/com.eed3si9n/sbt-buildinfo/scala_2.11.x/sbt_0.13/0.6.1/ivys/ivy.xml [warn] sbt-plugin-releases: tried [warn] https://repo.scala-sbt.org/scalasbt/sbt-plugin-releases/com.eed3si9n/sbt-buildinfo/scala_2.11.x/sbt_0.13/0.6.1/ivys/ivy.xml [warn] debian-local-maven: tried [warn] file:/usr/share/maven-repo/com/eed3si9n/sbt-buildinfo_2.11.x_0.13/0.6.1/sbt-buildinfo-0.6.1.pom [info] Resolving org.scala-sbt#logic;debian ... [warn] :: [warn] :: UNRESOLVED DEPENDENCIES :: [warn] :: [warn] :: com.eed3si9n#sbt-buildinfo;0.6.1: not found [warn] :: [warn] [warn] Note: Some unresolved dependencies have extra attributes. Check that these dependencies exist with the requested attributes. [warn] com.eed3si9n:sbt-buildinfo:0.6.1 (scalaVersion=2.11.x, sbtVersion=0.13) [warn] [warn] Note: Unresolved dependencies path: [warn] com.eed3si9n:sbt-buildinfo:0.6.1 (scalaVersion=2.11.x, sbtVersion=0.13) (/home/ao2/WIP/scala/scala/project/project/plugins.sbt#L1-2) [warn]+- default:scala-build-build:0.1-SNAPSHOT (scalaVersion=2.11.x, sbtVersion=0.13) sbt.ResolveException: unresolved dependency: com.eed3si9n#sbt-buildinfo;0.6.1: not found ... --- the sbt-buildinfo plugin for sbt 0.13 is not available for scala 2.11: https://dl.bintray.com/sbt/sbt-plugin-releases/com.eed3si9n/sbt-buildinfo/scala_2.11/ But only for scala 2.10: https://dl.bintray.com/sbt/sbt-plugin-releases/com.eed3si9n/sbt-buildinfo/scala_2.10/ However this is only part of the problem, other dependencies too would need to be updated in debian, like libjarjar-java which now have a new upstream: https://github.com/pantsbuild/jarjar I know this is not really helpful, I just wanted to give sbt a try and see where we were at. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages scala depends on: ii libjline2-java 2.14.6-1 ii openjdk-8-jre-headless [java7-runtime-headless] 8u191-b12-2 ii scala-library2.11.12-4 ii scala-parser-combinators 1.0.3-3 ii scala-xml1.0.3-3 scala recommends no packages. Versions of packages scala suggests: pn scala-doc -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#892229: wireless-regdb: Missing support for kernel direct loading
Package: wireless-regdb Version: 2016.06.10-1 Followup-For: Bug #892229 Dear Maintainer, ping. An update to the latest master-2018-10-24[1] would fix this bug and #892475. If you need help I can find some time. Thanks, Antonio [1] https://git.kernel.org/pub/scm/linux/kernel/git/sforshee/wireless-regdb.git/ -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled wireless-regdb depends on no packages. wireless-regdb recommends no packages. Versions of packages wireless-regdb suggests: ii crda 3.18-1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#917399: bambootracker: Package description is too terse
Package: bambootracker Severity: wishlist Dear Maintainer, the package description could give some more context to help understanding right off the bat what the software is actually about (what is a YM2608?). I also suggested this upstream: https://github.com/rerrahkr/BambooTracker/pull/43 Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages bambootracker depends on: ii libc6 2.28-3 ii libgcc11:8.2.0-13 ii libqt5core5a 5.11.3+dfsg-2 ii libqt5gui5 5.11.3+dfsg-2 ii libqt5multimedia5 5.11.3-2 ii libqt5multimedia5-plugins 5.11.3-2 ii libqt5widgets5 5.11.3+dfsg-2 ii libstdc++6 8.2.0-13 bambootracker recommends no packages. bambootracker suggests no packages. -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#779416: dash: set -e breaks trap
On Tue, 16 Oct 2018 15:53:19 +0200 Antonio Ospite wrote: > Package: dash > Version: 0.5.10.2-1 > Followup-For: Bug #779416 > > Dear Maintainer, > [...] > I sent a tentative patch upstream which seems to fix the issue: > https://marc.info/?l=dash=153969445911884=2 > Upstream accepted the patch: https://marc.info/?l=dash=154476682007838=2 https://git.kernel.org/pub/scm/utils/dash/dash.git/commit/?id=06204f0c9f539fcb8cb532166656e80b81bd689a so this bug can be closed when a new upstream release becomes available. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#873341: SBT is uninstallable; depends on nonexistent packages
Package: sbt Version: 0.13.13-2 Followup-For: Bug #873341 Dear Maintainer, just a curiosity, are you trying to package the latest 0.13.x version or the newer 1.x version? https://www.scala-sbt.org/download.html JFYI I would use sbt to try to build the Kitai Struct compiler: https://github.com/kaitai-io/kaitai_struct_compiler Thank you, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sbt depends on: ii libsbt-java0.13.13-2 ii openjdk-8-jre [java8-runtime] 8u191-b12-2 sbt recommends no packages. sbt suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#913216: checkstyle: wrapper script gives warning about unrecognized JVM flavor
Package: checkstyle Version: 8.14-1 Severity: minor Dear Maintainer, when running checkstyle on Debian unstable I get this warning: --- $ checkstyle -c checkstyle-easy.xml file.java [warning] /usr/bin/checkstyle: JVM flavor 'sunmin5' not understood ... --- Everything seems to work fine, but the warning made me think that something was wrong with checkstyle itself while it's the wrapper scripts which gives it instead. Not sure what the cause is, this is the java version I am using: --- $ java --version openjdk 11.0.1 2018-10-16 OpenJDK Runtime Environment (build 11.0.1+13-Debian-2) OpenJDK 64-Bit Server VM (build 11.0.1+13-Debian-2, mixed mode, sharing) --- Thank you, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages checkstyle depends on: ii antlr 2.7.7+dfsg-9.2 ii default-jre-headless [java7-runtime-headless] 2:1.11-70 ii java-wrappers 0.3 ii libantlr4-runtime-java4.6-2 ii libcommons-beanutils-java 1.9.3-1 ii libcommons-cli-java 1.4-1 ii libcommons-lang3-java 3.8-1 ii libcommons-logging-java 1.2-2 ii libguava-java 19.0-1 ii openjdk-10-jre-headless [java7-runtime-headless] 10.0.2+13-2 ii openjdk-11-jre-headless [java7-runtime-headless] 11.0.1+13-2 checkstyle recommends no packages. Versions of packages checkstyle suggests: pn ant-optional pn junit4 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#913152: jsoup: New upstream version 1.11.3 available
Source: jsoup Severity: wishlist Dear Maintainer, a more recent upstream release of jsoup is available at https://jsoup.org/ There have been quite some fixes and performance improvements since version 1.10.2 available in Debian, it would be great if the package could be updated. Thank you, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#912155: svgwrite: New upstream release 1.2.0 available
Source: svgwrite Severity: wishlist Dear Maintainer, upstream has released version 1.2.0 which adds some useful new functionalities and fixes some bugs: https://github.com/mozman/svgwrite/releases/tag/v1.2.0 This s the upstream changelog: https://github.com/mozman/svgwrite/blob/v1.2.0/NEWS.rst If you need help to package it let me know and I'll see if I can find some time. I don't know if the new version also helps with https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911711 Thank you, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#779416: dash: set -e breaks trap
Package: dash Version: 0.5.10.2-1 Followup-For: Bug #779416 Dear Maintainer, I too noticed the issue with the following test script: --- #!/bin/dash set -e trap 'ret=$?; echo "EXIT: $ret"' EXIT trap 'exit 2' HUP INT QUIT PIPE TERM read variable --- I would expect the EXIT trap to be executed whan sending Ctrl-C, but dash does not do that, while bash and zsh do, with or without "set -e". I sent a tentative patch upstream which seems to fix the issue: https://marc.info/?l=dash=153969445911884=2 However I do not know the dash codebase very well, so a comment from upstream would be useful to understand if my change breaks something else. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages dash depends on: ii debianutils 4.8.6 ii dpkg 1.19.2 ii libc62.27-6 dash recommends no packages. dash suggests no packages. -- debconf information: * dash/sh: true -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#908516: Apparmor profile breaks print preview
Package: evince Version: 3.30.0-2 Followup-For: Bug #908516 Dear Maintainer, this bug also affects opening links in the external browser, which is rather annoying. For googling sake, here's the exact error message from the UI: Failed to execute child process “/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop” (Permission denied) And in the kernel log: [29389.904351] audit: type=1400 audit(1536848541.036:361): apparmor="DENIED" operation="exec" profile="/usr/bin/evince" name="/usr/lib/x86_64-linux-gnu/glib-2.0/gio-launch-desktop" pid=28068 comm="evince" requested_mask="x" denied_mask="x" fsuid=1000 ouid=0 The temporary solution provided the OP works well. Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evince depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.0-1 ii evince-common3.30.0-2 ii gsettings-desktop-schemas3.28.0-1 ii libatk1.0-0 2.30.0-1 ii libc62.27-6 ii libcairo-gobject21.15.12-1 ii libcairo21.15.12-1 ii libevdocument3-4 3.30.0-2 ii libevview3-3 3.30.0-2 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-4 ii libglib2.0-0 2.58.0-3 ii libgnome-desktop-3-173.30.0-1 ii libgtk-3-0 3.24.0-3 ii libnautilus-extension1a 3.30.0-2 ii libpango-1.0-0 1.42.4-3 ii libpangocairo-1.0-0 1.42.4-3 ii libsecret-1-00.18.6-2 ii shared-mime-info 1.9-2 Versions of packages evince recommends: ii dbus-user-session [default-dbus-session-bus] 1.12.10-1 ii dbus-x11 [dbus-session-bus] 1.12.10-1 Versions of packages evince suggests: ii gvfs 1.38.0-2 ii nautilus-sendto 3.8.6-2 ii poppler-data 0.4.9-2 ii unrar1:5.5.8-1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#888620: evince: apparmor profile prevents loading git-annex files
Package: evince Followup-For: Bug #888620 Dear OP, I am not the maintainer or anything, but I am curios, what are the permissions of the _destination_ file? I mean, what does "ls -l --dereference meltdown.pdf" say? Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.18.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages evince depends on: ii dconf-gsettings-backend [gsettings-backend] 0.30.0-1 ii evince-common3.30.0-2 ii gsettings-desktop-schemas3.28.0-1 ii libatk1.0-0 2.30.0-1 ii libc62.27-6 ii libcairo-gobject21.15.12-1 ii libcairo21.15.12-1 ii libevdocument3-4 3.30.0-2 ii libevview3-3 3.30.0-2 ii libgdk-pixbuf2.0-0 2.38.0+dfsg-4 ii libglib2.0-0 2.58.0-3 ii libgnome-desktop-3-173.30.0-1 ii libgtk-3-0 3.24.0-3 ii libnautilus-extension1a 3.30.0-2 ii libpango-1.0-0 1.42.4-3 ii libpangocairo-1.0-0 1.42.4-3 ii libsecret-1-00.18.6-2 ii shared-mime-info 1.9-2 Versions of packages evince recommends: ii dbus-user-session [default-dbus-session-bus] 1.12.10-1 ii dbus-x11 [dbus-session-bus] 1.12.10-1 Versions of packages evince suggests: ii gvfs 1.38.0-2 ii nautilus-sendto 3.8.6-2 ii poppler-data 0.4.9-2 ii unrar1:5.5.8-1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#908063: sylpheed: TLS connection to imap.gmail.com returns self-signed certificate with openssl 1.1.0
Package: sylpheed Version: 3.7.0-3+b1 Severity: important Tags: upstream patch Dear Maintainer, when using openssl 1.1.0 (now in Unstable) the gmail servers require clients to set the Server Name Indication, responding with an invalid self-signed certificate if this is not the case. Sylpheed does not set the SNI. Here is a link to the upstream bug report in which I provide a patch and a link to a better explanation: https://sylpheed.sraoss.jp/redmine/issues/306 Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.17.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages sylpheed depends on: ii libassuan0 2.5.1-2 ii libatk1.0-0 2.28.1-1 ii libc62.27-6 ii libcairo21.15.12-1 ii libcompfaceg11:1.5.2-5+b2 ii libenchant1c2a 1.6.0-11.1 ii libfontconfig1 2.13.0-5 ii libfreetype6 2.8.1-2 ii libfribidi0 1.0.5-3 ii libgdk-pixbuf2.0-0 2.36.12-2 ii libglib2.0-0 2.58.0-2 ii libgpg-error01.32-1 ii libgpgme11 1.11.1-1 ii libgtk2.0-0 2.24.32-3 ii libgtkspell0 2.0.16-1.2 ii libldap-2.4-22.4.46+dfsg-5 ii libonig5 6.8.2-1 ii libpango-1.0-0 1.42.4-2 ii libpangocairo-1.0-0 1.42.4-2 ii libpangoft2-1.0-01.42.4-2 ii libssl1.11.1.1~~pre9-1 ii pinentry-gtk21.1.0-1+b1 Versions of packages sylpheed recommends: ii aspell-it [aspell-dictionary] 2.4-20070901-0-3 ii bogofilter 1.2.4+dfsg1-13 ii bsfilter 1:1.0.19-2 ii ca-certificates20180409 ii sylpheed-i18n 3.7.0-3 Versions of packages sylpheed suggests: pn claws-mail-tools ii curl 7.61.0-1 pn sylpheed-doc ii sylpheed-plugins 3.7.0-3+b1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#884765: ITP: drupal-init-tools -- helper commands to create and install new Drupal projects
On Fri, 22 Dec 2017 15:18:12 -0600 Gunnar Wolf wrote: > Antonio Ospite dijo [Tue, Dec 19, 2017 at 11:45:52AM +0100]: > > (...) > > I am the upstream author of drupal-init-tool and I plan on maintaining > > the Debian package myself, but I am not a Debian Developer or a Debian > > Maintainer. > > > > I do have a sponsor who is kind enough to upload some other packages of > > mine, but if someone is interested in web stuff and want to sponsor me > > for this one, my usual sponsor and I would surely appreciate it. :) > > FWIW, as the maintainer of Drupal7 (FWIW, I requested for it to be > removed from unstable yesterday), I am interested in having it. I'm > currently away from home and with low network availability, but am > willing to look at the packaging sponsor your uploads if needed (but > expect end-of-the-year-time delays) Ping. I released upstream version 0.1.2 and updated the debian packaging in the debian/master branch to 0.1.2-1: https://git.ao2.it/drupal-init-tools.git/ https://git.ao2.it/drupal-init-tools.git/shortlog/refs/heads/debian/master drupal-init-tools now works better with modern MySQL/MariaDB versions, and with Drush 9. The old tutorial is still valid: https://ao2.it/en/blog/2017/08/02/drupal-init-tools-quick-and-easy-drupal-8-setup The package description can be improved, now it assumes that the user knows drupal 8 and how it is supposed to work, but I'd like to know if the package has any chances to be sponsored before putting more time into it. Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#900824: Empty twitter feeds
On Tue, 05 Jun 2018 10:03:03 -0400 Jim Paris wrote: > Package: tweeper > Version: 1.2.0-1 > Severity: normal > Tags: upstream patch > > Upstream patch is needed to continue to support Twitter: > > https://git.ao2.it/tweeper.git/commit/d9aa66bef1f3724e1714d4ae6b45fca98e0dcd11 > > Tweeper.php: update the User-Agent string to fix parsing twitter.com > > It looks like twitter.com started serving the mobile version of the site > to old browsers and Tweeper cannot parse that content. > > By using a more up to date User-Agent string twitter.com returns the > desktop version of the page which Tweeper can process without problems > > Thanks, > Jim Hi Jim, thanks for the reminder. I hope I can prepare a new release in the next days. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#894439: pitivi: fails to start with message "gtk not found on the system"
Package: pitivi Version: 0.99-2+b1 Severity: important Dear Maintainer, since GStreamer 1.14 pitivi may fail to start when freshly installed because of a missing dependency: $ sudo apt-get install pitivi $ LANG=C pitivi ERROR - The following hard dependencies are unmet: == - gtk not found on the system Missing soft dependency: - GSound not found on the system -> enables sound notifications when rendering is complete This is because the GStreamer gtk stuff has moved to a separate package, installing gstreamer1.0-gtk3 fixes the issue: $ sudo apt-get install gstreamer1.0-gtk3 Having an explicit dependency would be great. BTW I've seen other users bitten by this split in GStreamer plugins. I do like the split but maybe things can be improved a little: - Recommend or a least suggest the split packages from the one they are split from. - Use a more familiar naming? Someone proposed something like "gstreamer1.0-plugins-good-gtk3" but I am not sure if you meant to hide the -good/-bad/-ugly origin on purpose here. As always, thanks. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pitivi depends on: ii gir1.2-gdkpixbuf-2.02.36.11-2 ii gir1.2-ges-1.0 1.14.0-1 ii gir1.2-glib-2.0 1.56.0-2 ii gir1.2-gst-plugins-base-1.0 1.14.0-1 ii gir1.2-gstreamer-1.01.14.0-1 ii gir1.2-gtk-3.0 3.22.29-2 ii gir1.2-pango-1.01.42.0-1 ii gstreamer1.0-gl [gstreamer1.0-videosink]1.14.0-1 ii gstreamer1.0-gtk3 [gstreamer1.0-videosink] 1.14.0-1 ii gstreamer1.0-plugins-bad [gstreamer1.0-videosink] 1.14.0-1 ii gstreamer1.0-plugins-base 1.14.0-1 ii gstreamer1.0-plugins-good [gstreamer1.0-videosink] 1.14.0-1 ii gstreamer1.0-pulseaudio [gstreamer1.0-audiosink]1.14.0-1 ii gstreamer1.0-x [gstreamer1.0-videosink] 1.14.0-1 ii libc6 2.27-2 ii libcairo2 1.15.10-2 ii libglib2.0-02.56.0-4 ii libgstreamer-plugins-base1.0-0 1.14.0-1 ii libgstreamer1.0-0 1.14.0-1 ii libpython3.63.6.5~rc1-3 ii python3 3.6.5~rc1-1 ii python3-cairo 1.16.2-1 ii python3-dbus1.2.6-1 ii python3-gi 3.28.1-1 ii python3-gi-cairo3.28.1-1 ii python3-gst-1.0 1.14.0-1 ii python3-matplotlib 2.1.1-2 ii python3-numpy 1:1.13.3-2 ii python3-xdg 0.25-4 ii python3.6 3.6.5~rc1-3 pitivi recommends no packages. Versions of packages pitivi suggests: pn frei0r-plugins ii gir1.2-gnomedesktop-3.03.28.0-1 ii gir1.2-notify-0.7 0.7.7-3 ii gstreamer1.0-libav 1.14.0-1 ii gstreamer1.0-plugins-ugly 1.14.0-1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#894351: gnome-session-binary listens on TCP sockets
Package: gnome-session-bin
Version: 3.28.0-1
Severity: normal
Tags: upstream
Dear Maintainer,
I noticed that gnome-session-binary 3.28.0 listens on TCP sockets:
$ sudo ss -tunlp | grep -E '(gnome-session|State)'
Netid State Recv-Q Send-QLocal Address:Port Peer Address:Port
tcp LISTEN 0128 0.0.0.0:34651 0.0.0.0:*
users:(("gnome-session-b",pid=1554,fd=12))
tcp LISTEN 0128 0.0.0.0:32835 0.0.0.0:*
users:(("gnome-session-b",pid=840,fd=12))
tcp LISTEN 0128[::]:44309 [::]:*
users:(("gnome-session-b",pid=840,fd=11))
tcp LISTEN 0128[::]:38204 [::]:*
users:(("gnome-session-b",pid=1554,fd=11))
I don't remember this happening with previous versions.
Talking with upstream it turns out that the issue is caused by the
combination of these two facts:
1. gnome-session switched to meson as its build system;
2. the code was still relying on the autoconf variable HAVE_XTRANS to
disable TCP sockets, and meson was not defining it.
Upstream suggests to cherry-pick this change from the git repository:
https://git.gnome.org/browse/gnome-session/commit/?id=1ece66e683258a0bfa044d074becfe207d04a748
Thanks,
Antonio
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages gnome-session-bin depends on:
ii dbus-x11 1.12.6-2
ii dconf-gsettings-backend [gsettings-backend] 0.26.1-3
ii gsettings-desktop-schemas3.28.0-1
ii libc62.27-2
ii libegl1 1.0.0+git20180308-1
ii libepoxy01.4.3-1
ii libgl1 1.0.0+git20180308-1
ii libgles2 1.0.0+git20180308-1
ii libglib2.0-0 2.56.0-4
ii libgnome-desktop-3-173.28.0-1
ii libgtk-3-0 3.22.29-2
ii libice6 2:1.0.9-2
ii libjson-glib-1.0-0 1.4.2-3
ii libsm6 2:1.2.2-1+b3
ii libsystemd0 238-3
ii libx11-6 2:1.6.5-1
ii libxcomposite1 1:0.4.4-2
ii upower 0.99.7-2
ii xwayland 2:1.19.6-1
Versions of packages gnome-session-bin recommends:
ii libpam-systemd 238-3
gnome-session-bin suggests no packages.
-- no debconf information
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Bug#893694: gajim: fails to start if python3-distutils is not installed (missing dependency?)
Package: gajim Version: 1.0.0-1 Severity: important Dear Maintainer, the new gajim version failed to start on my system with the following messages: $ gajim Traceback (most recent call last): File "/usr/lib/python3/dist-packages/gajim/gajim.py", line 146, in _startup from distutils.version import LooseVersion as V ModuleNotFoundError: No module named 'distutils' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/gajim/gajim.py", line 264, in _activate from gajim.gui_interface import Interface File "/usr/lib/python3/dist-packages/gajim/gui_interface.py", line 54, in from gajim.common import app File "/usr/lib/python3/dist-packages/gajim/common/app.py", line 35, in from distutils.version import LooseVersion as V ModuleNotFoundError: No module named 'distutils' Traceback (most recent call last): File "/usr/lib/python3/dist-packages/gajim/gajim.py", line 316, in do_shutdown from gajim.common import app File "/usr/lib/python3/dist-packages/gajim/common/app.py", line 35, in from distutils.version import LooseVersion as V ModuleNotFoundError: No module named 'distutils' Installing python3-distutils fixes the problem; does it need to be added to the dependencies? Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages gajim depends on: ii gir1.2-gtk-3.03.22.29-1 ii python3 3.6.4-1 ii python3-gi3.26.1-2 ii python3-gi-cairo 3.26.1-2 ii python3-idna 2.6-1 ii python3-nbxmpp0.6.4-1 ii python3-openssl 17.5.0-1 ii python3-pyasn10.4.2-3 Versions of packages gajim recommends: ii alsa-utils 1.1.3-1 ii aspell-it [aspell-dictionary] 2.4-20070901-0-2.1 ii ca-certificates20170717 ii dbus 1.12.6-2 ii fonts-noto-color-emoji 0~20180102-1 ii gajim-omemo2.5.7-1 ii gajim-pgp 1.2.2-1 ii gir1.2-farstream-0.2 0.2.8-4 ii gir1.2-geoclue-2.0 2.4.7-1 ii gir1.2-gspell-11.6.1-1 ii gir1.2-gst-plugins-base-1.01.12.4-1 ii gir1.2-gstreamer-1.0 1.12.4-1 ii gir1.2-gupnpigd-1.00.2.5-2 ii gir1.2-networkmanager-1.0 1.10.6-2 ii gir1.2-secret-10.18.5-6 ii gnome-flashback [notification-daemon] 3.26.0-3 ii gnome-shell [notification-daemon] 3.28.0-1 pn gstreamer0.10-plugins-ugly ii pulseaudio-utils 11.1-4 ii python3-crypto 2.6.1-8 ii python3-dbus 1.2.6-1 ii python3-gnupg 0.4.1-2 ii python3-keyring10.6.0-1 ii python3-pil5.0.0-1 ii python3-precis-i18n1.0.0-1 Versions of packages gajim suggests: ii avahi-daemon 0.7-3.1 ii libxss1 1:1.2.2-1+b2 ii nautilus-sendto 3.8.6-2 pn python3-avahi pn python3-gconf pn python3-gnome2 pn python3-kerberos ii python3-pycurl 7.43.0.1-0.2 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#893480: lintian: Wrong URL in debian-control-has-obsolete-dbg-package
Package: lintian
Version: 2.5.79
Severity: minor
Tags: patch
Dear Maintainer,
the current URL[1] in debian-control-has-obsolete-dbg-package brings to
a generic Wiki page, it misses a trailing 's'.
I am attaching a patch to use the correct URL[2] which gets directly to
the page about Automatic Debug Packages.
Ciao,
Antonio
[1] https://wiki.debian.org/AutomaticDebugPackage
[2] https://wiki.debian.org/AutomaticDebugPackages
-- System Information:
Debian Release: buster/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8),
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages lintian depends on:
ii binutils 2.30-7
ii bzip2 1.0.6-8.1
ii diffstat 1.61-1+b1
ii dpkg 1.19.0.5
ii file 1:5.32-2
ii gettext 0.19.8.1-4
ii intltool-debian 0.35.0+20060710.4
ii libapt-pkg-perl 0.1.33
ii libarchive-zip-perl 1.60-1
ii libclass-accessor-perl0.51-1
ii libclone-perl 0.39-1
ii libdpkg-perl 1.19.0.5
ii libemail-valid-perl 1.202-1
ii libfile-basedir-perl 0.07-1
ii libipc-run-perl 0.96-1
ii liblist-moreutils-perl0.416-1+b3
ii libparse-debianchangelog-perl 1.2.0-12
ii libperl5.26 [libdigest-sha-perl] 5.26.1-5
ii libtext-levenshtein-perl 0.13-1
ii libtimedate-perl 2.3000-2
ii liburi-perl 1.73-1
ii libxml-simple-perl2.24-1
ii libyaml-libyaml-perl 0.69+repack-1
ii man-db2.8.2-1
ii patchutils0.3.4-2
ii perl 5.26.1-5
ii t1utils 1.41-2
ii xz-utils 5.2.2-1.3
Versions of packages lintian recommends:
ii libperlio-gzip-perl 0.19-1+b4
Versions of packages lintian suggests:
pn binutils-multiarch
ii dpkg-dev 1.19.0.5
ii libhtml-parser-perl3.72-3+b2
ii libtext-template-perl 1.47-1
-- no debconf information
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
>From 8c29d57a53240fd4efc0beb92e20f9d1e92c82ea Mon Sep 17 00:00:00 2001
From: Antonio Ospite <a...@ao2.it>
Date: Mon, 19 Mar 2018 10:33:15 +0100
Subject: [PATCH] Fix wrong URL in debian-control-has-obsolete-dbg-package
X-Face: z*RaLf`X<@C75u6Ig9}{oW$H;1_\2t5)({*|jhM<pyWR#k60!#=#>/Vb;]yA5<GWI5`6u&+
;6b'@y|8w"wB;4/e!7wYYrcqdJFY,~%Gk_4]cq$Ei/7<j(m`ku?pX.&+~:_/wC~dwn^)MizBG
!pE^+iDQQ1yC6^,)YDKkxDd!T>\I~93>J<_`<4)A{':UrE
The current URL brings to a generic Wiki page, use the correct URL which
gets directly to the page about Automatic Debug Packages.
---
checks/control-file.desc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/checks/control-file.desc b/checks/control-file.desc
index 18b3d8cf4..ce13d48d4 100644
--- a/checks/control-file.desc
+++ b/checks/control-file.desc
@@ -49,7 +49,7 @@ Info: The debian/control file includes declaration of
Tag: debian-control-has-obsolete-dbg-package
Severity: wishlist
Certainty: possible
-Ref: https://wiki.debian.org/AutomaticDebugPackage
+Ref: https://wiki.debian.org/AutomaticDebugPackages
Info: The debian/control file includes declaration of
-dbg package.
.
--
2.16.2
Bug#760210: fluidsynth: systemd not supported?
Package: fluidsynth Version: 1.1.10-1 Followup-For: Bug #760210 Dear Maintainer, the 1.1.10 upstream release installs a systemd unit to make it possible to launch fluidsynth as a systemd _user_ service. Please consider adding this to the Debian package. Thank you for your work. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages fluidsynth depends on: ii libc6 2.27-2 ii libfluidsynth1 1.1.10-1 Versions of packages fluidsynth recommends: ii qsynth 0.5.0-2 fluidsynth suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#865931: mysql-server: Does not allow me to change root password
Package: mariadb-server-10.1 Followup-For: Bug #865931 Dear Maintainer, I think this bug can be closed because MariaDB works as intended and as documented in /usr/share/doc/mariadb-server-10.1/README.Debian.gz The database root user is not supposed to log in with a password, but via the unix_socket plugin with the system root user. To the users who reported the issue: please don't change the settings of the root user, you'll break the maintenance scripts. Creating an additional admin user is what Debian maintainers recommend in /usr/share/doc/mariadb-server-10.1/README.Debian.gz in the PASSWORDS section, also here: https://salsa.debian.org/mariadb-team/mariadb-10.1/blob/stretch/debian/mariadb-server-10.1.README.Debian#L73 Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.15.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), LANGUAGE=it_IT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages mariadb-server-10.1 depends on: ii adduser 3.117 ii debconf [debconf-2.0] 1.5.66 ii galera-3 25.3.22-1 ii gawk 1:4.1.4+dfsg-1+b1 ii iproute2 4.15.0-2 ii libaio1 0.3.110-5 ii libc6 2.27-1 ii libdbi-perl 1.640-1 ii libpam0g 1.1.8-3.7 ii libstdc++68-20180218-1 ii libsystemd0 238-1 ii lsb-base 9.20170808 ii lsof 4.89+dfsg-0.1 ii mariadb-client-10.1 1:10.1.29-6 ii mariadb-common1:10.1.29-6 ii mariadb-server-core-10.1 1:10.1.29-6 ii passwd1:4.5-1 ii perl 5.26.1-5 ii psmisc23.1-1 ii rsync 3.1.2-2.1 ii socat 1.7.3.2-2 ii zlib1g1:1.2.8.dfsg-5 Versions of packages mariadb-server-10.1 recommends: ii libhtml-template-perl 2.97-1 Versions of packages mariadb-server-10.1 suggests: ii mailutils [mailx] 1:3.4-1 ii netcat-openbsd 1.187-1 pn tinyca -- debconf information excluded -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#876237: Doesn't display all commits
On Sun, 4 Feb 2018 07:57:47 +1100
Carlos Maddela <e7ap...@gmail.com> wrote:
> I'm not sure if this bug can be safely closed now, since I don't know if the
> behaviour I described previously was intended.
>
> What has been resolved with the release of libgit2-glib/0.26.2-1 is that the
> 'Preferences' menu becomes available again in gitg, and you can choose
> the 'Show history in topological order' to restore the original behaviour in
> version 0.24.
>
Sorry but I still see the issue with gitg, it can be replicated cloning
the repository mentioned in the upstream report:
https://bugzilla.gnome.org/show_bug.cgi?id=788090
Enabling topological order to fix the gitg issue is just a workaround.
My test case is a simple repository with only one branch, and gitg fails
to show all the commits, while the git command line tools work fine.
I am not sure if this is a libgit2 issue TBH, this simple pygit2 example
shows all the commits:
#!/usr/bin/env python3
import pygit2
#mode = pygit2.GIT_SORT_NONE
#mode = pygit2.GIT_SORT_TOPOLOGICAL
mode = pygit2.GIT_SORT_TIME
#mode |= pygit2.GIT_SORT_REVERSE
repo = pygit2.Repository('.git')
for commit in repo.walk(repo.head.target, mode):
print(commit.id, commit.message.split('\n')[0])
----
Ciao,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Bug#885965: pylint3: False positive about "Unused variable '__class__'"
Package: pylint3 Version: 1.7.4-2 Followup-For: Bug #885965 Dear Maintainer, I am not sure why this is titled FTBFS, it looks like it's "just" a regression when running the program on the user source code. JFTR these are the upstream issues: https://github.com/PyCQA/pylint/issues/1784 https://github.com/PyCQA/pylint/issues/1790 The problem should be fixed in 1.8.1 and I see that this version is already in the source package repository, good. There could still be some false positives related to this issue even in the newer upstream release: https://github.com/PyCQA/pylint/issues/1825 However these latter should be less frequent than the current ones with 1.7.4. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-3-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages pylint3 depends on: ii python3 3.6.4-1 ii python3-astroid 1.6.0-1 ii python3-isort 4.2.5+ds1-3 ii python3-logilab-common 1.4.1-1 ii python3-setuptools 38.2.4-2 Versions of packages pylint3 recommends: ii python3-tk 3.6.4-2 Versions of packages pylint3 suggests: pn pylint-doc ii python3-mccabe 0.6.1-2 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#884765: ITP: drupal-init-tools -- helper commands to create and install new Drupal projects
On Tue, 19 Dec 2017 11:45:52 +0100 Antonio Ospite <a...@ao2.it> wrote: > Package: wnpp > Severity: wishlist > Owner: Antonio Ospite <a...@ao2.it> > > * Package name: drupal-init-tools > Version : 0.1.1 > Upstream Author : Antonio Ospite <a...@ao2.it> > * URL : https://git.ao2.it/drupal-init-tools.git/ > * License : GPL-2+ > Programming Lang: Bash > Description : helper commands to create and install new Drupal projects > > The Debian packaging bits can be found in the "debian" branch of the upstream repository: https://git.ao2.it/drupal-init-tools.git/tree/refs/heads/debian:/debian The package is very simple. It builds fine under pbuilder, is lintian-clean and passes all piuparts checks. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#884765: ITP: drupal-init-tools -- helper commands to create and install new Drupal projects
Package: wnpp Severity: wishlist Owner: Antonio Ospite <a...@ao2.it> * Package name: drupal-init-tools Version : 0.1.1 Upstream Author : Antonio Ospite <a...@ao2.it> * URL : https://git.ao2.it/drupal-init-tools.git/ * License : GPL-2+ Programming Lang: Bash Description : helper commands to create and install new Drupal projects When setting up a new Drupal project with drupal-composer/drupal-project, drush and drupal-console are not available yet and some repetitive tasks can use a nicer command line interface. These scripts are especially useful when setting up projects in user web directories[1]. [1] http://httpd.apache.org/docs/current/howto/public_html.html Some more info about the upstream project is available at https://ao2.it/en/blog/2017/08/02/drupal-init-tools-quick-and-easy-drupal-8-setup Since Drupal 8 is not available in Debian I think that having drupal-init-tools in the official archive can make it easier for users to set up a Drupal site on their machine. I am the upstream author of drupal-init-tool and I plan on maintaining the Debian package myself, but I am not a Debian Developer or a Debian Maintainer. I do have a sponsor who is kind enough to upload some other packages of mine, but if someone is interested in web stuff and want to sponsor me for this one, my usual sponsor and I would surely appreciate it. :) Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#884358: marked as done (gajim: broken dependencies, gajim no longer starts)
On Sun, 17 Dec 2017 00:27:57 +0100 Antonio Ospite <a...@ao2.it> wrote: > Hi, > > I had to fix the "logs.db" database to be able to have the history > working with gajim 0.16.11 so I am pasting some info below in case > someone else needs it. > When I wrote 0.16.11 I actually meant 0.16.11.git20171214-1 from Debian experimental. [...] > See the attached script, you might have to slightly change it to make > it work according to what previous version of gajim you were using > before, I had 0.16.8-5 but I am not sure if the misspelled > "additinal_data" column was there from some version from git I might > have run at some point. > The misspelled 'additinal_data' column was introduced here https://dev.gajim.org/gajim/gajim/blob/gajim-1.0.0-alpha1/gajim/common/optparser.py#L866 when updating from a previous version. However the code, and newly created tables, actually use 'additional_data'. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#884358: marked as done (gajim: broken dependencies, gajim no longer starts)
Hi, I had to fix the "logs.db" database to be able to have the history working with gajim 0.16.11 so I am pasting some info below in case someone else needs it. The error I was getting was like: The database file (/home/ao2/.local/share/gajim/logs.db) cannot be read. Try to repair it (see https://dev.gajim.org/gajim/gajim/wikis/help/DatabaseBackup) or remove it (all history will be lost). However the pointed wiki page only gave instructions about backing up the database, not about repairing it. So, some SQL dance was necessary. See the attached script, you might have to slightly change it to make it work according to what previous version of gajim you were using before, I had 0.16.8-5 but I am not sure if the misspelled "additinal_data" column was there from some version from git I might have run at some point. Make sure you have run the instructions on the wiki to backup the _original_ database, just to have a safety net: $ sqlite3 ~/.local/share/gajim/logs.db .dump > backup.sql $ mv ~/.local/share/gajim/logs.db ~/.local/share/gajim/logs.db.old You might have to remove any new database created only with the new version (rm -i ~/.local/share/gajim/logs.db). Restore the backup and repair the database: $ sqlite3 ~/.local/share/gajim/logs.db < backup.sql $ sqlite3 ~/.local/share/gajim/logs.db < gajim_0.16.8_fix_logs_table_for_0.16.11.sql Start gajim. Keep in mind that you have to select a contact first to be able to see the logs history. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? gajim_0.16.8_fix_logs_table_for_0.16.11.sql Description: application/sql
Bug#779207: unzip fails to unpack filenames containing 'ä' 'ö' 'ü' -> results in "(invalid encoding)"
On Fri, 24 Nov 2017 09:30:26 +0100 Antonio Ospite <a...@ao2.it> wrote: [...] > You'll need to compile with -DUSE_ICONV_MAPPING to enable this, and > depend on the iconv library. > Well, the changelog mentions the "iconv library", but on linux the functionality is in glibc, so no extra dependencies should be needed. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#779207: unzip fails to unpack filenames containing 'ä' 'ö' 'ü' -> results in "(invalid encoding)"
Package: unzip Version: 6.0-21 Followup-For: Bug #779207 Dear Maintainer, it looks like some upstream beta version from 2010 fixes this by adding the -I and -O option, and the changelog says it's based on the unzip60-alt-iconv-utf8.patch proposed in this thread. This is the beta version: ftp://ftp.info-zip.org/pub/infozip/beta/unzip610b.zip You'll need to compile with -DUSE_ICONV_MAPPING to enable this, and depend on the iconv library. Mentioned also in #197427 and maybe other related bugs are also #696914 and #483290. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages unzip depends on: ii libbz2-1.0 1.0.6-8.1 ii libc6 2.25-2 unzip recommends no packages. Versions of packages unzip suggests: ii zip 3.0-11+b1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#828960: closed by Dmitry Smirnov <only...@debian.org> (Bug#828960: fixed in gnumeric 1.12.35-1)
On Tue, 07 Nov 2017 04:21:04 + ow...@bugs.debian.org (Debian Bug Tracking System) wrote: > This is an automatic notification regarding your Bug report > which was filed against the gnumeric package: > > #828960: gnumeric: missing-pkgconfig-dependency libspreadsheet-1.12 => > libgsf-1 > > It has been closed by Dmitry Smirnov <only...@debian.org>. > [...] >* Suggests += "libgsf-1-dev" (Closes: #828960). Just a comment: the change improves the situation as it suggests a solution, however by default adequate still gives the message. I guess it's not worth spending too much time to fix this, so I am accepting the resolution. Thanks Dmitry. Ciao, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#858173: audacity: please upgrade audacity to 2.2.0
Package: audacity Version: 2.1.2-2 Followup-For: Bug #858173 Dear Maintainer, just a heads up, version 2.2.0 of Audacity has been released: http://wiki.audacityteam.org/wiki/Release_Notes_2.2.0 Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages audacity depends on: ii audacity-data 2.1.2-2 ii libasound2 1.1.3-5 ii libavcodec577:3.3.4-2+b3 ii libavformat57 7:3.3.4-2+b3 ii libavutil55 7:3.3.4-2+b3 ii libc6 2.24-17 ii libexpat1 2.2.3-2 ii libflac++6v51.3.2-1 ii libflac81.3.2-1 ii libgcc1 1:7.2.0-12 ii libgdk-pixbuf2.0-0 2.36.11-1 ii libglib2.0-02.54.2-1 ii libgtk2.0-0 2.24.31-2 ii libid3tag0 0.15.1b-12 ii liblilv-0-0 0.24.2~dfsg0-1 ii libmad0 0.15.1b-8.1 ii libmp3lame0 3.100-2 ii libogg0 1.3.2-1+b1 ii libportaudio2 19.6.0-1 ii libportsmf0 0.1~svn20101010-5 ii libsbsms10 2.0.2-2 ii libsndfile1 1.0.28-4 ii libsoundtouch1 1.9.2-2+b1 ii libsoxr00.1.2-3 ii libstdc++6 7.2.0-12 ii libsuil-0-0 0.10.0~dfsg0-1 ii libtwolame0 0.3.13-3 ii libvamp-hostsdk3v5 2.7.1~repack0-1 ii libvorbis0a 1.3.5-4 ii libvorbisenc2 1.3.5-4 ii libvorbisfile3 1.3.5-4 ii libwxbase3.0-0v53.0.3.1+dfsg2-1 ii libwxgtk3.0-0v5 3.0.3.1+dfsg2-1 audacity recommends no packages. Versions of packages audacity suggests: ii caps [ladspa-plugin] 0.9.24-4 ii swh-plugins [ladspa-plugin] 0.4.17-2 ii tap-plugins [ladspa-plugin] 0.7.3-2 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#880571: sylpheed: cannon connect to servers using TLSv1 and TLSv1.1
Package: sylpheed
Version: 3.6.0-1
Severity: normal
Tags: patch
Dear Maintainer,
the Debian openssl package deprecated TLSv1 and TLSv1.1 in August 2017,
see:
https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
https://anonscm.debian.org/viewvc/pkg-openssl/openssl/branches/1.1.0/debian/patches/tls1_2_default.patch?revision=912=markup
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875423
It's not clear if this decision is final and will affect the next Debian
stable release, however in the meantime, sylpheed in Debian unstable
cannot connect to servers using older TLS protocol versions.
Sylpheed gives this message when connecting to a server using TLSv1:
(sylpheed:20968): LibSylph-WARNING **: SSL_connect() failed with error 1, ret
= -1 (error:1417118C:SSL routines:tls_process_server_hello:version too low)
The OpenSSL error is:
SSL routines:tls_process_server_hello:version too low
I am attaching a patch to fix this behavior.
I am not sure if this change should be in the official package, let me
know what your opinion is on this matter.
Thanks,
Antonio
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8),
LANGUAGE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages sylpheed depends on:
ii libassuan0 2.4.3-3
ii libatk1.0-0 2.26.1-1
ii libc62.24-17
ii libcairo21.15.8-2
ii libcompfaceg11:1.5.2-5+b2
ii libdbus-1-3 1.12.0-1
ii libdbus-glib-1-2 0.108-2
ii libenchant1c2a 1.6.0-11.1
ii libfontconfig1 2.12.3-0.2
ii libfreetype6 2.8.1-0.1
ii libgdk-pixbuf2.0-0 2.36.11-1
ii libglib2.0-0 2.54.2-1
ii libgpg-error01.27-4
ii libgpgme11 1.9.0-6
ii libgtk2.0-0 2.24.31-2
ii libgtkspell0 2.0.16-1.1
ii libldap-2.4-22.4.45+dfsg-1
ii libpango-1.0-0 1.40.13-1
ii libpangocairo-1.0-0 1.40.13-1
ii libpangoft2-1.0-01.40.13-1
ii libssl1.11.1.0f-5
ii pinentry-gtk21.0.0-3
Versions of packages sylpheed recommends:
ii aspell-it [aspell-dictionary] 2.4-20070901-0-2.1
ii ca-certificates20170717
ii sylpheed-i18n 3.6.0-1
ii xfonts-100dpi 1:1.0.4+nmu1
ii xfonts-75dpi 1:1.0.4+nmu1
Versions of packages sylpheed suggests:
ii bogofilter1.2.4+dfsg1-10
pn bsfilter
pn claws-mail-tools
ii curl 7.56.1-1
pn jpilot
pn sylpheed-doc
-- no debconf information
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
>From 97235129beab0b3a23ec95db3e922321cdf43cf3 Mon Sep 17 00:00:00 2001
From: Antonio Ospite <a...@ao2.it>
Date: Thu, 2 Nov 2017 13:37:53 +0100
Subject: [PATCH] libsylph/ssl.c: explicitly enable the supported protocol
versions
X-Face: z*RaLf`X<@C75u6Ig9}{oW$H;1_\2t5)({*|jhM<pyWR#k60!#=#>/Vb;]yA5<GWI5`6u&+
;6b'@y|8w"wB;4/e!7wYYrcqdJFY,~%Gk_4]cq$Ei/7<j(m`ku?pX.&+~:_/wC~dwn^)MizBG
!pE^+iDQQ1yC6^,)YDKkxDd!T>\I~93>J<_`<4)A{':UrE
The Debian openssl package deprecated TLSv1 and TLSv1.1 in August 2017,
see:
https://lists.debian.org/debian-devel-announce/2017/08/msg4.html
https://anonscm.debian.org/viewvc/pkg-openssl/openssl/branches/1.1.0/debian/patches/tls1_2_default.patch?revision=912=markup
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=875423
It's not clear if this decision is final and will affect the next Debian
stable release, however in the meantime, sylpheed in Debian unstable
cannot connect to servers using older TLS protocol versions.
Work around that by explicitly setting the minimum protocol versions.
---
libsylph/ssl.c | 4
1 file changed, 4 insertions(+)
diff --git a/libsylph/ssl.c b/libsylph/ssl.c
index 84139250..61e770f8 100644
--- a/libsylph/ssl.c
+++ b/libsylph/ssl.c
@@ -132,6 +132,8 @@ void ssl_init(void)
debug_print(_("SSLv23 not available\n"));
} else {
debug_print(_("SSLv23 available\n"));
+ /* XXX workaround for Debian systems, see Debian bug #875423 */
+ SSL_CTX_set_min_proto_version(ssl_ctx_SSLv23, SSL3_VERSION);
if ((certs_file || certs_dir) &&
!SSL_CTX_load_verify_locations(ssl_ctx_SSLv23, certs_file,
certs_dir))
@@ -144,6 +146,8 @@ void ssl_init(void)
debug_print(_("TLSv1 not available\n"));
} else {
debug_print(_("TLSv1
Bug#880497: pytimechart: missing dependencies
After that pytimechart works fine. Thanks, Antonio P.S. the link in the Homepage field of the package is broken, I think the current upstream is https://github.com/tardyp/pytimechart -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages pytimechart depends on: ii python 2.7.14-1 ii python-chaco 4.5.0-1 ii python-enthoughtbase 3.1.0-2 ii python-gtk2 2.24.0-5.1 ii python-wxgtk3.0 3.0.2.0+dfsg-5 pytimechart recommends no packages. pytimechart suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#876864: VBinDiff 3.0 beta 5 — 10 Sep 2017
Package: src:vbindiff Followup-For: Bug #876864 Dear Maintainer, ping. The new upstream release also fixes a crash so it would be great to have it in the official archives. And the changes provided by Mathieu will also fix #865050. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.13.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#876257: libwebkit2gtk-4.0-37: blocks upgrade path for libgstreamer-plugins-bad1.0-0 1.12.3
Package: libwebkit2gtk-4.0-37 Version: 2.18.0-2 Severity: important Dear Maintainer, it looks like libwebkit2gtk-4.0-37 is blocking the upgrade path for libgstreamer-plugins-bad1.0-0 1.12.3, looking at the package dependencies I spotted these constraints: libgstreamer-plugins-bad1.0-0 (>= 1.12.2), libgstreamer-plugins-bad1.0-0 (<< 1.12.3) which explain the issue. However I am not sure about why both constraints are there. Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libwebkit2gtk-4.0-37 depends on: ii libatk1.0-0 2.26.0-2 ii libc6 2.24-17 ii libcairo2 1.14.10-1 ii libegl1 0.2.999+git20170802-4 ii libenchant1c2a 1.6.0-11+b2 ii libfontconfig1 2.12.3-0.2 ii libfreetype62.8-0.2 ii libgcc1 1:7.2.0-5 ii libgcrypt20 1.7.9-1 ii libgdk-pixbuf2.0-0 2.36.10-1 ii libgl1 0.2.999+git20170802-4 ii libglib2.0-02.54.0-1 ii libgstreamer-plugins-bad1.0-0 1.12.2-1+b1 ii libgstreamer-plugins-base1.0-0 1.12.3-1 ii libgstreamer1.0-0 1.12.3-1 ii libgtk-3-0 3.22.21-1 ii libharfbuzz-icu01.4.2-1 ii libharfbuzz0b 1.4.2-1 ii libhyphen0 2.8.8-5 ii libicu5757.1-6 ii libjavascriptcoregtk-4.0-18 2.18.0-2 ii libjpeg62-turbo 1:1.5.2-2 ii libnotify4 0.7.7-2 ii libpango-1.0-0 1.40.12-1 ii libpng16-16 1.6.32-1 ii libsecret-1-0 0.18.5-3.1 ii libsoup2.4-12.60.0-1 ii libsqlite3-03.20.1-1 ii libstdc++6 7.2.0-5 ii libtasn1-6 4.12-2.1 ii libwayland-client0 1.14.0-1 ii libwayland-egl1-mesa [libwayland-egl1] 17.2.1-1 ii libwayland-server0 1.14.0-1 ii libwebp60.6.0-3 ii libx11-62:1.6.4-3 ii libxcomposite1 1:0.4.4-2 ii libxdamage1 1:1.1.4-3 ii libxml2 2.9.4+dfsg1-4 ii libxslt1.1 1.1.29-2.1 ii zlib1g 1:1.2.8.dfsg-5 Versions of packages libwebkit2gtk-4.0-37 recommends: ii gstreamer1.0-plugins-base 1.12.3-1 ii gstreamer1.0-plugins-good 1.12.3-1 ii libgl1-mesa-dri17.2.1-1 Versions of packages libwebkit2gtk-4.0-37 suggests: ii libwebkit2gtk-4.0-37-gtk2 2.18.0-2 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#874791: gajim: Crash on startup with python-gnupg >= 0.4 without gpg1
Package: gajim Version: 0.16.8-4 Followup-For: Bug #874791 Dear Maintainer, I am afraid the fix in 0.16.8-4 is not complete. Now gajim sets GPG_BINARY to '/usr/bin/gpg2', but this binary is only provided by the "gnupg2" package which is a transitional package and it may not be always installed. For example, on my system I end up with this error: -- $ gajim 14/09/2017 08:53:34 (E) gajim.c.gnupg Unable to run gpg - it may not be available. Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/gnupg.py", line 755, in __init__ p = self._open_subprocess(["--version"]) File "/usr/lib/python2.7/dist-packages/gnupg.py", line 831, in _open_subprocess startupinfo=si) File "/usr/lib/python2.7/subprocess.py", line 390, in __init__ errread, errwrite) File "/usr/lib/python2.7/subprocess.py", line 1025, in _execute_child raise child_exception OSError: [Errno 2] File o directory non esistente Traceback (most recent call last): File "gajim.py", line 512, in interface = Interface() File "/usr/share/gajim/src/gui_interface.py", line 2926, in __init__ gajim.connections[account] = Connection(account) File "/usr/share/gajim/src/common/connection.py", line 785, in __init__ CommonConnection.__init__(self, name) File "/usr/share/gajim/src/common/connection.py", line 150, in __init__ self.gpg = gpg.GnuPG() File "/usr/share/gajim/src/common/gpg.py", line 37, in __init__ gnupg.GPG.__init__(self, gpgbinary=gajim.GPG_BINARY, use_agent=use_agent) File "/usr/lib/python2.7/dist-packages/gnupg.py", line 759, in __init__ raise OSError(msg) OSError: Unable to run gpg - it may not be available. -- A workaround is to install the gnupg2 package (if this is your preferred solution then gajim should depend on the gnupg2 package), but I am not sure this is the right solution, maybe setting GPG_BINARY = 'gpg' is better? The original reporter of this bug was suggesting this too. IIUC the versioned dependency on python-gnupg (>= 0.4.1) should assure that the installed gnupg package (as an indirect dependency) is indeed version 2.x and that the 'gpg' binary is indeed gpg2. Ideally python-gnupg could make this clearer adding a versioned dependency on gnupg (>= 2) but it's not a big deal. Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gajim depends on: ii dnsutils1:9.10.3.dfsg.P4-12.6 ii python 2.7.13-2 ii python-gtk2 2.24.0-5.1 ii python-nbxmpp 0.5.4-1 ii python-openssl 16.2.0-1 ii python-pyasn1 0.1.9-2 Versions of packages gajim recommends: ii alsa-utils 1.1.3-1 ii ca-certificates20170717 ii dbus 1.11.16+really1.10.22-1 ii gnome-flashback [notification-daemon] 3.24.0-2 ii gnome-shell [notification-daemon] 3.22.3-3 ii notification-daemon3.20.0-1+b1 ii pulseaudio-utils 11.0-2 ii python-crypto 2.6.1-7+b1 ii python-dbus1.2.4-1+b2 ii python-gnupg 0.4.1-1 ii sox14.4.1-5+b2 Versions of packages gajim suggests: ii aspell-it [aspell-dictionary] 2.4-20070901-0-2.1 ii avahi-daemon 0.6.32-2 ii dvipng 1.14-2+b3 ii gnome-keyring 3.20.1-1 pn gstreamer0.10-plugins-ugly pn kwalletcli ii libgtkspell0 2.0.16-1.1 ii libxss11:1.2.2-1+b2 pn nautilus-sendto pn network-manager pn python-avahi ii python-gconf 2.28.1+dfsg-1.2 ii python-gnome2 2.28.1+dfsg-1.2 ii python-gnomekeyring2.32.0+dfsg-4 pn python-gupnp-igd pn python-kerberos ii python-pycurl 7.43.0-2+b1 ii texlive-latex-base 2017.20170818-1 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#823004: gplaycli: sensitive information in config file
On Wed, 23 Aug 2017 14:00:55 +0200 Matlink <matl...@matlink.fr> wrote: > Well, this issue has been fixed in the github repository since the > version 0.2.2 of gplaycli. Instead of using email and password for > credentials, gplaycli will fetch a server to get a token that will be > used for further authentication. Thus, gplaycli no longer needs to ship > sensitive informations in the configuration file. > > See https://github.com/matlink/gplaycli > > However, I'm a bit messed up with the debian way to provide .deb > packages, that's why the debian repo of gplaycli has been abandoned > quite long time ago. Gplaycli is now at version 0.2.10 and I'll will be > glad to be helped to update the debian upstream repository. > Someone offered their help in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871828 I'll see if I too can spend some time on gplaycli packaging myself. Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#843615: gplaycli: missing man page for gplaycli
Package: gplaycli Version: 0.2.1-1 Followup-For: Bug #843615 Dear Maintainer, take a look at the "help2man" program, it can help creating a basic man page from the output of the "--help" option. Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gplaycli depends on: ii androguard 2.0-3 ii python 2.7.13-2 ii python-clint0.5.1-1 ii python-ndg-httpsclient 0.4.2-1 ii python-protobuf 3.0.0-9 ii python-pyasn1 0.1.9-2 ii python-requests 2.18.1-1 Versions of packages gplaycli recommends: ii dummydroid1.1-1 pn fdroidserver gplaycli suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#823004: gplaycli: sensitive information in config file
Package: gplaycli Version: 0.2.1-1 Followup-For: Bug #823004 Dear Maintainer, Ping. See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=871828 I verified that newer versions work fine by cloning the upstream git repo and running ./gplaycli/gplaycli using the debian dependencies of the 0.2.1-1 package. Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.12.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages gplaycli depends on: ii androguard 2.0-3 ii python 2.7.13-2 ii python-clint0.5.1-1 ii python-ndg-httpsclient 0.4.2-1 ii python-protobuf 3.0.0-9 ii python-pyasn1 0.1.9-2 ii python-requests 2.18.1-1 Versions of packages gplaycli recommends: ii dummydroid1.1-1 pn fdroidserver gplaycli suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#870772: libgsl misses some breaks/replaces
On Mon, 7 Aug 2017 13:37:39 +1200 Ben Caradoc-Davies <b...@transient.nz>
wrote:
> Is there something wrong with libgsl23 2.4+dfsg-4? nco which depends on
> libgsl23 and {inkscape, qgis} which depend on libgsl2 are not
> coinstallable. Should libgsl23 have libgsl2 in its "Replaces:"? I do not
> understand, but I suspect that something is wrong.
>
IMHO "Replaces" is not a good solution short-term:
libgsl2 provides API version 19
libgsl23 provides API version 23
Software depending on libgsl2 might not be ready for API version 23.
The problem is that libgsl23 depends on libgslcblas0 but the
latter rightfully conflicts with libgsl2 because both packages ship
libgslcblas.so.0
This makes libgsl2 and libgsl23 not co-installable, which makes
the package name change a little less useful.
A possible solution could be to release a last libgsl2 version (maybe
2.4 +dfsg-2.1 ?) which does not ship libgslcblas.so.0 but instead
depends on the libgslcblas0 package, also restricting the conflict in
libgslcblas0 to libgsl2 versions *preceding* that version.
Long-term there could be a transition to libgsl23 for all the packages
which depend on libgsl2, but I don't know how that is triggered.
Just my 2c.
Ciao ciao,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Bug#869781: libgsl2: bumped library version without soname change, breaking reverse dependencies
Package: libgsl2 Version: 2.4+dfsg-1 Severity: normal Dear Maintainer, since libgsl2=2.4+dfsg-1 reverse dependencies are broken, I experienced the problem with bogofilter (which depends on bogofilter-bdb which depends on libgsl2): bogofilter: error while loading shared libraries: libgsl.so.19: cannot open shared object file: No such file or directory This seems to happens because 2.4+dfsg-1 bumped the library version but the package name is always the same and does not reflect the SONAME change. In libgsl2=2.4+dfsg-1 we have: libgsl2: /usr/lib/x86_64-linux-gnu/libgsl.so.23 libgsl2: /usr/lib/x86_64-linux-gnu/libgsl.so.23.0.0 In libgsl2=2.3+dfsg-1 we had: /usr/lib/x86_64-linux-gnu/libgsl.so.19 /usr/lib/x86_64-linux-gnu/libgsl.so.19.3.0 as bogofilter expects. Downgrading to libgsl2=2.3+dfsg-1 fixes the problem with bogofilter. Rebuilding the reverse dependencies would also work but maybe this is the chance to fix the package name of libgsl2? Thanks, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages libgsl2 depends on: ii libc6 2.24-12 libgsl2 recommends no packages. Versions of packages libgsl2 suggests: pn gsl-ref-psdoc | gsl-doc-pdf | gsl-doc-info | gsl-ref-html -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#857986: npm: package is 3 years old (consider removal?)
Removing npm could bring some more attention at packaging yarn[1,2], which seems to be better and more secure than npm (says a brief google search...). Ciao, Antonio [1] https://yarnpkg.com/en/ [2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843021 -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#862333: RFP: bower -- Package manager for the Web
Hi, bower maintainers themselves[1] recommend using yarn[2]. Maybe this bug can be closed? IMHO efforts should be focused on packaging yarn[3]. Ciao, Antonio [1] https://github.com/bower/bower [2] https://yarnpkg.com/en/ [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843021 -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#866129: lilypond: segfault using lilypond buster testing
Package: lilypond Version: 2.18.2-7 Followup-For: Bug #866129 Dear Maintainer, lilyopnd devs suggest[1] that this could be an issue with gcc-6, reported in the issue 4814 on sf.net[2], which has been fixed by commit b0dce76daf27 (Issue 4814: grob.cc segfaults with gcc6)[3]. [1] http://lists.gnu.org/archive/html/lilypond-devel/2017-06/msg00165.html [2] https://sourceforge.net/p/testlilyissues/issues/4814/?page=1 [3] http://git.savannah.gnu.org/cgit/lilypond.git/commit/?id=b0dce76daf27721ba157cd2ac5d7662d4c8d75f8 I cannot verify this anytime soon but maybe the provided info could help someone else to check if the problem is actually related to Issue 4814. Can the OP send a backtrace? Ciao, Antonio -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.11.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8), LANGUAGE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages lilypond depends on: ii ghostscript9.21~dfsg-1 ii libc6 2.24-12 ii libfontconfig1 2.12.3-0.1 ii libfreetype6 2.6.3-3.2 ii libgcc11:7.1.0-7 ii libglib2.0-0 2.52.3-1 ii libgmp10 2:6.1.2+dfsg-1 ii libltdl7 2.4.6-2 ii libpango-1.0-0 1.40.5-1 ii libpangoft2-1.0-0 1.40.5-1 ii libstdc++6 7.1.0-7 ii lilypond-data 2.18.2-7 ii python 2.7.13-2 Versions of packages lilypond recommends: ii texlive-latex-base 2017.20170623-1 Versions of packages lilypond suggests: ii lilypond-doc 2.18.2-7 -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#857631: bug #857631 : why isn't this fixed?
On Sun, 7 May 2017 00:45:21 -0700 <ian_br...@mail.ru> wrote: > Antonio Ospite <a...@ao2.it> wrote: > > > I saw that 4.0-5 has been uploaded without this fix, > > is this fix going to be in 4.0.1? > > It appears that the answer to this question is "no": [...] > Can the same fix that was applied to llvm-3.9 be applied to llvm-4.0? > It is apparently a ONE-LINE PATCH. (see initial bug report for reference.) It looks like the fix made it into 1:4.0.1~+rc3-1, as per https://bugs.llvm.org/show_bug.cgi?id=30217 and https://bugs.llvm.org/show_bug.cgi?id=32473 Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#861879: ges1.0-tools: Missing man page for ges-launch-1.0
Package: ges1.0-tools Version: 1.12.0-1 Severity: minor Tags: patch Dear Maintainer, GES 1.12 has a man page for ges-launch-1.0 but the debian package does not ship it. The attached patch fixes the problem. BTW, are the GStreamer/GES debian source packages available in some public repository? I don't see any Vcs-* fields in the control files. Thanks. Ciao ciao, Antonio -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (900, 'unstable'), (600, 'experimental'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages ges1.0-tools depends on: ii libc6 2.24-10 ii libges-1.0-01.12.0-1 ii libglib2.0-02.50.3-2 ii libgstreamer-plugins-base1.0-0 1.12.0-1 ii libgstreamer1.0-0 1.12.0-1 ges1.0-tools recommends no packages. ges1.0-tools suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? >From a06d5e41beae15dafa15bdcbe05362e2e6b4f6b4 Mon Sep 17 00:00:00 2001 From: Antonio Ospite <a...@ao2.it> Date: Fri, 5 May 2017 11:37:17 +0200 Subject: [PATCH] Ship the ges-launch-1.0 man page in the ges1.0-tools package --- debian/ges1.0-tools.manpages | 1 + 1 file changed, 1 insertion(+) create mode 100644 debian/ges1.0-tools.manpages diff --git a/debian/ges1.0-tools.manpages b/debian/ges1.0-tools.manpages new file mode 100644 index 000..4450a71 --- /dev/null +++ b/debian/ges1.0-tools.manpages @@ -0,0 +1 @@ +debian/tmp/usr/share/man/man1/*.1 -- 2.11.0
Bug#857631: mesa-opencl-icd: openCL is broken in LLVM < v5
On Wed, 12 Apr 2017 23:52:51 +0200 Antonio Ospite <a...@ao2.it> wrote: > Source: llvm-toolchain-4.0 > Followup-For: Bug #857631 > > Dear Maintainer, > > It looks like that since libllvm3.9_3.9.1-6~exp1 the issue is fixed > experimental for libllvm3.9, hoever libllvm4.0 still has it. > [...] > Can we please have a fixed 4.0 version uploaded to experimental? > The same fixes from #857623 should be enough. Hi, I saw that 4.0-5 has been uploaded without this fix, is this fix going to be in 4.0.1? Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#857631: mesa-opencl-icd: openCL is broken in LLVM < v5
Source: llvm-toolchain-4.0
Followup-For: Bug #857631
Dear Maintainer,
It looks like that since libllvm3.9_3.9.1-6~exp1 the issue is fixed
experimental for libllvm3.9, hoever libllvm4.0 still has it.
$ cat ptr-expr2.c
int ptr_expr(int *p)
{
if (!p)
return(0);
else
return(1);
}
$ clang-3.9 -x cl -emit-llvm -S ptr-expr2.c
$ # compilation succeeds
$ clang-4.0 -x cl -emit-llvm -S ptr-expr2.c
ptr-expr2.c:3:9: error: invalid argument type 'int *' to unary expression
if (!p)
^~
1 error generated.
Can we please have a fixed 4.0 version uploaded to experimental?
The same fixes from #857623 should be enough.
Thanks,
Antonio
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (900, 'unstable'), (600, 'experimental'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Bug#858011: netbase: Define ip4-localhost and ip4-loopback in /etc/hosts, for symmentry with IPv6
Package: netbase
Version: 5.4
Severity: wishlist
Dear Maintainer,
as per the subject, what about defining ip4-localhost and ip4-loopback
in /etc/hosts?
diff --git a/debian/netbase.postinst b/debian/netbase.postinst
index 4876e47..a893435 100644
--- a/debian/netbase.postinst
+++ b/debian/netbase.postinst
@@ -4,7 +4,7 @@ create_hosts_file() {
if [ -e /etc/hosts ]; then return 0; fi
cat > /etc/hosts <<-EOF
- 127.0.0.1 localhost
+ 127.0.0.1 localhost ip4-localhost ip4-loopback
::1 localhost ip6-localhost ip6-loopback
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
I see this was proposed also in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427067#5
It's nothing major of course and it can be added locally, but it's quite
convenient.
I was testing some web app locally with both IPv4 and IPv6 and the test
links look a lot nicer and symmetric using the host names.
I can send a proper patch as attachment if there is interest.
Thanks,
Antonio
-- System Information:
Debian Release: 9.0
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'unstable-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
-- no debconf information
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Bug#852299: [Pkg-alsa-devel] Bug#852299: alsa-utils: ship alsaucm man page
Control: tags -1 patch On Mon, 23 Jan 2017 15:20:59 +0100 Elimar Riesebieter <riese...@lxtec.de> wrote: > * Antonio Ospite <a...@ao2.it> [2017-01-23 13:17 +0100]: > [...] > > If you are building from tarballs and alsaucm.rst is missing there, this > > has been fixed after 1.1.3, see: > > http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=c6bdde171e1532f7b37333a5a746b6e662f12c53 > > > > If this is the case tell if you want me to send a patch which adds > > alsucm.rst at packaging time, until the next stable tarball. > > We are building the package from the latest stable tarball. There is > no alsaucm.rst available, though. To build the manpage we need at > least the rstfile and a patch to the Makefile.am. Is it possible to > cherrypick it from ALSA's git? > Hi Elimar, the Makefile.am bits are already there, the issue was only about "make dist" not picking up alsaucm.rst. The attached patch (against the source package debian/ dir) adds the missing file and the needed build-dependency. Tested with pbuilder. As said, the problem has been fixed after the release tarball was created, so the next release won't have this problem and the patch in debian/patches/ could be dropped for 1.1.4. Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? Index: debian/control === --- debian/control (revisione 2974) +++ debian/control (copia locale) @@ -11,6 +11,7 @@ libncursesw5-dev, libsamplerate-dev, pkg-config, + python-docutils, xmlto Standards-Version: 3.9.8 Homepage: https://www.alsa-project.org/ Index: debian/patches/add_missing_alsaucm_man_page.diff === --- debian/patches/add_missing_alsaucm_man_page.diff (nonexistent) +++ debian/patches/add_missing_alsaucm_man_page.diff (copia locale) @@ -0,0 +1,252 @@ +Author: Antonio Ospite <a...@ao2.it> +Description: Add back the missing source of the alsaucm man page + +The reStructuredText source document for the alsaucm man page was missing in +in the 1.1.3 release tarball, so add it back with a patch for the time being. +The problem has already been fixed upstream: +http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=c6bdde171e1532f7b37333a5a746b6e662f12c53 + +This mean that the tarball of the next 1.1.4 will contain alsaucm.rst and this +patch could then be dropped. + +Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=9 + +diff -pruN ../alsa-utils-1.1.3/alsaucm/alsaucm.rst alsa-utils-1.1.3/alsaucm/alsaucm.rst +--- ../alsa-utils-1.1.3/alsaucm/alsaucm.rst 1970-01-01 01:00:00.0 +0100 alsa-utils-1.1.3/alsaucm/alsaucm.rst 2017-01-24 12:19:00.0 +0100 +@@ -0,0 +1,235 @@ ++= ++ alsaucm ++= ++ ++--------- ++ALSA Use Case Manager ++- ++ ++:Author: Antonio Ospite <a...@ao2.it> ++:Date: 2016-09-22 ++:Copyright: GPLv2+ ++:Manual section: 1 ++:Manual group: General Commands Manual ++ ++SYNOPSIS ++ ++ ++*alsaucm* [command] ++ ++DESCRIPTION ++=== ++ ++alsaucm (ALSA Use Case Manager) is a program to use the ALSA `Use Case ++Interface`_ from the command line. ++ ++On complex sound cards, setting up audio routes is not trivial and mixer ++settings can conflict one another preventing the audio card to work at all. ++ ++The ALSA Use Case Manager is a mechanism for controlling complex audio ++hardware establishing a relationship between hardware configurations and ++meaningful use cases that the end-user can relate with. ++ ++The use case manager can also be used to switch between use cases when ++necessary, in a consistent way. ++ ++At a lower level, the use case manager works by configuring the sound card ++ALSA kcontrols to change the hardware digital and analog audio routing to ++match the requested device use case. ++ ++The use case manager kcontrol configurations are stored in easy to modify text ++files. An audio use case can be defined by a **verb** and **device** parameter. ++ ++The verb describes the use case action i.e. a phone call, listening to music, ++recording a conversation etc. The device describes the physical audio capture ++and playback hardware i.e. headphones, phone handset, bluetooth headset, etc. ++ ++ ++OPTIONS ++=== ++ ++Available options: ++ ++ **-h**, **--help** ++this help ++ ++ **-c**, **--card** `NAME` ++open card NAME ++ ++ **-i**, **--interactive** ++interactive mode ++ ++ **-b**, **--batch** `FILE` ++batch mode (use ``'-'`` for the stdin input) ++ ++ **-n**, **--no-open** ++do not open first card found ++ ++ ++Available co
Bug#852299: alsa-utils: ship alsaucm man page
Package: alsa-utils Version: 1.1.3-1 Severity: wishlist Dear Maintainer, since alsa-utils 1.1.3 alsa-utils ships a man page for the alsaucm utility program. It would be great if you can ship it in the debian package. The unix man page is built from a reStructuredText source file using the rst2man program which in Debian can be found in python-docutils or python3-docutils; so build-depending on either one of these should be enough to make the build system generate alsaucm.1. If you are building from tarballs and alsaucm.rst is missing there, this has been fixed after 1.1.3, see: http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=c6bdde171e1532f7b37333a5a746b6e662f12c53 If this is the case tell if you want me to send a patch which adds alsucm.rst at packaging time, until the next stable tarball. Thanks, Antonio -- System Information: Debian Release: 9.0 APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.9.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages alsa-utils depends on: ii dialog1.3-20160828-2 ii kmod 23-2 ii libasound21.1.3-1 ii libc6 2.24-9 ii libfftw3-single3 3.3.5-3 ii libncursesw5 6.0+20161126-1 ii libsamplerate00.1.8-8 ii libtinfo5 6.0+20161126-1 ii lsb-base 9.20161125 ii whiptail 0.52.19-1 alsa-utils recommends no packages. alsa-utils suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#704037: [Piuparts-devel] Bug#704037: piuparts: fail with umount while mounting /proc/sys/fs/binfmt_misc
On Sun, 11 Dec 2016 19:55:13 + Holger Levsen <hol...@layer-acht.org> wrote: > control: tags -1 + patch > thanks > > Hi Antonio, > > On Sun, Dec 11, 2016 at 07:40:23PM +0100, Antonio Ospite wrote: > > I am attaching a patch which adds the workaround. > > awesome, thanks! [...] > > I'm basically about to leave for > https://reproducible-builds.org/events/berlin2016/ so it will take some > days til I'll find time to apply this. Feel free to ping me again in a > week! > > Ping. -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#704037: [Piuparts-devel] Bug#704037: piuparts: fail with umount while mounting /proc/sys/fs/binfmt_misc
On Fri, 9 Dec 2016 19:58:17 +
Holger Levsen <hol...@layer-acht.org> wrote:
> On Wed, Dec 07, 2016 at 10:15:25AM +0100, Antonio Ospite wrote:
> > Ping. Is the change from below OK? If it is I will send a proper patch.
>
> yes, please send a git patch. +thanks!
>
> also a debian bug against the binfmt-support package would be
> appreciated, so that it also gets fixed properly there.
>
Hi Holger,
I am attaching a patch which adds the workaround.
I also reported the issue to binfmt-support:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847788
Thanks,
Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
>From 5a5ae7619afadbc97f607a4d8370496333e8299f Mon Sep 17 00:00:00 2001
From: Antonio Ospite <a...@ao2.it>
Date: Sun, 11 Dec 2016 17:16:14 +0100
Subject: [PATCH] Umount /proc/sys/fs/binfmt_misc to work around a binfmt bug
Some java packages (e.g. "signtos") trigger update-binfmts, which mounts
/proc/sys/fs/binfmt_misc but never unmounts it.
When dealing with such scenario piuparts cannot unmount the chroot
successfully because /proc results busy.
Work around the issue by force-unmounting /proc/sys/fs/binfmt_misc
before anything else.
The same workaround was also used in other projects:
https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/534211
https://lists.debian.org/debian-live/2007/01/msg00039.html
Closes: #704037
---
piuparts.py | 6 ++
1 file changed, 6 insertions(+)
diff --git a/piuparts.py b/piuparts.py
index dbf2b18d..f9b0b126 100644
--- a/piuparts.py
+++ b/piuparts.py
@@ -1577,6 +1577,12 @@ class Chroot:
def unmount_all(self):
"""Unmount everything we mount()ed into the chroot."""
+
+# Workaround to unmount /proc/sys/fs/binfmt_misc which is mounted by
+# update-binfmts but never unmounted, see:
+# https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704037
+run(["umount", self.relative("/proc/sys/fs/binfmt_misc")], ignore_errors=True)
+
for mountpoint in reversed(self.mounts):
run(["umount", mountpoint], ignore_errors=True)
--
2.11.0
Bug#847788: binfmt-support: update-binfmt mounts /proc/sys/fs/binfmt_misc but does not unmount it
Package: binfmt-support Version: 2.1.6-1 Severity: minor Dear Maintainer, in some cases update-binfmt mounts /proc/sys/fs/binfmt_misc but then it does not unmount it. This can causes problems if that happened in a chroot environment because it leaves /proc busy and so a cleanup task run when exiting the chroot can fail. For instance we noticed this behavior with piuparts, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704037 In that bug report there are also instructions to reproduce the issue. Piuparts is adding a workaround for the problem, but it would be great if this could be solved properly in binfmt-support. Thanks, Antonio -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages binfmt-support depends on: ii init-system-helpers 1.46 ii libc62.24-8 ii libpipeline1 1.4.1-2 ii lsb-base 9.20161125 binfmt-support recommends no packages. binfmt-support suggests no packages. -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#704037: piuparts: fail with umount while mounting /proc/sys/fs/binfmt_misc
On Sat, 29 Oct 2016 16:47:56 +0200
Antonio Ospite <a...@ao2.it> wrote:
> Package: piuparts
> Version: 0.72
> Followup-For: Bug #704037
>
> Dear Maintainer,
>
> I ran into this issue when working on a java package, it is indeed related to
> binfmt-support as the original submitter said.
>
Ping. Is the change from below OK? If it is I will send a proper patch.
Thanks,
Antonio
> I am not attaching the log as it looks a lot like the one already posted.
>
> I found some more info in an Ubuntu bug report:
> https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/534211
>
> And it looks like debian-live has a workaround for this issue as well:
> https://lists.debian.org/debian-live/2007/01/msg00039.html
>
> I can reproduce the problem with the "signtos" package, which has
> similar dependencies to the one I am working on which is not in debian
> yet (in particular they both depend on jarwrapper).
>
> Here's how to reproduce it with a pbuilder chroot:
>
> $ DIST=sid ARCH=amd64 BUILDER=pbuilder git pbuilder create
> $ wget
> http://deb.debian.org/debian/pool/main/a/android-platform-build/signtos_6.0.1+r55-3_all.deb
> $ DIST=sid ARCH=amd64 eval sudo piuparts --log-level dump
> --list-installed-files --pedantic-purge-test --warn-on-leftovers-after-purge
> --warn-on-others -b '/var/cache/pbuilder/base-$DIST-$ARCH.tgz'
> signtos_6.0.1+r55-3_all.deb
>
> The change below works around it, after applying it piuparts unmounts the
> chroot successfully:
>
> --
> --- /usr/sbin/piuparts2016-08-03 11:24:56.0 +0200
> +++ piuparts 2016-10-29 15:23:16.137417215 +0200
> @@ -1576,6 +1576,13 @@ class Chroot:
>
> def unmount_all(self):
> """Unmount everything we mount()ed into the chroot."""
> +
> +# Hack to umount /proc/sys/fs/binfmt_misc which is mounted by
> +# update-binfmts, see
> +#
> https://bugs.launchpad.net/ubuntu/+source/binfmt-support/+bug/534211
> +# https://lists.debian.org/debian-live/2007/01/msg00039.html
> +run(["umount", self.relative("/proc/sys/fs/binfmt_misc")],
> ignore_errors=True)
> +
> for mountpoint in reversed(self.mounts):
> run(["umount", mountpoint], ignore_errors=True)
>
> ------
>
> I don't know if this can or should be fixed in binfmt-support, but if you want
> to add the workaround to piupoarts I can send a proper patch.
>
> Thanks,
>Antonio
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
Bug#746005: Still FTBFS with lilypond 2.19-50
On Tue, 22 Nov 2016 23:01:16 +0100 Antonio Ospite <a...@ao2.it> wrote: [...] > The updated patchset is here: > https://ao2.it/tmp/lilypond-guile2/patches_2016-11-22/ > Hi, any update on this? BTW now there is also a dev/guile-v2-work branch in the upstream lilypond repository with the same changes from above. Ciao, Antonio > Note that in order to have useful results when using guile-2.0 lilypond > has to be run in a UTF-8 locale. > > That holds true for the make commands too, so make sure the locale is > set up appropriately when you build the debian package. > > I know that depending on the locale is not ideal, in the log run > lilypond should be made more locale independent, but we have to live > with this limitation for now. > -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#743599: lintian: false positive python-script-but-no-python-dep when using #!/usr/bin/python2
Control: tags -1 patch On Tue, 29 Nov 2016 20:56:00 + Niels Thykier <ni...@thykier.net> wrote: > > Hi, > > Thanks for the provided patches. > [...] > > I have applied the changes to the test case. However, the changes to > the data files (regardless of which one I apply) cause a test regression > there after AFAICT. > > The test failure is: > > $ t/runtests -k -j1 t debian/test-out legacy-scripts > > ENV[PATH]=/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games > > tests::legacy-scripts: diff -u t/tests/legacy-scripts/tags > > [...]/tests/scripts/tags.scripts > > --- t/tests/legacy-scripts/tags 2016-11-29 20:42:28.674312854 + > > +++ [...]/tests/scripts/tags.scripts2016-11-29 20:50:22.238324980 > > + > > @@ -13,11 +13,11 @@ > > E: scripts: init.d-script-needs-depends-on-lsb-base etc/init.d/skeleton > > (line 40) > > E: scripts: missing-dep-for-interpreter jruby => jruby | jruby1.0 | > > jruby1.1 | jruby1.2 (usr/bin/jruby-broken) > > E: scripts: missing-dep-for-interpreter lefty => graphviz > > (usr/bin/lefty-foo) > > +E: scripts: missing-dep-for-interpreter python2 => python:any | > > python-minimal:any (usr/bin/py2foo) > > E: scripts: package-installs-python-bytecode > > usr/lib/python2.3/site-packages/test.pyc > > E: scripts: php-script-but-no-phpX-cli-dep usr/share/scripts/php5foo > > E: scripts: php-script-but-no-phpX-cli-dep usr/share/scripts/phpfoo > > E: scripts: python-script-but-no-python-dep usr/bin/py2.Xfoo > > -E: scripts: python-script-but-no-python-dep usr/bin/py2foo > > E: scripts: python-script-but-no-python-dep usr/bin/pyfoo > > E: scripts: shell-script-fails-syntax-check usr/bin/sh-broken > > E: scripts: wrong-path-for-interpreter usr/bin/lefty-foo > > (#!/usr/local/bin/lefty != /usr/bin/lefty) > > fail tests::legacy-scripts: output differs! > > I don't think that change was intentional, so I am sending the patch > back for another review. > Lintian is right, I forgot to add the changes to t/tests/legacy-scripts/tags. New patch attached, rebased on top of the master branch. I also updated the commit message to explain why the emitted error changed, I hope it explains the changes clearly enough. Thanks, Antonio -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? >From 347c834e66b9d21d7379ec2a32907d21c378a759 Mon Sep 17 00:00:00 2001 From: Antonio Ospite <a...@ao2.it> Date: Mon, 7 Nov 2016 16:55:26 +0100 Subject: [PATCHv2] data/scripts/interpreter.txt: fix false positive with python2 as interpreter When using dh_python2 the package ends up depending on pyhton:any (Debian does not have a python2:any package). However if a script uses python2 as the interpreter, the lintian dependency checks fails: E: scripts: python-script-but-no-python-dep usr/bin/script_name Basically lintian tries to look for a dependency on python2:any, it does not know that python:any is OK as a dependency for scripts using python2 in the shebang line. This can be verified by temporarily adding "python:any" to t/tests/legacy-scripts/debian/debian/control and running the test: debian/rules runtests onlyrun=legacy-scripts Lintian will not give the error anymore for pyfoo, but it will still emit it for py2foo which is wrong. Fix the issue adding python2 to the unversioned interpreters, the rationale being that the python2 interpreter requires unversioned dependencies. After the fix, lintian will give a clearer error when the dependency is really missing: E: scripts: missing-dep-for-interpreter python2 => python:any | python-minimal:any (usr/bin/py2foo) And to prove that the false positive is not occurring anymore, temporarily adding "python:any" to t/tests/legacy-scripts/debian/debian/control will not give the error anymore for py2foo either when running: debian/rules runtests onlyrun=legacy-scripts --- data/scripts/interpreters | 1 + t/tests/legacy-scripts/tags | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/data/scripts/interpreters b/data/scripts/interpreters index 81100d2..3f5e2d5 100644 --- a/data/scripts/interpreters +++ b/data/scripts/interpreters @@ -73,6 +73,7 @@ plackup=> /usr/bin, libplack-perl procmail => /usr/bin pypy => /usr/bin python => /usr/bin, python:any | python-minimal:any +python2=> /usr/bin, python:any | python-minimal:any pforth => /usr/bin racket => /usr/bin rake => /usr/bin diff --git a/t/tests/legacy-scripts/tags b/t/tests/legacy-scripts/tags index 58d6d62..913844d 1006
Bug#834135: mplayer crashes with SIGSEGV when taking a screenshot
Package: mplayer Version: 2:1.3.0-5 Followup-For: Bug #834135 Dear Maintainer, the crash when taking screenshots is still there in 2:1.3.0-5. The patch in my previous message fixes it, please consider applying it. Thanks, Antonio -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'unstable-debug') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Init: systemd (via /run/systemd/system) Versions of packages mplayer depends on: ii liba52-0.7.4 0.7.4-18 ii libaa11.4p5-44 ii libasound21.1.2-1 ii libass5 0.13.4-1 ii libaudio2 1.9.4-5 ii libavcodec57 7:3.2-2 ii libavformat57 7:3.2-2 ii libavutil55 7:3.2-2 ii libbluray11:0.9.3-3 ii libbs2b0 3.1.0+dfsg-2.2 ii libc6 2.24-6 ii libcaca0 0.99.beta19-2+b1 ii libcdio-cdda1 0.83-4.2+b1 ii libcdio-paranoia1 0.83-4.2+b1 ii libcdio13 0.83-4.2+b1 ii libdca0 0.0.5-10 ii libdirectfb-1.2-9 1.2.10.0-5.2+b1 ii libdv41.0.0-11 ii libdvdnav45.0.3-2 ii libdvdread4 5.0.3-2 ii libenca0 1.19-1 ii libfaad2 2.8.0~cvs20161113-1 ii libfontconfig12.11.0-6.7 ii libfreetype6 2.6.3-3+b1 ii libfribidi0 0.19.7-1 ii libgif7 5.1.4-0.4 ii libgl1-mesa-glx [libgl1] 12.0.4-2 ii libjack-jackd2-0 [libjack-0.116] 1.9.10+20150825git1ed50c92~dfsg-3 ii libjpeg62-turbo 1:1.5.1-2 ii liblirc-client0 0.9.4c-4 ii libmad0 0.15.1b-8 ii libmpeg2-40.5.1-7 ii libmpg123-0 1.23.8-1 ii libogg0 1.3.2-1 ii libopenal11:1.17.2-4 ii libpng16-16 1.6.26-2 ii libpostproc54 7:3.2-2 ii libpulse0 9.0-5 ii libsdl1.2debian 1.2.15+dfsg1-4 ii libsmbclient 2:4.4.7+dfsg-1 ii libspeex1 1.2~rc1.2-1 ii libswresample27:3.2-2 ii libswscale4 7:3.2-2 ii libtheora01.1.1+dfsg.1-14 ii libtinfo5 6.0+20160917-1 ii libvdpau1 1.1.1-5 ii libvorbisidec11.0.2+svn18153-0.2 ii libx11-6 2:1.6.3-1 ii libxext6 2:1.3.3-1 ii libxinerama1 2:1.1.3-1+b1 ii libxss1 1:1.2.2-1 ii libxv12:1.0.10-1+b1 ii libxvidcore4 2:1.3.4-1 ii libxvmc1 2:1.0.9-1 ii libxxf86dga1 2:1.1.4-1+b1 ii libxxf86vm1 1:1.1.4-1 ii zlib1g1:1.2.8.dfsg-2+b3 mplayer recommends no packages. Versions of packages mplayer suggests: ii bzip2 1.0.6-8 ii fontconfig 2.11.0-6.7 ii fonts-freefont-ttf 20120503-4 pn mplayer-doc pn netselect | fping -- no debconf information -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
Bug#569668: Is there still interest in davmail for Debian?
On Sun, 30 Oct 2016 09:20:37 +0100 Antonio Ospite <a...@ao2.it> wrote: [...] > Upstream is looking at the "no-headers" issue, but in the meantime we > can finish the packaging work. > Hi again, upstream seems busy and does not reply to the bug report[1], I also had confirmation from the javamail developer[2] that the fix should be in davmail; so let's just include the fix I proposed[3] and try to have davmail uploaded. What do you think Alexandre? Thanks, Antonio [1] https://sourceforge.net/p/davmail/bugs/633/ [2] https://kenai.com/bugzilla/show_bug.cgi?id=8562 [3] https://sourceforge.net/p/davmail/bugs/_discuss/thread/23c46505/f175/1549/attachment/0001-Fix-the-usage-of-the-MimeMessage-class-with-javamail.patch -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing?
