Package: apktool
Version: 2.1.1+dfsg-2
Severity: serious
Justification: Policy 3.5
I just installed apktool, and when I run it, it fails like so:
$ apktool
Exception in thread "main" java.lang.UnsupportedClassVersionError:
org/jf/baksmali/baksmali : Unsupported major.minor version 52.0
at
Oops, my mistake, I accidentally sent the first message to the bug's email
instead of to control, let me try again.
On Tue, Mar 22, 2016 at 7:55 PM, Simon Ruggier wrote:
> Hi Antonio, as a fellow Debian user and mediatomb user, I backported the
> current version of the mediatomb p
Hi Antonio, as a fellow Debian user and mediatomb user, I backported the
current version of the mediatomb package from unstable to Jessie and tried
it on a system I'd recently upgraded to Jessie. It seemed to work fine for
me without any problems, so I've changed the severity of this bug to
'import
severity 803173 important
Yesterday, I built mediatomb/unstable for Jessie and tested it on my
system, which I had just upgraded from Wheezy. It started up successfully,
and seems to work as well as the Wheezy version did. It seems safe to
assume that the original reporter assigned a severity of g
No, version 1.1.0 installs fine on my system after the previous
version is removed, but when I tried to upgrade to it from 1.0.0,
that problem occured, which to me seems like a bug in the 1.1.0
packaging.
On Thu, Dec 22, 2011 at 3:24 AM, Soeren Sonnenburg wrote:
> You had shogun 1.0.0 installed.
Package: shogun-python-modular
Version: 1.1.0-1
Severity: grave
Justification: renders package unusable
The issue is illustrated in the following command output:
$ sudo aptitude safe-upgrade
Resolving dependencies...
The following packages will be upgraded:
shogun-python-modular
1 packages upgr
package: iceweasel
version: 5.0-2
justification: policy 4.9
severity: serious
tags: experimental
after building the iceweasel-5.0 source package and running the clean target,
the following files are left modified:
modules/libpref/test/unit/data/savepref.js
toolkit/components/places/tests/unit/defa
Have you tried starting firefox 3.5 using a new profile? I'm using the
iceweasel 3.5.4-1 right now on an x86_64 Debian testing system, and it works
fine for me. Of course, it's still a bug even if it's profile related, but
it wouldn't be as severe of a bug.
On 6/29/08, Jon Dowland <[EMAIL PROTECTED]> wrote:
> Putting the screenshots in the packages would mean you would need to
> install the package to see it in the package browser, and the use-case
> is more "I fancy playing a game, let's see what is available..."
I think this is a more general pr
That's perfectly understandable - I took interest in openglad because
I played the commercial version of it a decade ago. Since the free
version is a port of the original source code, I didn't want to see it
go to waste, but it looks like upstream has lost interest as well, so
the game's future is
I switched to an amd64 system last month in the process of replacing a
failed computer, but because of school, I haven't had enough time to
fix this bug. Oddly enough, I tried running openglad on my system
unpatched, and it didn't segfault, but everything the game draws had
artifacts that looked l
Would you be able to get a backtrace for this crash? I can't reproduce
it on my current setup.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On 10/9/07, Cyril Brulebois <[EMAIL PROTECTED]> wrote:
> Exactly because they are handled in the clean target, from which you
> propose to remove them. I might have troubles understanding your logic,
> if any.
You remove them in the clean target, and copy them back in a later
target after the sour
13 matches
Mail list logo
