Request for upload: supercollider 3.5.3 new version

Jonas Smedegaard dr at jones.dk
Sun Jun 24 20:21:42 UTC 2012


On 12-06-24 at 12:57pm, Felipe Sateler wrote:
> On Sun, Jun 24, 2012 at 9:56 AM, Jonas Smedegaard <dr at jones.dk> wrote:
> > On 12-06-24 at 11:05am, Dan S wrote:
> >> SuperCollider 3.5.3 is now out. This comes very soon after we got 
> >> 3.5.2 into the debian repo, so no rush - but this release fixes a 
> >> couple of bugs and upstreams most of our patches (hooray). The diff 
> >> against 3.5.2 is fairly simple so I don't foresee controversy. If 
> >> anyone feels like pushing this one then please feel free.
> >
> > I am looking at it now...
> >
> > Regarding earlier released 1:3.5.2-1:
> >
> >  * the changelog entries should have been merged for unreleased   
> >    packaging versions.
> 
> I'm not sure this is really necessary. But this is of course personal 
> preference. I prefer to show real history in the changelog.

To me, "real history" is changes from one packaging release to the next.

Changes not part of an official packaging release e.g. because it was 
rolled back again or shadowed by other changes is not "real history" in 
the context of debian/changelog.

(it is "real history" in the context of git log, but that is a different 
story).



> >  * Commit 25aee8 ("Import and adapt debian packaging...") touched
> >    all but 5 lines of the rules file and therefore really was a
> >    major rewrite of packaging and should have been described as
> >    such.
> 
> Indeed. However, strictly speaking the description is true. SC 3.5
> involved large changes relative to 3.4: the build system changed from
> scons to cmake, the server was renamed to supernova, and the layout of
> files was changed. Most of the changes in the rules file in that
> commit involve the switch from scons to cmake, and dropping
> scons-related workarounds. Therefore "adapt debian packaging for 3.5"
> is pretty much the description of what's being done.

Then let me rephrase:

I would dearly appreciate if large changes was clearly described as such 
in debian/changelog, and preferably also committed as smaller chunks to 
ease following what is really going on.

In this concrete case, it was not documented (or "strictly speaking" it 
was not obvious to *me*) that the change involved dropping copyright 
tracking.


> > As I understand it, Dan is not a DD or DM, which means someone else 
> > approved the above.  It seems to be Felipe Sateler, but finding that 
> > out requires detective work, which is bad IMO :-(
> >
> > Project-wide there are several ways to act as proxy for a non-DD/DM, 
> > some of which makes the the responsible party more visible than 
> > others.
> >
> > Can we please in this team mandate that the actual uploader of a 
> > packaging release is listed in the final line of the changelog 
> > entry?
> 
> Yes, it was me. For this team, we already have the information since 
> our policy is that the uploading DD/DM signs the debian/* tags. 
> debian/3.5.2-1 is signed by me.
> I prefer (as I have stated before) to have the person mostly 
> responsible for /preparing/ the upload in the changelog signature.

Oh, sorry I bother you with things you've already refused before.

Let me then rephrase:

@Everyone but Felipe: I strongly urge you to please consider the style 
of putting the actual current signing uploader into the final line of 
the changelog entry, to make it more clear who did what.

If person A did all packaging changes and all you do is verify, sign and 
upload, then this makes it clear in changelog who did what:

  [ Person A ]
  * Some change.
  * Another change.

  -- Person B <some.mail at address>  time-of-this edit


Regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20120624/9865079d/attachment-0001.pgp>


More information about the pkg-multimedia-maintainers mailing list