The APK format is a ZIP file that always includes the files
AndroidManifest.xml and classes.dex. Then it also always
has a JAR signature (i.e. META-INF/). It does not have the
JAR magic number CAFEBABE in it.
___
Reproducible-builds mailing list
Repro
Ако не
виждате добре писмото или не работят
линковете, моля натиснете ТУК, за да го отворите в
Интернет.
ОФИС СТОЛОВЕ Виж всички в промоция ТУК
КОПИРНА ХАРТИЯ Виж всички в промоция ТУК
АРХИВИРАНЕ И СЪХРАНЕНИЕ
Виж всички в промоция ТУК
КАНЦЕЛАРСКИ МАТЕР
> Thanks for replying.
>Yes, the code using antlr is for generating parser.
>Actually we are using apache hive and apache storm, and antlr code I said
> is in hive(e.g. HiveParser.g) and clojure code is in storm(e.g. config.clj).
>Is this kind of problem solvable?
>
> Regards,
From
Здравейте,
Включете се към
лятното издание на тренинга Виртуоз в
продажбите и научете виртуозни техники
за успешни продажби.
Виртуоз в продажбите – част
първа
Пет стъпки за
продажба + две за виртуозни
търговци
Яснота, разбиране и
практика извън границите на
стандарта
В днешния търговски
Adrian Bunk wrote:
> How is this supposed to work for DSAs?
> Do you want to claim a security update is reproducible without checking,
> or do you want to delay DSAs until the packages have been reproduced
> for all architectures?
[…]
> Why should this be a per-package user-visible issue instead
On Mon, Jul 24, 2017 at 09:46:27PM +0100, Chris Lamb wrote:
>...
> Related to this is how we show/expose reproducibility to end users, if it
> all. Some discussion of sorts is happening on #863622 (src:apt).
>...
How is this supposed to work for DSAs?
Do you want to claim a security update is repr
>...
> Debian Policy
> =
>
> We are in the process of making reproducibility of packages something
> properly documented in policy. Writing patches for policy is not easy,
> so we welcome input from everyone to be able to better consider all the
> needed facets. See bug #844431 [16]
Hi Juliana,
> Just found out what was going wrong.
>
> XMLFile returns an array with the Difference object, while the
> previous TextFile class doesn't. So test_apk was looking for a
> unified_diff in the wrong place.
Neat — looking forward to your patch! In fact, can you commit it
directly? :)
Hi Adrian,
> What tool(s) in buster will allow users to download the .buildinfo files
> matching the packages they are using and what is the canonical location
> where such tools will download them from
Mirrors. As https://buildinfo.debian.net/ states, it is entirely proof-of-
concept a experim
On Sun, Jul 23, 2017 at 01:54:32PM +0200, Mattia Rizzolo wrote:
>...
> Buildinfo files
> ===
>
> We have been playing with .buildinfo files [9] for more than two years,
> and dpkg finally started producing them with version 1.18.11 (Nov 2016).
>
> Some weeks later dak started to store
Hi Mattia,
Actually I havent. Looks like minidom is vulnerable to both
[billion laughs] and [quadratic blowup].
Should we migrate to defusexml? What you think? (:
2017-07-21 14:22 GMT-03:00 Mattia Rizzolo :
> On Fri, Jul 21, 2017 at 10:48:07AM +0100, Chris Lamb wrote:
> > … And I've now also
Hey Chris,
Just found out what was going wrong.
XMLFile returns an array with the Difference object, while the
previous TextFile class doesn't. So test_apk was looking for a
unified_diff in the wrong place.
This is easily fixed, but I've got a new question. Since XMLFile
now returns an array, th
Hi all,
This week's blog post draft is available for review:
https://reproducible.alioth.debian.org/blog/drafts/117/
Feel free to commit fixes directly to drafts/117.mdwn in
https://anonscm.debian.org/git/reproducible/blog.git/
I'll wait at least 24 hours from the time of this email for any co
Control: tags -1 - pending
Hans-Christoph Steiner:
> [..]
>
> I'd like a way to force the file type in diffoscope. We are calling it
> from a build process, so we already know all files are going to be APKs.
> Also, I tried to get this added to libfile, but upstream is not willing
> to accept
Processing control commands:
> tags -1 - pending
Bug #868486 [diffoscope] diffoscope often fails to detect APKs
Removed tag(s) pending.
--
868486: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868486
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hey Juliana,
> Yes! I would like to work on fixing that. Also, I'll take a look at the
> other failed tests and get back at you. (:
Any news on this? We'd love to get the tests all passing again :)
Regards,
--
,''`.
: :' : Chris Lamb, Debian Project Leader
`. `'` la.
Hi William,
> these code were compiled into different bytecode every time. the
> randomness are from some ordering problem for variable definitions
> or instruction sequences when i using javap to disassemble the class.
First, is the code in question a parser generator? If so, those often
result
17 matches
Mail list logo