On Oct 11, 2015, at 12:28 AM, Brian May wrote:
>What branches do I need to put the debian/README.source file in? There are
>six debian/* branches, don't think it is a good idea to try and maintain a
>consistent debian/README.source in all branches.
>
>Maybe debian/experimental would be sufficient?
On Monday, October 12, 2015 09:25:43 PM Rene Engelhard wrote:
> Hi,
>
> On Mon, Oct 12, 2015 at 10:24:02AM -0400, Scott Kitterman wrote:
> > Additionally, looking ahead to the next transition that makes python3.5
> > the
> > default python3, it would be good to look at the packages that build-dep
Hi,
On Mon, Oct 12, 2015 at 10:24:02AM -0400, Scott Kitterman wrote:
> Additionally, looking ahead to the next transition that makes python3.5 the
> default python3, it would be good to look at the packages that build-dep on
> python3-dev and see if it's reasonable to have them build-dep on pyth
Hi Scott (2015.10.10_07:43:29_+0200)
> http://git.debian.org/?p=python-modules/packages/ redirects to
> http://anonscm.debian.org/cgit/python-modules/packages which doesn't show a
> repository for django-ajax-selects, so it looks like it's actually missing.
We've been having some repository visi
On Monday, October 12, 2015 03:09:16 PM Barry Warsaw wrote:
> On Oct 12, 2015, at 11:57 AM, Piotr Ożarowski wrote:
> >transition is not over, our policy still mentions SVN only...
>
> Unless I'm missing it, not in python-policy.sgml (Debian Python Policy)
> though.
That's Python policy for all py
On Oct 12, 2015, at 11:57 AM, Piotr Ożarowski wrote:
>transition is not over, our policy still mentions SVN only...
Unless I'm missing it, not in python-policy.sgml (Debian Python Policy) though.
Cheers,
-Barry
On October 12, 2015 1:27:41 AM EDT, Brian May
wrote:
>As far as I know this actually did work despite the complaining about
>no
>parent commit... What does that mean?
>
>git-dpm import-new-upstream --ptc --rebase-patched
>../django-model-utils_2.3.1.orig.tar.gz
>There were no patches recorded,
On Oct 12, 2015, at 05:22 AM, Brian May wrote:
>git push --tags
>Total 0 (delta 0), reused 0 (delta 0)
>remote: Sending notification emails to:
>python-modules-comm...@lists.alioth.debian.org,
>python-django_...@packages.qa.debian.org
>remote: Sending notification emails to:
>python-modules-comm..
On Oct 12, 2015, at 05:27 AM, Brian May wrote:
>As far as I know this actually did work despite the complaining about no
>parent commit... What does that mean?
No idea, but I've seen it before. I don't think it has any negative effect.
>git-dpm import-new-upstream --ptc --rebase-patched
>../dja
On Monday, October 12, 2015 08:13:41 PM Daniel Stender wrote:
> I've got a push back error here:
>
> $ git push
> Counting objects: 22, done.
> Delta compression using up to 4 threads.
> Compressing objects: 100% (21/21), done.
> Writing objects: 100% (22/22), 2.72 KiB | 0 bytes/s, done.
> Total 2
On 08.10.2015 17:06, Stefano Rivera wrote:
> Hi Barry (2015.10.02_16:24:28_+0200)
>> 8-Oct - Assuming no objections or showstoppers, turn off write access to all
>> of DPMT svn.
>
> Done. And kicking off the migration now...
>
> SR
Thanks for the work, things likes automatically updated Vcs fiel
Modulo waiting for mips to catch up, the transition to add python3.5 as a
supported python3 version is done, with the following exceptions [1]:
apparmor: #799449 FTBFS: test suite segfaults on mips and mipsel
pygpgme: #797776 FTBFS: Ran 55 tests in 54.866s: FAILED (failures=2, errors=2)
woo: #8
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 2015-10-12 08:56, Brian May wrote:
> Hello,
>
> Why are packages missing from anonscm.debian.org which are on
> git.debian.org?
>
> e.g.
>
> https://anonscm.debian.org/cgit/python-modules/packages/django-model-u
tils.git
>
>
> https://anons
[Jan-Pascal van Best, 2015-10-10]
> Since the git transition seems to be done, how about adding me to the
transition is not over, our policy still mentions SVN only...
> debian python teams so I can create the repos on Alioth and push my work
> so far to them?
you're in, though. Welcome :)
(and
On Sun, 11 Oct 2015, Brian May wrote:
> Just noticed how it named the upstream branches.
>
> * [new branch] upstream-debian/experimental -> upstream-debian/experimental
> * [new branch] upstream-debian/jessie -> upstream-debian/jessie
> * [new branch] upstream-debian/sid -> upstream-debian/sid
>
Hi,
On Sat, 10 Oct 2015, Barry Warsaw wrote:
> >And I would suggest that we generalize the DEP-14 naming scheme as part of
> >our git packaging policy...
>
> I'm all for standardization, but I do like the shorter names for the common
> case where you only need the unstable version. Certainly if
On Sun, 11 Oct 2015, Brian May wrote:
> What branches do I need to put the debian/README.source file in? There are
> six debian/* branches, don't think it is a good idea to try and maintain a
> consistent debian/README.source in all branches.
>
> Maybe debian/experimental would be sufficient? Or p
17 matches
Mail list logo
