Quoting Christian PERRIER (bubu...@debian.org): > Quoting micah (mi...@riseup.net): > > > I've just gone through the ubuntu shadow package and pulled the pieces > > that Debian doesn't have and committed them to my local clone of the > > shadow repository. Because I don't have access to push to shadow, I've > > sent those patches to this bug report. > > > > If it is easier for me to push these somewhere so you can pull my > > remote, i'm happy to do that, just let me know! > > Well: You've just been added to pkg-shadow on Alioth, Micah..;-) > > So, in short: please push your changes to the main git repo and either > I can try to find some time to build and upload the package...or feel > free to do it....
OK, so you did..:-) Now, we have another problem. The master branch is about packaging new "upstream" 4.2. However, pristine-tar and upstream branches are still imports from the Debian package and, therefore, are 4.1.5.1 So, someone needs to "release" a 4.2 tarball....and the only place to do this from is, if I'm correct, the master branch : in short, dropping debian/ and .git/ from there, cook up a tarball, call it 4.2 and then import it into upstream and pristine-tar. Is there a cleaner way to do this?
signature.asc
Description: Digital signature
