Package: mr
Version: 1.00
Severity: normal

I concur to Lars suggestion. Now that D-I switch to a multiple git
repo, I get something like this when running my cronned "mr -p -q
update":

cperrier@mykerinos:~/src/debian/debian-installer/trunk$ mr -q -p update
U    manual/cs/appendix/preseed.xml
U    packages/po/sublevel1/ru.po
Actualisé à la révision 66294.
Already up-to-date.
Already up-to-date.
Already up-to-date.
Already up-to-date.
.../...

In this case, of course, I expect the first lines to display....but th
emain problem are the "Already up-to-date" lines (which can be removed
with "git pull -q").


-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

mr depends on no packages.

Versions of packages mr recommends:
ii  libhtml-parser-perl           3.68-1     collection of modules that parse H
ii  libwww-perl                   5.837-1    simple and consistent interface to
ii  perl                          5.10.1-17  Larry Wall's Practical Extraction 

Versions of packages mr suggests:
ii  bzr                        2.3.0~beta3-1 easy to use distributed version co
ii  curl                       7.21.3-1      Get a file from an HTTP, HTTPS or 
ii  cvs                        1:1.12.13-12  Concurrent Versions System
ii  darcs                      2.4.4-3       a distributed, interactive, smart 
pn  fossil                     <none>        (no description available)
ii  git [git-core]             1:1.7.2.3-2.2 fast, scalable, distributed revisi
ii  liburi-perl                1.56-1        module to manipulate and access UR
ii  mercurial                  1.6.4-1       scalable distributed version contr
ii  subversion                 1.6.12dfsg-4  Advanced version control system

-- no debconf information



--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to