Fwd: ffado git repository
Sorry for answering privately. On Sat, Apr 3, 2010 at 22:20, Felipe Sateler wrote: > On Mon, Sep 7, 2009 at 02:48, Adrian Knoth wrote: >> On Sun, Sep 06, 2009 at 05:28:25PM -0400, Felipe Sateler wrote: >> >>> I can't seem to update the repo. Is anyone else having this problem? >> >> Same here: >> >> a...@chopin:/tmp$ git clone git://git.debian.org/pkg-multimedia/ffado >> Initialized empty Git repository in /tmp/ffado/.git/ >> remote: Counting objects: 1003, done. >> remote: Compressing objects: 100% (763/763), done. >> remote: Total 1003 (delta 412), reused 680 (delta 219) >> Receiving objects: 100% (1003/1003), 1.09 MiB | 660 KiB/s, done. >> Resolving deltas: 100% (412/412), done. >> error: * Ignoring funny ref 'refs/tags/debian/2.0~rc1+svn1539-1' locally >> error: * Ignoring funny ref 'refs/tags/debian/2.0~rc2+svn1569-1' locally >> error: * Ignoring funny ref 'refs/tags/debian/2.0~rc2+svn1569-2' locally >> >> a...@chopin:/tmp/ffado$ git pull origin >> From git://git.debian.org/pkg-multimedia/ffado >> ! [new tag] debian/2.0~rc1+svn1539-1 -> >> debian/2.0~rc1+svn1539-1 (unable to update local ref) >> ! [new tag] debian/2.0~rc2+svn1569-1 -> >> debian/2.0~rc2+svn1569-1 (unable to update local ref) >> ! [new tag] debian/2.0~rc2+svn1569-2 -> >> debian/2.0~rc2+svn1569-2 (unable to update local ref) >> >> >>> Apparently git doesn't like tags with ~ in them. >> >> Git bug? The git tags manpage doesn't say a thing about "invalid >> characters" or something like this... > > From man git-check-ref-format (referenced from man git-tag): > > 4. They cannot have ASCII control characters (i.e. bytes whose > values > are lower than \040, or \177 DEL), space, tilde ~, caret ^, colon > :, question-mark ?, asterisk *, or open bracket [ anywhere. > > > Is it possible to delete those tags? > > -- > > Saludos, > Felipe Sateler > -- Saludos, Felipe Sateler ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processed: fixed 558502 in 1.1.2-2
Processing commands for cont...@bugs.debian.org: > fixed 558502 1.1.2-2 Bug #558502 [src:gavl] Missing autoreconf to fix 554821 or similar bugs in the future The source gavl and version do not appear to match any binary packages Bug Marked as fixed in versions gavl/1.1.2-2. > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Bug#576069: marked as done (unnecessary build-depend)
Your message dated Sat, 03 Apr 2010 16:29:00 + with message-id and subject line Bug#576069: fixed in libffado 2.0.0+svn1806-2 has caused the Debian Bug report #576069, regarding unnecessary build-depend to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 576069: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=576069 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libffado Source: libffado Version: 2.0.0+svn1806-1 libffado should not build-depend on pyqt-tools, this is a PyQt3 package but libffado uses PyQt4 diff -u libffado-2.0.0+svn1806/debian/changelog libffado-2.0.0+svn1806/debian/changelog --- libffado-2.0.0+svn1806/debian/changelog +++ libffado-2.0.0+svn1806/debian/changelog @@ -1,3 +1,10 @@ +libffado (2.0.0+svn1806-2) lucid; urgency=low + + * Do not build-depend on pyqt-tools, it is a PyQt3 package and +libffado uses PyQt4 + + -- Jonathan Riddell Wed, 31 Mar 2010 15:50:35 +0100 + libffado (2.0.0+svn1806-1) unstable; urgency=low * New upstream release (fixes FTBFS on powerpc) diff -u libffado-2.0.0+svn1806/debian/control libffado-2.0.0+svn1806/debian/control --- libffado-2.0.0+svn1806/debian/control +++ libffado-2.0.0+svn1806/debian/control @@ -2,7 +2,7 @@ Priority: optional Maintainer: Debian Multimedia Maintainers Uploaders: Adrian Knoth , Free Ekanayaka -Build-Depends: debhelper (>= 7.0), scons, libraw1394-dev (>= 1.3.0), libxml2-dev (>= 2.6.13), libiec61883-dev (>= 1.1.0), cdbs, pkg-config, dbus (>= 1.0.0), python, python-dbus, python-qt4, pyqt4-dev-tools, dh-buildinfo, libexpat1-dev, libxml++2.6-dev, libdbus-1-dev, pyqt-tools, python-qt4-dbus, autotools-dev +Build-Depends: debhelper (>= 7.0), scons, libraw1394-dev (>= 1.3.0), libxml2-dev (>= 2.6.13), libiec61883-dev (>= 1.1.0), cdbs, pkg-config, dbus (>= 1.0.0), python, python-dbus, python-qt4, pyqt4-dev-tools, dh-buildinfo, libexpat1-dev, libxml++2.6-dev, libdbus-1-dev, python-qt4-dbus, autotools-dev Standards-Version: 3.8.4 DM-Upload-Allowed: yes Section: libs --- End Message --- --- Begin Message --- Source: libffado Source-Version: 2.0.0+svn1806-2 We believe that the bug you reported is fixed in the latest version of libffado, which is due to be installed in the Debian FTP archive: ffado-dbus-server_2.0.0+svn1806-2_i386.deb to main/libf/libffado/ffado-dbus-server_2.0.0+svn1806-2_i386.deb ffado-mixer-qt4_2.0.0+svn1806-2_i386.deb to main/libf/libffado/ffado-mixer-qt4_2.0.0+svn1806-2_i386.deb ffado-tools_2.0.0+svn1806-2_i386.deb to main/libf/libffado/ffado-tools_2.0.0+svn1806-2_i386.deb libffado-dev_2.0.0+svn1806-2_i386.deb to main/libf/libffado/libffado-dev_2.0.0+svn1806-2_i386.deb libffado2_2.0.0+svn1806-2_i386.deb to main/libf/libffado/libffado2_2.0.0+svn1806-2_i386.deb libffado_2.0.0+svn1806-2.diff.gz to main/libf/libffado/libffado_2.0.0+svn1806-2.diff.gz libffado_2.0.0+svn1806-2.dsc to main/libf/libffado/libffado_2.0.0+svn1806-2.dsc A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 576...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adrian Knoth (supplier of updated libffado package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 01 Apr 2010 13:38:49 +0200 Source: libffado Binary: libffado-dev libffado2 ffado-tools ffado-dbus-server ffado-mixer-qt4 Architecture: source i386 Version: 2.0.0+svn1806-2 Distribution: unstable Urgency: low Maintainer: Debian Multimedia Maintainers Changed-By: Adrian Knoth Description: ffado-dbus-server - FFADO D-Bus server ffado-mixer-qt4 - FFADO D-Bus mixer applets (QT4) ffado-tools - FFADO debugging and firmware tools libffado-dev - FFADO API - development files libffado2 - FFADO API Closes: 576069 Changes: libffado (2.0.0+svn1806-2) unstable; urgency=low . [ Reinhard Tartler ] * convert to multiline fields . [ Jonathan Riddell ] * drop unnecessary build-depend, Closes: #576069 Checksums-Sha1: 4a11bcec49ccde274e1fe5cbf0eee2c9f1155c4b 2381 libffado_2.0.0+svn1806-2.dsc 7a2f584ebc46a7280977d173ca3ab2f1734142e8 5320 libffado_2.0.0+svn1806-2.diff.gz f12dab82ffaf5bcc1042fa1cc2b36cccbc73e74a 16480 libffado-dev_2.0.0+svn1806-2_i386.deb 1c3e83555225d9778752859137a02a05ac028898 93368
Re: jackd2 ready to roll
On Fri, Apr 02, 2010 at 01:30:21AM +0200, Jonas Smedegaard wrote: On Thu, Apr 01, 2010 at 11:00:18PM +0200, Adrian Knoth wrote: On Thu, Apr 01, 2010 at 09:53:19PM +0200, Jonas Smedegaard wrote: In short: I would very much like to volunteer to repackage the current vcs-tarball as pristine-tarball + vcs-patch. Is that acceptable? Different approach: make us the jackd2 repository. ;) So we simply use git, wildly patch whatever we want, no need to wait for upstream to apply my patches and pull from their svn repo from time to time. ;) This way, we can ship the extracted (and checked) waf code, strip *.dll from the package and all the other tweaks that will be required. Might sound completely crazy, probably because it isi, but it surely has its advantages... ;) It certainly has its advantages if upstream also use Git to then maintain upstream and our branches in a single Git. For packaging development. But it still makes best sense to base our final releases on pristine tarballs (or not pristine, if upstream tarballs are not DFSG-free). Is it ok with you that I repackage from the current vcs-tarball to pristine-(or-repackaged)-tarball + vcs-patch? We can then _also_ extend to track upstream Git as well, but let's do one thing at a time. You can have a look at e.g. "debcheckout sugar" and read its debian/README.source for a suggestion on how to do it. Or ask if that file is not easy to comprehend, and I'd be happy to elaborate :-) Ping! - Jonas -- * Jonas Smedegaard - idealist & Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ [x] quote me freely [ ] ask before reusing [ ] keep private signature.asc Description: Digital signature ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
liblrdf_0.4.0-3_amd64.changes ACCEPTED
Accepted: liblrdf0-dev_0.4.0-3_amd64.deb to main/libl/liblrdf/liblrdf0-dev_0.4.0-3_amd64.deb liblrdf0_0.4.0-3_amd64.deb to main/libl/liblrdf/liblrdf0_0.4.0-3_amd64.deb liblrdf_0.4.0-3.debian.tar.gz to main/libl/liblrdf/liblrdf_0.4.0-3.debian.tar.gz liblrdf_0.4.0-3.dsc to main/libl/liblrdf/liblrdf_0.4.0-3.dsc Override entries for your package: liblrdf0-dev_0.4.0-3_amd64.deb - optional libdevel liblrdf0_0.4.0-3_amd64.deb - optional libs liblrdf_0.4.0-3.dsc - source libs Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
libffado_2.0.0+svn1806-2_i386.changes ACCEPTED
Accepted: ffado-dbus-server_2.0.0+svn1806-2_i386.deb to main/libf/libffado/ffado-dbus-server_2.0.0+svn1806-2_i386.deb ffado-mixer-qt4_2.0.0+svn1806-2_i386.deb to main/libf/libffado/ffado-mixer-qt4_2.0.0+svn1806-2_i386.deb ffado-tools_2.0.0+svn1806-2_i386.deb to main/libf/libffado/ffado-tools_2.0.0+svn1806-2_i386.deb libffado-dev_2.0.0+svn1806-2_i386.deb to main/libf/libffado/libffado-dev_2.0.0+svn1806-2_i386.deb libffado2_2.0.0+svn1806-2_i386.deb to main/libf/libffado/libffado2_2.0.0+svn1806-2_i386.deb libffado_2.0.0+svn1806-2.diff.gz to main/libf/libffado/libffado_2.0.0+svn1806-2.diff.gz libffado_2.0.0+svn1806-2.dsc to main/libf/libffado/libffado_2.0.0+svn1806-2.dsc Override entries for your package: ffado-dbus-server_2.0.0+svn1806-2_i386.deb - optional sound ffado-mixer-qt4_2.0.0+svn1806-2_i386.deb - optional sound ffado-tools_2.0.0+svn1806-2_i386.deb - optional sound libffado-dev_2.0.0+svn1806-2_i386.deb - optional libdevel libffado2_2.0.0+svn1806-2_i386.deb - optional libs libffado_2.0.0+svn1806-2.dsc - source libs Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 576069 Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
jamin_0.97.14~cvs~81203-3_amd64.changes ACCEPTED
Accepted: jamin_0.97.14~cvs~81203-3.debian.tar.gz to main/j/jamin/jamin_0.97.14~cvs~81203-3.debian.tar.gz jamin_0.97.14~cvs~81203-3.dsc to main/j/jamin/jamin_0.97.14~cvs~81203-3.dsc jamin_0.97.14~cvs~81203-3_amd64.deb to main/j/jamin/jamin_0.97.14~cvs~81203-3_amd64.deb Override entries for your package: jamin_0.97.14~cvs~81203-3.dsc - source sound jamin_0.97.14~cvs~81203-3_amd64.deb - optional sound Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
hydrogen_0.9.4.1-1_amd64.changes ACCEPTED
Accepted: hydrogen_0.9.4.1-1.debian.tar.gz to main/h/hydrogen/hydrogen_0.9.4.1-1.debian.tar.gz hydrogen_0.9.4.1-1.dsc to main/h/hydrogen/hydrogen_0.9.4.1-1.dsc hydrogen_0.9.4.1-1_amd64.deb to main/h/hydrogen/hydrogen_0.9.4.1-1_amd64.deb hydrogen_0.9.4.1.orig.tar.gz to main/h/hydrogen/hydrogen_0.9.4.1.orig.tar.gz Override entries for your package: hydrogen_0.9.4.1-1.dsc - source sound hydrogen_0.9.4.1-1_amd64.deb - optional sound Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
gavl override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): libgavl-doc_1.1.2-2_all.deb: package says priority is optional, override says extra. libgavl1_1.1.2-2_amd64.deb: package says priority is optional, override says extra. Please note that a list of new sections were recently added to the archive: cli-mono, database, debug, fonts, gnu-r, gnustep, haskell, httpd, java, kernel, lisp, localization, ocaml, php, ruby, vcs, video, xfce, zope. At this time a script was used to reclassify packages into these sections. If this is the case, please only reply to this email if the new section is inappropriate, otherwise please update your package at the next upload. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please file a bug against ftp.debian.org and explain why. Please INCLUDE the list of packages as seen above, or we won't be able to deal with your request due to missing information. Please make sure that the subject of the bug you file follows the following format: Subject: override: BINARY1:section/priority, [...], BINARYX:section/priority Include the justification for the change in the body of the mail please. [NB: this is an automatically generated mail; if you already filed a bug and have not received a response yet, please ignore this mail. Your bug needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
gavl_1.1.2-2_amd64.changes ACCEPTED
Accepted: gavl_1.1.2-2.diff.gz to main/g/gavl/gavl_1.1.2-2.diff.gz gavl_1.1.2-2.dsc to main/g/gavl/gavl_1.1.2-2.dsc libgavl-dev_1.1.2-2_amd64.deb to main/g/gavl/libgavl-dev_1.1.2-2_amd64.deb libgavl-doc_1.1.2-2_all.deb to main/g/gavl/libgavl-doc_1.1.2-2_all.deb libgavl1-dbg_1.1.2-2_amd64.deb to main/g/gavl/libgavl1-dbg_1.1.2-2_amd64.deb libgavl1_1.1.2-2_amd64.deb to main/g/gavl/libgavl1_1.1.2-2_amd64.deb Override entries for your package: gavl_1.1.2-2.dsc - source sound libgavl-dev_1.1.2-2_amd64.deb - optional libdevel libgavl-doc_1.1.2-2_all.deb - extra doc libgavl1-dbg_1.1.2-2_amd64.deb - extra debug libgavl1_1.1.2-2_amd64.deb - extra libs Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
audacity_1.3.12-1_amd64.changes ACCEPTED
Accepted: audacity-data_1.3.12-1_all.deb to main/a/audacity/audacity-data_1.3.12-1_all.deb audacity-dbg_1.3.12-1_amd64.deb to main/a/audacity/audacity-dbg_1.3.12-1_amd64.deb audacity_1.3.12-1.debian.tar.bz2 to main/a/audacity/audacity_1.3.12-1.debian.tar.bz2 audacity_1.3.12-1.dsc to main/a/audacity/audacity_1.3.12-1.dsc audacity_1.3.12-1_amd64.deb to main/a/audacity/audacity_1.3.12-1_amd64.deb audacity_1.3.12.orig.tar.bz2 to main/a/audacity/audacity_1.3.12.orig.tar.bz2 Override entries for your package: audacity-data_1.3.12-1_all.deb - optional sound audacity-dbg_1.3.12-1_amd64.deb - extra debug audacity_1.3.12-1.dsc - source sound audacity_1.3.12-1_amd64.deb - optional sound Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of gavl_1.1.2-2_amd64.changes
gavl_1.1.2-2_amd64.changes uploaded successfully to localhost along with the files: gavl_1.1.2-2.dsc gavl_1.1.2-2.diff.gz libgavl1_1.1.2-2_amd64.deb libgavl1-dbg_1.1.2-2_amd64.deb libgavl-dev_1.1.2-2_amd64.deb libgavl-doc_1.1.2-2_all.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of liblrdf_0.4.0-3_amd64.changes
liblrdf_0.4.0-3_amd64.changes uploaded successfully to localhost along with the files: liblrdf_0.4.0-3.dsc liblrdf_0.4.0-3.debian.tar.gz liblrdf0-dev_0.4.0-3_amd64.deb liblrdf0_0.4.0-3_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of hydrogen_0.9.4.1-1_amd64.changes
hydrogen_0.9.4.1-1_amd64.changes uploaded successfully to localhost along with the files: hydrogen_0.9.4.1-1.dsc hydrogen_0.9.4.1.orig.tar.gz hydrogen_0.9.4.1-1.debian.tar.gz hydrogen_0.9.4.1-1_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of audacity_1.3.12-1_amd64.changes
audacity_1.3.12-1_amd64.changes uploaded successfully to localhost along with the files: audacity_1.3.12-1.dsc audacity_1.3.12.orig.tar.bz2 audacity_1.3.12-1.debian.tar.bz2 audacity-data_1.3.12-1_all.deb audacity_1.3.12-1_amd64.deb audacity-dbg_1.3.12-1_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of jamin_0.97.14~cvs~81203-3_amd64.changes
jamin_0.97.14~cvs~81203-3_amd64.changes uploaded successfully to localhost along with the files: jamin_0.97.14~cvs~81203-3.dsc jamin_0.97.14~cvs~81203-3.debian.tar.gz jamin_0.97.14~cvs~81203-3_amd64.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of libffado_2.0.0+svn1806-2_i386.changes
libffado_2.0.0+svn1806-2_i386.changes uploaded successfully to localhost along with the files: libffado_2.0.0+svn1806-2.dsc libffado_2.0.0+svn1806-2.diff.gz libffado-dev_2.0.0+svn1806-2_i386.deb libffado2_2.0.0+svn1806-2_i386.deb ffado-tools_2.0.0+svn1806-2_i386.deb ffado-dbus-server_2.0.0+svn1806-2_i386.deb ffado-mixer-qt4_2.0.0+svn1806-2_i386.deb Greetings, Your Debian queue daemon (running on host ries.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] Debian packaging for jack-audio-connection-kit branch, master.jackd2, updated. debian/1.9.4+svn3842-2-41-g15d16a4
Hi Reinhard (and others), On Sat, Apr 03, 2010 at 10:04:11AM +0200, Reinhard Tartler wrote: On Fri, Apr 02, 2010 at 20:59:02 (CEST), Jonas Smedegaard wrote: Jonas, perhaps you answer these questions: - do you commit the quilt control directory .pc/? - do you commit the tree with patches applied? - if not, is everyone expected to run 'quilt pop -a' before committing changes to the tree? So there is your answer to the questions: No - I commit unapplied patches, not applied ones or quilt noise! Hm, but requires additional manual overhead to make sure that you don't commit noise. Does this really make packaging easier then? Sorry for the too short answer (thought I covered the details in my other mail fired off right before I saw tha above question) - let me try elaborate a bit more here too: First it was claimed that git-buildpackage did not work with the new source format. I believe that to be untrue (and suspect it to be a rumor held alive by developers that have not actually tried, and perhaps misunderstood and blown out of proprtions info like that bugreport from Colin). Here you raise the more relevant concern if the new format is beneficial or brings mors hassle. I certainly believe it it beneficial (and from that bugreport I get the impression that Colin feel the same - it is just a _wishist_ bug and he introduces by higly prising the new format in general): The distributed source is much easier to handle: a tarball of upstream source and another tarball of Debian source, rather than the latter being a diff - which in the case of changes to upstream source becomes convolutes diffs-inside-a-diff. some may not care, but personally I use Midnight Commander and frequently inspect source package contents by "browsing" it using the mc virtual filesystem feature, and here it is much more usable to browse actual files and diffs than diffs and diffs-of-diffs. Upstream source can be redistributed as-is even when in bzip2 format. Some may not care. but I happen to prefer using pristine tarballs whenever possible, and work towards automated ways of validating such pristine sources when upstream publishes checksums of them - something which obviously is impossible when repackaging or even generating a custom tarball from upstream VCS source. Build process need not be more hassle. Some may not care but I happen to _like_ switching back and forth between pristine source and source with patches applied. As I believe I wrote already in an earlier response, those wanting things as simple and automated as possible have several options: 1) request git-buildpackage to do the build in a separate directory to not mess with the Git tree 2) tell Git to ignore the .pc directory, and instead of invoking "debuild clean" instead invoke "debuild clean && quilt pop -a". If 2) is the preferred way, but still too much hassle, I would be happy to help design a smapp debuild wrapper script that seemlessly a) removes .pc dir if only containing dotfiles, and b) unpatches whenever cleaning. I would not use such script myself, because (as I wrote above) I happen to use it as a feature, no matter if that was the intend of it :-) I use git-buildpackage, not topgit! I don't understand this comment. Topgit managing each "change" as a branch (AFAIUI). Ah, sorry again for being to short: At some point (last spring, I believe it was), I investigated Topgit as an alternative to git-buildpage. One of my concerns was that I would then loose control over the patches: With topgit patches are intended to be dynamically generated. What is tracked in the VCS is the applied patches, while the isolated patches are only autogenerated on demand and cannot properly be maintained in the VCS. Oh well - this might very well be me not fully understanding the wonders of the Topgit appreach. I did not mean to expand the discussion here to include truths and rumors of Topgit - I just instinctively saw a parallel between the Topgit style and what seems to be your preferred style: Not track isolated patches in VCS but have them generated on-the-fly. Perhaps you would be interested in gbp-pq, added recently to git-buildpackage. More information here (as mentioned in its manpage): https://honk.sigxcpu.org/piki/development/debian_packages_in_git/ I have not used it myself (I am sceptical to the dynamic generation of patches) and suspect that it won't solve the noise with dpkg format 3.0, so just a side note... Sorry, I still think this mode of operation is pretty silly. I'd much prefer if the patches were maintained by git-buildpackage as proper git commits instead of text files. Upon source package generation, these commits need to be exported as quilt patches of course. This way, updating to a new upstream version would use git's conflict resolution mechanisms instead of quilt (which can only merge 2-way, git can do a 3-way merge). I guess o
Processing of jamin_0.97.14~cvs~81203-3_amd64.changes
jamin_0.97.14~cvs~81203-3_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: jamin_0.97.14~cvs~81203-3.dsc jamin_0.97.14~cvs~81203-3.debian.tar.gz jamin_0.97.14~cvs~81203-3_amd64.deb Greetings, Your Debian queue daemon (running on host ravel.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of audacity_1.3.12-1_amd64.changes
audacity_1.3.12-1_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: audacity_1.3.12-1.dsc audacity_1.3.12.orig.tar.bz2 audacity_1.3.12-1.debian.tar.bz2 audacity-data_1.3.12-1_all.deb audacity_1.3.12-1_amd64.deb audacity-dbg_1.3.12-1_amd64.deb Greetings, Your Debian queue daemon (running on host ravel.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of hydrogen_0.9.4.1-1_amd64.changes
hydrogen_0.9.4.1-1_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: hydrogen_0.9.4.1-1.dsc hydrogen_0.9.4.1.orig.tar.gz hydrogen_0.9.4.1-1.debian.tar.gz hydrogen_0.9.4.1-1_amd64.deb Greetings, Your Debian queue daemon (running on host ravel.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of gavl_1.1.2-2_amd64.changes
gavl_1.1.2-2_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: gavl_1.1.2-2.dsc gavl_1.1.2-2.diff.gz libgavl1_1.1.2-2_amd64.deb libgavl1-dbg_1.1.2-2_amd64.deb libgavl-dev_1.1.2-2_amd64.deb libgavl-doc_1.1.2-2_all.deb Greetings, Your Debian queue daemon (running on host ravel.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Processing of liblrdf_0.4.0-3_amd64.changes
liblrdf_0.4.0-3_amd64.changes uploaded successfully to ftp-master.debian.org along with the files: liblrdf_0.4.0-3.dsc liblrdf_0.4.0-3.debian.tar.gz liblrdf0-dev_0.4.0-3_amd64.deb liblrdf0_0.4.0-3_amd64.deb Greetings, Your Debian queue daemon (running on host ravel.debian.org) ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
Re: [SCM] Debian packaging for jack-audio-connection-kit branch, master.jackd2, updated. debian/1.9.4+svn3842-2-41-g15d16a4
On Fri, Apr 02, 2010 at 20:59:02 (CEST), Jonas Smedegaard wrote: > >>Jonas, perhaps you answer these questions: >> >> - do you commit the quilt control directory .pc/? >> >> - do you commit the tree with patches applied? >> >> - if not, is everyone expected to run 'quilt pop -a' before committing >> changes to the tree? > > So there is your answer to the questions: No - I commit unapplied > patches, not applied ones or quilt noise! Hm, but requires additional manual overhead to make sure that you don't commit noise. Does this really make packaging easier then? > I use git-buildpackage, not topgit! I don't understand this comment. Topgit managing each "change" as a branch (AFAIUI). >> Sorry, I still think this mode of operation is pretty silly. I'd much >> prefer if the patches were maintained by git-buildpackage as proper >> git commits instead of text files. Upon source package generation, >> these commits need to be exported as quilt patches of course. This >> way, updating to a new upstream version would use git's conflict >> resolution mechanisms instead of quilt (which can only merge 2-way, >> git can do a 3-way merge). >> >> I guess other VCS systems like hg or bzr at least try something in >> that directions (although I have to admit that I didn't follow the >> latest developments there). > > You are free to find git-buildpackage silly, and prefer different VCSes > altogether. This is not what I said, and granted, I shouldn't have used the word 'silly' but a less strong word. I think that Format 3.0 does not work well with git-buildpackage. At least, git-buildpackage should integrate more with dpkg so that unnecessary "commit noise" is avoided. > Am I free to not find it silly? As part of this team? I'd very much prefer to work on a consistent set of packages. Having some packages maintained in this and some in another way leads individuals to look and care only after a subset of our team's packages. -- Gruesse/greetings, Reinhard Tartler, KeyID 945348A4 ___ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/pkg-multimedia-maintainers
