Stéphane Glondu glo...@debian.org writes:
Le 06/03/2012 15:22, Benoît Knecht a écrit :
I think it important for any maintainer to clearly differentiate in
their mind upstream from Debian, even if they happen to be the same
person. Otherwise, you're artificially limiting your software to
Benoît Knecht benoit.kne...@fsfe.org writes:
Goswin von Brederlow wrote:
Benoît Knecht benoit.kne...@fsfe.org writes:
Goswin von Brederlow wrote:
[...]
The package is native because I am both maintainer and upstream
author. Does a watch file make sense for a native package?
Le 07/03/2012 09:14, Goswin von Brederlow a écrit :
I really don't get that argument. Nothing in having a debian directory
in the source hinders any other distribution. And plenty of sources
contain spec files for building rpms to no detriment to Debian. If any
non rpm based distribution picks
Le 07/03/2012 09:52, Goswin von Brederlow a écrit :
That is what major, minor and subversions (x.y.z) are for. If I change
only something in Debian I would not increment x or y and I would not
create a new tarball for release on e.g. ocamlforge.
I find this confusing. Debian has standardized
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package rubyripper
* Package name: rubyripper
Version : 0.6.2-1
Upstream Author : Bouke Woudstra boukewouds...@gmail.com
* URL : https://code.google.com/p/rubyripper/
*
Stéphane Glondu glo...@debian.org writes:
Le 07/03/2012 09:52, Goswin von Brederlow a écrit :
That is what major, minor and subversions (x.y.z) are for. If I change
only something in Debian I would not increment x or y and I would not
create a new tarball for release on e.g. ocamlforge.
I
Stéphane Glondu glo...@debian.org writes:
Le 07/03/2012 09:14, Goswin von Brederlow a écrit :
With a moments thought I would have 3 branches:
- master
- upstream
- pristine-tar
All developement would happen in the master branch. Then before the
Debian upload I would merge master -
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package shc
* Package name: shc
Version : 3.8.7-1
Upstream Author : Francisco Rosales fro...@fi.upm.es
* URL : http://www.datsi.fi.upm.es/~frosal/sources/
[there
Processing commands for cont...@bugs.debian.org:
severity 662968 wishlist
Bug #662968 [sponsorship-requests] RFS: shc/3.8.7-1
Severity set to 'wishlist' from 'normal'
retitle 662968 RFS: shc/3.8.7-1 [ITP] -- Generic shell script compiler
Bug #662968 [sponsorship-requests] RFS: shc/3.8.7-1
tag 662968 moreinfo
thanks
Hi Vibhav,
Vibhav Pant wrote:
I am looking for a sponsor for my package shc
* Package name: shc
Version : 3.8.7-1
Upstream Author : Francisco Rosales fro...@fi.upm.es
* URL : http://www.datsi.fi.upm.es/~frosal/sources/
[there
Processing commands for cont...@bugs.debian.org:
tag 662968 moreinfo
Bug #662968 [sponsorship-requests] RFS: shc/3.8.7-1 [ITP] -- Generic shell
script compiler
Added tag(s) moreinfo.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
662968:
Vibhav Pant wrote:
I am looking for a sponsor for my package shc
* Package name: shc
Version : 3.8.7-1
Upstream Author : Francisco Rosales fro...@fi.upm.es
* URL : http://www.datsi.fi.upm.es/~frosal/sources/
[there is no such homepage for this program]
*
Hi Vibhav,
Please have a look at:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=327263
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=508109
--
pub 4096R/0E4BD0AB people.fccf.net/danchev/key pgp.mit.edu
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject
Goswin von Brederlow goswin-...@web.de writes:
Given the above idea how would you lay out the git then?
With a moments thought I would have 3 branches:
- master
- upstream
- pristine-tar
All developement would happen in the master branch. Then before the
Debian upload I would merge
Hi Benoît,
thank you again for these notices.
Il 06/03/2012 23:25, Benoît Knecht ha scritto:
Giulio Paci wrote:
thank you for your comment. I updated the package, adding the missing
libxslt1-dev dependency and fixing a couple of other minor issues.
A few things to look into:
Your message dated Wed, 07 Mar 2012 23:22:08 +0100
with message-id 4f57df90.4020...@debian.org
and subject line Closing
has caused the Debian Bug report #662031,
regarding RFS: trophy/2.0.2-1 (updated package) -- 2D car racing action game
to be marked as done.
This means that you claim that the
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package bibtool
* Package name: bibtool
Version : 2.54+ds-2
Upstream Author : Gerd Neugebauer g...@gerd-neugebauer.de
* URL
OK - I 'll try to fix it with 'dh_autoreconf'.
Thanks,
On Tue, Mar 6, 2012 at 11:13 AM, Paul Tagliamonte paul...@ubuntu.comwrote:
Your package also ftbfs when built twice in a row
From my output:
| dpkg-source -b tpb-0.6.4
| dpkg-source: info: using source format `3.0 (quilt)'
|
Russ Allbery r...@debian.org writes:
Goswin von Brederlow goswin-...@web.de writes:
Given the above idea how would you lay out the git then?
With a moments thought I would have 3 branches:
- master
- upstream
- pristine-tar
All developement would happen in the master branch. Then before
Goswin von Brederlow goswin-...@web.de writes:
Russ Allbery r...@debian.org writes:
http://www.eyrie.org/~eagle/notes/debian/git.html
Where were you 2 years ago when I first asked about how to use git when
being both upstream and debian maintainer? :)
Posting that site to Planet Debian. :)
20 matches
Mail list logo
