Hi, At Sat, 28 Jan 2012 18:02:24 +0100, Lucas Nussbaum <[email protected]> wrote: > > On 21/01/12 at 03:26 +0900, Youhei SASAKI wrote: > > There are 2 problems... > > > > - Currently, the old (transitional) packages and new package has same > > version number. How do we treat it? > > Version it 2.1.1.1-2, so that everything works fine for binary packages.
Thanks. I set version number to 2.1.1.1-2 > > - The upstream author release *same* source with different version > > number. One is 2.1.1.1 at rubyforge.org, the other is 2.1.1 at > > rubygems.org. > > Let's use 2.1.1.1 so that it's greater than the previous version in > Debian Ok. If bump up upstream gem's version number, we should change debian/watch. > There seems to be something broken with the git repo. The master branch > diverges from the upstream branch, and pristine-tar fails to generate > the orig.tar.gz file. I'm very sorry, I forgot push tags "upstream/2.1.1.1". I commit it. Best Wishes, --- Youhei SASAKI <[email protected]> <[email protected]> GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/87sjizofia.wl%[email protected]
