Re: python-babel
On 11.02.2020 16:55, Håvard Flaget Aasen wrote: On 11.02.2020 15:44, Thomas Goirand wrote: On 2/11/20 11:16 AM, Håvard Flaget Aasen wrote: I tried to build python-babel to sponsor the upload from what's in the Git in the DPMT, and it failed to build for me: # Generate the localedata folder data out of the xml files # downloaded in debian/repack scripts/import_cldr.py common Processing root.xml (Language = root; Territory = 001) root: Unsupported number system "adlm" in [... lots of lines like this one ...] I'm also getting these lines. I tested with the current 2.6.0 which also gives the same messages, the build log for 2.6.0 in Ubuntu prints the same messages. Now for the files actually being processed It is 719 in version 2.4.0 745 in version 2.6.0 and 764 in version 2.8.0 Not that it is supposed to be this way of course. Though I do believe the actual content in the package is correct. I can have a look at what we are actually importing in d/repack and see if anything has changed from version 2.4.0 to 2.8.0 root: Unsupported number system "vaii" in Traceback (most recent call last): File "scripts/import_cldr.py", line 968, in main() File "scripts/import_cldr.py", line 193, in main dump_json=bool(options.dump_json) File "scripts/import_cldr.py", line 207, in process_data _process_local_datas(sup, srcdir, destdir, force=force, dump_json=dump_json) File "scripts/import_cldr.py", line 435, in _process_local_datas write_datafile(data_filename, data, dump_json=dump_json) File "scripts/import_cldr.py", line 167, in write_datafile with open(path, 'wb') as outfile: IOError: [Errno 2] No such file or directory: '/<>/babel/locale-data/root.dat' I can't replicate this. I tried with cowbuilder/pbuilder and sbuild and the build completes fine on my systems. Håvard In such case, could you provide me with the source package, rather than just letting me try with Git? Maybe this is going to work then... Thats ok, how do you want it? the orig.tar.gz is just over 25 MB When i try I only use git, with these commands: $ gbp clone $ gbp buildpackage Håvard I'm sorry to have wasted your time yesterday. It is indeed my system that does something it shouldn't. I created a CI in salsa which duplicated your error. I believe the repository with the pristine-tar and upstream branch is correct I will fix the package today and readd it on IRC when it's done. I was able to reproduce the error on my own system with $ dpkg-buildpackage -us -ui Håvard
Re: python-babel
On 2/11/20 4:45 PM, Sandro Tosi wrote: >> In such case, could you provide me with the source package, rather than >> just letting me try with Git? Maybe this is going to work then... > > whatever turns out to be, please ensure the package is buildable from > the git repo. and matches what's going to be uploaded. We have already > enough packages with missing pristine-tar deltas, with orig tarballs > that dont match what's in the upstream+pristine-tar output, let's not > increase that number. > > Thanks, Sure, we're on the same page. The purpose is just to diagnose what's going on, and fix it the Git repo! Cheers, Thomas
Re: python-babel
On 11.02.2020 15:44, Thomas Goirand wrote: On 2/11/20 11:16 AM, Håvard Flaget Aasen wrote: I tried to build python-babel to sponsor the upload from what's in the Git in the DPMT, and it failed to build for me: # Generate the localedata folder data out of the xml files # downloaded in debian/repack scripts/import_cldr.py common Processing root.xml (Language = root; Territory = 001) root: Unsupported number system "adlm" in [... lots of lines like this one ...] I'm also getting these lines. I tested with the current 2.6.0 which also gives the same messages, the build log for 2.6.0 in Ubuntu prints the same messages. Now for the files actually being processed It is 719 in version 2.4.0 745 in version 2.6.0 and 764 in version 2.8.0 Not that it is supposed to be this way of course. Though I do believe the actual content in the package is correct. I can have a look at what we are actually importing in d/repack and see if anything has changed from version 2.4.0 to 2.8.0 root: Unsupported number system "vaii" in Traceback (most recent call last): File "scripts/import_cldr.py", line 968, in main() File "scripts/import_cldr.py", line 193, in main dump_json=bool(options.dump_json) File "scripts/import_cldr.py", line 207, in process_data _process_local_datas(sup, srcdir, destdir, force=force, dump_json=dump_json) File "scripts/import_cldr.py", line 435, in _process_local_datas write_datafile(data_filename, data, dump_json=dump_json) File "scripts/import_cldr.py", line 167, in write_datafile with open(path, 'wb') as outfile: IOError: [Errno 2] No such file or directory: '/<>/babel/locale-data/root.dat' I can't replicate this. I tried with cowbuilder/pbuilder and sbuild and the build completes fine on my systems. Håvard In such case, could you provide me with the source package, rather than just letting me try with Git? Maybe this is going to work then... Thats ok, how do you want it? the orig.tar.gz is just over 25 MB When i try I only use git, with these commands: $ gbp clone $ gbp buildpackage Håvard
Re: python-babel
> In such case, could you provide me with the source package, rather than > just letting me try with Git? Maybe this is going to work then... whatever turns out to be, please ensure the package is buildable from the git repo. and matches what's going to be uploaded. We have already enough packages with missing pristine-tar deltas, with orig tarballs that dont match what's in the upstream+pristine-tar output, let's not increase that number. Thanks, -- Sandro "morph" Tosi My website: http://sandrotosi.me/ Me at Debian: http://wiki.debian.org/SandroTosi Twitter: https://twitter.com/sandrotosi
Re: python-babel
On 2/11/20 11:16 AM, Håvard Flaget Aasen wrote: > >> >> I tried to build python-babel to sponsor the upload from what's in the >> Git in the DPMT, and it failed to build for me: >> >> # Generate the localedata folder data out of the xml files >> # downloaded in debian/repack >> scripts/import_cldr.py common >> Processing root.xml (Language = root; Territory = 001) >> >> root: Unsupported number system "adlm" in >> >> [... lots of lines like this one ...] > > I'm also getting these lines. I tested with the current 2.6.0 which also > gives the same messages, the build log for 2.6.0 in Ubuntu prints the > same messages. > > Now for the files actually being processed > It is 719 in version 2.4.0 > 745 in version 2.6.0 and > 764 in version 2.8.0 > > Not that it is supposed to be this way of course. Though I do believe > the actual content in the package is correct. > I can have a look at what we are actually importing in d/repack and see > if anything has changed from version 2.4.0 to 2.8.0 > > >> >> root: Unsupported number system "vaii" in > numberSystem="vaii"> >> >> Traceback (most recent call last): >> File "scripts/import_cldr.py", line 968, in >> main() >> File "scripts/import_cldr.py", line 193, in main >> dump_json=bool(options.dump_json) >> File "scripts/import_cldr.py", line 207, in process_data >> _process_local_datas(sup, srcdir, destdir, force=force, >> dump_json=dump_json) >> File "scripts/import_cldr.py", line 435, in _process_local_datas >> write_datafile(data_filename, data, dump_json=dump_json) >> File "scripts/import_cldr.py", line 167, in write_datafile >> with open(path, 'wb') as outfile: >> IOError: [Errno 2] No such file or directory: >> '/<>/babel/locale-data/root.dat' >> > I can't replicate this. I tried with cowbuilder/pbuilder and sbuild and > the build completes fine on my systems. > > Håvard In such case, could you provide me with the source package, rather than just letting me try with Git? Maybe this is going to work then... FYI, I'm just using plain sbuild with git-buildpackage. Cheers, Thomas Goirand (zigo)
Re: python-babel
I tried to build python-babel to sponsor the upload from what's in the Git in the DPMT, and it failed to build for me: # Generate the localedata folder data out of the xml files # downloaded in debian/repack scripts/import_cldr.py common Processing root.xml (Language = root; Territory = 001) root: Unsupported number system "adlm" in [... lots of lines like this one ...] I'm also getting these lines. I tested with the current 2.6.0 which also gives the same messages, the build log for 2.6.0 in Ubuntu prints the same messages. Now for the files actually being processed It is 719 in version 2.4.0 745 in version 2.6.0 and 764 in version 2.8.0 Not that it is supposed to be this way of course. Though I do believe the actual content in the package is correct. I can have a look at what we are actually importing in d/repack and see if anything has changed from version 2.4.0 to 2.8.0 I believe this is the upstream change. [1] If it indeed are files were supposed to have in the package i guess it need some more work, if not we could either leave it as is, or comment out the log line. Håvard [1] https://github.com/python-babel/babel/commit/77dc9d4024b78c2339f7cf3bff1a2e8be8e2d0f7#diff-106585574531c31ab48c6bf45e566e40
Re: python-babel
On 2020/02/11 12:16, Håvard Flaget Aasen wrote: > I can't replicate this. I tried with cowbuilder/pbuilder and sbuild and > the build completes fine on my systems. Ok, thanks. I'll check on a chroot on my system later too to try to see what's going on, but swamped at the moment so can't check right now. -Jonathan -- ⢀⣴⠾⠻⢶⣦⠀ Jonathan Carter (highvoltage) ⣾⠁⢠⠒⠀⣿⡁ Debian Developer - https://wiki.debian.org/highvoltage ⢿⡄⠘⠷⠚⠋ https://debian.org | https://jonathancarter.org ⠈⠳⣄ Be Bold. Be brave. Debian has got your back.
Re: python-babel
I tried to build python-babel to sponsor the upload from what's in the Git in the DPMT, and it failed to build for me: # Generate the localedata folder data out of the xml files # downloaded in debian/repack scripts/import_cldr.py common Processing root.xml (Language = root; Territory = 001) root: Unsupported number system "adlm" in [... lots of lines like this one ...] I'm also getting these lines. I tested with the current 2.6.0 which also gives the same messages, the build log for 2.6.0 in Ubuntu prints the same messages. Now for the files actually being processed It is 719 in version 2.4.0 745 in version 2.6.0 and 764 in version 2.8.0 Not that it is supposed to be this way of course. Though I do believe the actual content in the package is correct. I can have a look at what we are actually importing in d/repack and see if anything has changed from version 2.4.0 to 2.8.0 root: Unsupported number system "vaii" in Traceback (most recent call last): File "scripts/import_cldr.py", line 968, in main() File "scripts/import_cldr.py", line 193, in main dump_json=bool(options.dump_json) File "scripts/import_cldr.py", line 207, in process_data _process_local_datas(sup, srcdir, destdir, force=force, dump_json=dump_json) File "scripts/import_cldr.py", line 435, in _process_local_datas write_datafile(data_filename, data, dump_json=dump_json) File "scripts/import_cldr.py", line 167, in write_datafile with open(path, 'wb') as outfile: IOError: [Errno 2] No such file or directory: '/<>/babel/locale-data/root.dat' I can't replicate this. I tried with cowbuilder/pbuilder and sbuild and the build completes fine on my systems. Håvard
Re: python-babel
Hi Håvard On 2020/02/11 10:33, Thomas Goirand wrote: > I tried to build python-babel to sponsor the upload from what's in the > Git in the DPMT, and it failed to build for me: I'm removing it from the channel topic in the meantime, please re-add when the building is resolved, thanks for your contribution! -Jonathan -- ⢀⣴⠾⠻⢶⣦⠀ Jonathan Carter (highvoltage) ⣾⠁⢠⠒⠀⣿⡁ Debian Developer - https://wiki.debian.org/highvoltage ⢿⡄⠘⠷⠚⠋ https://debian.org | https://jonathancarter.org ⠈⠳⣄ Be Bold. Be brave. Debian has got your back.
Re: python-babel
On 1/10/20 8:50 PM, Håvard Flaget Aasen wrote: > Hello, > > The python-babel [1] package is currently broken, there isn't any bugs > reported yet, but after the transit to > python3.8 it failed the testsuite. New upstream version 2.7.0 and above > fixes these issues. > To update the package there is a 'repack' script which i believe is > broken, I at least did most of the work > manually. For that reason I haven't dared push it to the official repo > yet, if anyone have time, it will be nice > with a second opinion. It's still some work left, but it builds and > tests fine. The version I updated is currently here [2] > > The script might only require a minor fix but i noticed that the files > being downloaded already exist > within Debian. The package unicode-cldr-core [3]. > Is it possible to have this as a build-dependency, have a Files-Excluded > in d/copyright file and > drop the repack script altogether? If there still is a reason to change > the files in the first place. > If this makes it any easier/better of course. > > I'll appreciate all kinds of feedback. > > > Håvard > > > [1] https://tracker.debian.org/pkg/python-babel > [2] https://salsa.debian.org/haava-guest/python-babel > [3] https://tracker.debian.org/pkg/unicode-cldr-core > Hi, I tried to build python-babel to sponsor the upload from what's in the Git in the DPMT, and it failed to build for me: # Generate the localedata folder data out of the xml files # downloaded in debian/repack scripts/import_cldr.py common Processing root.xml (Language = root; Territory = 001) root: Unsupported number system "adlm" in [... lots of lines like this one ...] root: Unsupported number system "vaii" in Traceback (most recent call last): File "scripts/import_cldr.py", line 968, in main() File "scripts/import_cldr.py", line 193, in main dump_json=bool(options.dump_json) File "scripts/import_cldr.py", line 207, in process_data _process_local_datas(sup, srcdir, destdir, force=force, dump_json=dump_json) File "scripts/import_cldr.py", line 435, in _process_local_datas write_datafile(data_filename, data, dump_json=dump_json) File "scripts/import_cldr.py", line 167, in write_datafile with open(path, 'wb') as outfile: IOError: [Errno 2] No such file or directory: '/<>/babel/locale-data/root.dat' Can you fix this? Cheers, Thomas Goirand (zigo)
Re: Python-babel 1.3 available from Sid
On 10/08/2013 07:28 PM, Sebastian Ramacher wrote:
He wrote that on Wed, 28th of Aug 2013. That's a long time ago, and as I
couldn't wait for more, as some or my packages for OpenStack
(build-)depends on Babel 1.3.
For a package that had to go through NEW anyway that's really no excuse.
Pinging him and waiting a day or two for a reply doesn't hurt.
You are writing this as if I knew that he had something ready. That is
*not* the case. Sorry, I don't spend my life on IRC reading channel
topics. This is the first time ever that I see a case of an RFS in a
channel topic, and frankly, this really isn't the proper way IMO. Also,
I've checked the VCS (as advertized on the VCS fields of the package),
and saw nothing. How could I guess that the sources moved? (don't reply
IRC channel topic again please...)
To stay on the IRC topic, you may have (not) notice that I did say that
I couldn't write in the advertized VCS of babel. Nobody noticed... And
that was before the upload, IIRC. See what I mean? IRC is a very bad way
to keep track of things.
Besides this, pointing fingers *twice* at me on a public list serves no
purpose. Can't you just move on?
Why does python-babel-doc depend on
python3-pkg-resources and why is ${sphinxdoc:Depends} missing?
This is a bad copy/past which should be fixed. Not a huge deal to fix
though (the bulk of the work in the other parts of the package was the
most important bit of what was urgently needed).
That's no excuse to upload an unfinished package.
What are you trying to achieve with this sentence? Piss me off? Well
done, you've succeeded. Do something more productive, this attitude
doesn't help.
Mind you, I spent hours on this update, and did quite some work. It's
not a perfect work I admit, but it did what it should have: have
python-babel and python3-babel available for others to use, on time for
my purpose (which is to have OpenStack ready for its release). So I say
it again: the -doc missing ${sphinxdoc:Depends} is a tiny small issue
which is fixable easily.
You are BTW welcome to do the work if you wish (and I will be happy to
sponsor it if you ask properly in this list, or if you highlight my nick
on IRC, in which case I will notice, but please, don't just use the
channel's topic...).
Thomas
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/5255ab9c.9030...@debian.org
Re: Python-babel 1.3 available from Sid
❦ 8 octobre 2013 07:18 CEST, Andrey Rahmatullin w...@wrar.name : Though probably writing in this bug would have been more efficient than writing in the topic of the IRC channel? Yes, that's my only mistake. Though of course it's a fundamental problem with non-DD packages: I've made a package I find ready for uploading, I've built and deployed it locally, I've published the changes, I've used some method to notify potential sponsors and I don't have any motivation to spend any more effort to get it uploaded. Please, ask here. -- Make sure all variables are initialised before use. - The Elements of Programming Style (Kernighan Plauger) signature.asc Description: PGP signature
Re: Python-babel 1.3 available from Sid
On 2013-10-08 09:13:54, Vincent Bernat wrote: ❦ 8 octobre 2013 07:18 CEST, Andrey Rahmatullin w...@wrar.name : Though probably writing in this bug would have been more efficient than writing in the topic of the IRC channel? Yes, that's my only mistake. Though of course it's a fundamental problem with non-DD packages: I've made a package I find ready for uploading, I've built and deployed it locally, I've published the changes, I've used some method to notify potential sponsors and I don't have any motivation to spend any more effort to get it uploaded. Please, ask here. That's not what we tell our non-DD members. [1] says Sponsorship requests can be sent on the main discussion list or on #debian-python IRC channel (OFTC network). Regards [1] http://python-modules.alioth.debian.org/python-modules-policy.html -- Sebastian Ramacher signature.asc Description: Digital signature
Re: Python-babel 1.3 available from Sid
On 2013-10-08 12:52:35, Thomas Goirand wrote:
On 10/08/2013 03:34 AM, Sebastian Ramacher wrote:
Hi
On 2013-10-08 00:50:27, Thomas Goirand wrote:
Hi,
FYI, I have uploaded python-babel 1.3 in Sid. I couldn't wait for more,
so I did the work...
I haven't pushed to the SVN, because git-svn is producing some weird
errors. Andrey, could you push the changes?
Cheers,
Thomas
How about you clean up the mess you've created?
Andrey clearly stated in the bug that he's working on it
He wrote that on Wed, 28th of Aug 2013. That's a long time ago, and as I
couldn't wait for more, as some or my packages for OpenStack
(build-)depends on Babel 1.3.
For a package that had to go through NEW anyway that's really no excuse.
Pinging him and waiting a day or two for a reply doesn't hurt.
and changed the topic of #debian-python to look for a sponsor.
I'm sorry that I missed it, and that I got fooled by the wrong VCS
fields in the old package. Though probably writing in this bug would
have been more efficient than writing in the topic of the IRC channel?
That's what we tell non-DDs to do. [1] says:
Sponsorship requests can be sent on the main discussion list or on
#debian-python IRC channel (OFTC network).
[1] http://python-modules.alioth.debian.org/python-modules-policy.html
So you could have at
least asked Andrey what's the status of the packaging and helped him
upload the changes he has prepared in the repository.
I find this behavior very inappropriate.
You want to talk about behaviors and include the -python list to add
some fun? Let's do that if you think that helps (I think it's a huge
waste of time). wRAR/Andrey's behavior is bordeline with me on IRC all
the time, and it starts to be quite annoying. I'd like this type of
harassment to to stop right away: it's not fun to read at all.
If I wanted to have fun I'd laugh about it somewhere private and go on.
But this is an team issue as our DDs appearently don't know where
non-DDs are supposed to look for a sponsor. But what's even worse is
that instead of sorting out personal issues with a team member, his work
is thrown away.
Apart from that your changes in debian/copyright are wrong.
Would you care explain what is wrong there?
Copyright 2007-2013 Edgewall Software is wrong. AUTHORS and LICENSE
should give you a hint what's actually true.
debian/changelog is inaccurate (python-pybabel is still there).
Yes right, because I saw that there was still some reverse dependencies
and reverted my change, then forgot to also revert the changelog. I have
filled bugs against packages that still depends on pybabel and I think
it's best to wait until they are fixed.
There is no ${python:Recommends}.
What do you mean there's no ${python:Recommends}?
dpkg-gencontrol: warning: Recommends field of package python-babel: unknown
substitution variable ${python:Recommends}
...
dpkg-gencontrol: warning: Recommends field of package python3-babel: unknown
substitution variable ${python3:Recommends}
Why does python-babel-doc depend on
python3-pkg-resources and why is ${sphinxdoc:Depends} missing?
This is a bad copy/past which should be fixed. Not a huge deal to fix
though (the bulk of the work in the other parts of the package was the
most important bit of what was urgently needed).
That's no excuse to upload an unfinished package.
Regards
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Re: Python-babel 1.3 available from Sid
Hi
On 2013-10-08 00:50:27, Thomas Goirand wrote:
Hi,
FYI, I have uploaded python-babel 1.3 in Sid. I couldn't wait for more,
so I did the work...
I haven't pushed to the SVN, because git-svn is producing some weird
errors. Andrey, could you push the changes?
Cheers,
Thomas
How about you clean up the mess you've created?
Andrey clearly stated in the bug that he's working on it and changed the
topic of #debian-python to look for a sponsor. So you could have at
least asked Andrey what's the status of the packaging and helped him
upload the changes he has prepared in the repository.
I find this behavior very inappropriate.
Apart from that your changes in debian/copyright are wrong.
debian/changelog is inaccurate (python-pybabel is still there). There is
no ${python:Recommends}. Why does python-babel-doc depend on
python3-pkg-resources and why is ${sphinxdoc:Depends} missing?
Regards
--
Sebastian Ramacher
signature.asc
Description: Digital signature
Re: Python-babel 1.3 available from Sid
On 10/08/2013 03:34 AM, Sebastian Ramacher wrote:
Hi
On 2013-10-08 00:50:27, Thomas Goirand wrote:
Hi,
FYI, I have uploaded python-babel 1.3 in Sid. I couldn't wait for more,
so I did the work...
I haven't pushed to the SVN, because git-svn is producing some weird
errors. Andrey, could you push the changes?
Cheers,
Thomas
How about you clean up the mess you've created?
Andrey clearly stated in the bug that he's working on it
He wrote that on Wed, 28th of Aug 2013. That's a long time ago, and as I
couldn't wait for more, as some or my packages for OpenStack
(build-)depends on Babel 1.3.
and changed the topic of #debian-python to look for a sponsor.
I'm sorry that I missed it, and that I got fooled by the wrong VCS
fields in the old package. Though probably writing in this bug would
have been more efficient than writing in the topic of the IRC channel?
So you could have at
least asked Andrey what's the status of the packaging and helped him
upload the changes he has prepared in the repository.
I find this behavior very inappropriate.
You want to talk about behaviors and include the -python list to add
some fun? Let's do that if you think that helps (I think it's a huge
waste of time). wRAR/Andrey's behavior is bordeline with me on IRC all
the time, and it starts to be quite annoying. I'd like this type of
harassment to to stop right away: it's not fun to read at all.
Apart from that your changes in debian/copyright are wrong.
Would you care explain what is wrong there?
debian/changelog is inaccurate (python-pybabel is still there).
Yes right, because I saw that there was still some reverse dependencies
and reverted my change, then forgot to also revert the changelog. I have
filled bugs against packages that still depends on pybabel and I think
it's best to wait until they are fixed.
There is no ${python:Recommends}.
What do you mean there's no ${python:Recommends}?
Why does python-babel-doc depend on
python3-pkg-resources and why is ${sphinxdoc:Depends} missing?
This is a bad copy/past which should be fixed. Not a huge deal to fix
though (the bulk of the work in the other parts of the package was the
most important bit of what was urgently needed).
Let's fix the above problems, though I'd like to know what's the way to
fix the VCS. What's the new path for it?
Thomas
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52538f93.8050...@debian.org
Re: Python-babel 1.3 available from Sid
On Tue, Oct 08, 2013 at 12:52:35PM +0800, Thomas Goirand wrote: Though probably writing in this bug would have been more efficient than writing in the topic of the IRC channel? Yes, that's my only mistake. Though of course it's a fundamental problem with non-DD packages: I've made a package I find ready for uploading, I've built and deployed it locally, I've published the changes, I've used some method to notify potential sponsors and I don't have any motivation to spend any more effort to get it uploaded. Let's fix the above problems, though I'd like to know what's the way to fix the VCS. What's the new path for it? svn+ssh://svn.debian.org/svn/python-modules/packages/python-babel/trunk -- WBR, wRAR signature.asc Description: Digital signature
