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 Compil
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.
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
wrote:
---
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 j
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
s
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 DF
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 messa
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
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 intera
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_", and
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: Attri
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 w
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, becau
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 inste
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 makin
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 explanatio
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 sys
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 build-d
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 debia
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, th
thank you simon, i've passed that on to christian.
l.
[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 distrib
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 li
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
---
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
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 wid
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 the
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"
> k
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 mozilla is really going to
On Mon, Feb 26, 2018 at 7:51 AM, Thijs Kinkhorst 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, and thus
&g
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 21345
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')
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, Apr 18, 2017 at 4:08 AM, Michel Dänzer 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 wrote:
>>
>>>> far from b
---
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 attach the Xorg log f
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 fvw
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 us
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 bugre
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
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 (whic
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 314da7cc1e56fc9fa9271bac2b
[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:
>> > >> Package: i965-va-driver
---
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
>>
>> i'm getting a vid
p.s. it's repeatable (stops at exactly the same point)
On Sat, Feb 25, 2017 at 3:54 AM, Luke Kenneth Casson Leighton
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 multiple
refr
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
> Followup-For: Bug #614
On Thu, Feb 23, 2017 at 9:41 PM, Ximin Luo 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 and 100% *guaranteed* wa
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
wro
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
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
---
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 + lkcl wrote:
>> Package: s
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 can
---
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: 4.8.15-2
>> Severity: nor
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.
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.
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). just
---
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
> virtualbox and u
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 causing a lock-up
of a
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!
>> simply running "apt-get
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 t
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 occurs
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
Depends: adduser, python (<< 2.8), python (>= 2.
---
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 to
>> all the source being availa
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, one handling mouse-even
---
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 information is misleading.
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 reme
On Fri, Jan 8, 2016 at 3:12 AM, Torsten Paul 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 that the issue was well-under
On Fri, Jan 8, 2016 at 2:22 AM, Luke Kenneth Casson Leighton
wrote:
> On Thu, Jan 7, 2016 at 9:25 PM, chrysn wrote:
>> luke, could you, for comparison, on the system where the new .deb
>> dragged and the fresh 21c8d2fc9 (that's openscad-2014.03, by the way)
>> build
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 in some cases also wit
On Thu, Jan 7, 2016 at 9:25 PM, chrysn 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 wrote:
>>
>> > so what i'm going to do is to find an older version of the openscad source
>>
On Wed, Aug 12, 2015 at 2:27 PM, chrysn 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
>&g
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
wr
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 licen
On Fri, Jul 17, 2015 at 1:39 PM, Emmanuel Bourg wrote:
> I couldn't find these T&C 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 like that. ok so
On Fri, Jul 17, 2015 at 1:11 PM, Emmanuel Bourg 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 on
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, pa
On Fri, May 29, 2015 at 1:08 PM, chrysn 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 the prob
On Sun, May 17, 2015 at 3:48 PM, Andreas Henriksson 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 uploaded
> and
On Tue, Feb 3, 2015 at 7:58 PM, Ben Hutchings 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 no lon
On Tue, Feb 3, 2015 at 9:28 PM, Luke Kenneth Casson Leighton
wrote:
> On Tue, Feb 3, 2015 at 7:58 PM, Ben Hutchings wrote:
>> Control: tag -1 important
>>
>> On Tue, 2015-02-03 at 15:39 +, lkcl wrote:
>>> Package: src:linux
>>> Version: 3.16.7-ckt2-
On Thu, Dec 11, 2014 at 6:30 PM, Robert Edmonds 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 before any
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 En
thanks for keeping an eye on this ben
On Wed, Sep 24, 2014 at 2:42 PM, Debian Bug Tracking System
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 e63ed0d7a98014fdfc2cfeb3f6dada31
On Fri, Apr 18, 2014 at 2:11 PM, Ben Hutchings 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 nothing-to-do-with-the-USB-DVD-drive USB h
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".
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
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 rec
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
wrote:
> Control: tags -1 + moreinfo unreproducible
>
> On 2014-04-17 14:24, lkcl wrote:
>>
>> Package: sgml-base
>> Version: 1.26+n
On Thu, Nov 28, 2013 at 9:22 AM, Andrei POPESCU
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 of
the alix6f2 (whic
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
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 received.
>
> Your
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)
d
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 GPIO_
On Mon, Jul 8, 2013 at 2:19 PM, Matteo F. Vescovi 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 soon enough
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 bui
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
#
CONFIG_
On Wed, May 1, 2013 at 10:56 AM, Luke Kenneth Casson Leighton
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_CS553
On Wed, May 1, 2013 at 3:33 AM, Debian Bug Tracking System
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 (needed for alix6f
On Tue, Apr 30, 2013 at 6:39 PM, Ben Hutchings 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 work wit
On Sun, Sep 9, 2012 at 6:22 PM, Paul Menzel 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 wrote:
>> > forwarded 684999 https://bugzilla.gnome.org/show_bug.cgi?id=683668
>> > tag
On Fri, Mar 2, 2012 at 8:50 AM, Didier 'OdyX' Raboud 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 polic
On Mon, Feb 20, 2012 at 7:09 AM, Mike Hommey wrote:
> On Mon, Feb 20, 2012 at 06:54:54AM +0000, Luke Kenneth Casson Leighton wrote:
>> On Mon, Feb 20, 2012 at 6:46 AM, Mike Hommey wrote:
>>
>> >> but that's not the problem: the problem is generically to *all* -
On Mon, Feb 20, 2012 at 6:46 AM, Mike Hommey wrote:
>> but that's not the problem: the problem is generically to *all* -dev
>> libraries. hmm... let me raise this somewhere on a debian list, but
>> essentially what i need to do is to create a package
>> python-hulahop-that-compiles-and-links-to
1 - 100 of 350 matches
Mail list logo
