Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18521 - {wsvn} diff from previous version sometimes works sometimes fails

Attached to Project: Arch Linux
Opened by solsTiCe (zebul666) - Monday, 01 March 2010, 23:53 GMT
Last edited by Dan McGee (toofishes) - Tuesday, 02 March 2010, 13:22 GMT
Task Type Bug Report
Category Web Sites
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

In SVN repo web interface for package on archlinux.org, depending on the package one can have the diff from previous or not.
when it works one have to do it the right way: follow the correct set of links not to have an empty page for the diff from previous version.
and for some package it does not work while for others it works.

it's a mess to use.

This task depends upon

Closed by  Dan McGee (toofishes)
Tuesday, 02 March 2010, 13:22 GMT
Reason for closing:  Not a bug
Additional comments about closing:  It's SVN, it has weirdness with copying, but it is doing exactly what we expect.
Comment by Dan McGee (toofishes) - Tuesday, 02 March 2010, 00:33 GMT
  • Field changed: Summary ({archweb} diff from previous version sometimes works sometimes fails → {wsvn} diff from previous version sometimes works sometimes fails)
  • Field changed: Details
  • Field changed: Status (Assigned → Unconfirmed)
  • Assignment removed
Gerardo- I do not just magically handle all website related bugs because I work on the front page.
Comment by Dan McGee (toofishes) - Tuesday, 02 March 2010, 00:34 GMT
This is one of the worst bug reports I have seen in a while. Where are the links to examples? Are you looking at one architecture or trunk? Community, core, extra, testing, etc?
Comment by solsTiCe (zebul666) - Tuesday, 02 March 2010, 09:50 GMT
ok. sorry but this is quite obvious if you browse the svn repo
core, i686, dcron

http://repos.archlinux.org/wsvn/packages/?op=comp&compare[]=/dcron/repos/testing-i686/PKGBUILD@63922&compare[]=/dcron/repos/core-i686/PKGBUILD@65208
http://repos.archlinux.org/wsvn/packages/dcron/repos/core-i686/PKGBUILD?op=diff&rev=0

it seems to work on [trunk]. then why not only include trunk in the web interface ? it's the only one that matter
Comment by Dan McGee (toofishes) - Tuesday, 02 March 2010, 13:22 GMT
Well "obvious" has a few other uses, like it is "obvious" you are doing it wrong.

Link 1 is telling you *exactly what you wanted to see*- that the package in [testing] at that revision was the same as the package in [core] at a later revision. SVN has a copy/branch concept so it is not showing you any differences because one was a copy of the other.
Link 2 is telling you that the latest revision doesn't have a diff (due to the copy thing mentioned above). However, you can find plenty of revision compares that do if you hand-select two revisions: http://repos.archlinux.org/wsvn/packages/?compare[]=%2Fdcron%2Frepos%2Fcore-i686%2FPKGBUILD%4070382&compare[]=%2Fdcron%2Ftrunk%2FPKGBUILD%4067372&comparesubmit=Compare+Revisions&op=comp

"It's the only one that matter". That is quite far from true- I'm sure plenty of people care about things other than the diffs, which makes those views just as useful as trunk.

Loading...