Re: packaging pyreport
so -- if you are keen on pretty much developing a fork further and maintaining existing codebase... packaging -- there is a bulk of tutorials on packaging (e.g. apt-get install packaging-tutorial), and you can kick start your packaging simply by adopting debian/ of another simple python module of your choice. >Hi Yaroslav, >Thanks for your reply. >I had asked Ga�l some time ago (less than one year I think) what his plans >for pyreport were. He had replied that he did not have any time to develop >it anymore. >However, I think that i have some ideas to maintain pyreport and I'm >currently trying to add some features to repyreport, but this is not worth >commiting them for the moment. >Jean -- =--= Keep in touch www.onerussian.com Yaroslav Halchenko www.ohloh.net/accounts/yarikoptic -- 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/20120303183742.gu16...@onerussian.com
getting rid of python-central
Hello lists, I've been seeing what it would take to remove python-central from my system and it wasn't actually that much so I sent patches to the BTS for the remaining packages and fixed a few python-apps-team and python-modules-team packages in SVN. The list of packages that remain to be fixed is not that long: http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pycentral-deprecation;users=debian-python@lists.debian.org Would anyone object if I start working on updating packages in python-apps-team and python-modules-team SVN repositories that: - use python-central - and have the maintainer set to the respective team (apps: gmail-notify, modules: libapache2-mod-python, python-axiom, pyopengl) I would update the packages to use dh_python2 instead. I would also consider uploading to unstable if the other outstanding changes seem reasonable (assuming the package is already in unstable). What about updating these packages to use the dh sequencer in debian/rules? (again assuming this is not too disruptive) What about doing the same for the packages that have the respective team in the Uploaders field (apps: fusion-icon, hotssh, wapiti, andvare, autokey, modules: bugz, rope, pyexcelerator, louie, python-pytc, python-authkit, ropemacs, python-pysearch, sclapp, python-socksipy, python-xmltv, python-reportlab, python-irclib). I'd like to get some input on whether this is useful or considered meddling in someone else's packages. What about other kind of cleanup operations (e.g. while searching I found a couple of control files that grep-dctrl had issues with due to spaces being present on lines that should be blank, packages that seem to be in both repositories, etc)? Thanks, -- -- arthur - adej...@debian.org - http://people.debian.org/~adejong -- signature.asc Description: This is a digitally signed message part
Re: getting rid of python-central
Il 03/03/2012 23:14, Arthur de Jong ha scritto:
> I've been seeing what it would take to remove python-central from my
> system and it wasn't actually that much so I sent patches to the BTS for
> the remaining packages and fixed a few python-apps-team and
> python-modules-team packages in SVN.
You could want to prepare QA uploads for the following orphaned packages
too:
source | version | bug
+--+
pyneighborhood | 0.5.1| 616975
snappea| 3.0d3-21 | 617065
FTR, I used this UDD query to obtain the list:
WITH packages AS (
SELECT source
FROM orphaned_packages
WHERE type = 'O'
UNION SELECT source
FROM sources_uniq
WHERE maintainer_name LIKE '%Debian QA%'
AND release IN ('sid', 'experimental') )
SELECT DISTINCT s.source, s.version, b.id AS bug
FROM sources_uniq s
JOIN packages p ON p.source = s.source
JOIN bugs b ON b.source = s.source
JOIN bugs_usertags bu ON bu.id = b.id
WHERE s.release IN ('sid', 'experimental')
AND b.status NOT IN ('done')
AND bu.email = 'debian-python@lists.debian.org'
AND bu.tag = 'pycentral-deprecation';
--
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/4f52d0a3.7000...@debian.org
Re: getting rid of python-central
Arthur de Jong wrote: >Hello lists, > >I've been seeing what it would take to remove python-central from my >system and it wasn't actually that much so I sent patches to the BTS >for >the remaining packages and fixed a few python-apps-team and >python-modules-team packages in SVN. > >The list of packages that remain to be fixed is not that long: >http://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=pycentral-deprecation;users=debian-python@lists.debian.org > >Would anyone object if I start working on updating packages in >python-apps-team and python-modules-team SVN repositories that: >- use python-central >- and have the maintainer set to the respective team >(apps: gmail-notify, modules: libapache2-mod-python, python-axiom, >pyopengl) > >I would update the packages to use dh_python2 instead. I would also >consider uploading to unstable if the other outstanding changes seem >reasonable (assuming the package is already in unstable). I think this would not be controversial. >What about updating these packages to use the dh sequencer in >debian/rules? (again assuming this is not too disruptive. I would suggest pinging the uploaders to see how they feel about more invasive changes. >What about doing the same for the packages that have the respective >team >in the Uploaders field (apps: fusion-icon, hotssh, wapiti, andvare, >autokey, modules: bugz, rope, pyexcelerator, louie, python-pytc, >python-authkit, ropemacs, python-pysearch, sclapp, python-socksipy, >python-xmltv, python-reportlab, python-irclib). These you should ask the maintainers about. I think it's OK to put the changes in SVN, but not to upload to the archive. >I'd like to get some input on whether this is useful or considered >meddling in someone else's packages. > >What about other kind of cleanup operations (e.g. while searching I >found a couple of control files that grep-dctrl had issues with due to >spaces being present on lines that should be blank, packages that seem >to be in both repositories, etc)? It's no issue to fix things so the package is in the right repository. For other things it depends if the team is maintainer or uploader. Scott K -- 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/d76114a9-c8a1-410e-9b8d-2334360b4...@email.android.com
