Re: VCS warnings

[Sergio Durigan Junior]

On Wednesday, December 12 2018, Andrey Rahmatullin wrote:

> On Wed, Dec 12, 2018 at 02:58:20PM -0500, Sergio Durigan Junior wrote:
>> >> I'm fixing the packaging of guile-cairo. I get the following warnings and
>> >> notes related to the VCS fields: vcs-obsolete-in-debian-infrastructure,
>> >> vcs-field-not-canonical, and vcs-field-uses-insecure-uri. Shall I ignore
>> >> these or remove the VCS fields from debian/control?
>> > If you use a VCS you should put the VCS info into these fields, otherwise
>> > you should remove them. I don't see a reason to ignore the warnings.
>> 
>> May I expand this a bit a say "otherwise, you should put your package on
>> Salsa and update the fields accordingly"?  There are fewer things more
>> frustrating than a package that doesn't use a VCS.
> Indeed, but I'm not sure what we think of putting unreleased packages to
> Salsa. OTOH one can always put them into their private namespace.
> ALso, if this is a package that existed only on Alioth and was never
> migrated, or if it WAS migrated, it's even more complicated...

Yeah, what I usually suggest for sponsees is to put the first version of
the unreleased package into their own namespaces, and switch to the
official "debian" namespace when the package gets accepted.

When the package was on Alioth but was never migrated, one could check
the Alioth archives and see if it's there.  Let me see...

... Yep, apparently it's there:

  https://alioth-archive.debian.org/git/collab-maint/guile-cairo.git.tar.xz

It should be easy to download the tarball and import the repo from salsa
afterwards.  I think this is the best approach in this case.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Re: VCS warnings

[Andrey Rahmatullin]

On Wed, Dec 12, 2018 at 02:58:20PM -0500, Sergio Durigan Junior wrote:
> >> I'm fixing the packaging of guile-cairo. I get the following warnings and
> >> notes related to the VCS fields: vcs-obsolete-in-debian-infrastructure,
> >> vcs-field-not-canonical, and vcs-field-uses-insecure-uri. Shall I ignore
> >> these or remove the VCS fields from debian/control?
> > If you use a VCS you should put the VCS info into these fields, otherwise
> > you should remove them. I don't see a reason to ignore the warnings.
> 
> May I expand this a bit a say "otherwise, you should put your package on
> Salsa and update the fields accordingly"?  There are fewer things more
> frustrating than a package that doesn't use a VCS.
Indeed, but I'm not sure what we think of putting unreleased packages to
Salsa. OTOH one can always put them into their private namespace.
ALso, if this is a package that existed only on Alioth and was never
migrated, or if it WAS migrated, it's even more complicated...

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: VCS warnings

[Sergio Durigan Junior]

On Wednesday, December 12 2018, Andrey Rahmatullin wrote:

> On Wed, Dec 12, 2018 at 03:46:32PM +0200, Tommi Höynälänmaa wrote:
>> 
>> I'm fixing the packaging of guile-cairo. I get the following warnings and
>> notes related to the VCS fields: vcs-obsolete-in-debian-infrastructure,
>> vcs-field-not-canonical, and vcs-field-uses-insecure-uri. Shall I ignore
>> these or remove the VCS fields from debian/control?
> If you use a VCS you should put the VCS info into these fields, otherwise
> you should remove them. I don't see a reason to ignore the warnings.

May I expand this a bit a say "otherwise, you should put your package on
Salsa and update the fields accordingly"?  There are fewer things more
frustrating than a package that doesn't use a VCS.

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


signature.asc
Description: PGP signature

Re: VCS warnings

[Jason Crain]

On 2018-12-12, Tommi Höynälänmaa  wrote:
> 
> I'm fixing the packaging of guile-cairo. I get the following warnings and
> notes related to the VCS fields: vcs-obsolete-in-debian-infrastructure,
> vcs-field-not-canonical, and vcs-field-uses-insecure-uri. Shall I ignore
> these or remove the VCS fields from debian/control?
> 
>  - Tommi Höynälänmaa
> 

git.debian.org and Alioth were discontinued a while ago so you should
remove those URLs from debian/control. If you are using some other site
to host a packaging repository, update the URLs to point at that
location. Debian has a GitLab instance at salsa.debian.org which you can
use. And try to use a 'https' url instead of 'http' in these fields.

Re: VCS warnings

[eamanu15]

Tommi,

I think that your problem is because the package must be on salsa repo. I
recommend create the repo on salsa, you will have to search someone who can
give you access. Then, you must update the vcs field on your d/control.

Cheers,


El mié., 12 de dic. de 2018 a la(s) 11:19, Tommi Höynälänmaa (
tommi.hoynalan...@gmail.com) escribió:

> The package is probably not on salsa. I just adopted the package so I'm
> not sure. The URL of guile-cairo is:
>
> https://www.nongnu.org/guile-cairo/download/
> It seems that the uscan links in the package are outdated.
>
>  - Tommi
>
> On 12.12.2018 16:09, eamanu15 wrote:
>
> Do you have the package on salsa? I am asking to see it try to help you
>
> El mié., 12 de dic. de 2018 a la(s) 11:03, Tommi Höynälänmaa (
> tommi.hoynalan...@gmail.com) escribió:
>
>>
>> I'm fixing the packaging of guile-cairo. I get the following warnings
>> and notes related to the VCS fields:
>> vcs-obsolete-in-debian-infrastructure, vcs-field-not-canonical, and
>> vcs-field-uses-insecure-uri. Shall I ignore these or remove the VCS
>> fields from debian/control?
>>
>>   - Tommi Höynälänmaa
>>
>>
>
> --
> Arias Emmanuel
> http://eamanu.com
> Github/Gitlab; @eamanu
> Debian: @eamanu-guest
>
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: VCS warnings

[Tommi Höynälänmaa]

The package is probably not on salsa. I just adopted the package so I'm 
not sure. The URL of guile-cairo is:


https://www.nongnu.org/guile-cairo/download/

It seems that the uscan links in the package are outdated.

 - Tommi

On 12.12.2018 16:09, eamanu15 wrote:

Do you have the package on salsa? I am asking to see it try to help you

El mié., 12 de dic. de 2018 a la(s) 11:03, Tommi Höynälänmaa 
(tommi.hoynalan...@gmail.com ) 
escribió:



I'm fixing the packaging of guile-cairo. I get the following warnings
and notes related to the VCS fields:
vcs-obsolete-in-debian-infrastructure, vcs-field-not-canonical, and
vcs-field-uses-insecure-uri. Shall I ignore these or remove the VCS
fields from debian/control?

  - Tommi Höynälänmaa



--
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: VCS warnings

[Andrey Rahmatullin]

On Wed, Dec 12, 2018 at 03:46:32PM +0200, Tommi Höynälänmaa wrote:
> 
> I'm fixing the packaging of guile-cairo. I get the following warnings and
> notes related to the VCS fields: vcs-obsolete-in-debian-infrastructure,
> vcs-field-not-canonical, and vcs-field-uses-insecure-uri. Shall I ignore
> these or remove the VCS fields from debian/control?
If you use a VCS you should put the VCS info into these fields, otherwise
you should remove them. I don't see a reason to ignore the warnings.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Re: VCS warnings

[eamanu15]

Do you have the package on salsa? I am asking to see it try to help you

El mié., 12 de dic. de 2018 a la(s) 11:03, Tommi Höynälänmaa (
tommi.hoynalan...@gmail.com) escribió:

>
> I'm fixing the packaging of guile-cairo. I get the following warnings
> and notes related to the VCS fields:
> vcs-obsolete-in-debian-infrastructure, vcs-field-not-canonical, and
> vcs-field-uses-insecure-uri. Shall I ignore these or remove the VCS
> fields from debian/control?
>
>   - Tommi Höynälänmaa
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest