pkg kde talk - Nov 2009 - Switch to orig.tar.bz2 & dpkg-source format 3.0 (quilt)?

Hello,

since Debian ftpmasters have made it possible to upload source packages 
packaged in the next generation formats:

1) I don''t see any blockers to use pristine KDE upstream tarballs
anymore
(renamed to appropriate orig.tar.bz2 of course).

2) What about dpkg-source format 3.0 (quilt) for all official KDE packages? I 
tested it and I was sort of pleased with results.

Added benefits:

* no quilt build dependency;
* no need to add/remove quilt build dependency when the first patch is added / 
all patches are removed;
* no patch system class in debian/rules (will need newer pkg-kde-tools).

Disadvantages:

* if our packages were kept upstream sources in packaging VCS, it would be a 
bit of inconvenient (esp. in the context of svn) not to commit debian-patched 
upstream files or do `quilt pop -a` after each test build. But since we only 
keep debian/ under VCS, I don''t see any blockers or regressions in a
workflow.

-- 
Modestas Vainius <modestas at vainius.eu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20091102/2146626b/attachment.pgp>

On Mon, Nov 02, 2009 at 08:35:11PM +0200, Modestas Vainius
wrote:
> Hello,
> 
> since Debian ftpmasters have made it possible to upload source packages 
> packaged in the next generation formats:
> 
> 1) I don''t see any blockers to use pristine KDE upstream tarballs
anymore
> (renamed to appropriate orig.tar.bz2 of course).
> 
> 2) What about dpkg-source format 3.0 (quilt) for all official KDE packages?
I
> tested it and I was sort of pleased with results.
> 
Fine on my side.

Ana

On Monday 02 November 2009 19:35:11 Modestas Vainius
wrote:
> Hello,
> 
> since Debian ftpmasters have made it possible to upload source packages
> packaged in the next generation formats:
> 
> 1) I don''t see any blockers to use pristine KDE upstream tarballs
anymore
> (renamed to appropriate orig.tar.bz2 of course).
I don''t mind this
> 2) What about dpkg-source format 3.0 (quilt) for all official KDE packages?
>  I tested it and I was sort of pleased with results.
But I''m not personally ready to go dpkg-source v3 yet. need to do more
reading
and practicing with it. I have quite some personal workflows around the 
.diff.gz files.

/Sune
-- 
Genius, I cannot disconnect a front-side bus, how does it work?

First you should turn on a display on the DirectGL cable and you neither must 
disable the mousepad, nor should install the floppy disk over a microprocessor 
on the hard disk for getting access on a Fast mother board.

Hi all,

As Sune: I''m fine for the tar.bz2 tarball but I need a closer look to
dpkg-source format 3.0.

cheers,

Fathi

On Tue, Nov 3, 2009 at 12:01 AM, Fathi Boudra <fabo at debian.org>
wrote:
> Hi all,
>
> As Sune: I''m fine for the tar.bz2 tarball but I need a closer look
to
> dpkg-source format 3.0.
>
Hi,

I will also need some time to learn the new format and adjust my
scripts, but I don''t mind switching to it. We could experiment with it
during the 4.4 beta/rc cycles, if everybody has agreed till then. And
maybe I''ll play with it on partitionmanager first...

Regards,
George

Hello,

On antradienis 03 Lapkritis 2009 00:53:10 George Kiagiadakis
wrote:
> I will also need some time to learn the new format and adjust my
> scripts, but I don''t mind switching to it. We could experiment
with it
> during the 4.4 beta/rc cycles, if everybody has agreed till then. And
> maybe I''ll play with it on partitionmanager first...
Unless scripts touch .diff.gz directly, there should not be much difference. 
Actually, there is only one difference important to us: after `dpkg-source -x 
*.dsc`, all patches in debian/patches will be applied by dpkg-source already, 
and when doing `dpkg-source -b`, all patches must be applied to the extracted 
source tree (or dpkg-source will autopush them). Everything else are only 
technical details. 

We neither ship debian specific binary files nor any non "series"
inline
patches so those features of v3 are not very important for us.

However, as you want to try 3.0 (quilt) with smaller packages first, we will 
probably get back to it some time later (maybe for late 4.4 dev packages as 
George suggests). On the other hand, orig.tar.bz2 (including snapshot tarballs 
if we do any) is effective immediately (for 4.3.3 and up) by common agreement.

-- 
Modestas Vainius <modestas at vainius.eu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20091103/2da6629f/attachment.pgp>

Hello,

On antradienis 03 Lapkritis 2009 01:13:04 Modestas Vainius
wrote:
>  packages as George suggests). On the other hand, orig.tar.bz2 (including
>  snapshot tarballs if we do any) is effective immediately (for 4.3.3 and
>  up) by common agreement.
Ok, I''m wrong. dpkg-source format 1.0 does NOT support orig.tar.bz2. If
we are
not switching to dpkg-source v3, we still have to repack :/

-- 
Modestas Vainius <modestas at vainius.eu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL:
<http://lists.alioth.debian.org/pipermail/pkg-kde-talk/attachments/20091104/d74d994b/attachment.pgp>