Hi,
The patches are always stored in debian/patches/*. The `gbp pq`
commands are helpers that read files from that path and convert them
into commits on a *temporary* branch, so they are easy to modify,
build with, cherry-pick to another branch for e.g. upstream submission
etc. You should always e
On Mon, Sep 15, 2025 at 06:32:35AM +0900, Yukiharu YABUKI wrote:
>
> Need to separate upstream source and debian/ directory.
> right? Upstream source code should work with gbp pq.
> debian/ directory works with git.
>
> Is this outlook for gbp correct?
Wrong. Master branch has comitted files in
Thank you for your quick response.
I merged your merge requests. I realized that I did not
understand what I did with gbp workflow. I need to grub
the basic concept and workflow with gbp buildpackage
and gbp pq.
Need to separate upstream source and debian/ directory.
right? Upstream source code
Hello!
The package has a bunch of git commits that modify files outside the
allowed debian/ directory:
± git diff --stat upstream
.gitignore | 2 ++
Disp.c | 2 +-
Makefile | 46
On Mon, Sep 15, 2025 at 04:38:15AM +0900, Yukiharu YABUKI wrote:
I am struggle with gbp buildpackage for build.
I am trying to fix FTBFS bug.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114447
I wrote inital fix code. But I do `dpkg-source --commit`
dquilt (see
https://www.debian.org/doc
Hi there.
I am struggle with gbp buildpackage for build.
I am trying to fix FTBFS bug.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1114447
I wrote inital fix code. But I do `dpkg-source --commit`
dquilt (see
https://www.debian.org/doc/manuals/debmake-doc/ch04.ja.html#gbp-setup)
or gbp pq i
Package: wnpp
Severity: wishlist
Owner: "Dr. Tobias Quathamer"
X-Debbugs-Cc: debian-devel@lists.debian.org, to...@debian.org
* Package name: fonts-atkinson-hyperlegible-next
Version : 0.0~git20250221.7925f50
Upstream Contact: https://github.com/googlefonts/atkinson-hyperlegible-n
Package: wnpp
Severity: wishlist
Owner: Philipp Kern
* Package name: golang-github-ysmood-gson
Version : 0.7.3-1
Upstream Author : Yad Smood
* URL : https://github.com/ysmood/gson
* License : Expat
Programming Lang: Go
Description : Read and alter JSON
Package: wnpp
Severity: wishlist
Owner: Carl Keinath
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: neovim-telescope-fzf-native
Version : 0~git20250312 (snapshot)
Upstream Contact: nvim-telescope team
* URL : https://github.com/nvim-telescope/telescope-fzf
Package: wnpp
Severity: wishlist
Owner: Alexander Fomin
X-Debbugs-Cc: debian-devel@lists.debian.org, fomin_a...@yahoo.com
* Package name: i2cexplorer
Version : 1.0.2
Upstream Contact: Alexander Fomin
* URL : https://salsa.debian.org/AlexFomin/i2cexplorer
* License
Hi Preuße, (2025.09.14_11:20:40_+)
I had a look at [1]. As my client is > 0.10.0 I used the automatic
installation, which seemed to work fine, at least I can create work
requests.
Glad to hear you got set up so easily.
The test mentioned on the page below however fails. Is it expected
wo
Package: wnpp
Severity: wishlist
Owner: Seyed Mohamad Amin Modaresi
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name : ssh-studio
* Version : 1.2.1-1
* URL : https://github.com/BuddySirJava/SSH-Studio
* License : GPL-3+
Description : Easy, GUI SSH config editor and validator built with
On 8/13/2025 6:03 PM, Raphael Hertzog wrote:
Hello,
TLDR summary
To limit the risk of breakage in unstable, and have a wide QA coverage of
your uploads, consider using debusine.debian.net for your uploads to
Debian.
I had a look at [1]. As my client is > 0.10.0 I used the autom
Package: wnpp
Severity: wishlist
Owner: Carl Keinath
X-Debbugs-Cc: debian-devel@lists.debian.org
* Package name: neovim-autopairs
Version : 0~git20250701
Upstream Contact: windwp
* URL : https://github.com/windwp/nvim-autopairs
* License : MIT
Programming La
14 matches
Mail list logo