On Sunday, December 11, 2016 12:57:40 PM MST Andrey Rahmatullin wrote: > On Sat, Dec 10, 2016 at 11:04:30PM -0700, Herminio Hernandez Jr wrote: > > I have a question regarding packaging using git and the watch file in the > > Debian directory. There is an open bug 794438 for the KDE Partition > > Manager. The current package is broken in Sid. In the thread it was > > mentioned that the KDE Neon has a working package. When I pulled the git > > repo it was only the Debian directory. So what I was following [1]the > > git-buildpackage manual I cloned the partition manager git repo added > > the debian directory and was able to build a working package. However > > after looking closely I begun to wonder if I understood what I was doing. > > So the upstream repro appears to be on version 2.9.90 and preparing to go > > to version 3.0. However the version that I built was 1.0.3. I did not > > understand how this could have happened. Then looking in the Debian > > directory I saw that the watch file is referencing a Source Forge repo > > with the v1.0.3 tar ball. So my question is when I built the package did > > I need to pull code from the upstream repo? Did the build tools just pull > > the tar file down from sf and used it instead? Any help understanding > > will be appreciated[2] > I didn't fully understand what are you asking but if you are asking why > did your package use the 1.0.3 version it's because the package version in > debian/changelog is 1.0.3. Let me try to clarify. Did my package use the code from upstream or the code from the watch file to build.
Attachment:
signature.asc
Description: This is a digitally signed message part.