Removal of packages Beast and Rapicorn in 2014
james410 at cowgill.org.uk
Wed Oct 21 22:12:05 UTC 2015
On Wed, 2015-10-21 at 23:57 +0200, Tim Janik wrote:
> On 18.10.2015 23:20, James Cowgill wrote:
> > For rapicon, there was a lull in development (as you can see on the
> > github contributors page) early 2014, just before the package was
> > removed.
> > From this page it was failing to build on all arches:
> > https://buildd.debian.org/status/logs.php?pkg=rapicorn
> Hm, I've looked at the logs to see what issues might still be unfixed upstream.
> I don't find amd64 on the list, are the logs for that kept somewhere else?
This is one of the intracacies of package uploads. The logs on that
site are generated by the autobuilders, but if the uploader of a
package uploads the debs for a particular architecture, the package is
not autobuilt again and no logs are produced.
In this case the uploader 'somehow' managed to build the package on
amd64 and uploaded it themselves.
> > If you are willing to maintain the package yourself in Debian, then
> > please read this:
> > http://mentors.debian.net/intro-maintainers
> > If you're looking for sponsors, try posting in any relevant packaging
> > lists (possibly including this one) and/or file a sponsorship-requests
> > bug.
> I'll post again once the packages are polished enough for an upload
> to mentors.debian.net, thanks again.
Ok. You can upload to mentors first though so that other people can
look at the package when you post again.
If you want the package to be 'team maintained' then there are some
other guidelines as well which can be found here:
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: This is a digitally signed message part
More information about the pkg-multimedia-maintainers