Bug#1033605: ITP: sphinxcontrib-jquery -- extension to include jQuery on newer Sphinx releases
Package: wnpp Severity: wishlist Owner: Dmitry Shachnev * Package name: sphinxcontrib-jquery Version : 4.1 Upstream Contact: Adam Turner * URL : https://github.com/sphinx-contrib/jquery * License : 0BSD Programming Lang: Python Description : extension to include jQuery on newer Sphinx releases sphinxcontrib-jquery ensures that jQuery is always installed for use in Sphinx themes or extensions. To use it, add sphinxcontrib.jquery as a Sphinx extension. I am going to maintain this package under the Debian Python Team umbrella. -- Dmitry Shachnev signature.asc Description: PGP signature
Re: dh_auto_test: use check target instead of the test target
On Mon, Mar 27, 2023 at 09:55:25PM +0200, Jerome BENOIT wrote: > Hi ! > Is there a simple way to force dh_auto_test(1) to use the `check` target but > not the `test` target ? > Thanks in advance, If I understand you correctly, something like the following might work: override_dh_auto_test: dh_auto_test -- check (any arguments after the ones that the debhelper tools understand will be passed right on through to the build tools that they execute) G'luck, Peter -- Peter Pentchev r...@ringlet.net r...@debian.org p...@storpool.com PGP key:http://people.FreeBSD.org/~roam/roam.key.asc Key fingerprint 2EE7 A7A5 17FC 124C F115 C354 651E EFB0 2527 DF13 signature.asc Description: PGP signature
Re: dh_auto_test: use check target instead of the test target
Hi Peter, thanks for your reply. On 28/03/2023 14:06, Peter Pentchev wrote: On Mon, Mar 27, 2023 at 09:55:25PM +0200, Jerome BENOIT wrote: Hi ! Is there a simple way to force dh_auto_test(1) to use the `check` target but not the `test` target ? Thanks in advance, If I understand you correctly, something like the following might work: override_dh_auto_test: dh_auto_test -- check (any arguments after the ones that the debhelper tools understand will be passed right on through to the build tools that they execute) I just tried this solution, but it does not work. I set up an workaround and I have just updated a bugreport related to this issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=924052 [and I increase its severity from whishlist to important]. Best wishes, Jerome G'luck, Peter -- Jerome BENOIT | calculus+at-rezozer^dot*net https://qa.debian.org/developer.php?login=calcu...@rezozer.net AE28 AE15 710D FF1D 87E5 A762 3F92 19A6 7F36 C68B OpenPGP_signature Description: OpenPGP digital signature
Re: Re-enabling os-prober for live images?
kilobyte wrote: >At this point, I'd just enable os-prober unconditionally, and think of a Erm, *no*?! os-prober corrupts data when called (in virtualisation/emulation guests, at the very least). Steve wrote: >I'm also pondering tweaking things in d-i to re-enable os-prober if >the system looks like it might have some other OS installed. Yes, I But what if the system has *both* other OSes installed *and* is used as virtualisation host (when booting Debian) at the same time? You’ll still get data corruption of unrelated data (VM guests). I consider that inacceptable, but apparently YMMV… bye, //mirabilos -- [...] if maybe ext3fs wasn't a better pick, or jfs, or maybe reiserfs, oh but what about xfs, and if only i had waited until reiser4 was ready... in the be- ginning, there was ffs, and in the middle, there was ffs, and at the end, there was still ffs, and the sys admins knew it was good. :) -- Ted Unangst über *fs
Re: Debian 9/stretch moved to archive.debian.org
Ansgar dixit: >the stretch, stretch-debug and stretch-proposed-updates suites have now >also been imported on archive.debian.org. People still interested in >these should update their sources.list. Might be useful to note that stretch-updates should be dropped from sources.list but has been empty on deb.d.o before anyway so that’s a nop. >I plan to remove the suites from the main archive in about a month >(2023-04-23 or later). > >The stretch-backports, stretch-backports-sloppy and related debug suites >will likely move soon as well and might be removed from the main archive >around the same time. Is there a rough idea about this “soon”, will it be in time before the removal, and will there be a notification as well? I’d rather go through changing the sources.list templates only once if possible. Thanks, //mirabilos -- /⁀\ The UTF-8 Ribbon ╲ ╱ Campaign against ╳ HTML eMail! Also, ╱ ╲ header encryption!
