Bug#991541: Related merge request
Dear maintainer, I have added a related merge request on salsa fast-forwarding the related git sub-module to the fixed version. https://salsa.debian.org/php-team/pear/php-pear/-/merge_requests/3 Not entirely sure if gitlab is the best route to help in this package case, but since I saw a couple of MRs closed, I decided to go that way. Let me know if other changes would be needed, or any other feedback, Best, -Marco
Bug#1001593: php-easyrdf: flaky autopkgtest: Unable to connect to localhost:10101
El Sun, 16 Jan 2022 22:14:37 +0200 Adrian Bunk escribió: > ... > > I've cancelled it. > > ... Adrian, thank you for canceling the upload. I have now published a related change over the git repository on the debian/bullseye branch targeting unstable. When I first looked at the problem I thought I have seen it before, and indeed, I have added a work-around for it for the first smoke test a while ago, but with curl and a fixed time to wait. Just to keep the same approach, I added similar lines to the second smoke test. Please find more details on the related[1] commit now on salsa. 1: https://salsa.debian.org/php-team/pear/php-easyrdf/-/commit/eb3ecb4dbd17ace43150b9fabd2a7bc2230724f6 Best, -Marco pgprPSgOpZyQ8.pgp Description: Firma digital OpenPGP
Bug#1001593: [pkg-php-pear] Bug#1001593: php-easyrdf: diff for NMU version 1.0.0-2.1
Adrian, Paul: Thanks for reporting and providing a possible solution for this. I see how this could be a racing problem. I see there may be a similar problem on the other test script, so I would add a similar change to the other. I see that I would need to add nc as a dev dependency for this to work correctly, so if possible, please prevent the NMU to arrive, I am not sure about the process to do that. I will try to get a working version of this for both debian/bullseye and mainline versions of the package before Monday ;-) Best, -Marco El Sat, 15 Jan 2022 20:52:46 +0200 Adrian Bunk escribió: > Control: tags 1001593 + patch > Control: tags 1001593 + pending > > Dear maintainer, > > I've prepared an NMU for php-easyrdf (versioned as 1.0.0-2.1) and > uploaded it to DELAYED/2. Please feel free to tell me if I should > cancel it. > > cu > Adrian
Bug#994209: Markdown links syntax performance issue
I am attaching here the related new patch, which is also available in
the merge request added at
https://salsa.debian.org/vim-team/vim/-/merge_requests/5.
Best,
-Marco
From: Marco Villegas
Date: Mon, 13 Sep 2021 12:42:32 -0500
Subject: Mitigate markdown syntax link performance issue
Adapted from K.Takata suggestion at
https://github.com/vim/vim/issues/6777#issuecomment-684776825
Upstream issue at https://github.com/vim/vim/issues/6777
Related issue https://github.com/vim/vim/issues/2049
Closes: #994209
Signed-off-by: Marco Villegas
---
runtime/syntax/markdown.vim | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/runtime/syntax/markdown.vim b/runtime/syntax/markdown.vim
index 17b61c2..860cfe5 100644
--- a/runtime/syntax/markdown.vim
+++ b/runtime/syntax/markdown.vim
@@ -79,7 +79,7 @@ syn region markdownUrlTitle matchgroup=markdownUrlTitleDelimiter start=+"+ end=+
syn region markdownUrlTitle matchgroup=markdownUrlTitleDelimiter start=+'+ end=+'+ keepend contained
syn region markdownUrlTitle matchgroup=markdownUrlTitleDelimiter start=+(+ end=+)+ keepend contained
-syn region markdownLinkText matchgroup=markdownLinkTextDelimiter start="!\=\[\%(\%(\_[^][]\|\[\_[^][]*\]\)*]\%( \=[[(]\)\)\@=" end="\]\%( \=[[(]\)\@=" nextgroup=markdownLink,markdownId skipwhite contains=@markdownInline,markdownLineStart
+syn region markdownLinkText matchgroup=markdownLinkTextDelimiter start="!\=\[\%(\_[^][]*\%(\[\_[^][]*\]\_[^][]*\)*]\%( \=[[(]\)\)\@=" end="\]\%( \=[[(]\)\@=" nextgroup=markdownLink,markdownId skipwhite contains=@markdownInline,markdownLineStart
syn region markdownLink matchgroup=markdownLinkDelimiter start="(" end=")" contains=markdownUrl keepend contained
syn region markdownId matchgroup=markdownIdDelimiter start="\[" end="\]" keepend contained
syn region markdownAutomaticLink matchgroup=markdownUrlDelimiter start="<\%(\w\+:\|[[:alnum:]_+-]\+@\)\@=" end=">" keepend oneline
Bug#994209: Markdown links syntax performance issue
Package: vim-runtime Version: 2:8.2.2434-3 Severity: important Tags: upstream On markdown files of a certain size, the markdown syntax regular expression to detect links can produce a E363 error. More specifically "E363: pattern uses more memory than 'maxmempattern'". This is likely expected since the regular expression is resource heavy. A sample markdown file is attached, where the problem can be reproduced. After opening with a command like the mentioned above, try to add a markdown link at the first word in the file; adding a "[" at the start of the file will produce the error. vim -u NONE -U NONE -c 'syntax enable' sample.md Gladly, there is already a work-around available to prevent the error, which improves the regular expression. More information at the upstream related issues https://github.com/vim/vim/issues/2049 and https://github.com/vim/vim/issues/6777. This is likely bug fix relevant for unstable, testing, and stable. I will provide related changes in a bit. Best, -Marco Vero iriure in dolor veniam ullamcorper ut commodo. Accumsan nisl et consectetuer dolore, nonummy duis te blandit quis duis vulputate eu. Ex wisi dolore in diam ea delenit nibh velit vero augue illum, consequat: delenit quis consequat. Nonummy dignissim feugait ullamcorper ea ut quis iusto ad in iriure! Qui duis minim ut veniam laoreet in erat. Commodo consequat nostrud zzril dolor tincidunt aliquam laoreet ad dolor magna aliquip dolore. Vero adipiscing magna vel sit consequat nulla lorem. Duis ullamcorper nulla suscipit ad vel, nulla esse. Et minim: blandit dolor molestie facilisis esse ea vulputate et adipiscing nibh. Quis ex te dolor ut duis iusto zzril, quis? Nulla dolor minim exerci, esse ea suscipit nibh autem. Zzril duis tincidunt et elit lorem commodo laoreet nibh magna luptatum delenit commodo veniam dolore! In qui -- quis eros dignissim dolore, dignissim autem lobortis ullamcorper nonummy, vero qui duis. Nonummy illum dolore lorem, vel dolor amet dignissim dolor nulla velit veniam illum minim at? Velit lobortis ut praesent lobortis molestie in eum! Erat et lobortis euismod nisl nibh -- vel dolor praesent! Praesent dolor velit, consectetuer illum facilisi suscipit volutpat ea, exerci: euismod et, minim duis facilisis, blandit. Erat dolore volutpat consequat facilisis duis, in accumsan veniam. Duis lorem praesent, odio, dolore vero dolor at enim luptatum odio nulla -- diam feugait. Volutpat, ut delenit wisi luptatum blandit illum commodo dignissim quis. Lobortis erat: eum veniam blandit vel ea dolore. Wisi ut nisl laoreet accumsan, in blandit, nisl, wisi ex consectetuer te tincidunt laoreet illum -- enim. Lorem dolore euismod aliquip eum, quis dolore vel feugait autem eu, ex vero dolore eros luptatum. Praesent nostrud consequat tation diam exerci duis luptatum eros eros hendrerit adipiscing wisi quis? Illum minim illum qui vero delenit luptatum ex ex. Quis aliquam delenit tation autem, aliquip in dignissim dolore facilisi exerci; sed esse suscipit minim. Feugait enim vel odio qui ea nisl feugiat quis aliquip in tation dolor consectetuer dolore at. Dignissim, quis praesent wisi lorem -- veniam et praesent. Nostrud ea wisi dignissim adipiscing tation; nonummy diam nulla, vel ex ut zzril in consequat. Wisi dolor iusto -- molestie, vero esse vulputate augue ex et praesent praesent enim dolor nostrud? Ut minim veniam nulla exerci veniam, exerci vel iusto dolor. Duis in dolore, amet dolore eum luptatum sit volutpat. Ut dolore feugiat zzril suscipit iriure et in, ullamcorper vulputate elit lobortis tation sit. Delenit nibh minim veniam augue suscipit consequat ut adipiscing vero nisl ex. Erat suscipit consectetuer nisl volutpat accumsan dolore iriure iusto sit in ex duis nonummy euismod. Nulla ullamcorper eum, qui feugiat accumsan duis nisl facilisis enim sed sit! Accumsan iriure dolor vel dolore blandit ut sit nonummy adipiscing elit velit, vel, nisl tation nonummy. Nisl odio sit in exerci ad dolore duis dolor duis diam veniam consectetuer diam hendrerit nulla. Ut vulputate facilisis suscipit dolore et feugait nostrud euismod iusto volutpat in praesent at commodo. Velit nulla diam autem lorem, qui qui ut volutpat duis. Ex ea illum consectetuer consequat nostrud delenit dolore tation elit dolor vel odio veniam? Elit, dolore nulla feugait quis feugiat sit et, suscipit iusto enim autem facilisi duis? Qui in aliquip, tincidunt ex sed delenit wisi. Euismod te, in facilisi illum qui minim vulputate, ut accumsan ea odio delenit minim, praesent feugait? Magna iusto qui eum at zzril at, nulla quis vel et eum suscipit dolor diam. Augue veniam in dignissim sed adipiscing ad ut dolore. Sit commodo laoreet hendrerit ad euismod exerci zzril, eros, nonummy ullamcorper autem veniam. Tation ex consectetuer nibh dignissim, vero laoreet -- ullamcorper illum. Facilisi, et, hendrerit dolor iusto vero tincidunt dolor nulla; ipsum, eros sit amet veniam? Et odio diam praesent iriure accumsan augue eum commodo facilisi lorem
Bug#337086: provide a link to the Debian Security Manual
It seems like the mentioned link[1] is not working anymore, and looking around a bit it seems to be at [2] now instead. I was thinking about the right place to add the link to. Even if there are some sections related to security, namely _Security uploads_ and _Handling security-related bugs_, they are only tangentially related to the contents for the linked resource. Hence, instead of adding it to an existing section, I have created a new one inside the _Best Packaging Practices_ section. This could also be useful if more information about security, or other links are wanted to be added in the future. The change is available at [3]. 1: http://www.debian.org/doc/manuals/securing-debian-howto/ch9.en.html 2: https://www.debian.org/doc/manuals/securing-debian-manual/ch09.en.html 3: https://salsa.debian.org/debian/developers-reference/-/merge_requests/30 -Marco
Bug#987037: ITP: vim-toml -- Vim support for TOML language
Package: wnpp Severity: wishlist Owner: Marco Villegas X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: vim-toml Version: 3c5face8e8944a217af45bc5bb708ff7dfcf1a54 Upstream Author: Caleb Spare * URL : https://github.com/cespare/vim-toml * License: Expat Programming Lang: Vim scripting Description: Vim support for TOML language Adds syntax support for Tom's Obvious Minimal Language, TOML, on Vim. Initial codebase available at https://salsa.debian.org/vim-team/vim-toml -Marco pgpZD3YlNN7k6.pgp Description: Firma digital OpenPGP
Bug#980389: Run phpunit test suite
Package: php-easyrdf Version: 0.9.1-5 Source: php-easyrdf Severity: normal Tags: upstream X-Debbugs-Cc: pkg-php-p...@lists.alioth.debian.org Originally, at the initially packaged 0.9.1 version, phpunit ~3.5 was required. That version was incompatible with the version at the unstable archive at the time of the initial packaging. From 1.0.0 up to current stable at 1.1.1, the phpunit requirement is ^7. Current phpunit at unstable has been four days ago[1], at version 9.5.0-5. As David pointed out at the mailing list, there is some upstream effort to make php8 compatibility. That is happening at the pr/test-php8-compatibility branch, with a related upstream pull request[2]. As njh points out there, those changes are mainly about compatibility with newer phpunit. Overall, it should be possible to run the test suite now. If not directly, maybe after adding some of the changes from that pull request commits set. Let us do that. Best, 1: https://tracker.debian.org/news/1219647/phpunit-950-5-migrated-to-testing/ 2: https://github.com/easyrdf/easyrdf/pull/373 - Marco
Bug#720456: [vim-scripts] Please include the solarized colorscheme
Nicholas, Thanks for the feedback, please see my replies below. BTW, James, copying you here to notify there is a new version of the package at the git repository, and that I am converting this bug into an ITP. On Sun, 20 Dec 2020 11:11:43 +0300 Nicholas wrote: > Hello! > > On Fri, 2020-12-11 at 16:09 -0500, Marco Villegas wrote: > > I have just added a new repository at > > https://salsa.debian.org/vim-team/vim-solarized which contains some > > extra changes to reflect the owner change. I also added a new signed > > tag with the first version. > > Thank you, Marco Villegas, for packaging original Solarized > color-scheme for Vim, my favorite color-scheme. > > Once you prepared a new package, I think it makes sense to convert > this bug to an ITP report[1] against the wnpp pseudo-package. Right, I will do that now. > And I noticed also your current variant of the package activates the > color-scheme instead of default one and so a description of the > package contradicts a little bit. A colorscheme in vim is used only when vimrc is configured to get it used. In dh-vim-addon, there is an way to define if an vim addon will be available by default or not, which is independent of the usage of it for the case of a colorscheme. I understand the confusion here, mainly on the description, which I have just changed. BTW I originally started it as an options addon, and changed it later, see description at the commit[1] for details > > > Description: Solarized Colorscheme for Vim > > Solarized is a sixteen color palette with eight monotones, and > > eight accent colors; designed for use with terminal and gui > > applications. . > > This plugin contains a vim colorscheme plugin using the Solarized > > palette. . > > It is installed as "optional" Vim package, which can be enabled by > > adding "packadd! solarized" to vimrc. > > You use the debian/*.vim-addon file, not debian/*.vim-opt-addon, and > so packadd! command is not needed. Is it intentional? > > [1]: https://wiki.debian.org/ITP Hence yes, it is intentional, and thanks for pointing it out. 1: https://salsa.debian.org/vim-team/vim-solarized/-/commit/36f394c7029ad3a1835aac27ffbf66e9226822e7 Best, -Marco pgpQEzd8GoTkJ.pgp Description: Firma digital OpenPGP
Bug#720456: [vim-scripts] Please include the solarized colorscheme
Thanks for granting me access to the vim team James! I have just added a new repository at https://salsa.debian.org/vim-team/vim-solarized which contains some extra changes to reflect the owner change. I also added a new signed tag with the first version. Let me know if the package looks good, and next steps. Best, -Marco
Bug#720456: [vim-scripts] Please include the solarized colorscheme
Hi James, As discussed on IRC, I have created a separate package for the solarized colorscheme, using dh-vim-addon as the base. The code can be found at https://salsa.debian.org/marvil07/vim-solarized BTW you probably have already received an invitation to the git repository. It would be great if it could be added under the salsa vim-team. I requested access there using gitlab UI, just in case. Do you think that would be a good idea? Let me know if the package looks good to you. Best, -Marco
Bug#720456: [vim-scripts] Please include the solarized colorscheme
James, thanks for making the changes for the conversion to dh-vim-addon on the package git repository! I see them in place now and even released as 20201113, which means I could re-try this with the new approach. While looking at the code changes, I noticed that color_sampler_pack was updated less than two weeks ago on the debian repository[1] to the version from 2012.10.28. It now includes a solarized color scheme, but sadly, it is including a old version; which based on the upstream repository, corresponds to upstream commit 646c69542e4759a7dd7e2b22b86287027614[2] from March 2011. It is also important to mention that color_sampler_pack is only adding the color scheme, without any documentation. Based on that, I think it is a good idea to add it independently. As stated at debian/vim-scripts.status, I am adding version from latest available commit on upstream, 528a59f26d12278698bb946f8fb82a63711eec21[3]. I have also updated html documentation on a separate commits, for easier review. The new code is now available at https://salsa.debian.org/vim-team/vim-scripts/-/merge_requests/2 1: https://salsa.debian.org/vim-team/vim-scripts/-/commit/2919ffd8093b8d30ba10629c9b63ea188cc2841a 2: https://github.com/altercation/vim-colors-solarized/blob/646c69542e4759a7dd7e2b22b86287027614/colors/solarized.vim 3: https://github.com/altercation/vim-colors-solarized/blob/528a59f26d12278698bb946f8fb82a63711eec21/colors/solarized.vim Best, -Marco
Bug#973462: ITP: podcasts -- Podcast application for GNOME written in Rust
Package: wnpp Severity: wishlist * Package name: podcasts Version : 0.4.8 Upstream Author : Jordan Petridis * URL : https://wiki.gnome.org/Apps/Podcasts * License : GPL-3.0-or-later Programming Lang: Rust Description : Podcast application for GNOME A podcatcher application for GNOME environment written on Rust and GTK. This is a nice podcatcher tightly integrated with GNOME. I think this is the first application trying to do this in the GNOME ecosystem specifically for podcasts. Alternatives I think liferea can also handle podcasts, but it is far from specialized on it. gpodder is another GTK application written on python. Even if both are available on debian, this would be a really nice addition for Debian, especially for GNOME users. podcasts application is listed under "Eventual goals" on rust team's debcargo-conf to-do file at https://salsa.debian.org/rust-team/debcargo-conf/-/blob/master/TODO.rst This application depends on many other rust crates, some of them already added to Debian by the rust team. An initial list of rust crates the application depends on that are not yet in Debian: - diesel-migrations - gstreamer-player - html2text - libhandy - mpris-player - podcasts-data To start, diesel migrations crate is now in the process of getting added, see https://salsa.debian.org/rust-team/debcargo-conf/-/merge_requests/125 Best, -Marco
Bug#934913: [pkg-php-pear] Bug#934913: php-easyrdf: should maybe link with librdf0 and suggest/recommend raptor2-utils
Hi Jonas, Thank you for reporting about this! On Fri, 16 Aug 2019 15:40:17 +0200 Jonas wrote: > Package: php-easyrdf > Version: 0.9.1-3 > Severity: normal > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Hi Marco, > > Thanks for packaging EasyRdf! It was definitely interesting! > > Upstream homepage http://www.easyrdf.org/ mentions optional support > for redland binding and rapper. Indeed, it seems to be supported, I tested it. > > Rapper is in binary package raptor2-utils. Thanks for pointing that out On rapper[1], I have added raptor2-utils as a suggested package. I also added a related smoke test. > > Changelog for release 0.7.2 seems to indicate that upstream may have > dropped support for Redland linkage (in which case it might make sense > to suggest to them to remove their then wrong statement). On redland[2], the php binding for the library, I see the binding is not yet packaged on Debian; but it is nice to see there is support for it on EasyRdf. I still see a related parser class for it, lib/EasyRdf/Parser/Redland.php, so it probably works, but again the dependency is not yet on Debian. If in the future it is packaged, a change similar to the one I made for rapper can be done. 1: http://librdf.org/raptor/ 2: http://librdf.org/docs/php.html > > Seems other tools are optionally used as well - including graphviz. > > Regards, > > - Jonas Best, -Marco pgpFCfuLmUE9D.pgp Description: Firma digital OpenPGP
Bug#932244: ITP: php-easyrdf -- PHP library for RDF
Hi, Some good news: * The package git repository has now been moved to the php team in salsa, see https://salsa.debian.org/php-team/pear/php-easyrdf * I managed to get gbp working correctly. In the process, while using pristine tar I noticed the release tarball is removing development related files, including tests, which is OK at this point, since they require an old version of phpunit, so the related debian package cannot run them, which is something that may be something to change upstream. * I have uploaded the new version of the package to mentors too, see https://mentors.debian.net/package/php-easyrdf Some context on why this package can be useful: * Resource Description Framework, RDF, is an official W3C Recommendation for Semantic Web data models. * There is no a RDF related php library in Debian. * This library is used by multiple upstream projects, see [1] for a list in packagist. So having it packaged will help to add any of those projects, e.g. drupal. On the packaged version: * The upstream project has a 0.9.x branch, which is used by many projects. * It also has a master branch, which contains on it a 0.10.0-alpha.1 tag, which I avoided since (i) it is not stable, and (ii) has several new dependencies. 1: https://packagist.org/packages/easyrdf/easyrdf/dependents Best, -Marco
Bug#930356: CVE-2019-12760
Just to mention that one of the authors of parso actually closed the related issue[1] pointing to the commit mentioned by Nicholas, 19de3eb. In the same comment, a new issue about replacing pickle[2] was created to avoid the problem altogether, and the author suggest it will not happen soon. This probably means that we want to go with the approach suggested by Piotr to disable cache if we want to avoid the removal. 1: https://github.com/davidhalter/parso/issues/75 2: https://github.com/davidhalter/parso/issues/79 Best, -Marco
Bug#932244: ITP: libphp-easyrdf -- A PHP library for RDF
I have created the initial version of the package. New resources: * salsa: https://salsa.debian.org/marvil07-guest/libphp-easyrdf * mentors page: https://mentors.debian.net/package/libphp-easyrdf Best, -Marco
Bug#932315: Extra links
A couple of related links: - salsa: https://salsa.debian.org/marvil07-guest/battery-plug-notifier - mentors: https://mentors.debian.net/package/battery-plug-notifier After some feedback from Eriberto, this package may be actually dropped because it seems to be too small. Best, -Marco
Bug#932315: ITP: battery-plug-notifier -- A simple notifier to hopefully extend battery life.
Package: wnpp Severity: wishlist Owner: Marco Villegas * Package name: battery-plug-notifier Version : 0.1.0 Upstream Author : Marco Villegas * URL : https://gitlab.com/marvil07/battery-plug-notifier * License : GPL Programming Lang: Shell Description : A simple notifier to hopefully extend battery life. A lot laptop batteries use [Lithium-ion batteries](https://en.wikipedia.org/wiki/Lithium-ion_battery). There is a simple technique to help extend battery life, by keeping the charge not so high, and not so low. Some laptops already include a feature to help with this, namely thinkpads with [tp_smapi](https://www.thinkwiki.org/wiki/Tp_smapi), but most do not have that feature. A work-around not having kernel level access to start/stop charging is to do it manually, but as humans it is hard to remember to monitor the percentage. This notifier helps with the task by sending notifications at those moments.
Bug#932244: ITP: libphp-easyrdf -- A PHP library for RDF
Package: wnpp Version: 0.9.0 Severity: wishlist * Package name: libphp-easyrdf Version: 0.9.0 Upstream Author: Nicholas J Humfrey * URL : http://www.easyrdf.org/ * License: BSD-3-Clause Description: EasyRdf is a PHP library designed to make it easy to consume and produce RDF. See https://github.com/njh/easyrdf -Marco
Bug#928893: Confirming gnome-disks problem
Starting from buster installer rc3, and installing minimal dependencies to run, I can confirm the problem exists. While trying to change the passphrase from gnome-disks, i.e. the old and new passphrases were entered, I see the following error message: "Error changing passphrase: Invalid argument (udisks-error-quark, 0)", screenshot attached. I have also tried to access again the disk from an external gparted after the attempt, and I could not unlock the partition with neither the old nor the new passphrase. Best,
Bug#720456: [vim-scripts] Please include the solarized colorscheme
Thanks for the feedback! I will be happy to re-attempt this after the restructuring. I will try to git fetch periodically, but an announce here would be great too. Best, -Marco On Sun, 3 Mar 2019 14:20:06 -0500 James wrote: > On Fri, Mar 01, 2019 at 10:26:45PM -0500, Marco Villegas wrote: > > I have used https://github.com/altercation/solarized repository as > > the base to add the solarized color scheme to the package. > > Thanks for working on this. > > > I am not entirely sure of the urls on metadata at > > debian/vim-scripts.status, but I guess that they are OK. It is > > important to notice that there is a vim.org page, i.e. > > https://www.vim.org/scripts/script.php?script_id=3520, for the color > > scheme, but sadly the code there contains an older version of what I > > find at the repository, and that is why I decided to use the version > > from the repository. > > > > I was a bit worried on how debian/vim-scripts.pl will handle the > > github url, but both doc and update actions seems to finish OK, > > naturally suggesting a false positive on the case of the new > > solarized addon. > > All of this is going to be reworked as I'm in the process of changing > this package from using vim-addon-manager to dh-vim-addon. > vim-addon-manager had various problems that were holding me back from > updating vim-scripts. I haven't been actively working on this since > it will have to wait until after Buster is released anyway. > > > Another detail I am not sure about is the value of disabledby at > > debian/vim-scripts.status for this new addon, so I have just > > skipped it. > > For a colorscheme, it's not needed. The user has to explicitly use > the colorscheme anyway. > > > Also, I have started by updating the html documentation for all > > addons, since I could not figure out a way to only do it for the > > new addon. It is in a separate commit, just in case that change is > > not a good idea. > > Agreed, that's not necessary right now. > > I would suggest holding off until the package gets restructured. I'll > try to make some time for that again so at the very least there's an > experimental branch this could be merged into. > > Cheers,
Bug#720456: [vim-scripts] Please include the solarized colorscheme
Dear maintainer, Thanks for providing the package, I find it really useful. I have used https://github.com/altercation/solarized repository as the base to add the solarized color scheme to the package. Based on the note at the README file, I concluded the license of the provided code is https://opensource.org/licenses/MIT. I am not entirely sure of the urls on metadata at debian/vim-scripts.status, but I guess that they are OK. It is important to notice that there is a vim.org page, i.e. https://www.vim.org/scripts/script.php?script_id=3520, for the color scheme, but sadly the code there contains an older version of what I find at the repository, and that is why I decided to use the version from the repository. I was a bit worried on how debian/vim-scripts.pl will handle the github url, but both doc and update actions seems to finish OK, naturally suggesting a false positive on the case of the new solarized addon. Another detail I am not sure about is the value of disabledby at debian/vim-scripts.status for this new addon, so I have just skipped it. Also, I have started by updating the html documentation for all addons, since I could not figure out a way to only do it for the new addon. It is in a separate commit, just in case that change is not a good idea. The code can be found at https://salsa.debian.org/vim-team/vim-scripts/merge_requests/1 Let me know if I can do something else to help this change get into the package. Best, -Marco
Bug#883036: disable-while-typing not working?
Package: libinput10
Version: 1.6.3-1
Severity: normal
Dear Mantainer,
It seems like disable-while-typing[1] feature is not working correctly,
even if it is enabled, it does not honor the timeouts in the code.
This feature has been in there for a while, but I guess I notice it in
Debian because libinput driver superseded synaptic Xorg driver in
stretch. disable-while-typing was possible with synaptic with
syndaemon/synclient, but libinput method seems to be more efficient[2].
At first, I thought the feature was simply not enabled.
GNOME seems to not have an UI for it until 3.24[3][4], but after
installing xinput I see it is enabled.
$ xinput | grep Touchpad
⎜ ↳ 1A586753:00 06CB:8323 Touchpadid=15 [slave
pointer (2)]
$ xinput list-props 15| grep Typing
libinput Disable While Typing Enabled (309):1
libinput Disable While Typing Enabled Default (310):1
To test this:
a. I start typing some sentence in a text editor,
b. then use the touchpad,
c. and the original application where I was typing is not in focus
anymore.
What I expected would be to the text editor to keep focus even if the
touchpad is pressed when the time between the last key pressed and the
touchpad is less than the established timeout, which in current
packaged version 1.6.3 is 500ms[5].
This setting sounds like a good candidate for a configuration option,
e.g. then it can be set with xinput; but I see in upstream similar
requests closed during issue triagging[6], but that is probably a new
upstream request altogether.
I may be not understanding the feature or stack correctly, so I would
really appreciate if you can point me in the right direction.
1:
https://wayland.freedesktop.org/libinput/doc/latest/palm_detection.html#disable-while-typing
2:
https://who-t.blogspot.pe/2016/08/libinput-and-disable-while-typing.html
3: https://bugzilla.gnome.org/show_bug.cgi?id=764852 4:
https://git.gnome.org/browse/gsettings-desktop-schemas/commit/?id=4c5b1c1df399d6afaaccb237e299ccd1d5d29ddd
5:
https://anonscm.debian.org/cgit/pkg-xorg/lib/libinput.git/tree/src/evdev-mt-touchpad.c?h=libinput-1.6.3-1#n35
6: https://bugs.freedesktop.org/show_bug.cgi?id=88353
-- System Information:
Debian Release: 9.1
Architecture: amd64 (x86_64)
Kernel: Linux 4.9.0-4-amd64 (SMP w/4 CPU cores)
$ dpkg-query --show -f='${binary:Package}\t${Version}\n' libinput*
libc6 libudev1 libwacom2 libevdev2 libmtdev1 libc6:amd64
2.24-11+deb9u1 libevdev2:amd64 1.5.6+dfsg-1
libinput-bin1.6.3-1
libinput10:amd641.6.3-1
libmtdev1:amd64 1.1.5-1+b1
libudev1:amd64 232-25+deb9u1
libwacom2:amd64 0.22-1+b1
-- no debconf information
Best,
-Marco
Bug#766144: nautilus: Please apply interactive_search.patch
+1 This seems to be explained in a detailed manner in the past[1] and also started a relevant discussion[2] on the upstream bug tracker. Hannes, thanks for adding the patch here, hopefully the maintainers would like to include it on jessie. IMHO it is important to add it to let the end user decide if searching is the right action to do, especially on machines with slow disks, when the former method is easier for navigation. Also, this seems to be a duplicate of another bug[3]. 1: https://mail.gnome.org/archives/nautilus-list/2012-August/msg6.html 2: https://bugzilla.gnome.org/show_bug.cgi?id=680118 3: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766144 Best, -- Marco Villegas -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#765473: dovecot-common: Dovecot (previous to V2.1) doesn't allow to disable SSLv3 which is bad: CVE-2014-3566
It seems like the patch mentioned before does not directly apply in
the code at squeeze-update branch on git repository, so I modified it a
little.
Sadly, I cannot really make it work, it seems to be doing what is
needed, but if I try a:
openssl s_client -connect example.com:1234 -ssl3
It still connects correctly, so I guess something else is missing.
Best,
--
Marco Villegas
From a415edd1a1e02ee991532e9a02a229da65ae83fc Mon Sep 17 00:00:00 2001
From: Marco Villegas g...@marvil07.net
Date: Thu, 16 Oct 2014 23:54:39 -0500
Subject: [PATCH] Disable SSLv3
A modified version of Timo Sirainen patch from
http://dovecot.org/list/dovecot/2014-October/098244.html
to let it apply.
---
debian/patches/0012-sslv3-disable.patch | 13 +
debian/patches/series |1 +
2 files changed, 14 insertions(+), 0 deletions(-)
create mode 100644 debian/patches/0012-sslv3-disable.patch
diff --git a/debian/patches/0012-sslv3-disable.patch b/debian/patches/0012-sslv3-disable.patch
new file mode 100644
index 000..bd926c1
--- /dev/null
+++ b/debian/patches/0012-sslv3-disable.patch
@@ -0,0 +1,13 @@
+diff --git src/login-common/ssl-proxy-openssl.c src/login-common/ssl-proxy-openssl.c
+index 72fa0fa..9efe3b9 100644
+--- src/login-common/ssl-proxy-openssl.c
src/login-common/ssl-proxy-openssl.c
+@@ -817,7 +817,7 @@ static void ssl_proxy_ctx_init(SSL_CTX *ssl_ctx)
+ {
+ const char *cafile;
+
+- SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL);
++ SSL_CTX_set_options(ssl_ctx, SSL_OP_ALL | SSL_OP_NO_SSLv3);
+
+ cafile = getenv(SSL_CA_FILE);
+ if (cafile != NULL) {
diff --git a/debian/patches/series b/debian/patches/series
index 29319ed..28f3703 100644
--- a/debian/patches/series
+++ b/debian/patches/series
@@ -9,3 +9,4 @@
0009-dovecot-mboxlocking.patch
0010-sendmail-path.patch
0011-CVE-2011-1929.patch
+0012-sslv3-disable.patch
--
1.7.2.5
Bug#687657: vlc: copyright file missing after squeeze-wheezy upgrade
It seems like the file is now on vlc-data package instead. I can see it there: dpkg -L vlc-data|grep copyright -- Marco Villegas signature.asc Description: PGP signature
Bug#681415: Add new changes from upstream
Package: mobile-broadband-provider-info Version: 20120402-1 There are several new commits on the upstream git repository, including also a new tag 20120614. The information in this package is really important for new users, so it would be great to have the updated data on the package. For example, the upstream version solves https://bugzilla.gnome.org/show_bug.cgi?id=675418 -- Marco Villegas http://marvil07.net signature.asc Description: PGP signature
Bug#648840: gnome-shell: Execution of main.js threw exception: Type Error: imports is undefined
Hi, I do not really know how to do the mentioned fix. I guess this involve: - Getting the gjs source(apt-get source gjs) - Change some configuration to use libmozjs8d (No idea on how to do it) - Build gjs(dpkg-buildpackage -us -uc) The fix also mentions that a gnome-shell rebuild is needed(same steps with no configuration change?). It would be great if someone can point me in the right direction. Thanks in advance, -- Marco signature.asc Description: PGP signature
Bug#616341: No more need to patch for gcc version
Package: speech-tools Version: 1:2.0.95~beta-2 Severity: important Since 2.0.95[1] festival and speech tools support newer GNU compilers, quoting the relevant part of the announce: New in 2.0.95 * Support for the new versions of C++ that have been released So, as mentioned in the bug #592052 opened[2] in debian festival package, there is no more need to patch for GNU compiler compatibility. 1: http://www.cstr.ed.ac.uk/downloads/festival/2.0.95/ANNOUCE-2.0.95 2: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=592052 -- Marco Villegas http://marvil07.net signature.asc Description: PGP signature
Bug#572650: libdevkit-power-gobject1: Suspend, Hibernate, battery applet, power management options broken
Installing upower, like Michel mention, solves the problem for me. Thanks! ___ Marco Villegas http://marvil07.net signature.asc Description: PGP signature
