[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: libbatik-java: Changed artifacts?



Dear Markus,

Thanks - that's useful to know.

ratt -dry_run batik_1.9-1_source.changes 2> >(wc -l)
554

Hmm, this could take a while... I guess it must be looking for
recursive reverse build dependencies?

Christopher



On 9 September 2017 at 19:31, Markus Koschany <apo@debian.org> wrote:
> Am 09.09.2017 um 20:22 schrieb Christopher Hoskin:
>>>
>>> One suggestion: If you update a library, it would be good to test
>>> whether any r-dep fails to build. There are not many for the case of
>>> batik.
>>>
>>
>> Is there an automated way to rebuild all of the reverse dependencies
>> of a package and see a summary of the outcome? libbatik-java has 25
>> immediate reverse dependencies which would take a while. It would be
>> good to leave it running in the background whilst I do something else.
>>
>> (Yes I could write a script, but as developers must be updating
>> libraries all the time, I suspect a well-polished one should already
>> exist.)
>>
>> Christopher
>
> There is for instance ratt [1] or debomatic [2].
>
> [1] https://tracker.debian.org/pkg/ratt
> [2] https://tracker.debian.org/pkg/debomatic
>
> We probably should collect all this information including your AWS
> mass-rebuild setup at wiki.debian.org. I'll give it a try soon.
>
> Markus
>


Reply to: