Le 01/08/2012 20:01, Bart Martens a écrit :
> On Wed, Aug 01, 2012 at 07:48:01PM +0200, Tomasz Buchert wrote:
>> Le 01/08/2012 18:48, Bart Martens a écrit :
>>> On Wed, Aug 01, 2012 at 11:24:20AM +0200, Tomasz Buchert wrote:
Hello mentors,
I am working on one bug of mine
(http://bugs
On Wed, Aug 01, 2012 at 07:48:01PM +0200, Tomasz Buchert wrote:
> Le 01/08/2012 18:48, Bart Martens a écrit :
> > On Wed, Aug 01, 2012 at 11:24:20AM +0200, Tomasz Buchert wrote:
> >> Hello mentors,
> >> I am working on one bug of mine
> >> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664457) a
Le 01/08/2012 18:48, Bart Martens a écrit :
> On Wed, Aug 01, 2012 at 11:24:20AM +0200, Tomasz Buchert wrote:
>> Hello mentors,
>> I am working on one bug of mine
>> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664457) and I've
>> noticed that, technically, my new package will have no upstream
On Wed, Aug 01, 2012 at 11:24:20AM +0200, Tomasz Buchert wrote:
> Hello mentors,
> I am working on one bug of mine
> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664457) and I've
> noticed that, technically, my new package will have no upstream.
When I read bug 664457 then this package would
Hello mentors,
I am working on one bug of mine
(http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664457) and I've
noticed that, technically, my new package will have no upstream. What is
the packaging workflow in this case? All tutorials/manuals I've read
assume that you work with upstream tarball
5 matches
Mail list logo