Bug#1005180: update-mime: conffile can't update settings
Le Wed, Mar 30, 2022 at 06:04:06PM +0300, Yair Yarom a écrit : > > This is a somewhat obscure feature (and not really documented), so I doubt > it breaks many systems, and so I'm not sure how urgent this is to be > backported. Thanks Yair for the fast answer, indeed, it is undocumented and I did not receive more reports about the breakage, so I will not backport or update stable unless there is more demand for it. Have a nice day, -- Charles
Bug#1005180: update-mime: conffile can't update settings
On Sun, 27 Mar 2022 at 12:21, Charles Plessy wrote: > Do you think a backport or a stable update would be needed ? > I don't really know the policies regarding when to update stable or create a backport, so I can't say. As I'm aware of it - I already have my workaround, but it will be nice to have it available (backport or stable). This is a somewhat obscure feature (and not really documented), so I doubt it breaks many systems, and so I'm not sure how urgent this is to be backported. Thanks, Yair. -- /| | \/ | Yair Yarom | System Group (DevOps) [] | The Rachel and Selim Benin School [] /\| of Computer Science and Engineering []//\\/ | The Hebrew University of Jerusalem [// \\ | T +972-2-5494522 | F +972-2-5494522 //\ | ir...@cs.huji.ac.il //|
Bug#1005180: update-mime: conffile can't update settings
Control: tag -1 pending Le Tue, Feb 08, 2022 at 04:30:09PM +0200, Yair Yarom a écrit : > > In update-mime, setting all variable with 'my' prevents them from > being updated by the conf file (/etc/update-mime.conf). Setting them > to 'our' solves this issue. Dear Yair, thank you for your report and the patch, and sorry for the regression. I have pushed a commit that changes `my` to `our` in all variables of that block, except for `$conffile` where `our` would not make sense. I am tagging this patch "pending" but it may take a bit of time before I upload an update, as I would like to go through of a couple of other open issues first. Do you think a backport or a stable update would be needed ? Have a nice day, Charles -- Charles Plessy Nagahama, Yomitan, Okinawa, Japan Tooting from work, https://mastodon.technology/@charles_plessy Tooting from home, https://framapiaf.org/@charles_plessy signature.asc Description: PGP signature
Bug#1005180: update-mime: conffile can't update settings
Package: mailcap Version: 3.69 Severity: normal Tags: patch Dear Maintainer, In update-mime, setting all variable with 'my' prevents them from being updated by the conf file (/etc/update-mime.conf). Setting them to 'our' solves this issue. We use this so that locally installed applications won't mess up the distribution's /usr/lib (specifically $appsdir and $mimedir). Regards, Yair. -- System Information: Debian Release: 11.2 APT prefers stable-security APT policy: (910, 'stable-security'), (900, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.10.79-aufs-1 (SMP w/1 CPU thread) Locale: LANG=en_IL.UTF-8, LC_CTYPE=en_IL.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en_GB:en Shell: /bin/sh linked to /usr/bin/bash Init: systemd (via /run/systemd/system) Versions of packages mailcap depends on: ii media-types 4.0.0 ii perl 5.32.1-4+deb11u2 Versions of packages mailcap recommends: ii bzip2 1.0.8-4 ii file 1:5.39-3 ii xz-utils 5.2.5-2 mailcap suggests no packages. -- Configuration Files: /etc/mailcap.order changed [not included] -- no debconf information --- /usr/sbin/update-mime 2021-02-25 20:24:36.0 +0200 +++ /tmp/update-mime2022-02-08 16:10:34.551409405 +0200 @@ -26,8 +26,8 @@ my $conffile = "/etc/update-mime.conf"; my $mailcap= "/etc/mailcap"; my $mailcapdef = "/usr/lib/mime/mailcap"; -my $mimedir= "/usr/lib/mime/packages"; -my $appsdir= "/usr/share/applications"; +our $mimedir = "/usr/lib/mime/packages"; +our $appsdir = "/usr/share/applications"; my $orderfile = "/etc/mailcap.order"; my $defpriority= 5; my $localgen = 0;
