Simon McVittie writes:
> On 19/08/14 09:33, Matthias Klose wrote:
> [Nikolaus Rath wrote:]
>>> That's a bug in the test (race condition) rather than in the program.
>>> It's fixed upstream.
>>
>> [...] If you don't care
>> about the autopkg tests, and if you are not ready to fix these but rather
On 08/19/2014 01:33 AM, Matthias Klose wrote:
> Control: severity -1 important
Care to provide a justification? There is no bug in the program itself,
so I don't see how this is has a "major effect on the usability of a
package".
>> That's a bug in the test (race condition) rather than in the pro
lazr.smtptest wasn't packaged in Debian yet, so I thought it would be a good
candidate for experimenting with one of the git-based workflows, from scratch.
The ITP is bug #758670. I decided to use git-dpm; here are my impressions so
far.
For reference I started with https://wiki.debian.org/Packag
On Aug 19, 2014, at 11:14 AM, Barry Warsaw wrote:
>I usually don't care much about preserving local intra-upload vcs history
Ah, except for the case where I want to collaborate with someone on the new
version, e.g. to get a code review of some packaging change *before* it gets
uploaded. This is
> If it were well integrated with quilt, I think it would be fine to have
> source-full branches. I like this aspect of UDD, but I've also become
> comfortable working with our svn debian-only branches. It usually means
> unpacking the tarball, cd'ing into that directory and symlinking in debian/
On Aug 09, 2014, at 06:02 PM, Brian May wrote:
>At the moment, in subversion, we only store the debian/* directory. Is
>there any requirement/benefit in putting the full upstream source in git
>too?
If it were well integrated with quilt, I think it would be fine to have
source-full branches. I l
On Aug 06, 2014, at 04:08 PM, Piotr Ożarowski wrote:
>and I would love to try them all before we make a decision¹
Me too.
Should we relax the team preference for one vcs to rule them all, at least for
a period of experimentation and experience sharing? I still *really* want to
end up in a plac
On Aug 06, 2014, at 02:28 PM, Dimitri John Ledkov wrote:
>I am on the edge. I prefer dgit, as it's the only one the guarantees
>round-trip save with the archive even when someone NMUs things without using
>dgit.
From this description, it sounds like dgit is the closest equivalent to Ubuntu
Distri
On Mon, Aug 18, 2014 at 2:58 PM, Olly Betts wrote:
> On Wed, Jul 23, 2014 at 03:33:03PM +0200, Matthias Klose wrote:
>> Asking what will happen with packages depending on wxPython 2.8 and
>> which cannot be converted to 3.0.
>
> There aren't many incompatible changes between wxPython 2.8 and 3.0.
On Aug 18, 2014, at 09:22 PM, Tianon Gravi wrote:
>On 18 August 2014 18:11, Brian May wrote:
>> Unfortunately, debian/watch (AFAIK) doesn't include any details of any
>> changes that were made to the tar.gz file by the package developer.
>
>It's been my understanding that this is exactly one of t
On 19/08/14 09:33, Matthias Klose wrote:
[Nikolaus Rath wrote:]
>> That's a bug in the test (race condition) rather than in the program.
>> It's fixed upstream.
>
> [...] If you don't care
> about the autopkg tests, and if you are not ready to fix these but rather wait
> for the fixes from upstrea
* Matthias Klose , 2014-08-19, 10:33:
Control: severity -1 important
The maintainer decides on the bug severity. Please don't abuse the BTS.
That's a bug in the test (race condition) rather than in the program.
It's fixed upstream.
Nikolaus, I find this kind of attitude rather disturbing. I
On 19 Aug 2014 18:04, "Raphael Hertzog" wrote:
> Did you fill that new directory with an initial migration generated with
> ./manage.py makemigrations?
Yes, did that, but than I realized I needed to do testapp.
So I did just testapp by itself, but suspect both django apps need to be
done.
At wh
Control: severity -1 important
> That's a bug in the test (race condition) rather than in the program.
> It's fixed upstream.
Nikolaus, I find this kind of attitude rather disturbing. If you don't care
about the autopkg tests, and if you are not ready to fix these but rather wait
for the fixes f
Hi,
On Tue, 19 Aug 2014, Brian May wrote:
> > For example, I renamed migrations to south_migrations and created a
> > Django1.7 compliant migrations directory, however still get the same error.
Did you fill that new directory with an initial migration generated with
./manage.py makemigrations?
C
On 2014-08-19 01:52, Brian May wrote:
> However, the packaging is in git, and I am not sure how to insert the
> latest upstream version in this git repository.
`git-import-orig `
Cheers,
--
Michael Fladischer
Fladi.at
signature.asc
Description: OpenPGP digital signature
On 19.08.2014 01:52, Brian May wrote:
> Hello,
>
> I would like to package the latest upstream version of librabbitmq.
>
> However, the packaging is in git, and I am not sure how to insert the
> latest upstream version in this git repository.
>
> From debian/control:
>
> Homepage: https://githu
17 matches
Mail list logo
