: tool to notify you when your YubiKey is waiting for a touch
This package provides a tool that can detect when the attached YubiKey
is waiting for your touch. It is designed to be integrated with other UI
components to display a visual indicator.
.
By default this tool offers a feed through a
Description : Puppet module for waiting for something
Puppet lets you centrally manage every important aspect of your system using a
cross-platform specification language that manages all the separate elements
normally aggregated in different files, like users, cron jobs, and hosts,
along with
: JavaScript
Description : The asap function executes a task as soon as
possible but not before it returns,
waiting only for the completion of the current event and previously
scheduled tasks.
.
ASAP strives to schedule events to occur before yielding for IO,
reflow, or redrawing.
ASAP provides
X-Debbugs-CC: debian-devel@lists.debian.org
Package: wnpp
Severity: wishlist
Owner: Debian Tryton Maintainers
* Package name: tryton-modules-commission-waiting
Version : 3.6.0
Upstream Author : Tryton project (www.tryton.org)
* URL : http://downloads.tryton.org/3.6
dopt) has been offered by a non DD, which
> is waiting for sponsorship. Typically, some of these potential
> maintainers may be active users or upstream maintainers.
>
> But who cares ?
>
> If such package are getting removed from testing (re. new release policy
> experiment), m
On Thu, Jan 30, 2014 at 02:40:55PM +, Neil Williams wrote:
> > Sometimes it _is_ helpful. Any tools that made it easier to judge when
> > would be good. Just being on the mentors list gives a poor overview of
> > how much is slipping through the net.
>
> Personally, I'm wondering how much of w
t) has been offered by a non DD, which
> is waiting for sponsorship. Typically, some of these potential
> maintainers may be active users or upstream maintainers.
>
> But who cares ?
>
> If such package are getting removed from testing (re. new release policy
> experiment), m
On Thu, 30 Jan 2014 13:41:16 +
Wookey wrote:
> +++ Neil Williams [2014-01-30 13:25 +]:
> > On Thu, 30 Jan 2014 13:51:40 +0100
> > Olivier Berger wrote:
> >
> > > I myself isn't very motivated to sponsor packages which I don't
> > > use... but maybe I'm not noticing at all (or didn't rea
Hi,
On 01/30/2014 02:25 PM, Neil Williams wrote:
> On Thu, 30 Jan 2014 13:51:40 +0100
> Olivier Berger wrote:
>
>> I myself isn't very motivated to sponsor packages which I don't
>> use... but maybe I'm not noticing at all (or didn't read
>> how-can-i-help messages ;-).
>
> That's the crux of i
+++ Neil Williams [2014-01-30 13:25 +]:
> On Thu, 30 Jan 2014 13:51:40 +0100
> Olivier Berger wrote:
>
> > I myself isn't very motivated to sponsor packages which I don't
> > use... but maybe I'm not noticing at all (or didn't read
> > how-can-i-help messages ;-).
>
> That's the crux of it -
On Thu, 30 Jan 2014 13:51:40 +0100
Olivier Berger wrote:
> I myself isn't very motivated to sponsor packages which I don't
> use... but maybe I'm not noticing at all (or didn't read
> how-can-i-help messages ;-).
That's the crux of it - a sponsor needs some level of interest in the
package, beyo
Hi.
I'm not sure this is really a problem we should address. Sorry if I'm
overlooking details.
I suspect we have quite a few orphaned old packages still in testing,
for which an ITA (Intent to Adopt) has been offered by a non DD, which
is waiting for sponsorship. Typically, som
Il giorno Fri, 04 Jun 2010 19:37:26 +0100
"Adam D. Barratt" ha scritto:
> > * 1 package has temporary dependency screwup
> What specifically does "temporary dependency screwup" mean?
http://people.debian.org/~dktrkranz/scons-2.0/depwait/gtkrsync_1.0.4-sid-i386-20100604-075618.22.log
gtkrsync req
Hi,
On Fri, 2010-06-04 at 16:30 +0200, Luca Falavigna wrote:
> So, I rebuilt reverse dependencies of SCons to spot some problems, and I
> published my results online. Here is a brief summary:
>
> * 58 packages build-depending on SCons
> * 53 packages built successfully (2 of them needed sourceful
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Il giorno Fri, 04 Jun 2010 13:12:52 -0400
Felipe Sateler ha scritto:
> Does SCons finally support SONAMES or do we still have to manually do
> that? I don't see any reference to that in the release text.
I don't think so. I remember I've seen a requ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/06/10 10:30, Luca Falavigna wrote:
> Hello,
>
> SCons developers are close to release new major release of SCons, which
> started to deprecate some obsolete function and dropped support for
> Python code older than 2.4. Full release notes can
Hello,
SCons developers are close to release new major release of SCons, which
started to deprecate some obsolete function and dropped support for
Python code older than 2.4. Full release notes can be found here:
http://sourceforge.net/projects/scons/files/scons/2.0.0.beta.20100531/RELEASE.txt/vie
On Sat, Aug 23, 2008 at 05:02:49AM +0800, [EMAIL PROTECTED] was heard to say:
> Say, often a developer upgrades a group of related packages, but they
> don't hit the mirrors at the same time. This causes apt-get
> dselect-upgrade and dist-upgrade to remove the older parts instead of
> holding back
TF> aptitude safe-upgrade
TF> aptitude dist-upgrade
OK works good and I am sold.
Maybe I can even use aptitude to solve my other posting today
"how to keep the latest linux-doc package installed?"
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [E
On Sat, Aug 23, 2008 at 06:07:46AM +0800, [EMAIL PROTECTED] wrote:
> I used to use aptitude, and even dselect, but I found one needed to
> use their full screen modes to use them to their full extent, which
> was too exciting for me, so retreated to the simpler apt-get
> dselect-upgrade to stay on
AP> apt-get dist-upgrade is not meant to be run on a daily basis on sid, but
AP> only as needed and for when you actually look at the output to make sure
AP> it doesn't remove something you actually want. Second of all, "real men"
AP> use aptitude, which handles these kinds of dependencies in a sma
I.e., here we see apt gets it right for php5, but not for gimp:
# apt-get -o Debug::pkgProblemResolver=true dist-upgrade
Investigating php5
Package php5 has broken dep on libapache2-mod-php5
Package php5 has broken dep on libapache2-mod-php5filter
Package php5 has broken dep on php5-cgi
Or group
Say, often a developer upgrades a group of related packages, but they
don't hit the mirrors at the same time. This causes apt-get
dselect-upgrade and dist-upgrade to remove the older parts instead of
holding back for the newer parts. One must use apt-get upgrade for the
many days the condition pers
On Wed, Jan 02, 2008 at 09:09:51PM +, Roger Leigh wrote:
> This is only a problem with the old version of sbuild in use on the
> buildds. The version in unstable has used the apt inside the chroot
> for well over two years. The patches to enable it do exist in the GIT
> repo, and could be tri
Aurelien Jarno <[EMAIL PROTECTED]> writes:
> Pierre Habouzit a écrit :
>> On Wed, Jan 02, 2008 at 05:18:58PM +, Julien BLACHE wrote:
>>> Hideki Yamane <[EMAIL PROTECTED]> wrote:
>>>
>> Agreed. OTOH couldn't the amd64 buildd's also act as i386 buildd's ? I
>> think that _most_ of the packages
On Wed, Jan 02, 2008 at 09:35:08PM +0100, Aurelien Jarno wrote:
> The main problem I see is that sbuild uses apt from the host
> installation, which means the host and the chroot should have the same
> architecture.
Two solutions present themselves:
* -o APT::Architecture=i386 (if that works)
Pierre Habouzit a écrit :
> On Wed, Jan 02, 2008 at 05:18:58PM +, Julien BLACHE wrote:
>> Hideki Yamane <[EMAIL PROTECTED]> wrote:
>>
>>> Umm, if build daemon is down, it is a problem, I think.
>>> As i386 it is not a serious, but it is just a problem.
>> It is a problem, and it is serious. I
Thijs Kinkhorst wrote:
> Several DSA's have been stalled the past months because of missing i386
> builds. It would be great if we can reduce that.
i386 d-i is also broken due to missing i386 builds now. (partman-*
version skew)
--
see shy jo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
On Wed, Jan 02, 2008 at 05:18:58PM +, Julien BLACHE wrote:
> Hideki Yamane <[EMAIL PROTECTED]> wrote:
>
> > Umm, if build daemon is down, it is a problem, I think.
> > As i386 it is not a serious, but it is just a problem.
>
> It is a problem, and it is serious. It's stalling the testing
>
Hideki Yamane <[EMAIL PROTECTED]> wrote:
> Umm, if build daemon is down, it is a problem, I think.
> As i386 it is not a serious, but it is just a problem.
It is a problem, and it is serious. It's stalling the testing
transition already due to missing builds.
i386 is no longer a special case a
Quoting Thijs Kinkhorst ([EMAIL PROTECTED]):
> Of course i386 machines are commonly available, but the suggested procedure
> of
> making uploads by hand is undesirable (especially for stable):
>
> a) it increases chances of dirty/broken build environments;
> b) it costs time;
> c) some packages
Hi,
On Wed, 02 Jan 2008 14:27:42 +0100
Aurelien Jarno <[EMAIL PROTECTED]> wrote:
> It seems the build daemon is down. However according to [1] it should
> not be a problem, you should build and upload the packages manually:
But I'm not a DD and not sylpheed package maintainer... ;-)
Umm, if bu
On Wednesday 2 January 2008 14:27, Aurelien Jarno wrote:
> It seems the build daemon is down. However according to [1] it should
>
> not be a problem, you should build and upload the packages manually:
> | Waiver (for redundancy, since there isn't any): Most developers upload
> | for i386; buildd d
Hideki Yamane a écrit :
> Hi list,
>
> I'm waiting sylpheed 2.4.8-1 package (i386) from 25th December, all
> architectures except i386 are built completed. sylpheed is still in
> build queue for one week.
> http://unstable.buildd.net/buildd/i386_Needs-Build_queu
Hi list,
I'm waiting sylpheed 2.4.8-1 package (i386) from 25th December, all
architectures except i386 are built completed. sylpheed is still in
build queue for one week.
http://unstable.buildd.net/buildd/i386_Needs-Build_queueorder.html
build percentage for i386 has decreased.
Nathanael Nerode <[EMAIL PROTECTED]> writes:
> I wrote this capability almost a year ago. It's languished in bugs
> #405886, #405888, #389450.
>
> This is the ability to load from a second source of udebs (non-free, for
> instance, or vendor supplied).
Non-free already works just fine and is al
I wrote this capability almost a year ago. It's languished in bugs
#405886, #405888, #389450.
This is the ability to load from a second source of udebs (non-free, for
instance, or vendor supplied).
It's utterly straightforward and actually rather uninvasive code. As designed
it
doesn't affec
Attn: Sir,
Am Simon Bunce ;an accredited vendor of Emirates International Holding (EIH); A
private equity funds holding company that focuses on hedge funds.
I have contacted you in the hope that you can be my associate to assume the new
recipient of a Fixed-Income deposit of my lates client,
Respected
Sir,
I got the job letters of NIGERA. They send me
agreement letters. So I want to conform that the Name
of person (Dr. MIKE ADENUGA)
Designation (HEAD OF VISA / PERMITS OPERATIONS)
Address (NIGERIAN IMMIGRATION SERVICES 2nd FLOOR, FED.
SECRETERIAT COMPLEX, OWERRI, IMO STATE NIGERIA) so
www.qfu4bxseujqp9t8.marvinfhlil.com
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Mon, Feb 21, 2005 at 03:53:44PM +0100, Goswin von Brederlow wrote:
> Bernd Eckenfels <[EMAIL PROTECTED]> writes:
> > In article <[EMAIL PROTECTED]> you wrote:
> What would help save many hours on slow systems is having a script
> automatically set "Dep-Wait: libbfoo (>> 1.2-3)" for all new sourc
roblem?
>
> A build log extract follows.
>
> [...]
> gcc -I. -I../../../../include -Wall -g -c ../../hbmlang.c -ohbmlang.o
> ../../../../source/compiler/linux/gcc/harbour ../../hbmake.prg -n -q0 -w
> -es2 -gc0 -I../../ -I../../../../include
> make[4]: *** wait: No ch
El Martes, 26 de Octubre de 2004 02:06, Anibal Monsalve Salazar escribió:
> Package harbour is FTBFS on alpha, s390, m68k, powerpc and mips, as
> you can see at:
>
> http://buildd.debian.org/build.php?pkg=harbour
>
> Could someone shed some light on this problem?
Hi Anibal.
I'm the maintainer of
../../../../source/compiler/linux/gcc/harbour ../../hbmake.prg -n -q0 -w -es2
-gc0 -I../../ -I../../../../include
make[4]: *** wait: No child processes. Stop.
make[4]: *** Waiting for unfinished jobs
make[4]: *** wait: No child processes. Stop.
make[3]: *** [descend] Error 2
make[1
On Fri, Apr 18, 2003 at 06:11:16AM +1000, Anthony Towns wrote:
> On Thu, Apr 17, 2003 at 08:11:52PM +0200, Sven Luther wrote:
> > I CCed you the bugreport where i explain everything, but the packages are :
> > libpgsql-ocaml
> > ocamlsdl
> > These are the source packages.
>
> You missed:
> o
On Fri, Apr 18, 2003 at 07:56:12AM +0200, Sven Luther wrote:
> Maybe Stefano could upload a version to testing-proposed-updates that
> drops the these two libraries. It should be ok, since meta-ocaml is an
> arch: all package, and don't needs the autobuilders.
Done: meta-ocaml 3.06.1testing
--
S
On Fri, Apr 18, 2003 at 06:11:16AM +1000, Anthony Towns wrote:
> On Thu, Apr 17, 2003 at 08:11:52PM +0200, Sven Luther wrote:
> > I CCed you the bugreport where i explain everything, but the packages are :
> > libpgsql-ocaml
> > ocamlsdl
> > These are the source packages.
>
> You missed:
> o
On Thu, Apr 17, 2003 at 11:31:21PM +0200, Matthias Klose wrote:
> Anthony Towns writes:
> > Yes; you were. I'm focussing on gcc and perl and such things at the
> > moment, and as of yet no one else is really able to do anything about this
> > stuff while I'm busy; hopefully both those things will c
Anthony Towns writes:
> Yes; you were. I'm focussing on gcc and perl and such things at the
> moment, and as of yet no one else is really able to do anything about this
> stuff while I'm busy; hopefully both those things will change soon enough.
and maybe python ...
AFAICS there are two issues:
On Thu, Apr 17, 2003 at 11:31:21PM +0200, Matthias Klose wrote:
> Anthony Towns writes:
> > Yes; you were. I'm focussing on gcc and perl and such things at the
> > moment, and as of yet no one else is really able to do anything about this
> > stuff while I'm busy; hopefully both those things will c
On Thu, Apr 17, 2003 at 08:11:52PM +0200, Sven Luther wrote:
> I CCed you the bugreport where i explain everything, but the packages are :
> libpgsql-ocaml
> ocamlsdl
> These are the source packages.
You missed:
ocaml-core | 3.06.3 | unstable | all
ocaml-libs | 3.06.3 | u
On Fri, Apr 18, 2003 at 02:17:41AM +1000, Anthony Towns wrote:
> On Thu, Apr 17, 2003 at 02:05:59PM +0200, Sven Luther wrote:
> > On Thu, Apr 17, 2003 at 09:33:32PM +1000, Anthony Towns wrote:
> > > On Thu, Apr 17, 2003 at 12:01:57PM +0200, Sven Luther wrote:
> > > > Well, i personnaly think that i
On Thu, Apr 17, 2003 at 09:56:22PM +0900, Junichi Uekawa wrote:
> Considering the libvorbis case, what needs to happen is the
> remaining packages that depend on libvorbis0 be recompiled
> against libvorbis0a.
The only packages that still dep on libvorbis0 in unstable/i386 seem to be:
bitco
On Thu, Apr 17, 2003 at 02:05:59PM +0200, Sven Luther wrote:
> On Thu, Apr 17, 2003 at 09:33:32PM +1000, Anthony Towns wrote:
> > On Thu, Apr 17, 2003 at 12:01:57PM +0200, Sven Luther wrote:
> > > Well, i personnaly think that in some case it would be much simpler to
> > > _remove_ the packages fro
Considering the libvorbis case, what needs to happen is the
remaining packages that depend on libvorbis0 be recompiled
against libvorbis0a.
Then, optionally, remove the packages from testing.
I would have thought that libvorbis0 and dependent packages merit a removal
from testing because woody
On Thu, Apr 17, 2003 at 09:33:32PM +1000, Anthony Towns wrote:
> On Thu, Apr 17, 2003 at 12:01:57PM +0200, Sven Luther wrote:
> > Well, i personnaly think that in some case it would be much simpler to
> > _remove_ the packages from testing, and let the new versions enter
> > testing as they can.
>
On Thu, Apr 17, 2003 at 12:01:57PM +0200, Sven Luther wrote:
> Well, i personnaly think that in some case it would be much simpler to
> _remove_ the packages from testing, and let the new versions enter
> testing as they can.
Yes, this generally happens. It's not really a good thing though -- it
On Thu, Apr 17, 2003 at 05:21:41PM +1000, Paul Hampson wrote:
> Anyway, now that I've done that... back to your actual interest:
> ocaml is also being recurred:
> i386: libpgsql-ocaml-dev, libsdl-ocaml, libsdl-ocaml-dev, ocaml-libs
>
> From sources:
> libpgsql-ocaml<== Unstable version bre
On Tue, Apr 15, 2003 at 08:42:40AM +0200, Sven Luther wrote:
> On Tue, Apr 15, 2003 at 12:31:44PM +1000, Paul Hampson wrote:
> Hardly, there are many RC bugs or FTBFS bugs in those. I think the main
> issue is that the PTS does not show the list of packages holding up. IT
> is not as easy, since th
On Tue, Apr 15, 2003 at 09:21:15AM -0400, Michael Furr wrote:
> On Tue, 2003-04-15 at 02:42, Sven Luther wrote:
> > * chromium : 1 RC bug, out of date on arm.
> Note this RC bug is tagged "sarge" so it doesn't really apply. The only
> thing holding this back is the arm autobuilder which I'm ho
On Tue, 2003-04-15 at 02:42, Sven Luther wrote:
> * chromium : 1 RC bug, out of date on arm.
Note this RC bug is tagged "sarge" so it doesn't really apply. The only
thing holding this back is the arm autobuilder which I'm hoping will
retry sometime soon with the newly uploaded openal package.
On Tue, Apr 15, 2003 at 12:31:44PM +1000, Paul Hampson wrote:
> On Wed, Apr 09, 2003 at 08:30:42PM +0200, Sven Luther wrote:
> > On Wed, Apr 09, 2003 at 05:59:26PM +0200, Michael Banck wrote:
> > > On Wed, Apr 09, 2003 at 04:40:31PM +0200, Sven Luther wrote:
> > > > depth, i cannot help all that mu
On Wed, Apr 09, 2003 at 08:30:42PM +0200, Sven Luther wrote:
> On Wed, Apr 09, 2003 at 05:59:26PM +0200, Michael Banck wrote:
> > On Wed, Apr 09, 2003 at 04:40:31PM +0200, Sven Luther wrote:
> > > depth, i cannot help all that much about it, and libvorbis is a valid
> > > candidate, but his install
Josip Rodin <[EMAIL PROTECTED]> writes:
> On Wed, Apr 09, 2003 at 12:54:34PM +0200, Petter Reinholdtsen wrote:
>> I suggest we remove packages which haven't entered testing after more
>> more then 300 days.
>
> Packages can be stuck out of testing due to their dependencies, so 300 days
> of lag on
On Wed, Apr 09, 2003 at 12:54:34PM +0200, Petter Reinholdtsen wrote:
> I suggest we remove packages which haven't entered testing after more
> more then 300 days.
Packages can be stuck out of testing due to their dependencies, so 300 days
of lag only indicates a serious problem with a package, it
On Wed, Apr 09, 2003 at 11:05:52PM +0200, Michael Banck wrote:
> On Wed, Apr 09, 2003 at 08:30:42PM +0200, Sven Luther wrote:
> > On Wed, Apr 09, 2003 at 05:59:26PM +0200, Michael Banck wrote:
> > > On Wed, Apr 09, 2003 at 04:40:31PM +0200, Sven Luther wrote:
> > > > depth, i cannot help all that m
On Wed, Apr 09, 2003 at 09:10:30PM +0100, Colin Watson wrote:
> On Wed, Apr 09, 2003 at 08:30:42PM +0200, Sven Luther wrote:
> > Ideally the testing script should be modified to output more verbose
> > data, but i don't speak perl.
>
> That's no excuse, since it's (nowadays) written in Python. :)
On Wed, Apr 09, 2003 at 03:10:46PM +0200, Petter Reinholdtsen wrote:
> [Michael Banck]
> > I object. Not entering testing could very well happen if the
> > package's dependencies are broken/buggy/uninstallable.
>
> Yes, there are many reasons for a package to get stuck in unstable.
>
> But I beli
ould benefit the project or not, it would benefit the
project to create an account for me.
Keep in mind that I don't take it _this_ serriously. The topic came up
and I commented that I was in the same situation. I'm still waiting
patiently and don't want to make a fuss. I only wish I
On Mon, Jan 08, 2001 at 11:23:05AM -0600, Adam Heath wrote:
> I created my pgp key on Dec. 27, 1997. 2 weeks later, I was a
> developer. Granted, this was before the closing, and the reorganization, but
> even for that time frame, that was fast.
>
> What I'm trying to say is that if you prove be
On Mon, 8 Jan 2001, Marek Habersack wrote:
> > Note that I did not flaunt my deeds to the new maintainer team. My nightly
> neither do I do that... It's just that I _really_ want to work and
> contribute to Debian and being a de-facto developer but not _Debian_
> developer my contributions are ve
ibute, I have the skills to
contribute but have no way to contribute. And this is the _only_ problem I
have wrt Debian.
> emails would have been a part of a normal developer updating his fellow
> maintainers. I was perfectly content to keep all those debs in a staging
> area, while I wait
On Mon, 8 Jan 2001, Marek Habersack wrote:
> ** On Jan 08, Adam Heath scribbled:
> > On Mon, 8 Jan 2001, Vince Mulhollon wrote:
> >
> > > Yes, it took me about a year's wait also.
> >
> > I created my pgp key on Dec. 27, 1997. 2 weeks later, I was a
> > developer. Granted, this was before the
** On Jan 08, Adam Heath scribbled:
> On Mon, 8 Jan 2001, Vince Mulhollon wrote:
>
> > Yes, it took me about a year's wait also.
>
> I created my pgp key on Dec. 27, 1997. 2 weeks later, I was a
> developer. Granted, this was before the closing, and the reorganization, but
> even for that time
On Mon, 8 Jan 2001, Vince Mulhollon wrote:
> Yes, it took me about a year's wait also.
I created my pgp key on Dec. 27, 1997. 2 weeks later, I was a
developer. Granted, this was before the closing, and the reorganization, but
even for that time frame, that was fast.
What I'm trying to say is t
75 matches
Mail list logo
