Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: closed by Sylvestre Ledru (Re: Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

ah! some fascinating news (from another discussion) pulled up the fact that ADA converted to a Certification Mark, back in 1987 http://archive.adaic.com/pol-hist/policy/trademrk.txt In order to be a validated Ada compiler, a compiler must pass an extensive suite of programs called the Ada

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: closed by Sylvestre Ledru (Re: Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

On Mon, Jul 18, 2022 at 11:06 AM Sylvestre Ledru wrote: > > This bug is fixed. i can see that you believe that to be true, otherwise you would not have closed it. what i am upset by is that you did not consider my opinion or insight to be worth consulting. i am deeply offended by that. l.

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Mon, Jul 18, 2022 at 10:16 AM Sylvestre Ledru wrote: > > Thanks for bringing it to our attention, I have consulted with the Rust > foundation, we have agreed a change, we think this change solves it. ah! we may have

Bug#1013920: closed by Sylvestre Ledru (Re: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel"))

reopen 1013920 sorry, Sylvestre, if you could possibly wait, on something this serious, for a response as to whether the fix is valid, that will avoid me having to spend my time reopening the issue or creating a second bugreport. On Mon, Jul 18, 2022 at 10:21 AM Debian Bug Tracking System

Bug#1013920: [Pkg-rust-maintainers] Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

i've opened up a second bug for gcc because it is also about to become affected, not in the same way, but in a worse way. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1015242 whilst 50% of DFSG 2 is violated by the Rust Trademark (as it stands, with the new clauses), gcc is in an even worse

Bug#1013920: rust-all: Debian violating Rust Trademark (as serious a situation as "iceweasel")

https://developers.slashdot.org/story/22/07/17/0110250/gcc-rust-approved-by-steering-committee-beta-likely-next-april and now it becomes Unlawful for Debian to distribute gcc with patches, as well [without the explicit consent of the Mozilla Foundation, an action which is in direct violation of

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > #958166: python3-all: python3 can't import gmpy2 > Python3.7 is no longer supported in Debian Unstable and Testing and will be > removed shortly. if you were talking about python 3.6, there would be absolutely no problem,

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

here is a package that contains a build system that, unlike the python3-numpy team, relies exclusively on python3-all. like python3-gmpy2, note that it does not contain enumeration of the minor versions of python. its control file does not list multiple versions of python3, either, choosing

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

you do realise, scott, that python3-numpy has been forced into a position of bypassing the careless unthinking decision that you've made, by including the capability to manually enumerate and compile up multiple versions for different versions of python3? instead of closing the bugreport and

Bug#958166: closed by Scott Kitterman (Re: [Python-modules-team] [critical] #958166 - python3-all has had python3.7 removed)

On Sun, Apr 19, 2020 at 1:36 PM Debian Bug Tracking System wrote: > > This is an automatic notification regarding your Bug report > which was filed against the python3-all package: > > #958166: python3-all: python3 can't import gmpy2 > > It has been closed by Scott Kitterman . > > Their

Bug#958166: severity 958166 critical

after some consideration, i realised that the removal of python3.7 as a dependency from python3-all results in "unrelated software on the whole system break", and that this is reminiscent of the critical error made by ubuntu, over 10 years ago. 1 criticalmakes unrelated software on the

Bug#958166: [critical] #958166 - python3-all has had python3.7 removed

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958166 this is serious enough to bring to a wider audience's attention, immediately. just as happened over 10 years ago, a mistake made by the ubuntu team making python-all depend on only a single version of python has just been repeated, in

Bug#958166: Processed: severity 958166 critical

https://alioth-lists.debian.net/pipermail/python-modules-team/2020-April/066373.html we're starting to see additional evidence of the seriousness of this one. an attempt to (auto-) build python3-pythonmagick failed due to libboost-python however i just attempted it myself, and: * apt-get

Bug#824848: xchat current debian/testing is out-of-date and specifically depends on libperl5.20

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, May 25, 2016 at 1:14 PM, Andreas Beckmann wrote: > Hi, > > On Fri, 20 May 2016 12:48:28 +0100 lkcl wrote: >> currently having to manually rebuild xchat (which is possible thanks

Bug#814331: repsnapper: nothing displayed in 3d window

ackage file says "anything >= x.x.x is ok" but actually it's not ok at all. does that ring true at all as a plausible hypothesis? l. --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Feb 24, 2016 at 9:51 PM, Luke Kenneth Casson Leighton <l...@lkcl.net&g

Bug#814331: repsnapper: nothing displayed in 3d window

> Hi Luke, > > Can you try "env LIBGL_ALWAYS_SOFTWARE=1 repsnapper" to see if it fixes? ok i can confirm that the latest version is working. also the (just-reported) bug with glib also goes away. so that one can be closed. l.

Bug#814331: repsnapper: nothing displayed in 3d window

On Mon, Feb 15, 2016 at 1:25 PM, Ying-Chun Liu (PaulLiu) wrote: >> any suggestions on things to try? >> >> l. >> > > Hi Luke, > > Can you try "env LIBGL_ALWAYS_SOFTWARE=1 repsnapper" to see if it fixes? sure... give me a clear few hours over the next day or so, as i am in

Bug#814331: repsnapper: nothing displayed in 3d window

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Feb 10, 2016 at 3:15 PM, Ying-Chun Liu (PaulLiu) wrote: > lkcl 於 2016年02月10日 21:08 寫道: >> Package: repsnapper >> Version: 2.4a0-1 >> Severity: grave >> Justification: renders package unusable

Bug#745038: sgml-base: dependency xml-core missing (missing update-xmlcatalog)

it's ok adam, i was reporting from a different machine, and somehow /usr/sbin was not in $PATH. bug's been closed. On Thu, Apr 17, 2014 at 2:39 PM, Adam D. Barratt a...@adam-barratt.org.uk wrote: Control: tags -1 + moreinfo unreproducible On 2014-04-17 14:24, lkcl wrote: Package: sgml-base

Bug#745038: Acknowledgement (sgml-base: dependency xml-core missing (missing update-xmlcatalog))

apologies please disregard this bugreport, /usr/sbin was somehow missing from $PATH. l. On Thu, Apr 17, 2014 at 2:27 PM, Debian Bug Tracking System ow...@bugs.debian.org wrote: Thank you for filing a new Bug report with Debian. This is an automatically generated reply to let you know your

Bug#726530: fvwm: random segfault

On Thu, Oct 17, 2013 at 2:26 AM, Vincent W. Chen vin...@gmail.com wrote: On Wed, Oct 16, 2013 at 6:57 AM, lkcl l...@lkcl.net wrote: Package: fvwm Version: 1:2.6.5.ds-2 Severity: grave Justification: causes non-serious data loss listed this as grave as it's the closest option available:

Bug#638896: Bug#636123: Info received (Bug#636123: linux-image-2.6.39-2-amd64: root filesystem not recognised - new bug report)

right - _finally_ i've encountered a requirement to upgrade a 2nd system that has lvm2 and (in this 2nd case 2.6.18-486) a linux kernel image, and have encountered the *exact* same problem as is in bugs 636123 and 638896. this time, however, i was anticipating that something might go wrong, so

Bug#528359: [Python-modules-team] Bug#528359: python-pycurl: dependencies incorrect

Thanks; we know and we are working on to fix it. yaay, cool. Next time, please check if other reports for the same problem exist, like in this case [1] whoops, sorry! [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=527546 -- To UNSUBSCRIBE, email to

Bug#509883: bzflag-client: libcares.so.2 nonexistent dependency

Package: bzflag-client Version: 2.0.13.20080902-1 Severity: serious Justification: Policy 3.5 bzflag [2] 20131 l...@gonzalez:~/src/shrdlu/winograd/code$ bzflag: error while loading shared libraries: libcares.so.2: cannot open shared object file: No such file or directory

Bug#451458: patch for mingw32 to enable building of libgcc_s

This patch enables building libgcc_s as a DLL on MinGW and Cygwin. This allows throwing exceptions across DLL boundaries when using a shared libgcc_s. http://archives.free.net.ph/message/20080818.185009.87903ba6.en.html pleaase dooo iincluuude it :) 24 hours of building webkit cross-compiled

Bug#412659: cupsys: number one useability complaint: my printer has stopped working

Package: cupsys Version: 1.1.23-10 Severity: grave this is an issue that has affected ordinary users constantly, and finally, the last straw: after having to tell THE SAME USER the SAME THING because they are too stressed to remember i FINALLY have to report this as a grave useability bug. the