On 6 February 2017 at 12:25, Narcis Garcia wrote:
> Very far from the number of libs/tools that cannot unmask something like
> Alexander Wirt formorer formorer de at anywhere of a page.
>
Probably this mentors mailing list isn't the right place for this discussion.
__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 06/02/17 a les 11:16, Alexander Wirt ha escrit:
> On Mon, 06 Feb 2017, Narcis Garcia wrote:
>
>> __
>> I'm using t
On Mon, 06 Feb 2017, Narcis Garcia wrote:
> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this list's archives. Mailing lists service
> administrator should fix this.
> El 06/02/17 a les 10:42, Alexander Wirt ha escrit:
> > On Mon, 06 Feb 201
__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 06/02/17 a les 10:42, Alexander Wirt ha escrit:
> On Mon, 06 Feb 2017, Narcis Garcia wrote:
>
>> __
>> I'm using t
On Mon, 06 Feb 2017, Narcis Garcia wrote:
> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this list's archives. Mailing lists service
> administrator should fix this.
We don't intend to. Debian is an open Distribution and we believe in being
__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 05/02/17 a les 21:25, Gianfranco Costamagna ha escrit:
> Hi,
>
>
>
>> You are expected to set that bit on the file and c
Hi,
>You are expected to set that bit on the file and commit it. Gitlab has
>nothing to do with this.
stuff like github now allows to modify files and commit them from the web
interface
(without having to checkout the repo).
I'm not sure about gitlab interface, but I don't think you can chmod
On Sun, Feb 05, 2017 at 07:29:21PM +0100, Narcis Garcia wrote:
> Another warning I don't know how to solve in GitLab:
> "dpkg-buildpackage: warning: debian/rules is not executable; fixing that"
> I don't find in GitLab CMS the way to set executable bit to a file.
You are expected to set that bit on
Oh good! With the tab fix completes deb generation! Thank your patience
Adrey!
A warning that can be pointing to the lack of target file problem:
"dpkg-genchanges: warning: package ntfsundelete-tree in control file but
not in files list"
file "files" contains:
ntfsundelete-tree admin extra
Anothe
On Sun, Feb 05, 2017 at 10:17:59AM +0100, Narcis Garcia wrote:
> I'm not kidding. With the default dh $@ only line, outputs an error message.
I've explained why. You were not using the tab character. Either the
instructions you are using don't mention that or you missed that part
(also, d/rules is
__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 04/02/17 a les 21:09, Andrey Rahmatullin ha escrit:
> On Sat, Feb 04, 2017 at 09:02:20PM +0100, Narcis Garcia wrote:
d
On Sat, Feb 04, 2017 at 09:02:20PM +0100, Narcis Garcia wrote:
> >> dpkg-buildpackage continues now, when my "rules" file has this only
> >> content:
> >>
> >> #!/usr/bin/make -f
> >> clean:
> >> binary:
> >> binary-arch:
> >> binary-indep:
> >> build:
> >> build-arch:
> >> build-indep:
> > Which,
__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 04/02/17 a les 20:37, Andrey Rahmatullin ha escrit:
> On Sat, Feb 04, 2017 at 06:57:56PM +0100, Narcis Garcia wrote:
>> dpk
On Sat, Feb 04, 2017 at 06:57:56PM +0100, Narcis Garcia wrote:
> dpkg-buildpackage continues now, when my "rules" file has this only content:
>
> #!/usr/bin/make -f
> clean:
> binary:
> binary-arch:
> binary-indep:
> build:
> build-arch:
> build-indep:
Which, of course, doesn't do anything useful.
dpkg-buildpackage continues now, when my "rules" file has this only content:
#!/usr/bin/make -f
clean:
binary:
binary-arch:
binary-indep:
build:
build-arch:
build-indep:
Now I'm at this point:
(...)
dpkg-genchanges >../ntfsundelete-tree_1.0.0-1_amd64.changes
dpkg-genchanges: warning: package n
On Sat, Feb 04, 2017 at 04:55:13PM +0100, Narcis Garcia wrote:
> wget --no-check-certificate -O ntfsundelete-tree_1.0.0.orig.tar
> https://git.actiu.net/libre/ntfsundelete-tree/repository/archive.tar?ref=master
This is not an orig.tar.
> I don't know what is the minimal expected to be in "debian/
I'm now trying with the following*:*
rm -fr /tmp/deb ; mkdir /tmp/deb ; cd /tmp/deb
wget --no-check-certificate -O ntfsundelete-tree_1.0.0.orig.tar
https://git.actiu.net/libre/ntfsundelete-tree/repository/archive.tar?ref=master
tar xf ntfsundelete-tree_1.0.0.orig.tar
cd ntfsundelete-tree-master*
Dear Narcis,
I am an upstream maintaining a Debian package. Frankly, I think you're
overcomplicating things. In particular, I strongly recommend ignoring
git-buildpackage, simply because it was not designed with your situation
in mind.
I suggest using a single branch, and building with dpkg-bui
On Tue, Dec 20, 2016 at 07:14:17PM +0100, Narcis Garcia wrote:
> You mean I really need to maintain 2 branches of code (master*+*debian)?
I didn't say that, you can put debian/ into your upstream sources.
> Then I imagine these are my steps to do:
> $ wget --no-check-certificate -O ntfsundelete-tr
You mean I really need to maintain 2 branches of code (master*+*debian)?
Then I imagine these are my steps to do:
$ wget --no-check-certificate -O ntfsundelete-tree_1.0.0.orig.tar
https://git.actiu.net/libre/ntfsundelete-tree/repository/archive.tar?ref=master
$ tar xf ntfsundelete-tree_1.0.0.orig
On Tue, Dec 20, 2016 at 04:48:30PM +0100, Narcis Garcia wrote:
> Currently, I'm editing files directly with GitLab web interface.
> For the moment, I only want "packaging from git":
> Git -> Packaging helper (single direction sense)
Well, you don't really need helpers, you can just checkout the deb
Currently, I'm editing files directly with GitLab web interface.
For the moment, I only want "packaging from git":
Git -> Packaging helper (single direction sense)
Thanks.
__
I'm using this express-made address because personal addresses aren't
masked enough at lists.debian.org archives.
On Tue, Dec 20, 2016 at 03:25:20PM +0100, Adam Borowski wrote:
> It also suffers from treating quilt as a god rather than an abomination
> it is. Using version control checked into another version control is a
> disaster.
gbp-pq
--
WBR, wRAR
signature.asc
Description: PGP signature
On 20/12/16 15:25, Adam Borowski wrote:
On Tue, Dec 20, 2016 at 11:00:20AM +0100, Narcis Garcia wrote:
Hello, I'm trying to maintain a small project in my public Git, and to
have an easy way to build a package for Debian OS obtaining a good/clean
result.
Even just using git directly without
On Tue, Dec 20, 2016 at 11:00:20AM +0100, Narcis Garcia wrote:
> Hello, I'm trying to maintain a small project in my public Git, and to
> have an easy way to build a package for Debian OS obtaining a good/clean
> result.
> After this, I will try to deploy my APT repository or contact some
> sponsor
I made a single file in ShellScript. To walk to Debian inclusion,
somebody suggested me to publish it in a control version system (as
Git). I've deployed this GitLab instance and now I only want to sure
this is packageable.
At this point, I prefer a single branch (master?) if it's possible, to
use
On 20/12/16 13:21, Andrey Rahmatullin wrote:
On Tue, Dec 20, 2016 at 01:10:03PM +0100, Alec Leamas wrote:
I have been struggling with this myself. My current approach
- One separate branch for the debian packaging
- In that branch, add the release branch as a git submodule
- In the debi
On Tue, Dec 20, 2016 at 01:10:03PM +0100, Alec Leamas wrote:
> I have been struggling with this myself. My current approach
>
> - One separate branch for the debian packaging
> - In that branch, add the release branch as a git submodule
> - In the debian branch, check in and tag the pristin
On Tue, Dec 20, 2016 at 12:57:21PM +0100, Narcis Garcia wrote:
> Maintaining debian-branch, upstream-branch and pristine-tar... Does it
> mean that I'll need to replicate "master" branch to those 3 sub-branches
> each time I wan to apply an update?
Working with the upstream git repo is covered at
f
On 20/12/16 12:57, Narcis Garcia wrote:
Maintaining debian-branch, upstream-branch and pristine-tar... Does it
mean that I'll need to replicate "master" branch to those 3 sub-branches
each time I wan to apply an update?
Same for each upstream/ subdirectories?
I have been struggling with this
Maintaining debian-branch, upstream-branch and pristine-tar... Does it
mean that I'll need to replicate "master" branch to those 3 sub-branches
each time I wan to apply an update?
Same for each upstream/ subdirectories?
__
I'm using this express-made address because personal addresses ar
On Tue, Dec 20, 2016 at 11:00:20AM +0100, Narcis Garcia wrote:
> Can the Git content be bad? Lack of files? Unnecessary files? Bad structure?
Yes.
gbp requires a special repo structure, see
file:///usr/share/doc/git-buildpackage/manual-html/gbp.intro.html#GBP.REPOSITORY
--
WBR, wRAR
signature.a
32 matches
Mail list logo
