Re: Getting Involved with Packaging [was Re: Building Debian Package From Upstream Source]

2016-09-27 Thread Byung-Hee HWANG (황병희, 黃炳熙) 
> [...]
> Start here: https://wiki.debian.org/HelpDebian

Yes, i know my position is translation, thanks!!!

-- 
^고맙습니다 _地平天成_ 감사합니다_^))//

Re: Getting Involved with Packaging [was Re: Building Debian Package From Upstream Source]

2016-09-27 Thread songbird 
Stephen Allen wrote:
> On Tue, Sep 27, 2016 at 10:40:53AM +0100, Darac Marjal wrote:
>> On Tue, Sep 27, 2016 at 05:37:40AM -0400, Stephen Allen wrote:
>
>> > Sounds interesting, where should one start? I'm retired so have some
>> > time. 8-)
>> 
>> Start here: https://wiki.debian.org/HelpDebian
>> 
>
> Thank-you

  also, if for some reason you don't know this already,
in many cases to build a package there are what are
called build dependencies.

  to get the required libraries/environment you may
want to add the sources repository to your list in
/etc/apt/sources.list

  and then do an update.

  then use:

   apt-get source pkg
   apt-get build-dep pkg

  and explore/play to your heart's content  :)


  songbird

Re: Getting Involved with Packaging [was Re: Building Debian Package From Upstream Source]

2016-09-27 Thread Stephen Allen 
On Tue, Sep 27, 2016 at 10:40:53AM +0100, Darac Marjal wrote:
> On Tue, Sep 27, 2016 at 05:37:40AM -0400, Stephen Allen wrote:

> > Sounds interesting, where should one start? I'm retired so have some
> > time. 8-)
> 
> Start here: https://wiki.debian.org/HelpDebian
> 

Thank-you

Re: Getting Involved with Packaging [was Re: Building Debian Package From Upstream Source]

2016-09-27 Thread Darac Marjal 

On Tue, Sep 27, 2016 at 05:37:40AM -0400, Stephen Allen wrote:

On Tue, Sep 27, 2016 at 11:11:37AM +1000, Ben Finney wrote:


You can also help out, if you want to exercise the skills: Figure out
the intent of those patches, get the Debian packaging VCS onto your
local environment, and see what has changed in the new version from
upstream that might affect the intent of the patches.

Debian package maintainers need people who can help out, and tangible
measurable work like this is a good way to get involved.


Sounds interesting, where should one start? I'm retired so have some
time. 8-)


Start here: https://wiki.debian.org/HelpDebian


--
For more information, please reread.


signature.asc
Description: PGP signature

Getting Involved with Packaging [was Re: Building Debian Package From Upstream Source]

2016-09-27 Thread Stephen Allen 
On Tue, Sep 27, 2016 at 11:11:37AM +1000, Ben Finney wrote:

> You can also help out, if you want to exercise the skills: Figure out
> the intent of those patches, get the Debian packaging VCS onto your
> local environment, and see what has changed in the new version from
> upstream that might affect the intent of the patches.
> 
> Debian package maintainers need people who can help out, and tangible
> measurable work like this is a good way to get involved.

Sounds interesting, where should one start? I'm retired so have some
time. 8-)

Re: Building Debian Package From Upstream Source

2016-09-26 Thread Ben Finney 
Stephen Allen  writes:

> On Mon, Sep 26, 2016 at 10:00:03AM +1000, Ben Finney wrote:
> > Especially when patches are needed, you shouldn't expect those
> > patches to apply to anything except the exact upstream version. The
> > work of a Debian package maintainer includes re-working the patches
> > for each version.
>
> OIC That's most likely the issue - I'll be patient and wait for
> the Debian maintainer to update.

You can also help out, if you want to exercise the skills: Figure out
the intent of those patches, get the Debian packaging VCS onto your
local environment, and see what has changed in the new version from
upstream that might affect the intent of the patches.

Debian package maintainers need people who can help out, and tangible
measurable work like this is a good way to get involved.

-- 
 \ “Skepticism is the highest duty and blind faith the one |
  `\   unpardonable sin.” —Thomas Henry Huxley, _Essays on |
_o__)   Controversial Questions_, 1889 |
Ben Finney

Re: Building Debian Package From Upstream Source

2016-09-26 Thread Stephen Allen 
On Mon, Sep 26, 2016 at 10:00:03AM +1000, Ben Finney wrote:
> Stephen Allen  writes:
> 
> > So, I downloaded the upstream source, downloaded the most recent
> > version of the Debian Package, so that I have a Debian source tree.
> 
> Is the upstream source you downloaded, different from the upstream source
> (the ‘….orig.tar.gz’) to which the Debian packaging is intended to apply?
> 
> Especially when patches are needed, you shouldn't expect those patches
> to apply to anything except the exact upstream version. The work of a
> Debian package maintainer includes re-working the patches for each version.

OIC That's most likely the issue - I'll be patient and wait for
the Debian maintainer to update.

Thanks all!

Re: Building Debian Package From Upstream Source

2016-09-25 Thread Ben Finney 
Stephen Allen  writes:

> So, I downloaded the upstream source, downloaded the most recent
> version of the Debian Package, so that I have a Debian source tree.

Is the upstream source you downloaded, different from the upstream source
(the ‘….orig.tar.gz’) to which the Debian packaging is intended to apply?

Especially when patches are needed, you shouldn't expect those patches
to apply to anything except the exact upstream version. The work of a
Debian package maintainer includes re-working the patches for each version.

-- 
 \   “You've got the brain of a four-year-old boy, and I'll bet he |
  `\ was glad to get rid of it.” —Groucho Marx |
_o__)  |
Ben Finney

Re: Building Debian Package From Upstream Source

2016-09-25 Thread Santiago Vila 
On Sun, Sep 25, 2016 at 10:43:04AM -0400, Stephen Allen wrote:
> Then I ran 'dpkg-buildpackage -us -uc -j4' as root' [...]

Note: Debian packages do not require to be built by root, so it's better
that you don't. Using fakeroot is the default. Just install it
and it will be used automatically by dpkg-buildpackage.

Re: Building Debian Package From Upstream Source

2016-09-25 Thread Mark Fletcher 
On Sun, Sep 25, 2016 at 10:43:04AM -0400, Stephen Allen wrote:
> Hi, wanting to upgrade to a newer version of Liferea than what's in
> Testing.
> 
> So, I downloaded the upstream source, downloaded the most recent version
> of the Debian Package, so that I have a Debian source tree. Next I
> copied the Debian source tree directory from the existing Debian source
> package into the upstream source, with Debian dsc and OrigSrc one level
> up.
> Then I ran 'dpkg-buildpackage -us -uc -j4' as root' which gave me the
> following error;
> 



>  dpkg-source: info: applying debian-example-feeds.patch
>  dpkg-source: info: applying www-browser.patch
>  patching file src/browser.c
>  Hunk #1 FAILED at 72.


I think what you have here is a package-specific problem. The Debian 
build is attempting to apply patches to the source. Since you have 
grafted in newer source, I suspect the affected source file has been 
updated in an incompatible way and now the patch doesn't work 
(presumably because the lines it expects to change are either gone or 
are no longer at the expected line numbers in the source file).

What can you do about this? Not a lot, except maybe if you have the 
skills take the Debian Testing source, apply the patch yourself to get 
the patched source file, then diff this with the newer source file and 
figure out if the intent of the patch is still needed. If so, you'd need 
to apply it manually to the updated source, or, if you are lucky, obtain 
an updated patch from somewhere.

Depending on how strong a programmer you are, you may or may not be able 
to do this. Another option would be to go back to the package developers 
(the original developers, not the Debian package maintainer) and ask if 
they have an updated version of the patch, if it is still needed / 
recommended.

I assume there isn't a sufficiently up to date version of the package in 
sid??? :-)

Mark

Building Debian Package From Upstream Source

2016-09-25 Thread Stephen Allen 
Hi, wanting to upgrade to a newer version of Liferea than what's in
Testing.

So, I downloaded the upstream source, downloaded the most recent version
of the Debian Package, so that I have a Debian source tree. Next I
copied the Debian source tree directory from the existing Debian source
package into the upstream source, with Debian dsc and OrigSrc one level
up.
Then I ran 'dpkg-buildpackage -us -uc -j4' as root' which gave me the
following error;

dpkg-buildpackage: info: source package liferea
dpkg-buildpackage: info: source version 1.10.19-2
dpkg-buildpackage: info: source distribution unstable
dpkg-buildpackage: info: source changed by David Michael Smith

dpkg-buildpackage: info: host architecture amd64
 dpkg-source --before-build liferea-1.12-rc1a
 dpkg-source: info: using options from
 liferea-1.12-rc1a/debian/source/options: --compression=xz
 dpkg-source: info: applying debian-example-feeds.patch
 dpkg-source: info: applying www-browser.patch
 patching file src/browser.c
 Hunk #1 FAILED at 72.
 1 out of 1 hunk FAILED
 patching file net.sf.liferea.gschema.xml.in
 dpkg-source: info: the patch has fuzz which is not allowed, or is
 malformed
 dpkg-source: info: if patch 'www-browser.patch' is correctly applied by
 quilt, use 'quilt refresh' to update it
 dpkg-source: info: restoring quilt backup files for www-browser.patch
 dpkg-source: error: LC_ALL=C patch -t -F 0 -N -p1 -u -V never -E -b -B
 .pc/www-browser.patch/ --reject-file=- <
 liferea-1.12-rc1a/debian/patches/www-browser.patch gave error exit
 status 1
 dpkg-buildpackage: error: dpkg-source --before-build liferea-1.12-rc1a
 gave error exit status 2

 

 I'm new to building Debian packages, so any suggestions appreciated,
 I'm running Debian 'Testing'.