around an
issue in libmspack0. It's probably been long enough that it's no longer
needed and can be removed.
Eric Sharkey
On Wed, Feb 5, 2020 at 1:39 AM Vagrant Cascadian <
vagr...@reproducible-builds.org> wrote:
> Package: cabextract
> Severity: normal
> Tags: patch
>
> Please consider switching away from automake-1.15 and using the regular
> automake package.
>
Looks good. I'll incorporate this into cabextract ov
1. There's no bug in it.
If you want to unblock libmspack and get that into buster, that's fine, and
1.9-1 is compatible with that. There's no need to do anything to
cabextract in buster due to the mspack bug.
Eric Sharkey
severity 915247 normal
merge 915247 914263
stop
On Sat, Dec 1, 2018 at 11:45 PM Davide Beatrici
wrote:
> Package: cabextract
> Version: 1.9-1
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> During the extraction of any .cab files which are extracted from a .e
On Thu, Nov 22, 2018 at 7:53 AM Eric Sharkey wrote:
> No, I think this is a duplicate of bug 912687.
>
Or, if you prefer, I can add a versioned dependency for cabextract on
libmspack >= 0.9.1-1 to ensure that cabextract will function properly.
Eric
On Wed, Nov 21, 2018 at 9:29 PM Jactry Zeng wrote:
> Hi Eric,
>
> 在 2018/11/22 上午3:59, Eric Sharkey 写道:
> > Perhaps your problem is in libmspack0 and not cabextract? On my test
> > system, I have 0.9.1-1 installed. Can you retest with an updated
> libmspack
> >
e82c373a8ba3d3946de3a38 jscript.dll
> Versions of packages cabextract depends on:
> ii libc6 2.27-8
> ii libmspack0 0.8-1
>
Perhaps your problem is in libmspack0 and not cabextract? On my test
system, I have 0.9.1-1 installed. Can you retest with an updated libmspack
package?
Eric Sharkey
On Mon, Nov 5, 2018 at 4:03 PM floris wrote:
> Package: cabextract
> Version: 1.6-1.1
> Severity: important
>
> Dear Maintainer,
>
> There is a new version of cabextract (1.9). This version has a fix which is
> necessary for winetricks.
>
Understood. I'll get
Thanks for taking care of that. Sorry I haven't been more attentive. I
mixed up this issue with another bug and had thought it was resolved, when
it wasn't.
Eric Sharkey
On Tue, Sep 27, 2016 at 3:32 PM, Helmut Grohne wrote:
> cabextract fails to cross build from source, because it uses the build
> architecture compiler. [] Please consider applying the attached
> patch.
Thanks,
I'll take a look.
Eric
On Sat, Feb 21, 2015 at 3:35 AM, Salvatore Bonaccorso wrote:
> Btw, please do not upload to security-master without prior
> coordination with the security-team, see
> https://www.debian.org/doc/manuals/developers-reference/pkgs.html#s5.6.4
I'm familiar with the developers' reference. Since this
On Thu, Feb 19, 2015 at 5:38 AM, Moritz Muehlenhoff wrote:
> Upstream fix is here:
> http://sourceforge.net/p/libmspack/code/217
>
> Since unstable has a more recent version than testing, could you make
> a targeted jessie upload with this patch?
I've written a new patch from scratch to fix cabex
I'm looking at upstream's patch now. It's not going to apply cleanly
to 1.4 and there's some stuff in there that looks a little off to me.
I'll follow up with Stuart.
Eric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact li
On Sat, Dec 13, 2014 at 9:44 AM, Sebastian Ramacher
wrote:
> This issue also affects libmspack. I noticed this while clamav was
> scanning Jakub's mail for malware and it was stuck in an infinite loop.
I'm planning not to fix this bug directly. I'll be uploading a new
build in a few days which f
On Thu, Dec 11, 2014 at 6:47 PM, Jakub Wilk wrote:
> Package: cabextract
> Version: 1.4-4+b1
> Severity: minor
> Usertags: afl
>
> The attached file makes cabextract hang forever (or at least for two
> minutes, after which I lost my patience :-P).
>
> This bug was found using American fuzzy lop:
>
' => sub {
! my $date = ParseDate($_[0]);
! return substr($date, 0 , 4) . '-' . substr($date, 4 , 2) .
'-' . substr($date, 6 , 2) .
!' ' . substr($date, 8 , 8);
! },
},
'subs' => {
'find_next' => sub { $warn_present ||= 1; $next_time = 'now' }
Eric Sharkey
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On Wed, Apr 4, 2012 at 9:07 AM, Lucas Nussbaum wrote:
> build-arch doesn't depend on configure-stamp.
Ah, thanks. Understood.
Eric
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
atest sid and did an apt-get source cabextract and
dpkg-buildpackage and it built just fine.
I can't imagine why the makefile would be missing. Is this
reproducible on your end?
Eric Sharkey
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
severity 643068 serious
stop
Thanks, I'll look into this shortly. I was aware of the issue when it
was a lintian warning. I didn't realize that this was going to be
considered a fatal condition so soon.
Eric Sharkey
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debia
#x27;ll take a look and see what I can do here.
Eric Sharkey
shar...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Subject: lcdproc: New upstream version 0.5.4 available
Package: lcdproc
Version: 0.5.2-3.1
Severity: wishlist
lcdproc 0.5.4 has been released upstream. It should be packaged for Debian.
Eric Sharkey
-- System Information:
Debian Release: 6.0
APT prefers unstable
APT policy: (500
Subject: egoboo: version 2.7.7 is too slow to be playable
Package: egoboo
Version: 1:2.7.7-1
Justification: renders package unusable
Severity: grave
Tags: upstream
The 2.7.7 version of egoboo runs so slowly that it cannot be played.
This bug has also been reported in other distributions:
Ubuntu
I'm aware of these issues and will be uploading a new cabextract
package shortly.
I'd just like to note that the potential for security vulnerabilities
here seems very small to me.
Eric Sharkey
shar...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.
2010/5/13 Ákos Ruszkai :
> Package: cabextract
> Version: 1.2-4
> Severity: minor
> Tags: squeeze l10n
>
> The localised translation of the package description in hungarian is childish
> and ridiculous.
> "Microsoft" and "Windows" in the description is referred as "M$", "Micro$oft"
> and "W$".
>
On Wed, Nov 4, 2009 at 8:17 AM, Sandro Tosi wrote:
>> I don't respond within a specified time take over. The way you've
>> done this is just rude.
>
> Oh dear, I would give a hug and a kiss on the head you'd be here
>
> Now, when you'd like to stop your blablabla and actually take care of
> y
On Tue, Nov 3, 2009 at 5:41 PM, Sandro Tosi wrote:
> Package: wnpp
> Severity: normal
>
> The current maintainer of cabextract, Eric Sharkey ,
> is apparently not active anymore. Therefore, I orphan this package now.
Isn't it polite to at least send me an email message
On Tue, Nov 3, 2009 at 4:41 PM, Sandro Tosi wrote:
> Package: wnpp
> Severity: normal
>
> The current maintainer of macutils, Eric Sharkey ,
> is apparently not active anymore. Therefore, I orphan this package now.
And yet here I am...
Eric Sharkey
shar...@debian.org
--
and there have been no new releases.
This bug is completely inappropriate.
Eric Sharkey
shar...@debian.org
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Upstream has released lirc 0.8.5 which includes support for kernel
2.6.29. All references to semaphore.h have been removed as far as I
can see. Moving to 0.8.5 should fix this bug and make this package
compatible with the default kernel in unstable.
Eric Sharkey
--
To UNSUBSCRIBE, email to
On Sat, Jun 13, 2009 at 2:30 AM, Brice Goglin wrote:
> Does this still happen with latest intel driver in unstable or
> experimental?
I haven't tried in quite some time. After failing to get the intel
driver to work, I installed an nvidia based card and started using
that. It's been my intention
On Thu, 2008-11-27 at 10:06 +0100, Adeodato Simó wrote:
> Because you should not have python2.3 installed anymore (note that etch
> didn't ship with python2.3 already
Why? I don't understand this position. Debian has no simple automated
mechanism to remove older packages during an upgrade, so pr
le.glGetConvolutionFilter )
^
SyntaxError: invalid syntax
How is this not an RC bug?
Eric Sharkey
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I upgraded to version 2:2.4.2-1 today, and the problem is not yet
resolved.
I cannot get the driver to run at 1080p/i at all. It tries to run at
1920x540 instead, and the display can't handle that. No amount of
manual modeline settings in the config file seem to make any difference.
I can't seem
> I just uploaded 2.4.1 to experimental. Let me know if you have better
> luck with that version; if it's still broken, we'll have to report it
> upstream.
I'm not getting a lockup with this version, but I don't have a usable
display either. It's insisting on picking a display resolution
which i
> I just uploaded 2.4.1 to experimental. Let me know if you have better
> luck with that version; if it's still broken, we'll have to report it
> upstream.
Thanks, I'll try it shortly.
> For lenny, we'll make X choose the vesa driver for the new intel
> chipsets, as that's more likely to work th
> By the way does the version in sid work? (I tried to backport the
> necessary patches for non-HDMI output from 2.4, but may have missed some
> and have no G4x hardware to test.)
I've tried downgrading back to the version in sid, but I'm no longer
able to get it to work at all with sid's driver.
> probably needs this commit:
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?h=xf86-video-intel-2.4-branch&id=01bbbd8c6c73229b5cb0c88e8eb2ac9b49a5dad8
After applying that patch manually, rebuilding and reinstalling the
package, and restarting the X server, I saw no change in be
> probably needs this commit:
> http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?h=xf86-video-intel-2.4-branch&id=01bbbd8c6c73229b5cb0c88e8eb2ac9b49a5dad8
Ok. I can merge that patch in and build a new package to test.
> By the way does the version in sid work? (I tried to backpo
(0xb010) indicate ring
buffer not flushed
(WW) intel(0): Existing errors found in hardware state.
I'm running in 32-bit mode (both kernel and userland).
Switching to the vesa driver allows X to work, but, of course,
performance is lacking.
Eric Sharkey
-- Package-specific info:
Conten
user.
It's not something I can solve in the cabextract package, since you
really want this to be defined whether cabextract is installed or not.
A bug report was filed agains kdelibs-data to get this fixed there,
but it doesn't seem to have been closed yet. See bug #374939.
Eric Sharkey
> A new upstream release is available since 2006-09-20:
>
> http://www.kyz.uklinux.net/downloads/cabextract-1.2.tar.gz
Thanks. I hadn't noticed that.
Eric
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Luca Bruno writes:
Runnnig `foomatic-db-engine -O` in gdb says that the bug is at line
1840:
Running it under valgrind is more telling. It's a buffer overflow.
I get this first:
==8614== Source and destination overlap in strcpy(0xBEEED388, 0xBEEED388)
==8614==at 0x401E83B: strcpy (mac_
> * Eric Sharkey <[EMAIL PROTECTED]>, the prospective maintainer,
>hasn't replied to my last ping; according to db.d.o, he was last
>seen in May.
Sorry for the delay. Real life getting the better of me.
Diskless has turned out to be a little too much for me to hand
> > When nut-cgi.postrm is called with the purge option, it deletes the
> > nut user from /etc/passwd. This can be a serious problem if you're
> > not removing nut itself, and just removing the cgi interface to nut.
> >
> > Only the nut package should remove the nut user on deinstallation.
>
> It
Package: nut-cgi
Version: 2.0.1-3
Severity: normal
When nut-cgi.postrm is called with the purge option, it deletes the
nut user from /etc/passwd. This can be a serious problem if you're
not removing nut itself, and just removing the cgi interface to nut.
Only the nut package should remove the nu
Package: xfig
Version: 1:3.2.5-alpha5-3
Severity: normal
I was looking at the xfig source and noticed this:
w_util.c:
static void
convert_gridstr(Widget widget, float mult)
{
double value, numer, denom, diff;
char*sval, fraction[20];
double fracts[] =
Did you tag the right bug? Maybye you meant 302352 and not 30235?
Eric Sharkey
> Processing commands for [EMAIL PROTECTED]:
>
> > tag 30235 +pending
> Bug#30235: macunpack fails on compression method "d"
> There were no tags set.
> Bug#26611: macutils: macun
Package: xbase-clients
Version: 4.3.0.dfsg.1-10
Severity: normal
When xclock is started without the -norender option, on a system with
xinerama enabled, the clock is completely blank when not on monitor 0.
I'm using the Matrox driver, and a dual head AGP G400 and a
PCI Millenium II.
Eric
-- Sy
48 matches
Mail list logo
