Urgent Please.
Hello dear, Did you receive my email message to you? Please, get back to me ASAP as the matter is becoming late. Expecting your urgent response. Regards, Sean --- This email has been checked for viruses by AVG. https://www.avg.com
Bug#909133: ITP: auto-dictionary-el -- automatic dictionary switcher for Emacs spell checking
Package: wnpp Severity: wishlist Owner: Nicholas D Steeves Package name: auto-dictionary-el Version : 1.1 Upstream Author : Nikolaj Schumacher URL : https://wiki.debian.org/EmacsenTeam/Team License : GPL-2+ Programming Lang: elisp Description : automatic dictionary switcher for Emacs spell checking Auto-dictionary is a minor mode that automatically sets 'ispell-dictionary'. It hooks into flyspell's on-the-fly spell checking, and extends these checks to also detect language. This package is useful for Emacs users who work in multiple languages. . Auto-dictionary supports the following languages: Catalan Classical Greek - ἑλληνικά Danish - Dansk English Esperanto French - Français German - Deutsch Hindi - हिन्दी Hungarian - Magyar Modern Greek - νέα ελληνικά Norwegian Bokmål Norwegian Nynorsk Portuguese - Português Romanian - Românâ, Româneşte Slovak - Slovenčina Slovene - Slovenian Spanish - Español Swedish - Svenska -- Antoine, does it detect language with per-buffer granularity, or support mixing languages in the same buffer? Thanks for mentioning that you use this software on #debian-emacs :-) P.S. please ping me if I take more than two weeks to package this I do not yet use this package and have been manually switching between languages, which is why I'm motivated to package it. I plan to maintain it as part of the Debian Emacsen Team, and the team policy is here: https://wiki.debian.org/EmacsenTeam/Team I will require a sponsor for the initial upload. Regards, Nicholas
Re: Package not compatible with old systemd
Hi, út 18. 9. 2018 v 12:27 odesílatel Michael Biebl napsal: > Fwiw, we had a similar issue in udev, see > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903224 > for the gory details. > thanks. > Have you tried running your swift service with an older (say v232 from > stable) systemd? > Does the service fail to start or does it have a proper fallback? > Tried. It starts (it ignores new unit directive) and if /var/cache/swift directory exists from past, it works fine. If it doesn't exists, some of swift components doesn't work correctly. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Package not compatible with old systemd
Hi, út 18. 9. 2018 v 12:18 odesílatel Michael Biebl napsal: > assume you (re)start your service in postinst? In this case you need a > running systemd >= 235 at that point. > yes. > We do re-exec systemd in postinst, but a versioned Breaks or Conflicts > does not give you the guarantee that systemd.postinst has run before > your postinst. > this is not issue for me, because when I'm upgrading swift package, /var/cache/swift directory already exists from the past (created by older version of swift with "old" method). Thanks. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Package not compatible with old systemd
Am 18.09.18 um 12:00 schrieb Michael Biebl: > I assume you (re)start your service in postinst? In this case you need a > running systemd >= 235 at that point. > We do re-exec systemd in postinst, but a versioned Breaks or Conflicts > does not give you the guarantee that systemd.postinst has run before > your postinst. > > This is not an issue for distros which do offline updates, but for > online updates this is problematic. > > My advice would be, to only use features that systemd from stable provides. Fwiw, we had a similar issue in udev, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=903224 for the gory details. Have you tried running your swift service with an older (say v232 from stable) systemd? Does the service fail to start or does it have a proper fallback? Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Package not compatible with old systemd
Am 18.09.18 um 09:21 schrieb Ondrej Novy: > Hi, > > my package src:swift is not compatible with old systemd, because I'm > using CacheDirectory in unit file. CacheDirectory is supported from > systemd 235. > > I think correct solution is to add to binary package this relation: > Breaks: systemd (<< 235~) > > Thomas Goirand (zigo) said it's wrong and correct solution is: > Depends: systemd (>= 235~) | sysv-init | openrc > > I don't currently depend on systemd, or any other init system. > > I think my solution is correct, because Swift works with any init system > and I want to only say "it doesn't work with older systemd". I don't > think it's correct to list all possible init systems in Depends. > I assume you (re)start your service in postinst? In this case you need a running systemd >= 235 at that point. We do re-exec systemd in postinst, but a versioned Breaks or Conflicts does not give you the guarantee that systemd.postinst has run before your postinst. This is not an issue for distros which do offline updates, but for online updates this is problematic. My advice would be, to only use features that systemd from stable provides. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: Package not compatible with old systemd
Hi, út 18. 9. 2018 v 10:30 odesílatel Lars Wirzenius napsal: > Would Conflicts work here? > Conflicts is just more strict Breaks, for example when files are overwritten. This is not case and Breaks "is enough". -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
Re: Package not compatible with old systemd
On Tue, Sep 18, 2018 at 09:21:11AM +0200, Ondrej Novy wrote: > I think my solution is correct, because Swift works with any init system > and I want to only say "it doesn't work with older systemd". I don't think > it's correct to list all possible init systems in Depends. Would Conflicts work here? Conflicts: systemd (<< 235~) -- I want to build worthwhile things that might last. --joeyh signature.asc Description: PGP signature
Package not compatible with old systemd
Hi, my package src:swift is not compatible with old systemd, because I'm using CacheDirectory in unit file. CacheDirectory is supported from systemd 235. I think correct solution is to add to binary package this relation: Breaks: systemd (<< 235~) Thomas Goirand (zigo) said it's wrong and correct solution is: Depends: systemd (>= 235~) | sysv-init | openrc I don't currently depend on systemd, or any other init system. I think my solution is correct, because Swift works with any init system and I want to only say "it doesn't work with older systemd". I don't think it's correct to list all possible init systems in Depends. Can you help us? Thanks. -- Best regards Ondřej Nový Email: n...@ondrej.org PGP: 3D98 3C52 EB85 980C 46A5 6090 3573 1255 9D1E 064B
