Introduction and vcs-pkg.org/people/ pages

there, which IkiWiki should do for you, but I think I've hit a bug. Well, it's all there on the page... If there are problems, please let me know. (also, if someone wants to actually make the page template and CSS pretty, talk to me.) -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian

Re: Introduction and vcs-pkg.org/people/ pages

also sprach Jesse Keating [EMAIL PROTECTED] [2008.03.17.2159 +0100]: Also, the template has Fedora as a tag, but the front page is looking for fedora as a tag. I changed my page manually. Fixed, although tags are case-insensitive, which I didn't know. -- .''`. martin f. krafft [EMAIL

Re: Requirements of a VCS packaging tool

this document will be entirely complete, please add anything else that you think is important. I made it a wiki page for this purpose: http://vcs-pkg.org/requirements/ -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http

direct ikiwiki repo access and alioth accounts

out commit access to interested people. Get yourself a new account http://alioth.debian.org/account/register.php and then follow this link: http://alioth.debian.org/project/request.php?group_id=100107 Cheers, -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer

Re: Branches to patches

, throwaway branch. It is *not* suitable for cooperation. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing

Re: How to handle Debian patches

currently swamped and can't read along. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems perl -e

Re: Extremadura work session in September

also sprach martin f krafft [EMAIL PROTECTED] [2008.05.18.1512 +0200]: Since we couldn't meet in April [0] (it was too short notice), we now have another chance from 2-7 September 2008 to meet in Extremadura and concentrate on getting vcs-pkg further. 0. http://lists.alioth.debian.org

Re: how to generate patches out of $DVCS branches: best practices?

has a README.source, and I'd love comments, especially how to improve the process: http://git.debian.org/?p=collab-maint/topgit.git;a=blob;f=debian/README.source;hb=HEAD -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user

Re: Introductory mail

offline, while the new query behavior would require network connection ... ... remind me again why we shouldn't just introduce Vcs-TopGit? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck

Re: Introductory mail

that this is the way to go, only time will tell which approach(es) are the successful ones. I'd love to see some standardisation across distros at some point. If we want to continue to scale, I think that's the way forward... -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author

patch series does not make VCS obsolete (was: Introductory mail)

, and the v3 quilt format will even make that unnecessary; - still allows you to keep using your treasured VCS - still allows everyone to inspect the history in your VCS, or use it instead of the source package. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer

v3 Debian source package formats (was: Introductory mail)

which source package format will become standard in Debian for squeeze or squeeze+1, I'd have to say v3 quilt, for *sure*. The git/bzr were nice ideas but are never going to make it, IMHO. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator

the goal of vcs-pkg (was: v3 Debian source package formats)

PROTECTED] -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems literature always anticipates life

debian/topics and conflict resolution (was: v3 Debian source package formats)

the orig.ar.gz and each of these patches, one can exactly replicate the tip of all the branches in use. Who resolved conflicts, if the serialisation (== conflict resolution) is expressively *not* done before building the source package? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud

Re: the goal of vcs-pkg

. It also introduces 100% redundancy into the source package, no? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than

commit IDs in changelog messsages (was: Introductory mail)

? -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info `- Debian - when you have better things to do than fixing systems women can keep a secret just as well as men

Re: commit IDs in changelog messsages (was: Introductory mail)

not have knowledge about each VCS (which I think is the design error you mention), so the benefit would stay 0. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author, administrator, and user `. `'` http://people.debian.org/~madduck - http://debiansystem.info

Re: Debian packaging with git and conflicts resolution

-living build branch into which you keep merging. git-rerere might be helpful. I think in general it would be better to avoid the situation altogether, simply by not introducing cycles into the merge trees. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud Debian developer, author

Re: exporting patches like bitkeeper

and into which you cherry-pick that which you want. In that case, I'd think that a branch dependency hierarchy managed by TopGit would be more manageable. I'd love to clone a repo where you make use of this to understand your steps better. Cheers, -- .''`. martin f. krafft [EMAIL PROTECTED

Rewriting history and TopGit (was: Debian packaging with git and conflicts resolution)

(which *never* rewrites history and builds on the premise that nothing else does[*]). [*] obviously, nothing is there to be said against git commit --amend or rebase -i to reorganise commits on branch heads that have not been published. -- .''`. martin f. krafft [EMAIL PROTECTED] : :' : proud

vcs-pkg.org now supports attachments (was: vcs-pkg.org infrastructure)

also sprach Adeodato Simó [EMAIL PROTECTED] [2008.11.22.1838 +0100]: * attachment: New plugin for uploading and managing attachments. This is now enabled on vcs-pkg.org with a maxsize of 50Kb and limited to image/* and text/* mime types. -- .''`. martin f. krafft [EMAIL PROTECTED

instances of cooperation between distros

Hey folks, Do you know of any instances of cross-distro collaboration where the VCS is shared between packagers? Have any of you reached out to other distros' packagers? Would you share your experiences? Cheers, -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud

Re: Debconf

of the RedHat/Fedora, Suse, Arch, Gentoo, YourDistroHere people interested? -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have

Re: Introducing myself

of working on svn-bp, you'd be interested in helping to make the above happen, then I think you should. I'll gladly assist wherever I can. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http

Re: Debconf

in. Good luck with your defence, Donnie. It'll be my time around then too, but I don't yet have a date. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org

Re: Debconf

(it's my first time ;-)). If it's not decided, I suggest you register anyway; you can always pull out again later. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck

Re: Debconf

know what merges are. They pretend to merge, and SVN 1.5 even pretends to keep track of what it merges, but in the end it just stays brittle IME. YMMV of course. Lack of merging could get in the way, if we decided to make merges an integral part of the workflow. -- .''`. martin f. krafft madd

Re: Debconf

to cast doom over SVN Co. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems

Re: Dealing with autotools

instead of patches. To me, it sounds like those are exactly our goals, so it seems as if build-depending on the autotools is the right way forward. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info

Re: TopGit: Is there still a need for a long-lived build branch?

to make time for it. If you want to have a shot, count me in on supporting you and helping out with explanations of TopGit internals, feedback, and ideas (if you want them). -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http

Re: TopGit: Is there still a need for a long-lived build branch?

this could also be useful for backports and security updates? (OTOH, I'm not particularly looking forward to having even more top-* refs that I'll forget to push...) You know you can set it up to auto-push, right? ;) -- .''`. martin f. krafft madd...@d.o Related projects

Re: TopGit: Is there still a need for a long-lived build branch?

a wishlist bug or bring it up on the mailing list? -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do

Re: TopGit: How to retire obsolete topic branches?

if this wouldn't make sense to be raised with the Git people. Comments welcome, of course. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when

deleting branches (was: TopGit: How to retire obsolete topic branches?)

also sprach martin f krafft madd...@debian.org [2009.05.09.1113 +0200]: b. teach Git how to retire/rename published branches I'll think about (b) for a bit and see if this wouldn't make sense to be raised with the Git people. Comments welcome, of course. http://colabti.org/irclogger

Re: Features of different version control package systems

not sure what you mean. Could you give an example or hypothetical scenario? -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have

Re: Dealing with autotools

summary and mixed with my opinion. Feel free to disagree and voice your counter-arguments! -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org

Re: Dealing with autotools

input! -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems dies ist eine manuell

Re: Dealing with autotools

that building from a VCS tag has the desired effect. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do

Re: Dealing with autotools

, and the VCS source is properly tagged, but SVN:keywords are in use. So if I build against VCS and create the Debian diff against the pristine tarball, the Debian diff will /revert/ $Id:$ expansions, e.g. - $Id: author date snapshot whatever$ + $Id:$ which isn't ideal either. -- .''`. martin f

Re: TopGit: Is there still a need for a long-lived build branch?

then file a wishlist against topgit, to replace the last Push: * line with : instead. As I stated in #528442, TopGit is currently growing a tg-push command, which should make those pushspecs obsolete. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer

Re: Using quilt to store patches

arguments. I'll need to try this approach Mehdi presented, unless any of you feel like providing a short run-down with examples. I don't think I can quite visualise it yet, especially not in a team context. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer

Fwd: [RFC][StGit PATCH] Add support for merge-friendly branches

-list $old_public..$new_public | wc -l) = 1 + ' + +test_done -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have

working the wiki (was: Building src.rpm from git/svn)

, rather than some sort of unusable, internal format (e.g. MoinMoin or Wikimedia). -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when

a workflow based on rebasing? (was: RFC: DEP-3: Patch Tagging Guidelines)

/pipermail/vcs-pkg-discuss/2009-May/000616.html, I'd love to see a detailed account of your workflow. I am failing to wrap my head around how it would work and would appreciate being able to learn from you. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer

RFC: vcs-pkg pre-discussion Sunday 22:00

also sprach martin f krafft madd...@debian.org [2009.07.21.1231 +0200]: Would someone (who agrees) please volunteer to organise this? Someone did. https://penta.debconf.org/penta/schedule/dc9/event/506.en.html That's on Sunday night, starting at 22:00 in the upper talk-room. Dinner supposedly

The five points raised in the vcs-pkg prep BoF

in the BoF room. -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems

Re: output from the vcs-pkg BoF @DebConf9

also sprach Manoj Srivastava sriva...@acm.org [2009.08.04.1859 +0200]: martin f krafft madd...@debconf.org wrote: The workflows I know currently are: my topgit workflow, Mehdi's quilt workflow, and Guido's git-buildpackage approach. There my be others. I am pretty sure

Re: rethinking patch management with GIT / topgit

to hear more about what you propose. Have you considered writing this up as a paper or website with graphs to help us get a better idea of who you'd implement this, and how users are supposed to use this solution? -- .''`. martin f. krafft madd...@d.o Related projects: : :' : proud Debian

git-flow

Dear folks, in case you missed this, it's worth a look (although I have not yet checked out the actual tool): http://jeffkreeftmeijer.com/2010/why-arent-you-using-git-flow/ -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http

Branch dependencies with Git hooks

a discussion about this. Cheers, -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing

Re: Patch mgmt workflow proposal

also sprach Thomas Koch tho...@koch.ro [2011.07.30.1229 +0200]: Martin F. Krafft (madduck) was so kind to remind me posting this here. We're right now at debconf discussing different patch mgmt workflows. Thanks to contributions from Joachim Breitner and Guido Günther I've written down

Re: Patch mgmt workflow proposal

://www.spinics.net/lists/git/msg162549.html is shaping up to be interesting. -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when

Re: Patch mgmt workflow proposal

by the user. Why is it a plus? If you already applied all changes, why bother exporting the patches? Thanks for your time, -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduck

Re: Patch mgmt workflow proposal

of a branch's dependencies. -- .''`. martin f. krafft madduck@d.o Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems