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: 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")

--- 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: [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#993957: closed by Christoph Biedl (Re: Bug#993957: (no subject))

On Sun, May 29, 2022 at 12:16 PM Debian Bug Tracking System wrote: > #993957: schroot: fails with non-existent subdirectory > > Their explanation is attached below along with your original report. > If this explanation is unsatisfactory and you have not received a > better one in a separate

Bug#991455: gitolite3: underscore in username causes corruption and incorrect behaviour

well, i just checked after upgrading to 3.6.11-2 and the repository in question has now *entirely disappeared* from the config! i've had to downgrade to 3.6.6-1 to get things functional (it's a live-running server) this does actually work, so during scheduled downtime moments i can switch to the

Bug#991455: gitolite3: underscore in username causes corruption and incorrect behaviour

i've created a test account, stupidly upgraded first so i cannot check the "broken" case. i will therefore use the original account with the underscore, however i need to ask a 3rd party to run the ssh command. the setup i have is quite comprehensive, 30 ssh keys 25 projects, it may be an

Bug#991455: gitolite3: underscore in username causes corruption and incorrect behaviour

Package: gitolite3 Version: 3.6.6-1 Severity: important Tags: upstream Dear Maintainer, i have used gitolite3 for many years, this is the first time i have ever had a major bug, and it involved a username with an underscore in it. ssh to the server reported "hello user" not "hello user_",

Bug#968666: electrum: exception which prevents startup "Non keyword-only attributes not allowed after..."

On Wed, Aug 19, 2020 at 3:29 PM Tristan Seligmann wrote: > > Control: tags -1 - upstream > Control: forcemerge 968563 -1 > > On Wed, 19 Aug 2020 at 14:48, lkcl wrote: > > > > ValueError: Non keyword-only attributes are not allowed after a > > keyword-only attribute. Attribute in question:

Bug#968666: electrum: exception which prevents startup "Non keyword-only attributes not allowed after..."

On Wed, Aug 19, 2020 at 6:34 PM Tristan Seligmann wrote: > > the normal approach to this would be to release a version of the > > electrum packaging that specifically depends on that specific version > > of python3-attr or above. the following to go into debian/control: > > Yes, the next upload

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: 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#958043: [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#958043: Acknowledgement (python3-gmpy2: import gmpy2 fails)

unfortunately, because of the way that python3-gmpy2 has been compiled, attempting to install an older version FORCE removes (or conflicts with) an existing installation of python 3.8. therefore if, as many people will have, they are transitioning from python 3.5 to 3.6, 3.6 to 3.7, 3.7 to 3.8,

Bug#949747: closed by Simon McVittie (Re: Bug#949747: gimp: dependency versions missing)

thank you simon, i've passed that on to christian. l.

Bug#864997: DEP-5 copyright checker

[apologies i can't reply inline, very limited HTML mailer due to seriously bandwidth/reliability-compromised internet connection] hi felix, violates my copyright by not containing my authorship assertion. in combination with no license file they should have contacted me for permission to

Bug#929709: libgdbm6: file exists in libgdbm-dev as well as gdbm

On Fri, May 31, 2019 at 5:09 AM Dmitry Bogatov wrote: > > Unpacking libgdbm-dev:amd64 (1.18.1-4) ... > > dpkg: error processing archive > > /var/cache/apt/archives/libgdbm-dev_1.18.1-4_amd64.deb (--unpack): > > trying to overwrite '/usr/share/info/gdbm.info.gz', which is also in > > package

Bug#909630: gitlab: no sysvinit scripts installed or available

On Wed, Sep 26, 2018 at 10:30 AM, Dmitry Smirnov wrote: > On Wednesday, 26 September 2018 3:05:32 PM AEST Luke Kenneth Casson Leighton > wrote: >> appreciated, dmitry: apologies, it catches me off-guard when things >> don't work. > > No worries. It would be nice t

Bug#909630: initscript found

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Sep 26, 2018 at 6:03 AM, Dmitry Smirnov wrote: > On Wednesday, 26 September 2018 2:10:09 PM AEST Luke Kenneth Casson Leighton > wrote: >> https://gitlab.com/gitlab-org/gitlab-ce/raw/master/lib/su

Bug#909630: gitlab: no sysvinit scripts installed or available

appreciated, dmitry: apologies, it catches me off-guard when things don't work. it was just that the decision to rail-road systemd in (which is software that itself is being developed incredibly unethically) - was itself made unethically (not thinking of the harm that could result, and without

Bug#909630: initscript found

https://gitlab.com/gitlab-org/gitlab-ce/raw/master/lib/support/init.d/gitlab this is semi-suitable: at least it has been possible to get things up and running, by removing the section starting "Script variable names" and relying on the entries in /etc/default/gitlab that are absolutely fine in

Bug#901006: closed by Ben Hutchings (Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" kernel messagee)

On Fri, Jun 8, 2018 at 2:27 AM, Debian Bug Tracking System wrote: > -- Forwarded message -- > From: Ben Hutchings > To: 901006-d...@bugs.debian.org > Cc: > Bcc: > Date: Fri, 08 Jun 2018 02:24:57 +0100 > Subject: Re: Bug#901006: linux-image-4.16.0-2-amd64: "core has locked up" >

Bug#892504: [PATCH] nspr: Please add support for the RISC-V architecture

On Fri, Mar 9, 2018 at 8:31 PM, Karsten Merker wrote: > There is one thing that I am a bit unsure about, though, and that > is Mozilla's use of WORD and DWORD in their size definitions as I > haven't found any documentation about that. hiya karsten, ok so someone from

Bug#891411: Acknowledgement (mailman critically (and unnecessarily) linked to apache2 (and not nginx))

On Mon, Feb 26, 2018 at 7:51 AM, Thijs Kinkhorst <th...@debian.org> wrote: > On Sun, February 25, 2018 12:13, Luke Kenneth Casson Leighton wrote: >> apologies, after downloading the source i noted that the debian/rules >> debian package. i've installed lighthttpd, disabled it

Bug#872036: Acknowledgement (AH00060: seg fault or similar nasty error detected in the parent process)

ok so a little more info here: the segfault occurs *directly* after a logrotate-inspired signal is received. [Sat Aug 19 06:25:37.746265 2017] [mpm_event:notice] [pid 21345:tid 3074504512] AH00493: SIGUSR1 received. Doing graceful restart [Sat Aug 19 06:25:39.647852 2017] [core:notice] [pid

Bug#860789: Acknowledgement (freecad: import of openscad file turns "differences" into "unions")

ah: i hadn't spotted this: it would appear that a legitimate scad file is considered to be a syntax error by freecad's parser. Parser Loaded Start Parser Vector Vector Vector Vector Vector Matrix Syntax error in input! LexToken(SEMICOL,';',23,603) Vector Vector Vector Vector Matrix ('$fn', '100')

Bug#848895: Chromium freezes randomly

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Tue, Apr 18, 2017 at 4:08 AM, Michel Dänzer <mic...@daenzer.net> wrote: > On 18/04/17 11:55 AM, Luke Kenneth Casson Leighton wrote: >> On Tue, Apr 18, 2017 at 3:27 AM, Michel Dänzer <mic...@

Bug#848895: Chromium freezes randomly

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Tue, Apr 18, 2017 at 3:27 AM, Michel Dänzer wrote: >> far from being 100% reproducible when resizing glxgears under fvwm2 >> with DRI2, glxgears freezing is now 100% *un*reproducible. > > Please

Bug#848895: Chromium freezes randomly

ok so i ended up with an unancipated reboot, which meant i had an opportunity to test DRI3 and since setting Option DRI "3" in xorg.conf i have *not* encountered a *single* lock-up, not with chromium, nor glxgears, nor openscad. far from being 100% reproducible when resizing glxgears under

Bug#848895: Chromium freezes randomly

ok i've raised this directly upstream with the mesa-dev team on freedesktop.org and also done a little investigation, and found that the processes are hanging waiting in a poll in libxcb. the mesa-dev team asked everyone who is affected *AND NOT* affected to report which version of DRI is being

Bug#858904: openscad: opengl / x11 strange "hanging" error (also found in other packages)

ok yes after using openscad consistently for several days now, i get recurrence of this well-known behaviour quite frequently. if i was to put an arbitrary percentage on it, it would be about... 2% (1-in-50) of every attempted move/rotate operation with the mouse. anyway, main point of this

Bug#858904: openscad: opengl / x11 strange "hanging" error (also found in other packages)

hi chrysn, i have an extremely powerful machine with 16gb of 2400mhz DDR4 RAM, 8-core i7 and a 2500mbyte/sec SSD. speed is *not* a problem :) a simple model easily gives a framerate of appx 30fps. however it is working really rather hard: i had openscad run with a window @ 1940 x 1400 and was

Bug#848895: Chromium freezes randomly

ha, that's very interesting: since starting the chat with my friend on facebook (a developer in china) for about 90 minutes i have had *three* lockups (each time recoverable with ctrl-alt-f1, ctrl-alt-f7). one in particular the cursor moved off-screen for a fraction of a second and back again

Bug#848895: Chromium freezes randomly

haaa! finally... after waiting for well over a week, at last! the bug *did* in fact reoccur. just to make sure we're on the right page this is from the chrome://version Chromium 56.0.2924.76 (Developer Build) built on Debian 9.0, running on Debian 7.4 (64-bit) Revision

Bug#857552: i965-va-driver: failing to play videos (stops half-way through)

[off-topic for this bugreport, separate response later, much appreciated the advice on mpv nicholas!] On Wed, Mar 15, 2017 at 11:03 PM, Nicholas D Steeves wrote: > I noticed something strange in the original bug report: > >> > > On 2017-03-12 13:31:24, lkcl wrote: >> > >>

Bug#857552: i965-va-driver: failing to play videos (stops half-way through)

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Sun, Mar 12, 2017 at 7:01 PM, Sebastian Ramacher wrote: > Control: tags -1 + moreinfo > > On 2017-03-12 13:31:24, lkcl wrote: >> Package: i965-va-driver >> Severity: important >> Tags: upstream

Bug#857552: Acknowledgement (i965-va-driver: failing to play videos (stops half-way through))

p.s. it's repeatable (stops at exactly the same point)

Bug#614296: xserver-xorg-video-intel: additional rendering corruption (screenshot included)

On Sat, Feb 25, 2017 at 3:54 AM, Luke Kenneth Casson Leighton <l...@lkcl.net> wrote: > is linux-kernel driver-related. 4.9.6 problem is gone. bug may be closed. darn it, sorry - no it can't: bug is still present, encountered on xpdf and gerbv. rendering still corrupted and requires

Bug#614296: xserver-xorg-video-intel: additional rendering corruption (screenshot included)

is linux-kernel driver-related. 4.9.6 problem is gone. bug may be closed. --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Fri, Jan 27, 2017 at 7:37 AM, lkcl wrote: > Package: xserver-xorg-video-intel > Version: 2:2.99.917+git20161105-1+b1 >

Bug#848895: Chromium freezes randomly

On Thu, Feb 23, 2017 at 9:41 PM, Ximin Luo <infini...@debian.org> wrote: > Luke Kenneth Casson Leighton: >> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87 >> >> now ain't that fascinating. optirun combined with fvwm2 is a >> sure-fire extremely fast a

Bug#855557: Acknowledgement (primus: gl framedropping isn't handled correctly, apps need a restart to recover)

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=848895 fascinating. seems to be related. using ctrl-alt-f1 followed by ctrl-alt-f7 "fixes" the problem. --- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Mon, Feb 20, 2017 at 3:45 AM, Debian Bug Tracking System

Bug#848895: Chromium freezes randomly

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=87 now ain't that fascinating. optirun combined with fvwm2 is a sure-fire extremely fast and 100% *guaranteed* way to repro this "freezing but you can ctrl-alt-f1 then ctrl-alt-f7 and it miraculously all works whoopidoo" problem. primus (and

Bug#855558: linux-image-4.9.0-1-amd64: ACPI boot error causes /sbin/init to segfault (!)

faakin 'ell :) woo, ok. setting acpi_os_name="Windows 2009" and also removing vesafb from /etc/initramfs-tools/modules resulted in a boot (attaching dmesg boot which contains two ACPI-related kernel-level warnings). sorry it's an attachment rather than inline. i don't know if it was the setting

Bug#855558: linux-image-4.9.0-1-amd64: ACPI boot error causes /sbin/init to segfault (!)

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Feb 22, 2017 at 12:06 PM, Ben Hutchings wrote: > Control: retitle -1 linux-image-4.9.0-1-amd64: Failed to execute /init > Control: tag -1 moreinfo > > On Mon, 20 Feb 2017 04:00:03 +

Bug#855558: linux-image-4.9.0-1-amd64: ACPI boot error causes /sbin/init to segfault (!)

http://www.linuxquestions.org/questions/linux-from-scratch-13/acpi-errors-when-booting-927408/ ah christ almighty, they're talking about "updating the bios fixes the problem" *sigh*. 3.16, 4.7 and 4.8 are all fine - so wtf is 4.9 doing not being capable of running /init when all prior version

Bug#855818: linux-image-4.8.0-2-amd64: segfault in intel 9815 drm kernel module

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Wed, Feb 22, 2017 at 2:38 AM, Ben Hutchings wrote: > Control: tag -1 - upstream > Control: tag -1 moreinfo > > On Wed, 2017-02-22 at 01:45 +, lkcl wrote: >> Package: src:linux >> Version:

Bug#848895: Chromium freezes randomly

btw fyi https://bugs.chromium.org/p/chromium/issues/detail?id=675411 i noted a vast and i mean constant monotonous barely-tolerable number of gpu freezing errors when operating inside of china. i therefore suspect that this is a race condition between networking code and the gpu code. l.

Bug#848895: Chromium freezes randomly

ah ha! when i did the latest "kill" i got this: [11121:11121:0207/112924:ERROR:gpu_process_transport_factory.cc(844)] Lost UI shared context.

Bug#848895: chromium: still freezing randomly but usually on changing virtual screens

oky, finally: yes, i can confirm that killing the gpu-process (ps aux | grep gpu) will make things "work" again... without actually having to kill off the entire chromium browser. examples where hanging occurred include PDF viewing (where, clearly, the GPU was asked to do the rendering).

Bug#848895: chromium: still freezing randomly but usually on changing virtual screens

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Tue, Jan 24, 2017 at 5:44 PM, lkcl wrote: > Package: chromium > Version: 55.0.2883.75-3 > Followup-For: Bug #848895 > > (hi! note: after the other bug in which virtualbox was being a pain i removed >

Bug#848895: chromium: still freezing randomly but usually on changing virtual screens

On Tue, Jan 24, 2017 at 5:44 PM, lkcl wrote: > Package: chromium > Version: 55.0.2883.75-3 > Followup-For: Bug #848895 > i'm currently going through the list of processes killing them one by > one to see if that helps... ah ha! it does. okay so *one* of the processes is

Bug#851984: dpkg failing with "locked by another process" on apt-get build-dep

On Sun, Jan 22, 2017 at 12:17 PM, Guillem Jover wrote: > Control: forcemerge 850417 -1 > > Hi > > On Fri, 2017-01-20 at 15:26:19 +, lkcl wrote: >> Package: dpkg >> Version: 1.18.18 >> Severity: important > >> weirdest bug i've encountered on debian, yet, in 12 years! >>

Bug#851984: dpkg failing with "locked by another process" on apt-get build-dep

upgraded to apt 1.4~beta3 and the problem's "gone away". so, this bug can be closed but can i suggest (i don't know how to do it myself, guillem) reassigning it to apt... and *then* closing it, so that there's a proper record associated with the right program, in case someone also encounters

Bug#851984: dpkg failing with "locked by another process" on apt-get build-dep

htttp://hands.com/~lkcl/dpkg_strace_851984_bug.tgz ah. we now have a candidate for a reassign: after doing that strace i tried doing "apt-get install libavdevice57" (one of the dependencies of blender) and that *worked*. so, it's *only* when doing "apt-get build-dep" that the dpkg bug-out

Bug#851179: closed by Michael Gilbert <mgilb...@debian.org> (re: chromium: dependency conflict)

it appears that there isn't a version of virtualbox from debian-testing. root@fizzy:/home/lkcl# apt-cache show virtualbox Package: virtualbox Version: 4.3.36-dfsg-1+deb8u1 Installed-Size: 56553 Maintainer: Debian Virtualbox Team Architecture: amd64

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#806670: rotation is dragging

On Thu, Jan 7, 2016 at 9:47 PM, Torsten Paul wrote: > That basically sums up the reports so far. On my system I can > reproduce the issue with debug builds, but not with release builds. right - i have a possible explanation for that. if there are two threads now in qt5,

Bug#820729: openscad: chris palmer's mendel90 openscad scripts cause a compile failure

--- crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68 On Mon, Apr 11, 2016 at 8:43 PM, Torsten Paul wrote: > On 04/11/2016 08:15 PM, lkcl wrote: >> Debian Release: 7.4 >> > That's Wheezy which has OpenSCAD 2011.12-3, right? sorry, the meta-tag

Bug#775310: ikiwiki: git mv on directories results in git merge/overwrite errors

simon, hi, many apologies for not following up: my friend running the server discovered, after around 18 months of puzzled investigation, that he had (or perhaps had not) added a certain critical system-required file to .gitignore as part of the upgrade to gitolite3. exact details are hard to

Bug#806670: rotation is dragging

On Thu, Jan 7, 2016 at 9:25 PM, chrysn <chr...@fsfe.org> wrote: > On Thu, Jan 07, 2016 at 06:36:07PM +0000, Luke Kenneth Casson Leighton wrote: >> On Thu, Jan 7, 2016 at 6:00 PM, lkcl <l...@lkcl.net> wrote: >> >> > so what i'm going to do is to find an

Bug#806670: rotation is dragging

On Thu, Jan 7, 2016 at 9:47 PM, Torsten Paul wrote: >> torsten, can you make anything of this? (lkcl's messages in full at >> http://bugs.debian.org/806670) >> > Yes, the event handling is likely the root cause of the issue, but > the exact same code works fine with Qt4 and

Bug#806670: rotation is dragging

On Fri, Jan 8, 2016 at 2:22 AM, Luke Kenneth Casson Leighton <l...@lkcl.net> wrote: > On Thu, Jan 7, 2016 at 9:25 PM, chrysn <chr...@fsfe.org> wrote: >> luke, could you, for comparison, on the system where the new .deb >> dragged and the fresh 21c8d2fc9 (that's o

Bug#806670: rotation is dragging

On Fri, Jan 8, 2016 at 3:12 AM, Torsten Paul <torsten.p...@gmx.de> wrote: > On 01/08/2016 03:36 AM, Luke Kenneth Casson Leighton wrote: > Thanks for providing this nice motivation to help. i was concerned for a moment that i'd misunderstood, and that the code-comment meant th

Bug#787127: closed by chr...@fsfe.org (Christian M. Amsüss) (Bug#787127: fixed in openscad 2015.03-1+dfsg-1)

On Wed, Aug 12, 2015 at 2:27 PM, chrysn chr...@fsfe.org wrote: hello luke, On Wed, Aug 12, 2015 at 01:39:55PM +0100, Luke Kenneth Casson Leighton wrote: i'm not seeing a version 2015.03-1+dfsg-1 here: https://packages.debian.org/search?keywords=openscad or here: http://ftp.uk.debian.org

Bug#787127: closed by chr...@fsfe.org (Christian M. Amsüss) (Bug#787127: fixed in openscad 2015.03-1+dfsg-1)

hi chris, i'm not seeing a version 2015.03-1+dfsg-1 here: https://packages.debian.org/search?keywords=openscad or here: http://ftp.uk.debian.org/debian/pool/main/o/openscad/ there is only 2014.03-1+dfsg-1. ... what gives? l. On Wed, Aug 12, 2015 at 1:24 PM, Debian Bug Tracking System

Bug#792670: androidsdk-ddms: android sdk license appears to violate debian charter

hi emmanuel, dr stallman investigated and has this to point out: The Google SDK license contains this text 3.5 Use, reproduction and distribution of components of the SDK licensed under an open source software license are governed solely by the terms of that open source software

Bug#792670: androidsdk-ddms: android sdk license appears to violate debian charter

On Fri, Jul 17, 2015 at 1:11 PM, Emmanuel Bourg ebo...@apache.org wrote: Le 17/07/2015 12:06, Luke Kenneth Casson Leighton a écrit : thoughts? The code from android.googlesource.com clearly comes with an Apache-2.0 license though. I wonder if these terms and conditions only apply to the SDK

Bug#792670: androidsdk-ddms: android sdk license appears to violate debian charter

On Fri, Jul 17, 2015 at 1:39 PM, Emmanuel Bourg ebo...@apache.org wrote: I couldn't find these TC in the upstream Git repository [1]. oh - that's very good. ok, that helps enormously... you don't need to go to the sdk site, you can just bypass it and compile the code directly from source. i

Bug#792670: androidsdk-ddms: android sdk license appears to violate debian charter

Package: androidsdk-ddms Severity: important Dear Maintainer, i've been alerted to the following in the android sdk terms and conditions: 3.4 You agree that you will not take any actions that may cause or result in the fragmentation of Android, including but not limited to distributing,

Bug#787127: openscad segfault

On Fri, May 29, 2015 at 1:08 PM, chrysn chr...@fsfe.org wrote: hello lkcl, On Thu, May 28, 2015 at 09:33:15PM +0100, lkcl wrote: openscad segfaults with the file that may be downloaded from the following location: http://lkcl.net/openscad_bug.scad thans for reporting this; i can reproduce

Bug#399608: fixed in sysvinit 2.88dsf-59.1

On Sun, May 17, 2015 at 3:48 PM, Andreas Henriksson andr...@fatal.se wrote: Hello Adrian! Thanks for raising awareness about this issue. If there's anything I can do to help please tell me. That the new util-linux version hasn't been built yet sounds like it can't be avoided as it was just

Bug#776959: linux-image-3.16.0-4-amd64: [regression] sd card reader in retina macbook pro no longer working

On Tue, Feb 3, 2015 at 7:58 PM, Ben Hutchings b...@decadent.org.uk wrote: Control: tag -1 important On Tue, 2015-02-03 at 15:39 +, lkcl wrote: Package: src:linux Version: 3.16.7-ckt2-1 Severity: important after upgrading from 3.13 where the built-in sd card worked perfectly, there is

Bug#776959: linux-image-3.16.0-4-amd64: [regression] sd card reader in retina macbook pro no longer working

On Tue, Feb 3, 2015 at 9:28 PM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: On Tue, Feb 3, 2015 at 7:58 PM, Ben Hutchings b...@decadent.org.uk wrote: Control: tag -1 important On Tue, 2015-02-03 at 15:39 +, lkcl wrote: Package: src:linux Version: 3.16.7-ckt2-1 Severity: important

Bug#748373: python-lmdb

On Thu, Dec 11, 2014 at 6:30 PM, Robert Edmonds edmo...@debian.org wrote: Hi, I'm planning on using py-lmdb for a project, and it appears no one else is working on a package, so I'll be happy to take this RFP. David Wilson wrote: * The binding is still receiving significant development, so

Bug#768171: RFP: yacy -- A free (libre) decentralised Internet Search Engine

Package: wnpp Severity: wishlist * Package name: yacy Version : 1.8 Upstream Author : * URL : http://www.yacy-websuche.de/wiki/index.php/En:DebianInstall * License : GPL Programming Lang: java Description : A free (libre) decentralised Internet Search

Bug#745147: closed by Ben Hutchings b...@decadent.org.uk (Re: WARNING on removal of SCSI device which is still in use)

thanks for keeping an eye on this ben On Wed, Sep 24, 2014 at 2:42 PM, Debian Bug Tracking System ow...@bugs.debian.org wrote: Subject: Re: WARNING on removal of SCSI device which is still in use Version: 3.15~rc5-1~exp1 This is supposed to be fixed in 3.15-rc1 by: commit

Bug#745142: Acknowledgement (debootstrap functions rely on Packages file existing (it doesn't in lenny archive))

ahh... a bit more investigation showed that this *might* have been due to running out of disk space. that may have masqueraded the error: a better error should really have been presented. l. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe.

Bug#744994: linux-image-3.13-1-amd64: segfault on use of external (usb) dvdrw

On Fri, Apr 18, 2014 at 2:11 PM, Ben Hutchings b...@decadent.org.uk wrote: Apr 17 09:24:08 teenymac kernel: [1201449.213969] usb 2-5: USB disconnect, device number 18 Drive removed. yes. bit of a melt-down on another USB hub, i had to unplug it (and the attached

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#730482: linux-image-3.9.6: PCI/USB reset not being done on Geode LX800 / CS5536

On Thu, Nov 28, 2013 at 9:22 AM, Andrei POPESCU andreimpope...@gmail.com wrote: Hi Kernel Maintainers, Since the package doesn't exist this landed in the wrong place. Could you please have a look and take over the bug if useful? thanks andrei. i've since observed that the two ethernet ports

Bug#721924: Acknowledgement (linux-image-3.10-2-amd64: btrfs writing several small files causes massive load spike)

https://bugzilla.kernel.org/show_bug.cgi?id=60860 cf upstream bugreport. On Thu, Sep 5, 2013 at 3:36 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 message has been

Bug#718281: Acknowledgement (race condition on execution of /etc/ifplugd/ifplug.action script and exit)

after some reflection overnight, i think a minor workaround would be to have in /lib/udev/ifplugd.agent a check to see if '-M' is in the $ARGS and if it is to *not* try to kill the ifplugd instance. for now however i am just commenting out the kill: remove|unregister)

Bug#471076: inkscape: tutorialare installed making a MASSIVE package not possible to install on low-disk-space machines

On Mon, Jul 8, 2013 at 2:19 PM, Matteo F. Vescovi mfv.deb...@gmail.com wrote: Hi! place: removing the tutorials fom the inkscape program. This is one of the things on my TODO list about inkscape. Probably not with the upcoming upload to unstable (that should happen during next weekend) but

Bug#715370: Acknowledgement (linux-image-3.9-1-486: CONFIG_GPIO_CS5535 has been set to 'y' when it should be 'M')

right. having enormous difficulty tracking this down, but there appears to be some kernel config dependencies of CONFIG_GPIO_CS5535 which are set to Y which are forcing CONFIG_GPIO_CS5535 to y. ... but that actually turns out not to be the main problem: the main problem is that although

Bug#706476: Info received (Bug#706476: Info received (Bug#706476 closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compile

ok, it turns out that CONFIG_SYSFS_GPIO is safe, because you have to explicitly take action in order to make GPIO accessible (export). following the instructions here was easy to do: https://sites.google.com/site/bifferboard/Home/gpio so, basically, CONFIG_SYSFS_GPIO could be switched on (as

Bug#706476: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2))

On Wed, May 1, 2013 at 3:33 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the linux-image-3.2.0-4-486 package: #706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled

Bug#706476: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2))

On Wed, May 1, 2013 at 10:56 AM, Luke Kenneth Casson Leighton l...@lkcl.net wrote: It *is* still enabled, but it's built-in on the 486 flavour because OLPC_XO1_SCI selects it. thanks ben... investigating further: # PCI GPIO expanders: # CONFIG_GPIO_CS5535=y # CONFIG_GPIO_LANGWELL

Bug#706476: Info received (Bug#706476 closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2)))

i've added these at the end of debian/config/i386/none/config.i486 and then checked debian/build/build_i386_none_486/.config but CONFIG_GPIO_CS5535 had been modified to y, ah well. fakeroot make -f debian/rules.gen -j16 binary-arch_i386_none_486 still running... # # GPIOLIB and SYSFS #

Bug#706476: linux-image-3.2.0-4-486: amd geode gpio-cs5535 module not being compiled (needed for alix6f2)

On Tue, Apr 30, 2013 at 6:39 PM, Ben Hutchings b...@decadent.org.uk wrote: On Tue, Apr 30, 2013 at 05:22:56PM +0100, lkcl wrote: Package: linux-image-3.2.0-4-486 Severity: important discovered from another debian bugreport that pc-engines systems can be upgraded to more recent firmware and

Bug#684999: ekiga: segfault on exit from video call

On Sun, Sep 9, 2012 at 6:22 PM, Paul Menzel pm.deb...@googlemail.com wrote: Am Sonntag, den 09.09.2012, 16:53 +0100 schrieb Luke Kenneth Casson Leighton: On Sun, Sep 9, 2012 at 2:25 PM, Paul Menzel pm.deb...@googlemail.com wrote: forwarded 684999 https://bugzilla.gnome.org/show_bug.cgi?id

Bug#637039: Re: lsb-release: parse_apt_policy in lsb_release.py fails

On Fri, Mar 2, 2012 at 8:50 AM, Didier 'OdyX' Raboud o...@debian.org wrote: tags 637039 +unreproducible +moreinfo thanks ok it's not exactly a patch but close: policy = commands.getoutput('LANG=C apt-cache policy 2/dev/null') should be: policy = commands.getoutput('LANG=C apt-cache policy

Bug#660487: xulrunner-dev: instant segfault in startup (related to jemalloc)

On 2/19/12, Mike Hommey m...@glandium.org wrote: On Sun, Feb 19, 2012 at 03:29:03PM +, lkcl wrote: Package: xulrunner-dev Version: 10.0.1-1 Severity: normal https://bugzilla.mozilla.org/show_bug.cgi?id=728500 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660178 there's a segfault

Bug#660487: xulrunner-dev: instant segfault in startup (related to jemalloc)

https://bugzilla.mozilla.org/show_bug.cgi?id=678977#c46 mike hi, it looks like this has been solved, and i leave it in your capable hands to sort out xulrunner - the question remaining is: what to do now about hulahop? i've been asked to help get hulahop into a working state, but xulrunner 10 is

  1   2   3   4   >