File: README.source

package info (click to toggle)
musescore 2.0.3%2Bdfsg1-2
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 202,532 kB
  • ctags: 58,769
  • sloc: cpp: 257,595; xml: 172,226; ansic: 139,931; python: 6,565; sh: 6,383; perl: 423; makefile: 290; awk: 142; pascal: 67; sed: 3
file content (26 lines) | stat: -rw-r--r-- 1,200 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
  IMPORTING NEW UPSTREAM RELEASES:
  Upstream tracks bugs against the Git short commit number (first 7 digits of
  upstream commit SHA). This is the "revision" displayed in MuseScore's Help ->
  About dialog. This number is stored in the file mscore/revision.h and must be
  set in the upstream code *after* importing a new upstream version. This is
  done automatically if the new version is imported via `gbp import-orig`,
  `uscan` or `debian/rules get-orig-source`. The easiest way to update is:

    $ gbp import-orig --uscan

  What this command does:

   1) Checks debian/gbp.conf for various options, then calls `uscan`.

   2) 'uscan' fetches the upstream tarball, removes files listed under
      "Files-Excluded" in debian/copyright, and then runs debian/repack.

   3) debian/repack checks for DFSG compliance and sets the revision number.

   4) gbp unpacks the tarball, updates debian/changelog, commits the changes.

  If you don't have gbp just run 'uscan --verbose', then delete everything in
  the repo (except for the "debian" and ".git" directories) and then unpack the
  dfsg tarball into the repo. Update the changelog. Commit the changes.

 -- Peter Jonas <pjonas56@gmail.com>