Package: wnpp
Severity: normal
I've not been doing the upstream author a favour by holding on to this package.
Releasing as discussed with Iain Lane and Philipp Marek .
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact li
On 03/01/11 12:23, Lucas Nussbaum wrote:
> How do you expect DDs to learn that you did the packaging work if you
> did not follow the procedure to find a sponsor?
I don't. It's an entirely unreasonable expectation. Hence my apology
for the knee-jerk reaction.
Ciao,
Sheldon.
--
To UNSUBSCRIB
On 03/01/11 10:04, Lucas Nussbaum wrote:
>> There is NO point encouraging someone else to waste more effort on this,
>> > when no Debian developer is interested.
> Did you look for a sponsor on debian-mentors@?
Nope. And looking at the feedback that the bug received (zero), maybe
it's pointless.
On 02/19/11 19:06, Lucas Nussbaum wrote:
> However, it is not recommended to keep ITP for a long time without acting on
> the package, as it might cause other prospective maintainers to refrain from
> packaging that software.
Actually, what causes prospective maintainers to refrain from packaging
Affects i686 as well.
Ciao,
Sheldon.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: nscd
Version: 2.3.6.ds1-13etch10
Severity: important
Applying security updates for DSA=1973-1 (gblic), I noticed nscd marked
as held. If I force an install, aptitude wants to install libc6-amd64
as well.
I've checked
/var/lib/apt/lists/security.debian.org_dists_etch_updates_main_bin
That explains a whole lot. aptitude unhold has never worked for me in
Etch (out of a guestimated 10 situations in which it would have been
useful). I recommend the work-around, although it has the unfortunate
side-effect of losing the "Automatically installed" status of the
package. Such is life
http://starjuice.net/e1000e/e1000e_1.1.2-1_i386.changes
http://starjuice.net/e1000e/e1000e_1.1.2-1.dsc
I appreciate that this package is pointless in Sid. However, it is my
hope that it be available for backports, because kernels prior to 2.6.31
lack support for recent Intel Pro/1000 PCI-Expres
Package: wnpp
Severity: wishlist
Owner: Sheldon Hearn
* Package name: e1000e
Version : 1.1.2
Upstream Author : Intel Wired Networking project
* URL : http://sourceforge.net/projects/e1000/
* License : GPL
Programming Lang: C
Description : Intel(R
On Sun, 2009-02-15 at 20:41 +0100, Peter Rabbitson wrote:
> http://debian.org/News/2009/20090214
>
> Now I can haz 1.1.17?
Uploaded, and finding its way through buildd. Expect migration into
squeeze/testing in due course.
Or, if you're impatient and would like to take a stab at backporting it
y
On Mon, 2009-02-09 at 21:13 +, Matthew Johnson wrote:
>
> > Unless the unfreeze is indeed around the corner (unlikely with
> debian :)
>
> Ask me that again on Saturday (-;
Ever the romantic. ;-)
Ciao,
Sheldon.
signature.asc
Description: This is a digitally signed message part
On Mon, 2009-02-09 at 12:40 +0100, Peter Rabbitson wrote:
> How come 3 months later it is still not in unstable if it is ready to
> go?
My mentor advised me against importing into unstable prior to the
release of Lenny, because if a security issue comes up before then,
it'll be a mission to deal w
Package: korganizer
Version: 4:4.1.96+svn911714-0r1
Severity: important
korganizer should depend on akonadi-server. Otherwise, resources
(phonebook etc) can't be imported into akonadi and used. This renders
at least the calendar unusable.
-- System Information:
Debian Release: 5.0
APT prefe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 07 January 2009 23:21:13 Florian Weimer wrote:
> I'm a bit in a hurry, so I can't give you a real-world example right
> now. But suppose we've got a vulnerability in a package foo, with
> the following versions:
>
> etch: 1.0-2
> si
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 07 January 2009 14:04:50 Florian Weimer wrote:
> Something is wrong because the -3 version is known to the tracker,
> but not listed in your output.
How would I verify that -3 is known to the tracker? It's not in
http://secure-testing.d
Package: debsecan
Version: 0.4.7
Severity: wishlist
When dealing with a suite like etch, debsecan looks for an exact version
match in a vulnerability's other_versions. This means that versions of a
package more recent than the version that fixed a vulnerability are
considered vulnerable.
For exa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Would this fix qualify for late entry into Lenny? Blocking SafeLabel
General significantly decreases dansguardian's usefulness. :-(
Ciao,
Sheldon.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
iD8DBQFJWHd1pGJX8XSgas0RAlgQAJ9xtIa3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday 18 November 2008 18:43:44 xavier renaut wrote:
> This release is important to me, I can use
> client certificates correctly :
> - New option "config_dir", important for client certificate
> authentication.
Regrettably, Lenny is not accept
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Could you extend your source package to build a php4-htscanner binary
package as well? I know it won't be useful in Sid and Lenny, but it'll
be very useful in Etch.
Thanks!
Sheldon.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Tim,
I ran into the same problem. I now do this, which fixes the problem:
Acquire::http::proxy "http://localhost:3142/";;
Acquire::http::proxy::packages.debian.org "DIRECT";
Thanks for your bug report, it helped me figure out what to do. My
g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 28 June 2008 22:55:53 Matthias Schmitz wrote:
> did you get this messages only if you run munin-run without any
> parameter? Or also in some other cases?
I'm sorry, I don't know. I don't think I tried other parameters.
Ciao,
Sheldon.
---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Saturday 12 July 2008 18:47:49 you wrote:
> Since this guide is written for Debian, I think I'll forge a native
> package, but I'll "grab" some code from Sheldon's package[2]
Awesome. Thank you so much for picking this up and running with it.
Cia
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I should have followed up on the bug to say that I did go ahead and
create a package, but couldn't find a mentor for it:
http://mentors.debian.net/debian/pool/main/l/libpkg-guide
I'm not heart-broken, just thought I'd include this information in th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Is there a workaround available this highly annoying bug?
Just got it out of the box on Etch.
Ciao,
Sheldon.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFIPp9ipGJX8XSgas0RAvEbAJ0R+TLXBxlcLdRBnieZl/UvQjLHEgCeIxP+
CCM4weoZPF
Package: k3b
Version: 1.0.4-6
Severity: normal
As soon as K3B reads the debian-40r2-i386-CD-1.iso image, it exits with:
k3b: symbol lookup error: /usr/lib/libk3b.so.3: undefined symbol: stat64
I'm not sure if this affects anyone else, so I'm reporting with a lame
Severity.
-- System Informatio
found 367976 169.07-2
found 459761 169.07-2
thanks
module-assistant still can't build 169.07-2, because the name of the
tarball installed is nvidia-kernel.tar.bz2 instead of
nvidia-kernel-source.tar.bz2.
I haven't marked this bug found in 169.07-2 because the changelog makes
it obvious that the u
Package: fsvs
Version: 1.1.11-1
Severity: minor
The fsvs binary links against libsvn_client-1, but doesn't use it.
This is the result of bitrot in a Makefile, fixed in upstream's
r1308.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Archit
Package: fsvs
Version: 1.1.11-1
Severity: normal
The way fsvs handles its softroot option for commits makes it impossible
to back up from an LVM snapshot without resorting to the use of chroot.
The chroot approach is fine for full backups of the root directory of a
running system, but that's not
Package: jackd
Version: 0.103.0-6
Followup-For: Bug #456368
Please remove the reference to the kernel-patch-realtime-preempt
package. I just spent an hour hunting it, so unless I'm a very special
kind of idiot, it's probably costing quite a lot of time. :-)
Thanks,
Sheldon.
-- System Informatio
On Saturday 05 January 2008 09:38:12 jamhed wrote:
> Could we agree that keeping every module and it config in one place,
> and enablig it to autoload by default is just not the "right thing" ?
You'll find a good example of this in the apache2 packages, which
have /etc/apache2/mods-available and
documentation and online help.
Gentlemen, thanks again for taking an interest and being willing to
invest your time.
Ciao,
Sheldon.
--
Sheldon Hearn
IT Director
Clue Technologies (PTY) Ltd
Web:http://www.clue.co.za/
Mail: [EMAIL PROTECTED]
Office: +27-21-913-8840
Mo
nged.
I remember now. It's because you don't provide src/Makefile, only
src/Makefile.in. So I left the autoconf run in the configure target.
Ciao,
Sheldon.
--
Sheldon Hearn
IT Director
Clue Technologies (PTY) Ltd
Web:http://www.clue.co.za/
Mail: [EMAIL PRO
m with the documentation that confuses the
crap out of new users. I suspect doxygen is introducing extraneous
whitespace into ignore pattern examples.
Philipp and I will work on it and I'll upload once that issue's
resolved.
Other than that, the new package for 1.1.11 works for m
On Sunday 09 December 2007 21:39:01 Sheldon Hearn wrote:
> > The debian/changelog can then also be reduced... Ah btw, what was
> > the technical reason to run autoconf?
>
> I was about to say "I don't remember, it was so long ago" and then
> took a long. I d
On Sunday 09 December 2007 18:41:27 Matthew Johnson wrote:
> Sheldon, if you change the description and check everything still
> works with 1.1.11, then send me a new source package I'll upload it.
It never rains, it pours. :-)
We now have two people offering to sponsor the package: Mario and
Ma
I should have updated this bug ages ago:
http://mentors.debian.net/debian/pool/main/f/fsvs/
Ciao,
Sheldon.
signature.asc
Description: This is a digitally signed message part.
On Monday 22 October 2007 14:32:15 you wrote:
> Huh? Who said this? We have 1.2.4 but we ship an extra patch
> which is not included in 1.2.4 to fix this so I don't see
> the point.
I wasn't aware of the additional patch you included.
Thanks,
Sheldon.
signature.asc
Description: This is a digita
5505
which states:
"The rails core team has released ruby on rails 1.2.5 to address a
potential XSS exploit with our json serialization. The CVE Identifier
for this problem is CVE-2007-3227"
In other words, I don't think rails-1.2.4 fully addressed the issue.
Ciao,
Sheldon.
--
Sh
The good news is, upstream seems to have taken disclosure complaints to
heart, and is now posting security advisories to the
rubyonrails-security Google Group:
The bad news is, it looks like CVE-2007-3227 is only fixed properly in
rails-1.2.5:
http://groups.google.com/group/rubyonrails-secur
I can confirm that this problem occurs with rubygems_0.9.0-5, but not
with rubygems_0.9.4-4.
Note that this looks like an upstream bug, because I encounter the same
problem if I install rubygems-0.9.0 by hand.
Ciao,
Sheldon.
signature.asc
Description: This is a digitally signed message part.
On Tuesday 16 October 2007 19:37:23 you wrote:
> As Manoj pointed out, the build and source symlinks in the
> linux-image package were removed at install time, but the
> inability to install linux-headers thereafter is a bit of
> a show-stopper. :-(
Actually, I see that it only happens if I use li
This causes another problem.
I've built a custom linux-2.6.18-5-686 package for our own repo
(to fix tx timeout hangs in the sky2 driver).
Once it's installed, I try to do a "module-assistant prepare" and get:
--
# module-assistant prepare
Getting source for kernel version: 2.6.18-5-686
apt
Please consider these patches for inclusion in the 2.6.18 kernel for
Etch.
The current Etch kernel occasionally drops all the sky2 NICs our
customer has off the network and the hosts require a reboot to resolve
the problem.
Given the maturity of the patch, I'm hoping its benefit:risk ratio wi
It's possible that no backporting is required for sid, because
rails-1.2.4 has been released:
http://weblog.rubyonrails.com/2007/10/5/rails-1-2-4-maintenance-release
So that would leave etch the only target, and I'm not even sure if
rails-1.1.6 had json support.
So that just leaves lenny, and
The new asterisk_1.4.11~dfsg-1 source package fails to backport in an
Etch chroot because of a broken Build-Depends.
The control file declares dependency on
libpri-dev (>= 1.4)
But it requires
libpri-dev (>= 1.4.1)
This is because 1.4.1 provides bristuffed/libpri.h, which is
I don't think this bug should block kdepim-3.5.7's inclusion in testing,
because it does not represent a regression from 3.5.5.
The original submitter claimed that this problem did not occur in
kmail-1.9.5 (kdepin-3.5.4), but upstream confirms that the bug was
present as early as kmail-1.9.4 (
Package: wnpp
Severity: wishlist
Owner: Sheldon Hearn <[EMAIL PROTECTED]>
* Package name: libpkg-guide
Version : 0.0.20070413
Upstream Author : Junichi Uekawa <[EMAIL PROTECTED]>
* URL : http://www.netfort.gr.jp/~dancer/column/libpkg-guide/
* License
On Thursday 17 May 2007 19:07, Sheldon Hearn wrote:
> So the binary-indep target in the rules file needs a chmod, as per
> the attached patch, which fixes this problem for me.
Oops, sorry.
Please use the attached patch instead.
Ciao,
Sheldon.
--
Sheldon Hearn
IT Director
Clue Technologie
because he isn't using
dpkg-source -x to unpack the source package and build from that;
rather, he's working from a package directory in which asterisk_fix is
executable. This is speculation.
Ciao,
Sheldon.
--
Sheldon Hearn
IT Director
Clue Technologies (PTY) Ltd
Web:
49 matches
Mail list logo
