logilab-devtools #9015 clumsy behaviour of the --orig-tarball option [resolved]
E:build: the provided tarball (logilab-mtconverter_0.6.0.orig.tar.gz) has not the expected filename (logilab-mtconverter-0.6.0.tar.gz) | |
| priority | important |
|---|---|
| type | bug |
| done in | 0.14.0 |
| load | 0.100 |
| load left | 0.000 |
| closed by | <not specified> |
similar entities
- logilab-devtools #5032 piuparts checker fails
- logilab-devtools #6273 Add Ubuntu distribution support
- apycot-moved #22622 Improve log parsing of lgp build
- logilab-devtools #6305 Add maintenance utility lgp setup
- logilab-devtools #9033 sortir les checks pour les rendre accessibles par appels systèmes
[see all]
Comments
-
2009/04/14 09:06
-
2009/04/14 09:23, written by nchauvat
-
2009/04/14 09:29, written by anon
-
2009/04/14 09:24, written by anon
add commentIf I recall correctly, this is because what we really want to use is the tarball publicly available from Logilab's FTP. This tarball is internally generated from the orig.tar.gz created by lgp by www-sync.sh.
Now, if we accept a .orig.tar.gz tarball, we can't be sure that it is not another tarball, and if that tarball doesn't have the same checksum as the one in the repository, it will cause problems, such as apt-get source refusing to work.
I'm not sure how this should be handled.
it is actually ~logilab/www/update-ftp.py that is called by www-synch and reuses .orig.tar.gz
juj: for our internal needs, we could use the .hg_archival.txt file to disambiguate the situation ?
juj: I think about a buggy version of lgc here. 0.13.6 (mercurial) should resolve this.
The rule should to permit the both filenames (logilab-mtconverter_0.6.0.orig.tar.gz, logilab-mtconverter-0.6.0.tar.gz) with a preference for the former (add a warning message).