Greegins, all.
A bug that I had marked as closed has been reopened (or rather,
re-reported) [1]. It seems like when running the tests as specified in
debian/rules/override_dh_auto_test,the test suite tries to write to a
forbidden location. The issue is that upon our request, after having
faced the
Hello Andreas,
Sorry for missing the previous bug, and for the delay responding to this
one. It's my first time and clearly my pipeline for checking for bugs is
broken.
I've just replied to the bug as you suggested, and I will now contact
upstream to figure out a fix for the issue.
Thank you for
Hi Andreas. Thank you for your work.
Cheers!
Tomás
On 14/10/13 14:59, Andreas Tille wrote:
> Hi Tomás,
>
> On Thu, Oct 10, 2013 at 04:17:02PM +0100, Tomás Di Domenico wrote:
>> I've just pushed a new python-csb version to the repo, following an
>> upstream update.
Greetings, all!
I've just pushed a new python-csb version to the repo, following an
upstream update. It's my first upgrade of a package, so if someone
could check whether something's missing/wrong, I'd really appreciate it.
Cheers!
Tomás
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.deb
On 21/12/12 23:24, Andreas Tille wrote:
> 12. November to 21. December 2012: Tomás Di Domenico packaging python-csb
>
> Tomás also successfully finished his MoM period which was a bit more
> than one month but he did a really studious work checking several times
> also on
On 21/12/12 16:27, Andreas Tille wrote:
> Removing debian/gbp.conf helped.
> (BTW, could you push this change?)
Glad it worked. I've pushed the change to the repo.
Cheers!
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas
Hi Andreas!
On 21/12/12 15:19, Andreas Tille wrote:
> Due to your effort now at least the error message has changed:
>
> $ git-buildpackage
> ...
> gbp:info: Orig tarball 'python-csb_1.1.1+dfsg.orig.tar.gz' not found at
> '../tarballs/'
> tar: /tmp/pristine-tar.rpEhoamtcq/recreatetarball: Wrote
Hey Andreas.
On 20/12/12 12:10, Andreas Tille wrote:
> Perhaps you might wait / ask here on this list for better advise how to
> fix the repository (BTW, what do you get when you are doing a fresh
> checkout?) It might be a time saving option to recreate the archive in
> the end - no idea what mi
On 20/12/12 12:10, Andreas Tille wrote:
>dh_clean
> gbp:info: Orig tarball 'python-csb_1.1.1+dfsg.orig.tar.gz' not found at
> '../tarballs/'
> fatal: Path 'python-csb_1.1.1+dfsg.orig.tar.gz.delta' does not exist in
> 'refs/heads/pristine-tar'
> pristine-tar: git show
> refs/heads/pristine-ta
On 20/12/12 11:43, Andreas Tille wrote:
> Did you imported the new version by using
>
>git import-orig --pristine-tar
Darn, I forgot the "--pristine-tar" option. I've done it now, hopefully
it will fix the problem. Sorry about the hiccup.
Cheers!
--
To UNSUBSCRIBE, email to debian-med-re
Hey Andreas!
On 20/12/12 09:55, Andreas Tille wrote:
> I'd recommend updating the repository and once
> this is done ping me for final sponsored upload.
I've updated the repo. Please let me know if there's anything else I
should do.
Thanks!
--
To UNSUBSCRIBE, email to debian-med-requ...@lists
Greets, Andreas.
I've just been notified by the authors of a new upstream version of CSB.
Should I update the repo, or would you rather we wait for comments from
the Python list before?
Thanks!
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Tro
Greetings, all.
Well, my MoM period is a bit overdue, but I feel it's been worth it.
I've just committed a new version of the package, which is now
generating binaries for Python2, Python3 and docs, and performing DEP8
automated testing.
As I've been doing since shortly after the first commits, I
Greets, all.
I've used Andreas Tille's uscan script [1] to get a version of my
upstream package with some files removed. uscan generates a tarball with
the name "python-csb_1.1.0+dfsg.orig.tar.gz". I imported this into the
git repo with git-import-orig, and the correct tag was generated. When I
ru
Greets, Andreas. Sorry for going silent for so long.
So, I've finally been able to get a grasp on both DEP8 testing and the
Python3 version. I'm sure there are many new details to fix, but
everything seems well underway. The tests are executed correctly, and
the Python3 version installs and works
Hi Andreas!
On 01/11/12 22:04, Andreas Tille wrote:
> Hi Tomás,
>
> On Thu, Nov 01, 2012 at 03:32:28PM +0100, Tomás Di Domenico wrote:
>> Your last email made things much clearer.
>
> Great! As far as I can see the packaging heading quite in the direction
> of beco
Hi Andreas,
Your last email made things much clearer. This is what I've done since then:
1) Recreated the git repository, as I had missed the first step for
creating the Debian Med standard branches
2) Submitted the ITP bug report
3) Committed the current version of the package. It currently bu
would be appreciated.
Tomás.
On 30/10/12 23:53, Andreas Tille wrote:
> On Tue, Oct 30, 2012 at 06:48:33PM +0100, Tomás Di Domenico wrote:
>> Greetings. Here's my first progress report for the packaging of the CSB
>> Toolbox [1].
>
> :-)
>
>> 1) I've cre
Greetings. Here's my first progress report for the packaging of the CSB
Toolbox [1].
1) I've created a git repository for the package, which I named
"python-csb" according to the Debian Python Policy. I hope this is correct.
2) I used pbuilder to setup a chroot in my computer. Even after reading
19 matches
Mail list logo
