Ah, for official backports see the procedure at
https://help.ubuntu.com/community/UbuntuBackports
The procedure is more of a quality-assurance (testing) one rather than a
build-and-upload workflow -- the build system takes care of the actual
backporting work
I'd recommend using prevu's build
sorry for that noise, solved it... my fault
What's next in the backport process?
2008/12/17 Schoap D
> First I need to solve this
> Command line parameter [nted_1.4.15-1ubuntu1.dsc] is not a valid .dsc file
> name
>
> I can t build it right now...
>
> About uploading... what is the next step af
First I need to solve this
Command line parameter [nted_1.4.15-1ubuntu1.dsc] is not a valid .dsc file
name
I can t build it right now...
About uploading... what is the next step after the request and the build of
the package?
Thanks,
\s
2008/12/17 John Dong
> Where are you trying to upload
Where are you trying to upload it to?
On Wed, Dec 17, 2008 at 7:56 PM, Schoap D wrote:
>
>
> 2008/12/17 Schoap D
>
>
>>
>> 2008/12/17 John Dong
>>
>>>
>>>
>>> On Wed, Dec 17, 2008 at 3:40 PM, Schoap D wrote:
>>>
fakeroot debian/rules clean
debian/rules:3: /usr/share/cdbs/1/rul
2008/12/17 Schoap D
>
>
> 2008/12/17 John Dong
>
>>
>>
>> On Wed, Dec 17, 2008 at 3:40 PM, Schoap D wrote:
>>
>>>
>>> fakeroot debian/rules clean
>>> debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: No such file or
>>> directory
>>> debian/rules:4: /usr/share/cdbs/1/class/autotools.mk: No
2008/12/17 John Dong
>
>
> On Wed, Dec 17, 2008 at 3:40 PM, Schoap D wrote:
>
>>
>> fakeroot debian/rules clean
>> debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: No such file or
>> directory
>> debian/rules:4: /usr/share/cdbs/1/class/autotools.mk: No such file or
>> directory
>> debian/r
On Wed, Dec 17, 2008 at 3:40 PM, Schoap D wrote:
>
> fakeroot debian/rules clean
> debian/rules:3: /usr/share/cdbs/1/rules/debhelper.mk: No such file or
> directory
> debian/rules:4: /usr/share/cdbs/1/class/autotools.mk: No such file or
> directory
> debian/rules:5: /usr/share/cdbs/1/rules/patch
I tried to backport nted, but got some errors:
first here:
$ dpkg-source -x nted_1.4.15-1.dsc
gpg: Signature made Wed 12 Nov 2008 22:38:04 GMT using DSA key ID 30825345
gpg: Can't check signature: public key not found
dpkg-source: extracting nted in nted-1.4.15
dpkg-source: info: unpacking nted_1
On Wed, Dec 17, 2008 at 1:12 PM, Schoap D wrote:
>
>
> Ok, thanks.
> Is it just like a update process?
>
> apt-get source
> wget
> mv hello-2.3.tar.gz hello_2.3.orig.tar.gz
> tar xfz hello_2.3.orig.tar.gz
> cd hello_2.3/
> zcat ../hello_2.2-2.diff.gz | patch -p1
> dch -i
>
No, it's even simpler
2008/12/17 John Dong
> Backport building is even easier. For the most part, no source changes are
> required. All you have to do is use "dch -i" to create a new changelog
> entry(*) acknowledging that it's a backport, then run pbuilder on this new
> source package.
>
> The exception is when the J
Backport building is even easier. For the most part, no source changes are
required. All you have to do is use "dch -i" to create a new changelog
entry(*) acknowledging that it's a backport, then run pbuilder on this new
source package.
The exception is when the Jaunty version requires a new build
Hi,
I followed some documentation and video tutorials about ubuntu packaging
with pbuilder. Now I'm wondering how to make a backport package, let say
from Jaunty for Intrepid, using pbuilder?
Thanks in advance,
\s
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.com
Modify setting
12 matches
Mail list logo
