Re: VCS repositories

[Aurélien COUDERC]

Le 29/05/2018 à 08:18, Warlich, Christof a écrit :
> 
> I'm a bit desperate to find out how the Debian project maintains its patches
> w.r.t. upstream repositories.

More of a side-answer but I recently discovered plotchangelog from the
devscripts package and found it cool.
It gives an interesting upstream vs. debian vs. time representation.


Cheers,
--
Aurélien

Re: VCS repositories

[Warlich, Christof]

Dear Gregor, dear Russ,

many thanks for your help, that's even much better than the information I was 
hoping for :-). Particularly the sources API and dgit are real gems that I 
would probably not have found myself.

Cheers,

Chris

Re: VCS repositories

[Russ Allbery]

"Warlich, Christof"  writes:

> I'm a bit desperate to find out how the Debian project maintains its
> patches w.r.t. upstream repositories. Thus, while I can explore the
> _current_ patches of a package by looking at the
> "*.debian.tar.gz"-archive after obtaining its sources through "apt-get
> source ", I'd be rather interested in both history and
> future of these patches along the lifetime of a Debian releases'
> maintainance period.

I suspect you may be looking for dgit, which exposes the history of a
package as a Git repository.  For maintainers that also use Git and make
dgit-aware uploads, this will be the full Git history; for packages whose
maintainers don't use dgit for whatever reason, it will just have one
revision per upload to the archive.  But that may still be enough
granularity for your purposes.

If you install dgit and then run man dgit-user, hopefully that should get
you started.

-- 
Russ Allbery (r...@debian.org)   

Re: VCS repositories

[gregor herrmann]

On Tue, 29 May 2018 06:18:44 +, Warlich, Christof wrote:

> I'm a bit desperate to find out how the Debian project maintains
> its patches w.r.t. upstream repositories. Thus, while I can explore
> the _current_ patches of a package by looking at the
> "*.debian.tar.gz"-archive after obtaining its sources through
> "apt-get source ",  I'd be rather interested in both
> history and future of these patches along the lifetime of a Debian
> releases' maintainance period.

That's indeed not that easy.
Apart from "apt-get source " ...
 
> At the first glance, things look quite straight forward: Starting
> with, say, the "glibc"-package, an "apt-get source glibc" tells me
> that I may get the git repo of the related Debian patches by
> cloning https://anonscm.debian.org/git/pkg-glibc/glibc.git. But as
> it turns out, this (and some other Debian) hosts went offline as
> they are being replaced by https://salsa.debian.org. So I finally
> get what I am looking for by cloning
> https://salsa.debian.org/glibc-team/glibc.git. Great.

... VCS repositories might exist. Unfortunately, as you noticed, the
information about them is kept in debian/control in the source
package which means that it can get outdated. - If you want to find
out repo locations, besides looking into the source package and using
the already mentioned debcheckout, the values are also published on
tracker: e.g. https://tracker.debian.org/glibc

Another useful resource besides snapshots.d.o is sources.debian.org,
e.g. for binutils: https://sources.debian.org/src/binutils/

sources.d.o also exposes patches directly, e.g.
https://sources.debian.org/patches/binutils/ or for the version in
sid https://sources.debian.org/patches/binutils/2.30-20/

And there's also an API; cf. https://sources.debian.org/doc/url/ and
https://sources.debian.org/doc/api/

> So finally, here is my question: When may I expect that
> VCS-repositories for all Debian packages may be available through
> https://salsa.debian.org (including updates of the packages to
> point to the new repository location on https://salsa.debian.org as
> printed by "apt-get source")

These very good questions hint at at least 2 problems:
- The one mentioned above that the Vcs-* info is kept in the source
  package and is therefor only updated in a new upload.
- The more general one:
  There is no requirement for maintainers to keep their source
  packages in git on salsa.
  There is no requirement for maintainers to keep their source
  packages in git in general.
  There is no requirement for maintainers to keep their source
  packages in any VCS at all.
  As long as this policy doesn't change the only canonical location
  for source packages is the archive itself, and apt-get source and
  sources.d.o the only reliable interfaces.


Cheers,
gregor

-- 
 .''`.  https://info.comodo.priv.at -- Debian Developer https://www.debian.org
 : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D  85FA BB3A 6801 8649 AA06
 `. `'  Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation Europe
   `-   NP: Ludwig Hirsch: Tante Marie


signature.asc
Description: Digital Signature

Re: VCS repositories

[Warlich, Christof]

> I think original poster is unaware of `debcheckout` from
> the package `devscripts`.

Yes, I wasn't aware of neither debcheckout.nor debsnap.
Looks like the devscripts package is a teasure trove of
useful scripts, many thanks for that pointer.

> > In case of binutils that will not help:
> > ...
> > > Ops, that's actually due to missing bzr :)
> > >
> > > Well, with installed bzr the result is quite the same due to missing repo.

The issue with missing repos or not updated repo entries
seems to be more general: 

$ debcheckout glibc
declared git repository at https://anonscm.debian.org/git/pkg-glibc/glibc.git
git clone https://anonscm.debian.org/git/pkg-glibc/glibc.git glibc ...
Cloning into 'glibc'...
fatal: repository 'https://anonscm.debian.org/git/pkg-glibc/glibc.git/' not 
found
checkout failed (the command above returned a non-zero exit code)

As I pointed out in my initial post already, I could find the repo on salsa
(https://salsa.debian.org/glibc-team/glibc.git), but if I was not just only
Unlucky, it looks like missing repos (as for the binutils package) or dangling
links (as for the glibc package) seems to be a rather common issue, geatly
deprecating the usefulness of such a useful tool like debcheckout. Is there
any hope that this is being addressed in the forseeable future, maybe while
doing the transition of repos to https://salsa.debian.org?

And finally: Is there any chance to find the binutils package somewhere
else?

Again, many thanks for your valuable help,

Chris

Re: VCS repositories

[Alex Mestiashvili]

On 05/29/2018 10:19 AM, Alex Mestiashvili wrote:
>> I think original poster is unaware of `debcheckout` from
>> the package `devscripts`.
>>
>> `debcheckout PACKAGE` does "VCS checkout (or cloning) of PACKAGE"
>>
>> Checkout URL is taken from debian/control  Vcs-Vcs: 
> 
> In case of binutils that will not help:
> 
> debcheckout binutils
> declared bzr repository at
> http://bazaar.launchpad.net/~doko/binutils/pkg-2.29-debian
> bzr branch http://bazaar.launchpad.net/~doko/binutils/pkg-2.29-debian
> binutils ...
> Can't exec "bzr": No such file or directory at /usr/bin/debcheckout line
> 573.
> checkout failed (the command above returned a non-zero exit code)

Ops, that's actually due to missing bzr :)

Well, with installed bzr the result is quite the same due to missing repo.

Re: VCS repositories

[Alex Mestiashvili]

> I think original poster is unaware of `debcheckout` from
> the package `devscripts`.
> 
> `debcheckout PACKAGE` does "VCS checkout (or cloning) of PACKAGE"
> 
> Checkout URL is taken from debian/control  Vcs-Vcs: 

In case of binutils that will not help:

debcheckout binutils
declared bzr repository at
http://bazaar.launchpad.net/~doko/binutils/pkg-2.29-debian
bzr branch http://bazaar.launchpad.net/~doko/binutils/pkg-2.29-debian
binutils ...
Can't exec "bzr": No such file or directory at /usr/bin/debcheckout line
573.
checkout failed (the command above returned a non-zero exit code)

I guess a tool like debsnap is more appropriate in this case.

Re: VCS repositories

[Geert Stappers]

On Tue, May 29, 2018 at 06:18:44AM +, Warlich, Christof wrote:
> Hi,
>
> I'm a bit desperate to find out how the Debian project maintains
> its patches w.r.t. upstream repositories. Thus, while I can
> explore the _current_ patches of a package by looking at the
> "*.debian.tar.gz"-archive after obtaining its sources through "apt-get
> source ",  I'd be rather interested in both history
> and future of these patches along the lifetime of a Debian releases'
> maintainance period.
>
> At the first glance, things look quite straight forward: Starting
> with, say, the "glibc"-package, an "apt-get source glibc" tells me
> that I may get the git repo of the related Debian patches by cloning
> https://anonscm.debian.org/git/pkg-glibc/glibc.git. But as it turns
> out, this (and some other Debian) hosts went offline as they are being
> replaced by https://salsa.debian.org. So I finally get what I am looking
> for by cloning https://salsa.debian.org/glibc-team/glibc.git. Great.
>
> Getting rather encouraged by that, I tried to find
> the repo for the "binutils" patches. Again, "apt-get
> source binutils" tells me that I should get it from
> http://bazaar.launchpad.net/~doko/binutils/pkg-2.28-debian. And again,
> http://bazaar.launchpad.net/~doko/binutils/pkg-2.28-debian is gone. But
> this time, I couldn't find a substitute on https://salsa.debian.org.
>
> Further looking around, it seems that there are still quite a few
> (if not most!) packages still missing on https://salsa.debian.org,
> although this transition was, as I recall, supposed to be completed
> by the end of Mai 2018.
>
> So finally, here is my question: When may I expect that
> VCS-repositories for all Debian packages may be available through
> https://salsa.debian.org (including updates of the packages to point to
> the new repository location on https://salsa.debian.org as printed by
> "apt-get source") and what could I do in the meantime w.r.t. packages
> like binutils, which are obviously gone from their old place, while
> they are still not available on https://salsa.debian.org?

I think original poster is unaware of `debcheckout` from
the package `devscripts`.

`debcheckout PACKAGE` does "VCS checkout (or cloning) of PACKAGE"

Checkout URL is taken from debian/control  Vcs-Vcs: 

There is no must on "git" and "salsa"


> Many thanks for any insight on that topic,

sudo apt install devscripts
debcheckout PACKAGE


Groeten
Geert Stappers
-- 
Leven en laten leven

VCS repositories

[Warlich, Christof]

Hi,

I'm a bit desperate to find out how the Debian project maintains its patches 
w.r.t. upstream repositories. Thus, while I can explore the _current_ patches 
of a package by looking at the "*.debian.tar.gz"-archive after obtaining its 
sources through "apt-get source ",  I'd be rather interested in 
both history and future of these patches along the lifetime of a Debian 
releases' maintainance period.

At the first glance, things look quite straight forward: Starting with, say, 
the "glibc"-package, an "apt-get source glibc" tells me that I may get the git 
repo of the related Debian patches by cloning 
https://anonscm.debian.org/git/pkg-glibc/glibc.git. But as it turns out, this 
(and some other Debian) hosts went offline as they are being replaced by 
https://salsa.debian.org. So I finally get what I am looking for by cloning 
https://salsa.debian.org/glibc-team/glibc.git. Great.

Getting rather encouraged by that, I tried to find the repo for the "binutils" 
patches. Again, "apt-get source binutils" tells me that I should get it from 
http://bazaar.launchpad.net/~doko/binutils/pkg-2.28-debian. And again, 
http://bazaar.launchpad.net/~doko/binutils/pkg-2.28-debian is gone. But this 
time, I couldn't find a substitute on https://salsa.debian.org.

Further looking around, it seems that there are still quite a few (if not 
most!) packages still missing on https://salsa.debian.org, although this 
transition was, as I recall, supposed to be completed by the end of Mai 2018.

So finally, here is my question: When may I expect that VCS-repositories for 
all Debian packages may be available through https://salsa.debian.org 
(including updates of the packages to point to the new repository location on 
https://salsa.debian.org as printed by "apt-get source") and what could I do in 
the meantime w.r.t. packages like binutils, which are obviously gone from their 
old place, while they are still not available on https://salsa.debian.org?

Many thanks for any insight on that topic,

Chris