Re: logkeys in Debian
On 08/16/2012 07:31 PM, Bart Martens wrote: On Thu, Aug 16, 2012 at 06:48:24PM +0200, Vedran Furač wrote: http://mentors.debian.net/package/logkeys But it doesn't work for me, logkeys uses 100% CPU and doesn't log anything, at least on Sid (someone please test). I don't see an open bug about this problem uses 100% CPU. http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=logkeys Hmm, should I file a bug report against a package from mentors? Since current package from stable works on stable and package from testing/unstable works on testing/unstable. Regards, Vedran attachment: vedran_furac.vcf
Re: [poke] RFS: xinetd
Heya, On 17 August 2012 14:44, Salvo Tomaselli tipos...@tiscali.it wrote: Let me know about the patches. I've uploaded the corrected version http://galileo.dmi.unict.it/~ltworf/xinetd/xinetd_2.3.14-8~exp1.dsc Thanks for the help. I jumped out of bound and did upload -8 into experimental. Oh, well. I should fix this mess now =) I will take your -8~exp1 and upload as -9~exp1, not that -8 has landed into experimental. Sorry for the mess =) Regards, Dmitrijs. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/canbhluhmqoujq-9brtjjsb6adlr7hiv40mkil8d-wmlhyxg...@mail.gmail.com
Re: logkeys in Debian
On Sat, Aug 18, 2012 at 02:20:20PM +0200, Vedran Furač wrote: On 08/16/2012 07:31 PM, Bart Martens wrote: On Thu, Aug 16, 2012 at 06:48:24PM +0200, Vedran Furač wrote: http://mentors.debian.net/package/logkeys But it doesn't work for me, logkeys uses 100% CPU and doesn't log anything, at least on Sid (someone please test). I don't see an open bug about this problem uses 100% CPU. http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=logkeys Hmm, should I file a bug report against a package from mentors? Since current package from stable works on stable and package from testing/unstable works on testing/unstable. I have compared 0.1.0-1 with 1:0.1.0-2 and at first sight I don't see differences that could introduce the problem uses 100% CPU. Are you sure that this problem is not in 0.1.0-1 ? Some changes are not mentioned in debian/changelog (bump Standards-Version, addition of Depends: kbd | console-tools, changes in debian/copyright). I suggest to revert any changes that may conflict with the freeze policy or document them well in debian/changelog with the bug numbers. Regards, Bart Martens -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120818145252.ga7...@master.debian.org
Bug#683184: RFS: suckless-tools/39-1 [ITA]
On 20:46 Thu 16 Aug , Jakub Wilk wrote:
* Vasudev Kamath kamathvasu...@gmail.com, 2012-07-30, 21:56:
It doesn't look like it's suitable for wheezy, so please make it
s/unstable/experimental/.
Done! When it should be moved to unstable? After wheezy release?
Yes, after wheezy is released.
Okay
+-$ $(tabbed -d /tmp/tabbed.xid); urxvt -embed $(/tmp/tabbed.xid);
++$ $(tabbed \-d /tmp/tabbed.xid); urxvt \-embed $(/tmp/tabbed.xid);
If you're fixing this, please also fix the security hole
(insecure use of temporary files).
Done too
So it's now:
TMPFILE=$(mktemp \-\-tmpdir tabbedxid.XXX);$(tabbed \-d ${TMPFILE});urxvt
\-embed $(${TMPFILE})
which is certainly better from security perspective, but not
necessarily from usability one. I think the reason for storing xid
in a file with predictable name was that it allowed you to connect
more than one urxvt to the same tabbed. So I think that:
1) TMPFILE is a bad variable name for this purpose;
2) you could have saved one level of indirection by storing tabbed
-d output directly into the variable (rather than into temporary
file);
3) perhaps it would make more sense to use a file somewhere in
$HOME.
Well yes that line looks most ugly :-). Now I'm choosing 2nd option
given by you and patch is cleaned up.
+ @cd /tmp
+ @tar -cvf - suckless-tools_$(CURRENT_VERSION) 2 /dev/null | gzip -9
../suckless-tools_$(CURRENT_VERSION).orig.tar.gz
+ @rm -rf /tmp/suckless-tools_$(CURRENT_VERSION)
This creates temporary files insecurely.
Fixed.
I see you did this:
get-orig-source: TMPDIR :=$(shell (mktemp --tmpdir -d suckless-tools.))
It looks like a nice hack, but... it will create a temporary
directory every time debian/rules is run (not only for the
get-orig-source target).
Since it was with get-orig-source: target I thought like all Makefiles
it should be called only when we do debian/rules get-orig-source but
looks like it creates directory even when I call debian/rules clean
which I don't understand why! Do you have any other alternatives for
this? and possibly reason why its being called on targets other than
get-orig-source?
I actually used this method from git-flow package of course its not
creating any TMPDIR but it does same for setting one variable. I asked
the package owner and he told that is only way to set the variable (or
at least that is what I interpreted )
Note: I referred git-flow because its also multi source package
I've pushed the changes and waiting for your comments
With Regards
--
Vasudev Kamath
http://copyninja.info
Connect on ~friendica: copyninja@{frndk.de | vasudev.homelinux.net}
IRC nick: copyninja | vasudev {irc.oftc.net | irc.freenode.net}
GPG Key: C517 C25D E408 759D 98A4 C96B 6C8F 74AE 8770 0B7E
signature.asc
Description: Digital signature
Re: logkeys in Debian
On 08/18/2012 04:52 PM, Bart Martens wrote: On Sat, Aug 18, 2012 at 02:20:20PM +0200, Vedran Furač wrote: On 08/16/2012 07:31 PM, Bart Martens wrote: On Thu, Aug 16, 2012 at 06:48:24PM +0200, Vedran Furač wrote: http://mentors.debian.net/package/logkeys But it doesn't work for me, logkeys uses 100% CPU and doesn't log anything, at least on Sid (someone please test). I don't see an open bug about this problem uses 100% CPU. http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=logkeys Hmm, should I file a bug report against a package from mentors? Since current package from stable works on stable and package from testing/unstable works on testing/unstable. I have compared 0.1.0-1 with 1:0.1.0-2 and at first sight I don't see differences that could introduce the problem uses 100% CPU. Are you sure that this problem is not in 0.1.0-1 ? Problem exists with 0.1.0-1 from stable as well when running under current unstable (though this situation would be rare as barely anyone would run packages from stable on an unstable Debian). Regards, Vedran attachment: vedran_furac.vcf
Bug#685077: marked as done (RFS: cvc3/2.4.1-4 [RC])
Your message dated Sun, 19 Aug 2012 04:20:06 + with message-id e1t2wze-0008a0...@quantz.debian.org and subject line closing RFS: cvc3/2.4.1-4 [RC] has caused the Debian Bug report #685077, regarding RFS: cvc3/2.4.1-4 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 685077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=685077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for the latest version of my package cvc3. The version fixes release-critical bugs in cvc3-el. Package name : cvc3 Version : 2.4.1-4 Upstream Author : Clark Barrett URL : http://www.cs.nyu.edu/acsys/cvc3/ License : BSD Section : math It builds those binary packages: cvc3 - Automatic theorem prover for SMT problems cvc3-el - Emacs mode for CVC3 libcvc3-5 - Automatic theorem prover library for SMT problems libcvc3-5-java - Java bindings for CVC3 (bytecode library) libcvc3-5-jni - Java bindings for CVC3 (native library) libcvc3-dev - Automatic theorem prover library for SMT problems (development files) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/cvc3 Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/c/cvc3/cvc3_2.4.1-4.dsc Changes since the last upload: cvc3 (2.4.1-4) unstable; urgency=low * Transfer package repo to Git. * Fix syntax errors in debian/copyright. * Keep 50cvc3-el.el after remove. (Closes: #684351) * Use ln -sf when linking cvc3-el emacsen files. (Closes: #684026) * Remove build dep on gcj-native-helper. (Closes: #678183) -- Christopher L. Conway ccon...@cs.nyu.edu Sun, 12 Aug 2012 17:15:51 -0400 Regards, Chris ---End Message--- ---BeginMessage--- Package cvc3 version 2.4.1-4 is in unstable now. http://packages.qa.debian.org/cvc3---End Message---
