Re: Pushing a bunch of packages to jessie-backports

On 11/24/2015 10:28 AM, Piotr Ożarowski wrote: > [Sandro Tosi, 2015-11-24] >> cool, will do soon then! do you want me to push a branch to git? if >> so, how would you like it to be called: 'jessie', 'bpo8', else? > > I don't have strong opinion about branch names yet. I like standards, so > I'd

Re: Pushing a bunch of packages to jessie-backports

On Fri, Nov 27, 2015 at 8:02 PM, Thomas Goirand wrote: > That's one of the multiple breakage that the NEW queue brings. There's > unfortunately no way to fix that for this kind of complex uploads with > inter-dependencies and updates of existing packages. The only way, > unfortunately, is to have

Re: Pushing a bunch of packages to jessie-backports

On 11/27/2015 11:31 AM, Piotr Ożarowski wrote: >> Will do. FYI, I'm still waiting for the removal of >> python-repoze.{what,what-plugins,who-plugins}, which is blocking the >> migration of Keystone, and which therefore makes my efforts useless >> (there's no point of uploading OpenStack without

Re: Pushing a bunch of packages to jessie-backports

❦ 26 novembre 2015 21:33 +0100, Piotr Ożarowski  : >> No, that's not necessary as long as the orig tarball is already >> present in the archive in another suite (which would be true for >> backports, since the package is supposed to be derived from the >> current version in

Re: Pushing a bunch of packages to jessie-backports

On 11/26/2015 04:02 PM, Piotr Ożarowski wrote: > that's why I don't believe you built it in jessie I did. I'm running with sbuild on Jessie + Jessie backports, and of course, I'm also managing a local repository with the packages already rebuilt for jessie-backports, which will be part of the

Re: Pushing a bunch of packages to jessie-backports

> > python-sphinx is not backported and you didn't mention any patches > > I did backport python-sphinx too. It is present in these packages, and I > also mentioned it in this list. you did mention you will backport sphinx. Yes, I missed that and I'm sorry for that. I did check if it's

Re: Pushing a bunch of packages to jessie-backports

[Vincent Cheng, 2015-11-26] > >> solution: pass -sa to dpkg-source ("--force-orig-source" in sbuild or > >> "--debbuildopts -sa" in pbuilder) > > No, that's not necessary as long as the orig tarball is already > present in the archive in another suite (which would be true for > backports, since

Re: Pushing a bunch of packages to jessie-backports

[Vincent Cheng, 2015-11-26] > > that's why I don't believe you built it in jessie. python-sphinx is not > > backported > > and you didn't mention any patches > > > > solutions: > > 1) backport python-sphinx, or > > 2) use patch from Ubuntu: > >

Re: Pushing a bunch of packages to jessie-backports

❦ 25 novembre 2015 00:00 +0100, Piotr Ożarowski  : >> > PS I'm getting all the emails from backports even if I wasn't the one >> > who uploaded so this is official after all. >> >> This isn't new, and it's been discussed at large. Basically, we would >> all like the BTS to

Re: Pushing a bunch of packages to jessie-backports

> This is not the policy for backports. Amend the policy if you > disagree. It's not fair to kick Zigo because he didn't follow the rules > and consider oneself above them when he respects them. fix it yourself, I'm getting all the bugs and emails so there's nothing that suggest I should use

Re: Pushing a bunch of packages to jessie-backports

On 2015-11-26 09:32, Piotr Ożarowski wrote: > PS I didn't "kick" him, i think the kick in question is not your disapproval of the current affair, but referring to past action <560c3acd.9000...@debian.org>. fgmasdr IOhannes

Re: Pushing a bunch of packages to jessie-backports

[IOhannes m zmölnig (Debian/GNU), 2015-11-26] > i think the kick in question is not your disapproval of the current > affair, but referring to past action <560c3acd.9000...@debian.org>. then I'm glad I did that. There's a change already (we had a mail! a mail BEFORE an upload!). I'm still not

Re: Pushing a bunch of packages to jessie-backports

On Thu, 26 Nov 2015 at 10:32 Piotr Ożarowski wrote: > > This is not the policy for backports. Amend the policy if you > > disagree. It's not fair to kick Zigo because he didn't follow the rules > > and consider oneself above them when he respects them. > > fix it yourself, I'm

Re: Pushing a bunch of packages to jessie-backports

> Note that regarding bug reports, the backports website states: > > "Please report bugs that you found in the packages to the backports > mailinglist and *NOT* to the > Debian BTS!" so why do I get them? DAK sends emails to me too and it doesn't

Re: Pushing a bunch of packages to jessie-backports

On 11/26/2015 09:32 AM, Piotr Ożarowski wrote: > I hope he > will realize one package will FTBFS in jessie Instead of playing such a game, would you mind telling which package you're talking about? Or is it more fun that you just keep the issue for yourself, and then use it as a mockery, just to

Re: Pushing a bunch of packages to jessie-backports

On 11/25/2015 12:07 PM, Piotr Ożarowski wrote: >>> debdiff of what you want to upload + time for me to check it (a week, I >>> will respond most probably in 24h, though) >> >> I'll have to repeat myself then: there's no change but an entry in > > I will not repeat myself. I already wrote why I

Re: Pushing a bunch of packages to jessie-backports

> I've uploaded all what I prepared to this URL: > http://sid.gplhost.com/bpo/ THANK YOU! | $ dget http://sid.gplhost.com/bpo/routes_2.2-1~bpo8+1.dsc | dget: retrieving http://sid.gplhost.com/bpo/routes_2.2-1~bpo8+1.dsc | % Total% Received % Xferd Average Speed TimeTime Time

Re: Pushing a bunch of packages to jessie-backports

[Piotr Ożarowski, 2015-11-26] > that's the first mistake most backporters do, they forgot to include orig > tarball > (ftp masters would detect that and reject your package, additional work for > them) > > solution: pass -sa to dpkg-source ("--force-orig-source" in sbuild or > "--debbuildopts

Re: Pushing a bunch of packages to jessie-backports

Hi Piotr, On Thu, Nov 26, 2015 at 7:09 AM, Piotr Ożarowski wrote: > [Piotr Ożarowski, 2015-11-26] >> that's the first mistake most backporters do, they forgot to include orig >> tarball >> (ftp masters would detect that and reject your package, additional work for >> them) >>

Re: Pushing a bunch of packages to jessie-backports

Hi Piotr, On Thu, Nov 26, 2015 at 7:02 AM, Piotr Ożarowski wrote: >> I've uploaded all what I prepared to this URL: >> http://sid.gplhost.com/bpo/ > > THANK YOU! > [build log snipped] > that's why I don't believe you built it in jessie. python-sphinx is not > backported > and

Re: Pushing a bunch of packages to jessie-backports

> > debdiff of what you want to upload + time for me to check it (a week, I > > will respond most probably in 24h, though) > > I'll have to repeat myself then: there's no change but an entry in I will not repeat myself. I already wrote why I think you should do that. -- Piotr Ożarowski

Re: Pushing a bunch of packages to jessie-backports

[Thomas Goirand, 2015-11-24] > Which part of it? The one where you're asking for a mail per package, or debdiff of what you want to upload + time for me to check it (a week, I will respond most probably in 24h, though) > the one where you're telling that your packages are off limit? The 2 >

Re: Pushing a bunch of packages to jessie-backports

On 11/25/2015 12:00 AM, Piotr Ożarowski wrote: > [Thomas Goirand, 2015-11-24] >> Which part of it? The one where you're asking for a mail per package, or > > debdiff of what you want to upload + time for me to check it (a week, I > will respond most probably in 24h, though) I'll have to repeat

Re: Pushing a bunch of packages to jessie-backports

On 11/24/2015 07:29 PM, Piotr Ożarowski wrote: > [Thomas Goirand, 2015-11-24] >> If you don't say you'll maintain the packages in backports (which I >> warmly would welcome) and at the same time tell that you don't want me >> to upload to stable-backports, what other choice do I have but to ignore

Re: Pushing a bunch of packages to jessie-backports

On 11/24/2015 01:32 PM, Sandro Tosi wrote: > On Tue, Nov 24, 2015 at 9:28 AM, Piotr Ożarowski wrote: >> [Sandro Tosi, 2015-11-24] >>> cool, will do soon then! do you want me to push a branch to git? if >>> so, how would you like it to be called: 'jessie', 'bpo8', else? >> >> I

Re: Pushing a bunch of packages to jessie-backports

On 11/23/2015 09:54 PM, Piotr Ożarowski wrote: >>> so my packages are out of limits for you >> >> Could you care to explain what you mean here? > > it means I ask you (as that's all I can do) to not upload packages I > maintain. If you don't say you'll maintain the packages in backports (which I

Re: Pushing a bunch of packages to jessie-backports

[Thomas Goirand, 2015-11-24] > If you don't say you'll maintain the packages in backports (which I > warmly would welcome) and at the same time tell that you don't want me > to upload to stable-backports, what other choice do I have but to ignore > you? see my first email PS I'm getting all the

Re: Pushing a bunch of packages to jessie-backports

❦ 23 novembre 2015 09:20 +0100, Thomas Goirand  : > alabaster contextlib2 kazoo python-cachetools python-cffi python-cliff > python-crank python-ddt python-docker python-eventlet python-git > python-gitdb python-hypothesis python-ldap3 python-mock python-mysqldb > python-pathlib

Re: Pushing a bunch of packages to jessie-backports

[Sandro Tosi, 2015-11-24] > gaah, sorry for not following up with this: we used that package to do > some training at work, and for various reason we cant upload the same > exact package we built here; anyway it was just a mare rebuild of > 1.0.8+ds1-1 in jessie with the bpo tag appended to the

Re: Pushing a bunch of packages to jessie-backports

[Sandro Tosi, 2015-11-24] > cool, will do soon then! do you want me to push a branch to git? if > so, how would you like it to be called: 'jessie', 'bpo8', else? I don't have strong opinion about branch names yet. I like standards, so I'd prefer one described in DEP but they're not compatible

Re: Pushing a bunch of packages to jessie-backports

Hi Thomas, On Mon, Nov 23, 2015 at 06:17:33PM +0100, Thomas Goirand wrote: >> I will appreciate if you backport Sphinx because I was recently asked about >> the same [1]. > > Cool. > >> You will maybe also want to backport sphinx-rtd-theme ≥ 0.1.8-2, >> where the dh_sphinxdoc experience was

Re: Pushing a bunch of packages to jessie-backports

On Tue, Nov 24, 2015 at 9:28 AM, Piotr Ożarowski wrote: > [Sandro Tosi, 2015-11-24] >> cool, will do soon then! do you want me to push a branch to git? if >> so, how would you like it to be called: 'jessie', 'bpo8', else? > > I don't have strong opinion about branch names yet. I

Re: Pushing a bunch of packages to jessie-backports

Hello Thomas, On Monday, November 23, 2015 09:20:40 AM Thomas Goirand wrote: > If you maintain one of the above packages and want to manage the bpo > upload yourself, please let me know ASAP. Thanks for backporting python-urllib3 and requests. If you did not have to make changes on the

Re: Pushing a bunch of packages to jessie-backports

Hi Thomas, On Mon, Nov 23, 2015 at 09:20:40AM +0100, Thomas Goirand wrote: > Hi, > > FYI, I intend to push the below packages to jessie-backports, as part of > the upload of OpenStack Liberty: > > alabaster contextlib2 kazoo python-cachetools python-cffi python-cliff > python-crank python-ddt

Re: Pushing a bunch of packages to jessie-backports

[Thomas Goirand, 2015-11-23] > FYI, I intend to push the below packages to jessie-backports, as part of > the upload of OpenStack Liberty: > > alabaster contextlib2 kazoo python-cachetools python-cffi python-cliff > python-crank python-ddt python-docker python-eventlet python-git > python-gitdb

Pushing a bunch of packages to jessie-backports

Hi, FYI, I intend to push the below packages to jessie-backports, as part of the upload of OpenStack Liberty: alabaster contextlib2 kazoo python-cachetools python-cffi python-cliff python-crank python-ddt python-docker python-eventlet python-git python-gitdb python-hypothesis python-ldap3

Re: Pushing a bunch of packages to jessie-backports

On 11/23/2015 09:32 AM, Piotr Ożarowski wrote: > [Thomas Goirand, 2015-11-23] >> FYI, I intend to push the below packages to jessie-backports, as part of >> the upload of OpenStack Liberty: >> >> alabaster contextlib2 kazoo python-cachetools python-cffi python-cliff >> python-crank python-ddt

Re: Pushing a bunch of packages to jessie-backports

On 11/23/2015 01:44 PM, Dmitry Shachnev wrote: > I will appreciate if you backport Sphinx because I was recently asked about > the same [1]. Cool. > You will maybe also want to backport sphinx-rtd-theme ≥ 0.1.8-2, > where the dh_sphinxdoc experience was greatly improved. As much as I could see,

Re: Pushing a bunch of packages to jessie-backports

On 11/23/2015 12:34 PM, Daniele Tricoli wrote: > Hello Thomas, > > On Monday, November 23, 2015 09:20:40 AM Thomas Goirand wrote: >> If you maintain one of the above packages and want to manage the bpo >> upload yourself, please let me know ASAP. > > Thanks for backporting python-urllib3 and

Re: Pushing a bunch of packages to jessie-backports

[Thomas Goirand, 2015-11-23] > > please follow the right procedure at least with packages I maintain. > > Would you mind explicitly tell what you call "the right procedure"? As > much as I know, it's not mandatory to do anything but uploading to > backports. I've wrote this message is just out of