Re: [RFS] updated libva and intel-vaapi-driver bpos
On Tue, Nov 22, 2016 at 10:07:18PM +0100, Mattia Rizzolo wrote: > On Mon, Nov 21, 2016 at 10:36:13PM -0500, Nicholas D Steeves wrote: > > > > The libva version I've requested migrates to testing tomorrow, > > > > assuming no bugs are reported in the next however many of hours :-) > > > > > > yeah, I'll wait for that to happen before looking at these anyway :P > > > I want everything but backports-master chasing after me, that wouldn't > > > be nice (also because I saw how bad that could be...). > > > > Sounds good! > > And uploaded both :) > I've actually first uploaded libva this morning, and now, after 2 > dinstalls, the built packages reached my mirror and I could build > intel-vaapi-driver using them ;) Wow Mattia! Thank you for uploading these so quickly :-D Cheers, Nicholas ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Mon, Nov 21, 2016 at 10:36:13PM -0500, Nicholas D Steeves wrote: > > > The libva version I've requested migrates to testing tomorrow, > > > assuming no bugs are reported in the next however many of hours :-) > > > > yeah, I'll wait for that to happen before looking at these anyway :P > > I want everything but backports-master chasing after me, that wouldn't > > be nice (also because I saw how bad that could be...). > > Sounds good! And uploaded both :) I've actually first uploaded libva this morning, and now, after 2 dinstalls, the built packages reached my mirror and I could build intel-vaapi-driver using them ;) -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Tue, Nov 22, 2016 at 03:23:27AM +0100, Mattia Rizzolo wrote: > On Mon, Nov 21, 2016 at 07:31:10PM -0500, Nicholas D Steeves wrote: > > Proof that they build is here: > > https://mentors.debian.net/package/libva > > https://mentors.debian.net/package/intel-vaapi-driver > > bah, no need for mentors (for me at least); I'm very happy to just use > the git repository. > > > I'm not sure what version of libva mentors builds intel-vaapi-driver > > against, but it seems to have worked. > > ? > mentors.d.n doesn't build anything. What do you mean by that? Oh! I've been assuming that the delay between when a package is uploaded to mentors.d.n and the time it appears under "My Packages" was because mentors was building the package... Either way, I won't bother using mentors.d.n for future bpos of these packages. > > When I built them locally I > > built libva first, and copied the debs to my local repo. The clean > > jessie pbuilder I use to build these intel-vaapi-driver then pulls in > > whatever version it needs. > > Yeah, well, the build-dep is very clear on the need of 1.7.3 of libva :) > In this case I usually test build locally by using the local repo, but > then upload source only and the have the buildd figure what to do (they > will not try the build until the needed libva is available). Oh good, I wasn't sure about this :-) > > Do you think the mipsel delays from the last run can be used to > > predict $DELAY for an upload of intel-vaapi-driver to deferred/$DELAY? > > umh, not sure what you mean here? > Why would we need to do anything to wait for mipsel? My bad, it skipped my mind that intel-vaapi-driver only builds for amd64 and i386! > > The libva version I've requested migrates to testing tomorrow, > > assuming no bugs are reported in the next however many of hours :-) > > yeah, I'll wait for that to happen before looking at these anyway :P > I want everything but backports-master chasing after me, that wouldn't > be nice (also because I saw how bad that could be...). Sounds good! Thanks again, Nicholas signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Mon, Nov 21, 2016 at 07:31:10PM -0500, Nicholas D Steeves wrote: > I have pushed updates. ack! > Proof that they build is here: > https://mentors.debian.net/package/libva > https://mentors.debian.net/package/intel-vaapi-driver bah, no need for mentors (for me at least); I'm very happy to just use the git repository. > I'm not sure what version of libva mentors builds intel-vaapi-driver > against, but it seems to have worked. ? mentors.d.n doesn't build anything. What do you mean by that? > When I built them locally I > built libva first, and copied the debs to my local repo. The clean > jessie pbuilder I use to build these intel-vaapi-driver then pulls in > whatever version it needs. Yeah, well, the build-dep is very clear on the need of 1.7.3 of libva :) In this case I usually test build locally by using the local repo, but then upload source only and the have the buildd figure what to do (they will not try the build until the needed libva is available). > Do you think the mipsel delays from the last run can be used to > predict $DELAY for an upload of intel-vaapi-driver to deferred/$DELAY? umh, not sure what you mean here? Why would we need to do anything to wait for mipsel? > The libva version I've requested migrates to testing tomorrow, > assuming no bugs are reported in the next however many of hours :-) yeah, I'll wait for that to happen before looking at these anyway :P I want everything but backports-master chasing after me, that wouldn't be nice (also because I saw how bad that could be...). -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Tue, Sep 13, 2016 at 09:08:38PM +, Mattia Rizzolo wrote: > On Tue, Sep 13, 2016 at 05:03:23PM -0400, Nicholas D Steeves wrote: > > Does "Needs-Build" status mean > > that the package is still waiting for CPU time on an armel, armhf, and > > mipsel system somewhere on the buildd network? > > Yes, it's waiting for a spare buildd to pick up the builds. > I don't know how the backports upload are considered in the build > priority, but clearly not near the top¹.. > > > > ¹ e.g. I know that security builds are scheduled before anything else, > then stable, then unstable, then experimental; and that within a > single suite there are other things dictating priorities (like, new > packages are built after updated ones, even if the latter came after). > I just don't know where backports is in that list. > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > more about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `- Hi Mattia, Thank you for sponsoring these uploads last time, and sorry this thanks is arriving so late! I have pushed updates. Proof that they build is here: https://mentors.debian.net/package/libva https://mentors.debian.net/package/intel-vaapi-driver I'm not sure what version of libva mentors builds intel-vaapi-driver against, but it seems to have worked. When I built them locally I built libva first, and copied the debs to my local repo. The clean jessie pbuilder I use to build these intel-vaapi-driver then pulls in whatever version it needs. Do you think the mipsel delays from the last run can be used to predict $DELAY for an upload of intel-vaapi-driver to deferred/$DELAY? The libva version I've requested migrates to testing tomorrow, assuming no bugs are reported in the next however many of hours :-) Thank you again for your continued support. Sincerely, Nicholas signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
Hi, On 15/09/16 01:15, Nicholas D Steeves wrote: > On Tue, Sep 13, 2016 at 09:08:38PM +, Mattia Rizzolo wrote: >> On Tue, Sep 13, 2016 at 05:03:23PM -0400, Nicholas D Steeves wrote: >>> Does "Needs-Build" status mean >>> that the package is still waiting for CPU time on an armel, armhf, and >>> mipsel system somewhere on the buildd network? >> >> Yes, it's waiting for a spare buildd to pick up the builds. >> I don't know how the backports upload are considered in the build >> priority, but clearly not near the top¹.. >> >> >> >> ¹ e.g. I know that security builds are scheduled before anything else, >> then stable, then unstable, then experimental; and that within a >> single suite there are other things dictating priorities (like, new >> packages are built after updated ones, even if the latter came after). >> I just don't know where backports is in that list. >> >> -- >> regards, >> Mattia Rizzolo > > Thank you for the clarification! Hm, I wonder if there aren't very > many mipsel build hosts, or if it's just that they're very slow? If > the problem is that there aren't enough, I wonder if it would be > useful to write a wiki page linked to from "ways to contribute to > Debian" detailing the process of how to repurpose an old router as a > buildd host. ;-) At the moment there are more mipsel buildds than mips, but the mipsel buildds are also used for building mips64el so they can seem a bit slow at times as they have double the work to do. Extra hardware is always useful, but I'm not sure an old router would be anywhere near powerful enough to operate a buildd :) Thanks, James signature.asc Description: OpenPGP digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Tue, Sep 13, 2016 at 09:08:38PM +, Mattia Rizzolo wrote: > On Tue, Sep 13, 2016 at 05:03:23PM -0400, Nicholas D Steeves wrote: > > Does "Needs-Build" status mean > > that the package is still waiting for CPU time on an armel, armhf, and > > mipsel system somewhere on the buildd network? > > Yes, it's waiting for a spare buildd to pick up the builds. > I don't know how the backports upload are considered in the build > priority, but clearly not near the top¹.. > > > > ¹ e.g. I know that security builds are scheduled before anything else, > then stable, then unstable, then experimental; and that within a > single suite there are other things dictating priorities (like, new > packages are built after updated ones, even if the latter came after). > I just don't know where backports is in that list. > > -- > regards, > Mattia Rizzolo Thank you for the clarification! Hm, I wonder if there aren't very many mipsel build hosts, or if it's just that they're very slow? If the problem is that there aren't enough, I wonder if it would be useful to write a wiki page linked to from "ways to contribute to Debian" detailing the process of how to repurpose an old router as a buildd host. ;-) Cheers, Nicholas signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Tue, Sep 13, 2016 at 05:03:23PM -0400, Nicholas D Steeves wrote: > Does "Needs-Build" status mean > that the package is still waiting for CPU time on an armel, armhf, and > mipsel system somewhere on the buildd network? Yes, it's waiting for a spare buildd to pick up the builds. I don't know how the backports upload are considered in the build priority, but clearly not near the top¹.. ¹ e.g. I know that security builds are scheduled before anything else, then stable, then unstable, then experimental; and that within a single suite there are other things dictating priorities (like, new packages are built after updated ones, even if the latter came after). I just don't know where backports is in that list. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Mon, Sep 12, 2016 at 06:43:07PM +, Mattia Rizzolo wrote: > On Mon, Sep 12, 2016 at 06:41:25AM +, Mattia Rizzolo wrote: > > Given that I gather intel-vaapi-driver needs the newer libva and today > > I'm too lazy to copy .deb in the local repository I'll wait for libva to > > reach the mirror before doing intel-vaapi-driver. > > apparently amd64 is comparable to mipsel, as it's kinda lagging. > https://buildd.debian.org/status/package.php?p=libva=jessie-backports > > I'm going to just trust you that it build and upload. > > -- > regards, > Mattia Rizzolo > > GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. > more about me: https://mapreri.org : :' : > Launchpad user: https://launchpad.net/~mapreri `. `'` > Debian QA page: https://qa.debian.org/developer.php?login=mattia `- Hi Mattia, Thank you for the sponsored uploads! Does "Needs-Build" status mean that the package is still waiting for CPU time on an armel, armhf, and mipsel system somewhere on the buildd network? Cheers, Nicholas signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
Re: [RFS] updated libva and intel-vaapi-driver bpos
On Mon, Sep 12, 2016 at 06:41:25AM +, Mattia Rizzolo wrote: > Given that I gather intel-vaapi-driver needs the newer libva and today > I'm too lazy to copy .deb in the local repository I'll wait for libva to > reach the mirror before doing intel-vaapi-driver. apparently amd64 is comparable to mipsel, as it's kinda lagging. https://buildd.debian.org/status/package.php?p=libva=jessie-backports I'm going to just trust you that it build and upload. -- regards, Mattia Rizzolo GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`. more about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'` Debian QA page: https://qa.debian.org/developer.php?login=mattia `- signature.asc Description: PGP signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
[RFS] updated libva and intel-vaapi-driver bpos
Hi! I've updated the jessie-backports branches of libva and intel-vaapi-driver, and have lightly tested the resulting packages. Fast-forwarding seems a bit smoother, but that might be placebo effect ;-) Please upload and tag these updated bpos. Kind regards, Nicholas signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
