On 21/04/2008, Ben Finney wrote:
> I'd appreciate any feedback from those more experienced with Debian
> packaging in general and Python packaging in particular.
I won't be able to comment much on the python part since you're using
-central, that I don't know.
Anyway, some quick comments:
- debh
On 18/05/2008, Monty Taylor wrote:
> 1. What are the real differences between these two?
> 2. Why, as a packager, would I choose one over the other?
A bit of stats:
# source-wise
$ for i in central support; do grep-dctrl -S -F Build-Depends python-$i
-sPackage /var/lib/apt/lists/*Sources | wc -l
Carlos <[EMAIL PROTECTED]> (08/07/2008):
> > "tiziano-guest" (btw, why *-guest?).
>
> AFAIK '-guest' is appended to every not-DD login.
Correct.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Hi folks,
I'm wondering whether there's a preferred place where to drop the
test(s) directory. I don't really know whether to choose
/usr/share/python-support/$package/test(s)
or
/usr/share/$package/test(s).
Since it isn't really needed for the module to correctly work, I'd be
tempted to
Cyril Brulebois <[EMAIL PROTECTED]> (14/07/2008):
> Since it isn't really needed for the module to correctly work, I'd be
> tempted to keep it out of python-support's paths, and to keep it under
> /usr/share/$package instead, but what do you think? Also, should it be
Kumar Appaiah <[EMAIL PROTECTED]> (18/09/2008):
> Now, this shouldn't really happen, since g++ is supposed to be present
> during the build, right? Also, note that the g++ package is being
> installed on arm and ia64, but not on mips and powerpc.
At least on ia64 (didn't check the others), looks l
Kel Modderman <[EMAIL PROTECTED]> (22/09/2008):
> > BTW, Since the bug in the previous revision practically renders
> > pyosd unusable, in order to have the chance to update this package
> > on Lenny would be OK to change the severity from 'normal' to
> > 'important' and/or the urgency to 'high'?
Mauro Lizaur <[EMAIL PROTECTED]> (22/09/2008):
> BTW, if you sponsor this package, the only thing left is to contact
> RMs explaining the situation, right?
Mostly, yes.
> [0] http://lusers.com.ar/packages/python-osd_0.2.14-4.dsc
Hmm, many remarks:
- debian/rules modifications aren't documented
Tristan Seligmann (20/12/2008):
> My personal preference ordering would probably be:
>
> hg, bzr, svn, git
git, FD, *
devotee to the rescue.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Ondrej Certik (05/02/2009):
> Ok. But we are wasting people's time. I just got another email from a
> Ubuntu user that he will rather consider compiling it for Ubuntu's PPA
> himself, because he cannot use debian experimental. Of course.
>
> So he needs to invest his time in the package, I need t
Ben Finney (06/02/2009):
> I'm unhappy about it too, but I don't understand it. Where can I find
> an explanation for the necessity of freezing ‘unstable’ when preparing
> to release ‘testing’?
For more than verbose explanations, see -devel@ a few weeks ago,
starting at <200812160703.00258.russ..
Hello.
There's no f* way in hell I'm gonna keep using SVN. (That's not a troll,
a flame, whatever. Just a statement.)
That's why I'm planning to move python-{networkx,pygraphviz} out of
DPMT's svn and move them to collab-maint's set of git repositories.
Now, question: should I keep DPMT in Uploa
Piotr Ożarowski (26/02/2009):
> > Now, question: should I keep DPMT in Uploaders, or drop it?
>
> please remove it, one exception will lead to other requests and I just
> love grep -r :-P
OK, did so.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Steve Langasek (02/03/2009):
> My rebuttal is that if git is technical superior to bazaar because
> bazaar has a mechanism to create repositories with only partial
> history, then bazaar is technically superior to git because git has
> rebasing as a first-class feature.
Oh my HEAD, it hurts.
Mra
Piotr Ożarowski (02/03/2009):
> [Ben Finney, 2009-03-02]
> > Why does this not happen automatically when the package is upgraded
> > from a version that uses python-central?
>
> how can dh_pysupport know that x versions ago this package was using
> python-central?
I suggest you check “6.6 Detail
Piotr Ożarowski (03/03/2009):
> [Cyril Brulebois, 2009-03-03]
> > Piotr Ożarowski (02/03/2009):
> > > [Ben Finney, 2009-03-02]
> > > > Why does this not happen automatically when the package is upgraded
> > > > from a version that uses python-central?
&
ebian/changelog
+++ docutils-writer-manpage-0.1~svn.r5663/debian/changelog
@@ -1,3 +1,10 @@
+docutils-writer-manpage (0.1~svn.r5663-3.1) unstable; urgency=low
+
+ * Non-maintainer upload.
+ * Ben's homework.
+
+ -- Cyril Brulebois Tue, 14 Apr 2009 04:09:10 +0200
+
docutils-writer-manpage
Cyril Brulebois (14/04/2009):
> I'm attaching a source debdiff […]
Oops, reading it upon receiving my answer makes me realise I didn't
meant to delete get-orig-source from .PHONY, sorry for that.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Ben Finney (14/04/2009):
> > Put them into /usr/lib/python*/site-packages, as documented in its
> > manpage?
>
> What, though, is ‘python*’ here? Remember, this is specifically for a
> module that (at present) has no build system upstream; the code is
> “installed” by manually copying files.
Giv
Bernd Zeimetz (28/08/2009):
> long time, actually there is even a plan (at least in my head) to
> make it possible to have modules in git or svn while still being
> able to checkout all of them in a useful way, but that means writing
> new code, and I didn't have the time to do so yet.
You meant
Alessandro Dentella (03/09/2009):
> Hi,
Hello,
> I'm trying to produce the python-sqlkit package. I'm both the upsteam
> author and the mantainer. I have /debian folder in original package. I
> recently read is not recommended but I found easier to manage to have it
> in the same mercuri
Dmitrijs Ledkovs (09/12/2009):
> Where is this git repository hosted? Or where can I get the current
> version of the policy as seen on the debian.org website?
$ debcheckout debian-policy
declared git repository at git://git.debian.org/git/dbnpolicy/policy.git
git clone git://git.debian.org/git/d
Piotr Ożarowski (06/01/2010):
> > 5. lintian complains about my not using my full name in the
> > package. Is that necessary? Is it bad if I use only my first
> > name?
>
> which lintian tag is it?
How do I grep?
$ noglob git grep -e ^Tag.*full -- checks/fields.desc
checks/fields.desc:Tag: mai
Ben Finney (15/01/2010):
> Now, this is a “pedantic”-level tag, but it does seem valid: the
> SOURCES.txt file is in fact modified from the original upstream
> source.
Just rm it in clean?
> Can I prevent this from happening, perhaps by an option to the
> Setuptools procedure? If not, can I reco
Scott Kitterman (17/12/2009):
> I believe that we are getting close to uploading Python 2.6 to
> Unstable and dropping Python 2.4 as a supported Python version. If
> we finish preparations in the next week, are there any ongoing
> transitions a python2.6/python- defaults upload would entangle tha
Hi,
Yaroslav Halchenko managed[1] to piss me off so badly that I'm not
sure I want to have anything to do with python-{networkx,pygraphviz}
anymore. It would be nice to see some python-savvy folks take care of
it from now on.
1. See #565319 for reference.
Mraw,
KiBi.
signature.asc
Description
Hi.
Sandro Tosi (30/01/2010):
> If you're decision is taken, I'd like to take the package back into
> DPMT repo and take care of them with the team.
Sure.
> If you still want to be in Uploaders it would be nice (but I'll
> understand if you don't),
No, thanks;
> and if you prefer to maintain
Sandro Tosi (17/02/2010):
> No, don't tell me it's because of the first round of binNMUs: either
> someone's going to fix them or they will be FTBFS with 2.6 as
> default, and better explicit than implicit (how many people look at
> those binNMUs except us?).
While 2.5 is the default, one can use
Jakub Wilk (17/02/2010):
> * Failures, which should be fixable by give-backs:
>
> jppy amd64 armel i386 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc
> twisted-runneralpha amd64 armel i386 kfreebsd-amd64 kfreebsd-i386
> mips mipsel powerpc
I think I've given twisted-runner back sever
Jonathan Wiltshire (28/02/2010):
> I think we need to do both before we end up running out of time. I
> propose that we upgrade/file bugs as serious so that they get
> maintainer attention where possible, and allow (let's say) 7 days to
> react.
What about providing with patches instead of only p
Jaromír Mikeš (07/04/2010):
> Or maybe spam filter? Is it allowed to sent attachments to this
> list?
Not if you exceed the (IIRC list-specific) size limit.
Mraw,
KiBi.
signature.asc
Description: Digital signature
Hi Lino,
Lino Mastrodomenico (20/04/2010):
> Given how much work is required to change the default Python, does
> it make sense to just skip Python 2.6 and use 2.7 as the default
> Python version in Squeeze?
Python 2.6 transition is already going on.
> The glaring downside of this is that 2.7 h
Hi.
Rick Thomas (21/04/2010):
> I don't know how this can happen, but it definitely did happen.
> Enjoy!
The list of Arch: all packages merged into the Packages list for a
given architecture depends (!) on the build status of the related
Arch: any packages.
I can think of the following referenc
anatoly techtonik (18/05/2010):
> Please translate to simple English.
This was simple English, even French guys understood it…
Mraw,
KiBi.
signature.asc
Description: Digital signature
Brian May (2014-08-21):
> Can somebody please tell me why python-openssl and python3-openssl isn't
> available in sid?
[…]
> It appears that the packages produced have changed to architecture
> dependant packages, seriously wondering if maybe this got DAK confused.
>
>
> (this problem is prevent
Paul Tagliamonte (2015-04-16):
> Background
> ==
>
> Python 2 is scheduled to be EOL'd upstream officially and for good in 2020.
> We're in 2015 now (wow, that went quickly), and keeping our release cadence up
> (3 years a pop) puts Stretch up in 2018, and Buster in 2021.
Wheezy was firs
36 matches
Mail list logo
