Control: severity -1 wishlist
> You raised the severity of this bug to serious.
I think that was by mistake. Since this is a "metabug", I am now giving it a
`wishlist`.
signature.asc
Description: OpenPGP digital signature
> So your choice --- we can either reassign this bug back to fastboot or
> android-sdk-platforms-tools, or I can downgrade the severity of this
> bug for e2fsprogs down to wishlist[1]. Let me know how you want to
> handle this.
I would say downgrade it for the moment. We can deal with it after
I am going to upload the Oreo version of src:android-platform-libcore to
`unstable` on 9 October if no one objects.
The Oreo (8.x) of this package only builds `android-platform-libcore-headers`
and `libandroid-json-java` so the majority of the SDK don't really rely on this
source package any
> Uploaded; thanks! Please address the Lintian errors on the next upload,
> mind you...
Thanks for the upload. Already fixed the error now, don't know why Lintian
never told me about that...
signature.asc
Description: OpenPGP digital signature
> No, sorry, please provide a HTTP-accessible link to .dsc with all the
> sources, etc. Just like a regular sponsor request…
I understand now, sorry I haven't used that procedure for a long time...
Here it is:
https://mentors.debian.net/package/android-platform-external-boringssl
And the link
Hello Chris,
> Sorry, please provide a .dsc; I am very busy, alas...
Understood...
I have attached the .buildinfo, .dsc and .changes files, hopefully they are
sufficient?
Format: 3.0 (quilt)
Source: android-platform-external-boringssl
Binary: android-libboringssl, android-libboringssl-dev
Hello Chris,
> I will happily sponsor individual uploads if provided with a .dsc but I
> am not in a position to evaluate the DM (I assume?) status.
Then sponsor it is, thanks. I just gave you access to the repository, and
prepared the changelog. We use the standard git-buildpackage workflow.
>
Hello Chris,
I just polished [1] the changelog file and I'm about to upload the fix. Could
you grant me the upload rights to this package? Thank you.
Cheers,
Kai-Chung Yan
[1]:
> Anyway, I sponsored this upload targetting experimental.
Thank you for the sponsor. I am surprised it got cleared in the queue so
quickly.
There's a FTFBS on MIPS, I think I can handle it.
signature.asc
Description: OpenPGP digital signature
> Who are the DD in the team? Are there other contributors currently
> following the process to become a DD?
Mostly Hans (eighthave) is the DD involved a lot, and Markus (apo) occasionally
helps. I am currently going through the process of becoming a DD but it is
going very slowly.
> It would
Hello Raphael,
Sorry for being dormant on the matter. We had been in the process of updating
the whole SDK suite to Oreo but it is blocked by an upload of this package. The
latest update produces several new packages so I don't have the permission to
upload it, and the DDs in the team were too
Package: openjdk-10-jre-headless
Version: 10.0.2+13-1
Severity: grave
This package fails to install on the Docker image "debian:sid-slim". The
postinst fails to execute successfully. Below is the log:
```
seamlik@zenbook:~$ sudo docker run --rm -it debian:sid-slim bash
[sudo] password for
Control: reassign -1 gradle-debian-helper 1.6
I would say this is not the fault of Gradle itself, but it the tricks can be
provided by `gradle-debian-helper`. We shouldn't modify the behavior of the
build tools too much.
Let's keep the severity as is for now, as FTBFS is quite serious indeed.
Control: forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795
signature.asc
Description: OpenPGP digital signature
forwarded -1 https://issues.apache.org/jira/browse/FELIX-5795
signature.asc
Description: OpenPGP digital signature
I removed the javadoc package now and it builds find in Sid. Shall I upload it
right now?
(I still need the upload permission)
signature.asc
Description: OpenPGP digital signature
I adopted the patch from Fedora and it looks good. The package builds fine now
and 154 of its reverse-build-dependencies built successfully. 27 failed:
* activemq-activeio
* activemq
* apache-directory-server
* dnssecjava
* istack-commons
* jackson-datatype-joda
* javassist
* jayway-jsonpath
*
I just tried building it and Groovy was fine enough, but now Gradle
complains
Theoretically, ALL Gradle packages FTBFS since the current version is too old
to play with Java 9's fancy version number.
signature.asc
Description: OpenPGP digital signature
This is getting awkward... Maven Bundle Plugin does not only rely on old Maven
Dependency Tree, but also targets Maven 2.x [1]. What's worse, Maven Dependency
Tree 2.x also relies on Maven 2.x [2].
I tried building Maven Dependency Tree 2.2 against Maven 3.x and found that it
uses removed
I propose to bring back Maven Dependency Tree 2.x as a new package that
coexists with its latest version.
Even in the latest (3.5.0) version, Maven Bundle Plugin still uses those
deprecated APIs in Maven Dependency Tree 2.x. These deprecated APIs have been
removed from Maven Dependency Tree
(I am one maintainer of android-platform-tools-swt)
To be honest, both should be removed since Google has abandoned
android-platform-tools-swt. That's why it remains unbuildable as of today.
signature.asc
Description: OpenPGP digital signature
21 matches
Mail list logo
