Bug#1051833: python3-poetry-core: does not work, i.e. "import poetry" fails at Python prompt, without python3-pep517
I cannot reproduce this on bookworm, with python3 3.11.2, and python3-poetry-core 1.4.0-4. So it seems to be obsolete by now. Best, Dima
Bug#1051833: python3-poetry-core: does not work, i.e. "import poetry" fails at Python prompt, without python3-pep517
Package: python3-poetry-core Version: 1.0.7-2~bpo11+1 Severity: important Dear Maintainer, Installed python3-poetry-core, tried running "import poetry" at the Python3 prompt, got an import error. Realised that I didn't have python3-pep517 package installed, installed it too, then the import error did not occur any more. python3-pep517 package should be a dependency of python3-poetry-core (and this applies to all the Debian versions) -- System Information: Debian Release: 11.7 APT prefers oldstable-updates APT policy: (500, 'oldstable-updates'), (500, 'oldstable-security'), (500, 'oldstable') Architecture: amd64 (x86_64) Kernel: Linux 5.15.117-19680-g54e910f94133 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) Versions of packages python3-poetry-core depends on: ii python3 3.9.2-3 python3-poetry-core recommends no packages. python3-poetry-core suggests no packages. -- no debconf information
Bug#994953: backport this fix to bullseye (stable)?
I see the same error on bullseye - the patch should be a bit
different, as the source
evolved.
The line to be replaced in
/usr/lib/python3/dist-packages/virtualenv/seed/embed/via_app_data/via_app_data.py
with the same as in the patch here fix
is
if name_to_whl['setuptools'].path.is_relative_to(BUNDLE_FOLDER):
_get('pkg_resources', Version.bundle)
(somewhere close to lines 120-126 - if you like I can produce a correct diff)
Best,
Dima Pasechnik
Bug#992003: [Debian-science-sagemath] Singular update
4.2.1.p2 appears to include an essential compatibility fix for Flint 2.8.4 On Sat, 20 Nov 2021, 17:48 Torrance, Douglas, wrote: > On Sat 20 Nov 2021 02:50:55 AM EST, Tobias Hansen > wrote: > > any chance we could get an update of singular to 4.2.1.p0 in > experimental? I tried to do it myself once but the package has many patches > and it was difficult to get everything right. > > I'm also interested in getting singular 4.2.x in Debian, as Macaulay2 > requires > it as well. (Fortunately, it still works with 4.1.x with a patch, but > upstream > claims it's buggy.) > > Doug > ___ > Debian-science-sagemath mailing list > debian-science-sagem...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-sagemath >
Bug#992003: [Debian-science-sagemath] Singular update
On Sat, 20 Nov 2021, 08:08 Tobias Hansen, wrote: > Hi Jerome, > > any chance we could get an update of singular to 4.2.1.p0 in experimental? > I tried to do it myself once but the package has many patches and it was > difficult to get everything right. > 4.2.1.p2 is already there: https://trac.sagemath.org/ticket/32907 > Best, > > Tobias > > > ___ > Debian-science-sagemath mailing list > debian-science-sagem...@alioth-lists.debian.net > > https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/debian-science-sagemath >
Bug#964848: mpir deprecated in favour of gmp in sagemath
Since at least SageMath 9.1, a default source installation will first look for GMP available on the system, and use it if it was found. Or, in fact, any GMP-compatible package available on the system, such as MPIR - but the latter is rather unusual; compatibility is only lightly tested, in the usual autoconf way (i.e. for presense of headers and library, and the version of GMP to be at least 6.1.0, by testing presense of certain GMP function)) If none of these was found, MPIR would be built and used, but this will change in SageMath 9.3, so that GMP would be built,not MPIR, cf https://trac.sagemath.org/ticket/30752
Bug#964848: Upstream reference
On Fri, 19 Mar 2021 22:48:11 +0100 Maarten Derickx wrote: > This is the location of the corresponding upstream bugreport: > https://trac.sagemath.org/ticket/31340 The fix offered there is a bit different from what's suggested on the bug report (and apparently passes all the Sage's tests, while the original fix wasn't quite up to the job). Note that this was discovered independently of the Debian bug report. It's unfortunate that it went unreported on any list monitored by the upstream developers, e.g. us, as this memory leak has caused quite a bit of trouble and a lot of time wasted. A report on debian-science-sagem...@alioth-lists.debian.net would be sufficient. Cheers Dima
Bug#600490: Russian phonetic layout on a jp keyboard?
On 8 December 2010 14:18, Samuel Thibault sthiba...@debian.org wrote: Dima Pasechnik, le Thu 02 Dec 2010 12:26:11 +0800, a écrit : $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [jp jp106] options = [terminate terminate:ctrl_alt_bksp,grp grp:ctrl_shift_toggle,grp grp:alt_space_toggle,grp grp:menu_toggle,grp grp:sclk_toggle] model = toshiba_s3000 Note jp106 string in gconftool-2. Indeed it looks suspicious. I do not know where it comes from (do I still have an old config file lying around?) and whether it is harmless. Well, in the gconf case, the config file is the gconf database, more precisely ~/.gconf/desktop/gnome/peripherals/keyboard. You can use the gconftool-2 command to change it. I used the gconf-editor to erase jp106 substring from layouts, and this has cured the popup error messages. This also disabled Russian keyboard, though. gconftool-2 showed layouts = [jp], as expected. Then I added the keyboard I need via Gnome interface, and got it working. gconftool-2 shows layouts = [jp, ru phonetic] as it was needed. I suppose this is resolved is some way, at least for me. (probably the squeeze installer/updater needs to be more aggressive in cleaning up unknown options...) Thank you all for your time, Dmitrii. PS. I wish the experience of fixing this did not resemble editing Windows registry that much :-) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600490: Russian phonetic layout on a jp keyboard?
On 3 December 2010 05:50, Samuel Thibault sthiba...@debian.org wrote: Dima Pasechnik, le Thu 02 Dec 2010 12:26:11 +0800, a écrit : I still get an occasional gnome popup indicating an xkb error. What is the error? Error activating XKB configuration. It can happen under various circumstances. [...] Xserver version data The X.Org Foundation Version 10707000 If you report this as a bug, please include: - The result of ... [...] I already followed the latter part of the popup message in my previous email. I certainly get this popup on startup, in the centre of the otherwise empty screen, and then after each resume (from RAM) from sleep. (Perhaps in other cases too, but I am not sure). The popup after resume is persistent, i.e. clicking OK in the popup immediately pops up the same window at the same place. There seems to be nothing of it reflected in /var/log/Xorg.0.log, dmesg, console terminal from which X was started, or anywhere esle I can think of... It does not affect the actual keyboard functioning. Dmitrii -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600490: Russian phonetic layout on a jp keyboard?
On 29 November 2010 07:36, Samuel Thibault sthiba...@debian.org wrote: [...] yes. In my /etc/X11/xorg.conf I used to have, in the keyboard section, Option XkbLayout jp,ru(phonetic) Option XkbVariant jp106 and it worked. Now I can select Russia Phonetic keyboard in Gnome Keyboard Preferences, but then I am stuck with Cyrillic characters only - the switching does not work. The only way out is to remove this keyboard choice and restart X. Did you try to put the same kind of parameter as xorg.conf into /etc/default/keyboard? It should be working exactly the same as xorg.conf (except that it'll additionally work on the linux console too!) Just tried it, and yes, it does fix the problem! Thank you for your time. I still get an occasional gnome popup indicating an xkb error. It asks to provide the following outputs: $ xprop -root | grep XKB _XKB_RULES_NAMES_BACKUP(STRING) = evdev, acpi, jp,ru, , grp:alt_shift_toggle _XKB_RULES_NAMES(STRING) = evdev, acpi, jp,ru(phonetic), , grp:alt_shift_toggle $ gconftool-2 -R /desktop/gnome/peripherals/keyboard/kbd layouts = [jp jp106] options = [terminate terminate:ctrl_alt_bksp,grp grp:ctrl_shift_toggle,grp grp:alt_space_toggle,grp grp:menu_toggle,grp grp:sclk_toggle] model = toshiba_s3000 Note jp106 string in gconftool-2. I do not know where it comes from (do I still have an old config file lying around?) and whether it is harmless. The model string content there is totally random, of course, and has nothing to do with the real keyboard. [...] Best, Dmitrii -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600490: Russian phonetic layout on a jp keyboard?
On 25 November 2010 18:00, Samuel Thibault sthiba...@debian.org wrote: Dima Pasechnik, le Thu 25 Nov 2010 12:35:45 +0800, a écrit : Installing the upgrades mentioned here did not enable any options for choosing the phonetic layout for Russian on the Japanese keyboard. You mean typing Russian on a Japanese keyboard? I didn't know about such thing. Why option were you using to achieve that? I guess you are talking about X keyboard layout, right? yes. In my /etc/X11/xorg.conf I used to have, in the keyboard section, Option XkbLayout jp,ru(phonetic) Option XkbVariant jp106 and it worked. Now I can select Russia Phonetic keyboard in Gnome Keyboard Preferences, but then I am stuck with Cyrillic characters only - the switching does not work. The only way out is to remove this keyboard choice and restart X. And it looks like a specific Japanese keyboard problem. On a machine with a standard US keyboard I run the same Debian version, and am able to select and use Russia Phonetic layout. For the record, it's a Panasonic CF-R5 laptop. (you probably also know that there seems to be no way to *select* an appropriate keyboard) An appropriate keyboard for what? The particular keyboard of that laptop or typing russian on a japanese keyboard? (The latter would just be a consequence of the above). In general, never assume we know anything about localization cases, as most of us don't are not from that localization, so although we usually have an idea, we usually don't know all the details. I meant an appropriate keyboard model for the laptop I am using. (in fact, there seem to be no jp106 keyboard layouts available in Gnome Keyboard Preferences.) When I try printing the keyboard, from Gnome Keyboard Preferences, the output does not show it right (many extra keys are not shown). It could be due to non-availability of an appropriate keyboard model. No wonder it does not really work right.. Samuel -- To unsubscribe, send mail to 600490-unsubscr...@bugs.debian.org. -- Dmitrii Pasechnik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600490: Russian phonetic layout on a jp keyboard?
Installing the upgrades mentioned here did not enable any options for choosing the phonetic layout for Russian on the Japanese keyboard. They were gone since I did an upgrade to squeeze. For the record, it's a Panasonic CF-R5 laptop. (you probably also know that there seems to be no way to *select* an appropriate keyboard) Thanks, Dmitrii http://www.ntu.edu.sg/home/dima/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#600490: is there any chance this is backported to squeeze?
I have a laptop with 106-key japanse keyboard, and since an upgrade to squeeze from lenny I cannot get normal functioning of it any more (forget about using a russian phonetic layout, for instance) Symptoms are similar to descibed here... Thanks, and sorry if this is totally ignorant of me... -- Dmitrii Pasechnik http://www.ntu.edu.sg/home/dima/ -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
