Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #221941 > unrolled thread
| Started by | l0f4r0@tuta.io |
|---|---|
| First post | 2020-04-25 23:00 +0200 |
| Last post | 2020-04-28 20:50 +0200 |
| Articles | 11 — 5 participants |
Back to article view | Back to linux.debian.user
Package integration date into repository l0f4r0@tuta.io - 2020-04-25 23:00 +0200
Re: Package integration date into repository Marco Möller <talby@debianlists.mobilxpress.net> - 2020-04-25 23:20 +0200
Re: Package integration date into repository Roberto C. Sánchez <roberto@debian.org> - 2020-04-26 01:40 +0200
Re: Package integration date into repository l0f4r0@tuta.io - 2020-04-26 01:40 +0200
Re: Package integration date into repository Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-26 09:20 +0200
Re: Package integration date into repository l0f4r0@tuta.io - 2020-04-27 01:20 +0200
Re: Package integration date into repository Andrei POPESCU <andreimpopescu@gmail.com> - 2020-04-27 08:40 +0200
Re: Package integration date into repository l0f4r0@tuta.io - 2020-04-28 14:00 +0200
Re: Package integration date into repository David Wright <deblis@lionunicorn.co.uk> - 2020-04-28 17:30 +0200
Re: Package integration date into repository Roberto C. Sánchez <roberto@debian.org> - 2020-04-28 18:30 +0200
Re: Package integration date into repository David Wright <deblis@lionunicorn.co.uk> - 2020-04-28 20:50 +0200
| From | l0f4r0@tuta.io |
|---|---|
| Date | 2020-04-25 23:00 +0200 |
| Subject | Package integration date into repository |
| Message-ID | <zZA41-6t-5@gated-at.bofh.it> |
Hi, Just a simple question: is there a CLI command to get the date from which a specific package is available through my configured repositories please? Or am I expected to directly check dates in "versioned links > changelog" at https://tracker.debian.org/pkg/ <https://tracker.debian.org/pkg/go-mtpfs>my_package? NB: I'm not interested in knowing the installation date. Thank you in advance :) l0f4r0
[toc] | [next] | [standalone]
| From | Marco Möller <talby@debianlists.mobilxpress.net> |
|---|---|
| Date | 2020-04-25 23:20 +0200 |
| Message-ID | <zZAnn-sb-11@gated-at.bofh.it> |
| In reply to | #221941 |
On 25.04.20 22:53, l0f4r0@tuta.io wrote: > is there a CLI command to get the date from which a specific package is available through my configured repositories please? > Or am I expected to directly check dates in "versioned links > changelog" at https://tracker.debian.org/pkg/ <https://tracker.debian.org/pkg/go-mtpfs>my_package? To receive the date from the changelog is the closest I would know of, after I for myself have been searching for this in the past. I then constructed some ugly but well working CLI (bash) command: apt-get changelog PACKAGENAME 2> /dev/null| grep -m 1 "^ --" 2> /dev/null| cut -d'>' -f2 2> /dev/null| cut -c 3- 2> /dev/null | cut -d' ' --complement -s -f6 2> /dev/null Good Luck! Marco.
[toc] | [prev] | [next] | [standalone]
| From | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| Date | 2020-04-26 01:40 +0200 |
| Message-ID | <zZCyR-1Gp-1@gated-at.bofh.it> |
| In reply to | #221943 |
On Sun, Apr 26, 2020 at 01:30:11AM +0200, l0f4r0@tuta.io wrote:
> Hi Marco,
>
> 25 avr. 2020 à 23:12 de talby@debianlists.mobilxpress.net:
>
> > To receive the date from the changelog is the closest I would know of, after I for myself have been searching for this in the past. I then constructed some ugly but well working CLI (bash) command:
> >
> > apt-get changelog PACKAGENAME 2> /dev/null| grep -m 1 "^ --" 2> /dev/null| cut -d'>' -f2 2> /dev/null| cut -c 3- 2> /dev/null | cut -d' ' --complement -s -f6 2> /dev/null
> >
> I didn't know about apt(-get) changelog, thank you :)
> However, I note there is no direct command to obtain the expected result according to you.
> NB: I have a suggestion for your command, same logic but probably less resource-consuming because there is only one pipe:
> apt-get changelog PACKAGENAME 2>/dev/null | awk 'BEGIN{FS=">"} /--/{sub(" ","",$2);print $2;exit}'
>
That's neat. You could turn into a shell function too:
roberto@miami:~$ pkg_date() {
> apt-get changelog "$1" 2>/dev/null | awk 'BEGIN{FS=">"} /--/{sub(" ","",$2);print $2;exit}'
> }
roberto@miami:~$ pkg_date chromium
Thu, 02 Apr 2020 22:23:57 +0000
Regards,
-Roberto
--
Roberto C. Sánchez
[toc] | [prev] | [next] | [standalone]
| From | l0f4r0@tuta.io |
|---|---|
| Date | 2020-04-26 01:40 +0200 |
| Message-ID | <zZCyR-1Gp-3@gated-at.bofh.it> |
| In reply to | #221943 |
Hi Marco,
25 avr. 2020 à 23:12 de talby@debianlists.mobilxpress.net:
> To receive the date from the changelog is the closest I would know of, after I for myself have been searching for this in the past. I then constructed some ugly but well working CLI (bash) command:
>
> apt-get changelog PACKAGENAME 2> /dev/null| grep -m 1 "^ --" 2> /dev/null| cut -d'>' -f2 2> /dev/null| cut -c 3- 2> /dev/null | cut -d' ' --complement -s -f6 2> /dev/null
>
I didn't know about apt(-get) changelog, thank you :)
However, I note there is no direct command to obtain the expected result according to you.
NB: I have a suggestion for your command, same logic but probably less resource-consuming because there is only one pipe:
apt-get changelog PACKAGENAME 2>/dev/null | awk 'BEGIN{FS=">"} /--/{sub(" ","",$2);print $2;exit}'
Best regards,
l0f4r0
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-04-26 09:20 +0200 |
| Message-ID | <zZJK1-6a4-3@gated-at.bofh.it> |
| In reply to | #221941 |
[Multipart message — attachments visible in raw view] — view raw
On Sb, 25 apr 20, 22:53:07, l0f4r0@tuta.io wrote: > > Just a simple question: is there a CLI command to get the date from > which a specific package is available through my configured > repositories please? > Or am I expected to directly check dates in "versioned links > > changelog" at https://tracker.debian.org/pkg/ > <https://tracker.debian.org/pkg/go-mtpfs>my_package? The changelog does not necessarily show when the package was uploaded, e.g. the package maintainer could prepare an upload (including the changelog entry) and upload days/weeks/months later. After uploading the package also has to be (re)built before becoming available on the mirrors. What are you trying to achieve? Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | l0f4r0@tuta.io |
|---|---|
| Date | 2020-04-27 01:20 +0200 |
| Message-ID | <zZYJ3-6Wy-1@gated-at.bofh.it> |
| In reply to | #221951 |
Hi Andrei, 26 avr. 2020 à 09:09 de andreimpopescu@gmail.com: > The changelog does not necessarily show when the package was uploaded, > e.g. the package maintainer could prepare an upload (including the > changelog entry) and upload days/weeks/months later. > > After uploading the package also has to be (re)built before becoming > available on the mirrors. > Interesting. I'm not sure it makes things easier for me... ;) > What are you trying to achieve? > I just would like to make some correlation between when new code is publicly available (through GitHub for example) and when it's integrated into official Debian repositories. Maybe I can use section "news" on https://tracker.debian.org/pkg/my_package? I suppose there is no mention of stable (only experimental, unstable, testing and backports) into this section because testing becomes stable when the latter is released? If true, it would be handy to mark somewhere the transition between both repositories though. NB: we can take a common example if it's easier to understand each other: copyq Best regards, l0f4r0
[toc] | [prev] | [next] | [standalone]
| From | Andrei POPESCU <andreimpopescu@gmail.com> |
|---|---|
| Date | 2020-04-27 08:40 +0200 |
| Message-ID | <A05AS-32f-7@gated-at.bofh.it> |
| In reply to | #221970 |
[Multipart message — attachments visible in raw view] — view raw
On Lu, 27 apr 20, 01:12:29, l0f4r0@tuta.io wrote: > 26 avr. 2020 à 09:09 de andreimpopescu@gmail.com: > > > What are you trying to achieve? > > > I just would like to make some correlation between when new code is > publicly available (through GitHub for example) and when it's > integrated into official Debian repositories. Sure... for what purpose? :) > Maybe I can use section "news" > on https://tracker.debian.org/pkg/my_package? I suppose there is no > mention of stable (only experimental, unstable, testing and backports) > into this section because testing becomes stable when the latter is > released? If true, it would be handy to mark somewhere the transition > between both repositories though. Yes, the news are closer to what you seem to need. There are also uploads to stable security and stable proposed-updates (staging for the next point release). Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser
[toc] | [prev] | [next] | [standalone]
| From | l0f4r0@tuta.io |
|---|---|
| Date | 2020-04-28 14:00 +0200 |
| Message-ID | <A0x46-2WV-3@gated-at.bofh.it> |
| In reply to | #221979 |
Hi Andrei, 27 avr. 2020 à 08:35 de andreimpopescu@gmail.com: > On Lu, 27 apr 20, 01:12:29, l0f4r0@tuta.io wrote: > >> 26 avr. 2020 à 09:09 de andreimpopescu@gmail.com: >> >> > What are you trying to achieve? >> > >> I just would like to make some correlation between when new code is >> publicly available (through GitHub for example) and when it's >> integrated into official Debian repositories. >> > Sure... for what purpose? :) > Initially, I just wanted to compare one of my debian packages with all its related GitHub releases (because I didn't know when it was out). But I soon realized that I could rely on the version numbering instead so it just became a theoretical question out of curiosity because I was almost sure this information would be accessible with the correct switch/option under CLI. Visibly I was wrong ;) Best regards, l0f4r0
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-04-28 17:30 +0200 |
| Message-ID | <A0Alk-506-7@gated-at.bofh.it> |
| In reply to | #221970 |
On Mon 27 Apr 2020 at 01:12:29 (+0200), l0f4r0@tuta.io wrote: > 26 avr. 2020 à 09:09 de andreimpopescu@gmail.com: > > > The changelog does not necessarily show when the package was uploaded, > > e.g. the package maintainer could prepare an upload (including the > > changelog entry) and upload days/weeks/months later. > > > > After uploading the package also has to be (re)built before becoming > > available on the mirrors. > > > Interesting. I'm not sure it makes things easier for me... ;) > > > What are you trying to achieve? > > > I just would like to make some correlation between when new code is publicly available (through GitHub for example) and when it's integrated into official Debian repositories. > > Maybe I can use section "news" on https://tracker.debian.org/pkg/my_package? I suppose there is no mention of stable (only experimental, unstable, testing and backports) into this section because testing becomes stable when the latter is released? If true, it would be handy to mark somewhere the transition between both repositories though. > > NB: we can take a common example if it's easier to understand each other: copyq Perhaps what you want is something like this: copyq-doc_3.7.3-1_all.deb 2019-02-08 17:40 890K copyq-doc_3.7.3-1~bpo9+1_all.deb 2019-02-10 07:29 888K copyq-doc_3.10.0-1_all.deb 2020-02-03 03:26 891K copyq-plugins_3.7.3-1_amd64.deb 2019-02-08 21:10 485K copyq-plugins_3.7.3-1_arm64.deb 2019-02-08 17:29 436K copyq-plugins_3.7.3-1_armel.deb 2019-02-08 20:14 401K copyq-plugins_3.7.3-1_armhf.deb 2019-02-08 17:45 408K copyq-plugins_3.7.3-1_i386.deb 2019-02-08 17:50 520K copyq-plugins_3.7.3-1_mips.deb 2019-02-08 18:26 411K copyq-plugins_3.7.3-1_mips64el.deb 2019-02-08 22:13 422K copyq-plugins_3.7.3-1_mipsel.deb 2019-02-08 22:59 421K copyq-plugins_3.7.3-1_ppc64el.deb 2019-02-08 17:14 485K copyq-plugins_3.7.3-1_s390x.deb 2019-02-08 17:14 428K copyq-plugins_3.7.3-1~bpo9+1_amd64.deb 2019-02-10 09:11 445K copyq-plugins_3.7.3-1~bpo9+1_arm64.deb 2019-02-09 21:12 413K copyq-plugins_3.7.3-1~bpo9+1_armel.deb 2019-02-11 15:30 389K copyq-plugins_3.7.3-1~bpo9+1_armhf.deb 2019-02-12 15:42 395K copyq-plugins_3.7.3-1~bpo9+1_i386.deb 2019-02-10 08:11 479K copyq-plugins_3.7.3-1~bpo9+1_mips.deb 2019-02-09 23:00 402K copyq-plugins_3.7.3-1~bpo9+1_mips64el.deb 2019-03-08 02:44 412K copyq-plugins_3.7.3-1~bpo9+1_mipsel.deb 2019-03-08 03:44 411K copyq-plugins_3.7.3-1~bpo9+1_ppc64el.deb 2019-02-09 21:12 440K copyq-plugins_3.7.3-1~bpo9+1_s390x.deb 2019-02-10 08:06 423K copyq-plugins_3.10.0-1_amd64.deb 2020-02-03 03:21 484K copyq-plugins_3.10.0-1_arm64.deb 2020-02-03 03:41 436K copyq-plugins_3.10.0-1_armel.deb 2020-02-03 03:41 409K copyq-plugins_3.10.0-1_armhf.deb 2020-02-03 03:41 416K copyq-plugins_3.10.0-1_i386.deb 2020-02-03 03:26 517K copyq-plugins_3.10.0-1_mips64el.deb 2020-02-03 04:27 424K copyq-plugins_3.10.0-1_mipsel.deb 2020-02-03 07:44 425K copyq-plugins_3.10.0-1_ppc64el.deb 2020-02-03 03:26 484K copyq-plugins_3.10.0-1_s390x.deb 2020-02-04 08:41 431K copyq_3.7.3-1.debian.tar.xz 2019-02-08 16:22 7.8K copyq_3.7.3-1.dsc 2019-02-08 16:22 2.1K copyq_3.7.3-1_amd64.deb 2019-02-08 21:10 1.2M copyq_3.7.3-1_arm64.deb 2019-02-08 17:29 1.2M copyq_3.7.3-1_armel.deb 2019-02-08 20:14 1.1M copyq_3.7.3-1_armhf.deb 2019-02-08 17:45 1.1M copyq_3.7.3-1_i386.deb 2019-02-08 17:50 1.3M copyq_3.7.3-1_mips.deb 2019-02-08 18:26 1.1M copyq_3.7.3-1_mips64el.deb 2019-02-08 22:13 1.1M copyq_3.7.3-1_mipsel.deb 2019-02-08 22:59 1.1M copyq_3.7.3-1_ppc64el.deb 2019-02-08 17:14 1.2M copyq_3.7.3-1_s390x.deb 2019-02-08 17:14 1.1M copyq_3.7.3-1~bpo9+1.debian.tar.xz 2019-02-08 18:10 7.9K copyq_3.7.3-1~bpo9+1.dsc 2019-02-08 18:10 2.1K copyq_3.7.3-1~bpo9+1_amd64.deb 2019-02-10 09:11 1.2M copyq_3.7.3-1~bpo9+1_arm64.deb 2019-02-09 21:12 1.2M copyq_3.7.3-1~bpo9+1_armel.deb 2019-02-11 15:30 1.1M copyq_3.7.3-1~bpo9+1_armhf.deb 2019-02-12 15:42 1.1M copyq_3.7.3-1~bpo9+1_i386.deb 2019-02-10 08:11 1.3M copyq_3.7.3-1~bpo9+1_mips.deb 2019-02-09 23:00 1.1M copyq_3.7.3-1~bpo9+1_mips64el.deb 2019-03-08 02:44 1.1M copyq_3.7.3-1~bpo9+1_mipsel.deb 2019-03-08 03:44 1.1M copyq_3.7.3-1~bpo9+1_ppc64el.deb 2019-02-09 21:12 1.2M copyq_3.7.3-1~bpo9+1_s390x.deb 2019-02-10 08:06 1.2M copyq_3.7.3.orig.tar.gz 2019-02-08 16:22 2.8M copyq_3.10.0-1.debian.tar.xz 2020-02-03 02:56 7.9K copyq_3.10.0-1.dsc 2020-02-03 02:56 2.1K copyq_3.10.0-1_amd64.deb 2020-02-03 03:21 1.3M copyq_3.10.0-1_arm64.deb 2020-02-03 03:41 1.2M copyq_3.10.0-1_armel.deb 2020-02-03 03:41 1.2M copyq_3.10.0-1_armhf.deb 2020-02-03 03:41 1.2M copyq_3.10.0-1_i386.deb 2020-02-03 03:26 1.3M copyq_3.10.0-1_mips64el.deb 2020-02-03 04:27 1.1M copyq_3.10.0-1_mipsel.deb 2020-02-03 07:44 1.1M copyq_3.10.0-1_ppc64el.deb 2020-02-03 03:26 1.3M copyq_3.10.0-1_s390x.deb 2020-02-04 08:41 1.2M copyq_3.10.0.orig.tar.gz 2020-02-03 02:56 2.7M from http://ftp.us.debian.org/debian/pool/main/c/copyq/ Cheers, David.
[toc] | [prev] | [next] | [standalone]
| From | Roberto C. Sánchez <roberto@debian.org> |
|---|---|
| Date | 2020-04-28 18:30 +0200 |
| Message-ID | <A0Bhn-5zn-1@gated-at.bofh.it> |
| In reply to | #222036 |
On Tue, Apr 28, 2020 at 10:20:26AM -0500, David Wright wrote: > On Mon 27 Apr 2020 at 01:12:29 (+0200), l0f4r0@tuta.io wrote: > > 26 avr. 2020 à 09:09 de andreimpopescu@gmail.com: > > > > > The changelog does not necessarily show when the package was uploaded, > > > e.g. the package maintainer could prepare an upload (including the > > > changelog entry) and upload days/weeks/months later. > > > > > > After uploading the package also has to be (re)built before becoming > > > available on the mirrors. > > > > > Interesting. I'm not sure it makes things easier for me... ;) > > > > > What are you trying to achieve? > > > > > I just would like to make some correlation between when new code is publicly available (through GitHub for example) and when it's integrated into official Debian repositories. > > > > Maybe I can use section "news" on https://tracker.debian.org/pkg/my_package? I suppose there is no mention of stable (only experimental, unstable, testing and backports) into this section because testing becomes stable when the latter is released? If true, it would be handy to mark somewhere the transition between both repositories though. > > > > NB: we can take a common example if it's easier to understand each other: copyq > > Perhaps what you want is something like this: > > copyq-doc_3.7.3-1_all.deb 2019-02-08 17:40 890K [SNIP] > That is giving you the date/time of that particular version of the package. If the maintainer makes some Debian-only tweaks (e.g., to fix something in a maintainer script) or cherry-picks an upstream commit and drops it into the Debian patch series for the package, then updates releases that updated Debian package, that will most likely be version 3.7.3-2 with some other date. Depending on how you interpret the version number and date, it could provide misleading information on the "correlation between when new code is publicly available ... and when it's integrated into official Debian repositories." Regards, -Roberto -- Roberto C. Sánchez
[toc] | [prev] | [next] | [standalone]
| From | David Wright <deblis@lionunicorn.co.uk> |
|---|---|
| Date | 2020-04-28 20:50 +0200 |
| Message-ID | <A0DsR-6NQ-3@gated-at.bofh.it> |
| In reply to | #222043 |
On Tue 28 Apr 2020 at 12:26:53 (-0400), Roberto C. Sánchez wrote: > On Tue, Apr 28, 2020 at 10:20:26AM -0500, David Wright wrote: > > On Mon 27 Apr 2020 at 01:12:29 (+0200), l0f4r0@tuta.io wrote: > > > 26 avr. 2020 à 09:09 de andreimpopescu@gmail.com: > > > > > > > The changelog does not necessarily show when the package was uploaded, > > > > e.g. the package maintainer could prepare an upload (including the > > > > changelog entry) and upload days/weeks/months later. > > > > > > > > After uploading the package also has to be (re)built before becoming > > > > available on the mirrors. > > > > > > > Interesting. I'm not sure it makes things easier for me... ;) > > > > > > > What are you trying to achieve? > > > > > > > I just would like to make some correlation between when new code is publicly available (through GitHub for example) and when it's integrated into official Debian repositories. > > > > > > Maybe I can use section "news" on https://tracker.debian.org/pkg/my_package? I suppose there is no mention of stable (only experimental, unstable, testing and backports) into this section because testing becomes stable when the latter is released? If true, it would be handy to mark somewhere the transition between both repositories though. > > > > > > NB: we can take a common example if it's easier to understand each other: copyq > > > > Perhaps what you want is something like this: > > > > copyq-doc_3.7.3-1_all.deb 2019-02-08 17:40 890K > [SNIP] > > > > That is giving you the date/time of that particular version of the > package. The OP has already said that they "could rely on the version numbering instead", so I assumed the version number is important to them. > If the maintainer makes some Debian-only tweaks (e.g., to fix > something in a maintainer script) or cherry-picks an upstream commit and > drops it into the Debian patch series for the package, then updates > releases that updated Debian package, that will most likely be version > 3.7.3-2 with some other date. > > Depending on how you interpret the version number and date, it could > provide misleading information on the "correlation between when new code > is publicly available ... and when it's integrated into official Debian > repositories." Before a package reaches this web page, it's going to be associated with timestamps all the way along the chain. I have no idea which one the OP is trying to determine, but I hadn't seen this timestamp mentioned. It's up to them to interpret whichever timestamps they choose to use. >From my viewpoint _as a user_, a package becomes "integrated into a repository" when apt-get update can index it and upgrade can fetch it. (Obviously I'd have to have sid ± experimental in my sources.list for the benefit of the update.) Examining this directory short-circuits that necessity, because AFAIK they all slop about in the pool. Cheers, David.
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web