Re: Updating pygccxml
El Dilluns, 12 de setembre de 2016, a les 14:54:50, Mattia Rizzolo va escriure: > On Mon, Sep 12, 2016 at 03:43:39PM +0200, Leopold Palomo-Avellaneda wrote: > > with uscan, I have: > > > > uscan --verbose --force-download --repack --compress xz > > > > it's something that I saw in debian science group and I like it > > umh... > > > The space gain is of > > > 281160 bytes, hardly something anybody can notice these days (and I > > > usually prefer to use upstream-provided tarballs). > > > > yes, but we have more than 10K source packages, so ... think that many > > times we repacked because there are Exclude files in the copyright file. > I'm not convinced that's an interesting place where to optimize. > Yes, repacking to remove huge unneded files or non-free files is a good > cause to repack. Repacking to save not even 300k, well… > > > Anyway, uploaded, enjoy! thanks -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Re: Updating pygccxml
On Mon, Sep 12, 2016 at 03:43:39PM +0200, Leopold Palomo-Avellaneda wrote: > with uscan, I have: > > uscan --verbose --force-download --repack --compress xz > > it's something that I saw in debian science group and I like it umh... > > The space gain is of > > 281160 bytes, hardly something anybody can notice these days (and I > > usually prefer to use upstream-provided tarballs). > > yes, but we have more than 10K source packages, so ... think that many times > we repacked because there are Exclude files in the copyright file. I'm not convinced that's an interesting place where to optimize. Yes, repacking to remove huge unneded files or non-free files is a good cause to repack. Repacking to save not even 300k, well… Anyway, uploaded, enjoy! -- 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
Re: Updating pygccxml
El Dilluns, 12 de setembre de 2016, a les 13:30:46, Mattia Rizzolo va escriure: > On Mon, Sep 12, 2016 at 03:16:14PM +0200, Leopold Palomo-Avellaneda wrote: > > > first of all, you haven't pushed pristine-tar data. > > > Given that you already imported the new source, now you'll have to > > > > > > manually call pristine-tar this way: > > > pristine-tar commit ../pygccxml_1.8.0.orig.tar.gz upstream/1.8.0 > > > > > > except that you also didn't push the upstream tag, so that command won't > > > work either (unless you have the tag locally, as I think you do). > > > > Yes, you are right. Sorry. It's done now. > > pygccxml_1.8.0.orig.tar.xz > > Though upstream doesn't distribute .xz, but only gz. Nonetheless the > content is the same. > Care to share what you did to get that, and why? with uscan, I have: uscan --verbose --force-download --repack --compress xz it's something that I saw in debian science group and I like it > The space gain is of > 281160 bytes, hardly something anybody can notice these days (and I > usually prefer to use upstream-provided tarballs). yes, but we have more than 10K source packages, so ... think that many times we repacked because there are Exclude files in the copyright file. > > Done, the only thing that I don't like is that we have an extra comma at > > the end of each field that has commas as separators. > > somebody calls that a feature :) :-D > > > Last, since yesterday we have a new debhelper compat level, I think it'd > > > be good to update packages when possible, so please read the changes > > > involved in debhelper(7), and bump the compat level to 10. > > > > I have done that but I have undo. I work mostly with stable and backports. > > I'm lintian complains that I needed to bumb debhelper. And I would like > > to maintain a backward compatibility. debhelper 10 doesn't offer nothing > > interesting for this package. At least IMHO. Please, don't make me change > > this, it's not needed. > > ok.. > I suppose that's just me being too pushy for very new stuff ^^ > debhelper 10 is most probably going to be in jessie-backports (that was > the original aim, but I've just been told there might be complications). Thanks Mattia, Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Re: Updating pygccxml
On Mon, Sep 12, 2016 at 03:16:14PM +0200, Leopold Palomo-Avellaneda wrote: > > first of all, you haven't pushed pristine-tar data. > > Given that you already imported the new source, now you'll have to > > manually call pristine-tar this way: > > pristine-tar commit ../pygccxml_1.8.0.orig.tar.gz upstream/1.8.0 > > except that you also didn't push the upstream tag, so that command won't > > work either (unless you have the tag locally, as I think you do). > > Yes, you are right. Sorry. It's done now. pygccxml_1.8.0.orig.tar.xz Though upstream doesn't distribute .xz, but only gz. Nonetheless the content is the same. Care to share what you did to get that, and why? The space gain is of 281160 bytes, hardly something anybody can notice these days (and I usually prefer to use upstream-provided tarballs). > Done, the only thing that I don't like is that we have an extra comma at the > end of each field that has commas as separators. somebody calls that a feature :) > > Last, since yesterday we have a new debhelper compat level, I think it'd > > be good to update packages when possible, so please read the changes > > involved in debhelper(7), and bump the compat level to 10. > > I have done that but I have undo. I work mostly with stable and backports. > I'm > lintian complains that I needed to bumb debhelper. And I would like to > maintain a backward compatibility. debhelper 10 doesn't offer nothing > interesting for this package. At least IMHO. Please, don't make me change > this, it's not needed. ok.. I suppose that's just me being too pushy for very new stuff ^^ debhelper 10 is most probably going to be in jessie-backports (that was the original aim, but I've just been told there might be complications). -- 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
Re: Updating pygccxml
El Dilluns, 12 de setembre de 2016, a les 11:39:05, Mattia Rizzolo va escriure: > On Mon, Sep 12, 2016 at 01:08:38PM +0200, Leopold Palomo-Avellaneda wrote: > > today I have found Markus mail, so, first of all sorry for the delay. > > nvm > > > I have done the changes and pushed to collab-maint. I have not done the > > tag, waiting to see if all is ok. > > > > So, please could you review and upload the package? > > So, I'll review and sponsor it for you! > > first of all, you haven't pushed pristine-tar data. > Given that you already imported the new source, now you'll have to > manually call pristine-tar this way: > pristine-tar commit ../pygccxml_1.8.0.orig.tar.gz upstream/1.8.0 > except that you also didn't push the upstream tag, so that command won't > work either (unless you have the tag locally, as I think you do). Yes, you are right. Sorry. It's done now. > Then, you added trailing newlines in d/control on lines 16 and 17. And > unzip is not properly sorted. please use wrap-and-sort to normalize > them (with the options '-ast' so it'll be like the other lines). Yes, I > already forsee there will be some other changes to other lines you > didn't touch, but that's fine. Done, the only thing that I don't like is that we have an extra comma at the end of each field that has commas as separators. > Last, since yesterday we have a new debhelper compat level, I think it'd > be good to update packages when possible, so please read the changes > involved in debhelper(7), and bump the compat level to 10. I have done that but I have undo. I work mostly with stable and backports. I'm lintian complains that I needed to bumb debhelper. And I would like to maintain a backward compatibility. debhelper 10 doesn't offer nothing interesting for this package. At least IMHO. Please, don't make me change this, it's not needed. > Once you solved this nitpicks I'll try to build and possibly upload :) > (haven't tried a build as my workflow requires pristine-tar being > up-to-date and working). Done!! Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Re: Updating pygccxml
On Mon, Sep 12, 2016 at 01:08:38PM +0200, Leopold Palomo-Avellaneda wrote: > today I have found Markus mail, so, first of all sorry for the delay. nvm > I have done the changes and pushed to collab-maint. I have not done the tag, > waiting to see if all is ok. > > So, please could you review and upload the package? So, I'll review and sponsor it for you! first of all, you haven't pushed pristine-tar data. Given that you already imported the new source, now you'll have to manually call pristine-tar this way: pristine-tar commit ../pygccxml_1.8.0.orig.tar.gz upstream/1.8.0 except that you also didn't push the upstream tag, so that command won't work either (unless you have the tag locally, as I think you do). Then, you added trailing newlines in d/control on lines 16 and 17. And unzip is not properly sorted. please use wrap-and-sort to normalize them (with the options '-ast' so it'll be like the other lines). Yes, I already forsee there will be some other changes to other lines you didn't touch, but that's fine. Last, since yesterday we have a new debhelper compat level, I think it'd be good to update packages when possible, so please read the changes involved in debhelper(7), and bump the compat level to 10. Once you solved this nitpicks I'll try to build and possibly upload :) (haven't tried a build as my workflow requires pristine-tar being up-to-date and working). -- 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
Re: Updating pygccxml
El Dimarts, 6 de setembre de 2016, a les 17:19:00, Markus Koschany va escriure: > On 06.09.2016 10:31, Mattia Rizzolo wrote: > > On Tue, Sep 06, 2016 at 09:26:44AM +0200, Leopold Palomo-Avellaneda wrote: > >> I have cloned the git repo and imported (locally) the new version. I have > >> not checked copyright. The only issues that I have found have been: > >> > >> - one collision with the .gitignore file > >> - needed to add python3-sphinx-rtd-theme and python-sphinx-rtd-theme. > >> > >> I have added that dependencies because I think that both are needed, but > >> maybe with just one it's sufficient. > >> > >> I'm DM (with collab-maint permissions) and maybe I could push my changes, > >> but I would prefer not do it because I'm not familiar with this package.> > > From what I remember that was a pretty simple package. I did those QA > > uploads because I was working on removing gccxml, I don't have a real > > interested in the package. > > I have done two QA uploads because pygccxml was RC buggy and threatened > to remove one of my team maintained packages. An update should be > straightforward. > > >> So, please, could you prepare a new version of pygccxml? I should be very > >> easy. > > > > Looks like Markus is taking care of pygccxml, so perhaps he could? :) > > Otherwise I don't think I will, but if you want to give it a try you > > could push to some repository of yours and I can review and if it is > > good upload ^^ > > I can sponsor a new version of pygccxml if you prepare the package and > push the changes either to Git (collab-maint) or to mentors.debian.net. > Just send me a ping via e-mail. > Hi Markus and Mattia, today I have found Markus mail, so, first of all sorry for the delay. I have done the changes and pushed to collab-maint. I have not done the tag, waiting to see if all is ok. So, please could you review and upload the package? Best regards, Leopold -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
Re: Updating pygccxml
On 06.09.2016 10:31, Mattia Rizzolo wrote: > On Tue, Sep 06, 2016 at 09:26:44AM +0200, Leopold Palomo-Avellaneda wrote: >> I have cloned the git repo and imported (locally) the new version. I have >> not >> checked copyright. The only issues that I have found have been: >> >> - one collision with the .gitignore file >> - needed to add python3-sphinx-rtd-theme and python-sphinx-rtd-theme. >> >> I have added that dependencies because I think that both are needed, but >> maybe >> with just one it's sufficient. >> >> I'm DM (with collab-maint permissions) and maybe I could push my changes, >> but >> I would prefer not do it because I'm not familiar with this package. > > From what I remember that was a pretty simple package. I did those QA > uploads because I was working on removing gccxml, I don't have a real > interested in the package. I have done two QA uploads because pygccxml was RC buggy and threatened to remove one of my team maintained packages. An update should be straightforward. >> So, please, could you prepare a new version of pygccxml? I should be very >> easy. > > Looks like Markus is taking care of pygccxml, so perhaps he could? :) > Otherwise I don't think I will, but if you want to give it a try you > could push to some repository of yours and I can review and if it is > good upload ^^ I can sponsor a new version of pygccxml if you prepare the package and push the changes either to Git (collab-maint) or to mentors.debian.net. Just send me a ping via e-mail. Regards, Markus signature.asc Description: OpenPGP digital signature
Re: Updating pygccxml
On Tue, Sep 06, 2016 at 09:26:44AM +0200, Leopold Palomo-Avellaneda wrote: > I have cloned the git repo and imported (locally) the new version. I have not > checked copyright. The only issues that I have found have been: > > - one collision with the .gitignore file > - needed to add python3-sphinx-rtd-theme and python-sphinx-rtd-theme. > > I have added that dependencies because I think that both are needed, but > maybe > with just one it's sufficient. > > I'm DM (with collab-maint permissions) and maybe I could push my changes, but > I would prefer not do it because I'm not familiar with this package. From what I remember that was a pretty simple package. I did those QA uploads because I was working on removing gccxml, I don't have a real interested in the package. > So, please, could you prepare a new version of pygccxml? I should be very > easy. Looks like Markus is taking care of pygccxml, so perhaps he could? :) Otherwise I don't think I will, but if you want to give it a try you could push to some repository of yours and I can review and if it is good 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
Updating pygccxml
Hi, I'm working to package (again) pyplusplus [1]. The current maintainer of pyplusplus told me that he needs the last version of pygccxml with the latest patches. You know, the last, last last of all. Current pygccxml version in Debian is 1.7.6. This weekend upstream releases 1.8.0, that is the version that I need. I have cloned the git repo and imported (locally) the new version. I have not checked copyright. The only issues that I have found have been: - one collision with the .gitignore file - needed to add python3-sphinx-rtd-theme and python-sphinx-rtd-theme. I have added that dependencies because I think that both are needed, but maybe with just one it's sufficient. I'm DM (with collab-maint permissions) and maybe I could push my changes, but I would prefer not do it because I'm not familiar with this package. So, please, could you prepare a new version of pygccxml? I should be very easy. Best regards, Leopold [1] https://bitbucket.org/ompl/pyplusplus -- -- Linux User 152692 GPG: 05F4A7A949A2D9AA Catalonia - A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing in e-mail? signature.asc Description: This is a digitally signed message part.
