Le 09/12/2018 à 04:18, Dmitry Bogatov a écrit :
> Package: devscripts
> Version: 2.18.11
> Severity: normal
>
> Dear Maintainer,
>
> I installed devscripts/experimental to get `salsa' script and did
> following:
>
> $ salsa fork lintian/lintian --verbose
>
> and got this:
>
> salsa error Unknown command fork
> salsa info: Can't locate Devscripts/Salsa/chechout.pm in @INC (you may need
> to install the Devscripts::Salsa::chechout module) (@INC contains: /etc/perl
> /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1
> /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5
> /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28
> /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at
> /usr/share/perl5/Module/Runtime.pm line 314.
> at /usr/share/perl5/Devscripts/Salsa/fork.pm line 9.
> Compilation failed in require at /usr/share/perl5/Module/Runtime.pm line 314.
Hello,
sorry for this stupid bug introduced during a function rename. Here is
the fix if you want to continue to test:
--- a/usr/share/perl5/Devscripts/Salsa/fork.pm
+++ b/usr/share/perl5/Devscripts/Salsa/fork.pm
@@ -6,7 +6,7 @@ use Devscripts::Output;
use Dpkg::IPC;
use Moo::Role;
-with 'Devscripts::Salsa::chechout';
+with 'Devscripts::Salsa::checkout';
sub fork {
my ($self, $project) = @_;
@@ -14,7 +14,7 @@ sub fork {
$self->api->fork_project($project, { namespace => $path });
my $p = $project;
$p =~ s#.*/##;
- $self->chechout($p);
+ $self->checkout($p);
chdir $p;
spawn(
exec => [
>
> According to salsa(1) it is valid:
>
> fork
> Forks a project in group/user repository and set "upstream" to
> original project. Example:
>
> $ salsa fork js-team/node-mongodb --verbose
> ...
> salsa.pl info: node-mongodb ready in node-mongodb/
> $ cd node-mongodb
> $ git remote --verbose show
> origin g...@salsa.debian.org:me/node-mongodb (fetch)
> origin g...@salsa.debian.org:me/node-mongodb (push)
> upstream g...@salsa.debian.org:js-team/node-mongodb (fetch)
> upstream g...@salsa.debian.org:js-team/node-mongodb (push)
>
> For a group:
>
> salsa fork --group js-team user/node-foo
>
> Oh, and by the way, it is quite unfortunate, that reportbug by default
> insert content of ~/.devscripts into bugreport. It could contain quite
> sensible SALSA_TOKEN. Not sure, whether it is bug in devscripts or
> reportbug.
Sure it's a bug. Report it against devscripts, then if needed we will
reassign it.
Thanks to take time to test salsa !
Cheers,
Xavier
