• Re: debian/watch: How to watch version tags and what to capture?

    From c.buhtz@posteo.jp@21:1/5 to All on Sun Sep 17 08:40:02 2023
    Might it just be that "uscan" doesn't run every day on the Debian
    servers? :)

    I tried to reproduce it on my local machine. But there the new version
    is recognized without problems.


    $ uscan --verbose
    uscan info: uscan (version 2.21.3+deb11u1) See uscan(1) for help
    uscan info: Scan watch files in .
    uscan info: Check debian/watch and debian/changelog in .
    uscan info: package="backintime" version="1.3.3-4" (as seen in debian/changelog)
    uscan info: package="backintime" version="1.3.3" (no epoch/revision)
    uscan info: ./debian/changelog sets package="backintime" version="1.3.3"
    uscan info: Process watch file at: debian/watch
    package = backintime
    version = 1.3.3
    pkg_dir = .
    uscan info: Last orig.tar.* tarball version (from debian/changelog): 1.3.3 uscan info: Last orig.tar.* tarball version (dversionmangled): 1.3.3
    uscan info: Requesting URL:
    https://github.com/bit-team/backintime/tags
    uscan info: Matching pattern:
    (?:(?:https://github.com)?\/bit\-team\/backintime\/)?.*/v?(\d.*)(?i)(?:\.(?:tar\.xz|tar\.bz2|tar\.gz|zip|tgz|tbz|txz))
    uscan info: Found the following matching hrefs on the web page (newest first):
    https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.tar.gz (1.4.0) index=1.4.0-1
    https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.tar.gz (1.4.0) index=1.4.0-1
    https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.zip (1.4.0) index=1.4.0-0
    https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.zip (1.4.0) index=1.4.0-0
    https://github.com/bit-team/backintime/archive/refs/tags/v1.3.3.tar.gz (1.3.3) index=1.3.3-1
    https://github.com/bit-team/backintime/archive/refs/tags/v1.3.3.tar.gz (1.3.3) index=1.3.3-1
    https://github.com/bit-team/backintime/archive/refs/tags/v1.3.3.zip (1.3.3) index=1.3.3-0
    https://github.com/bit-team/backintime/archive/refs/tags/v1.3.3.zip (1.3.3) index=1.3.3-0
    https://github.com/bit-team/backintime/archive/refs/tags/v1.3.2.tar.gz (1.3.2) index=1.3.2-1
    https://github.com/bit-team/backintime/archive/refs/tags/v1.3.2.tar.gz (1.3.2) index=1.3.2-1
    https://github.com/bit-team/backintime/archive/refs/tags/v1.3.2.zip (1.3.2) index=1.3.2-0
    https://github.com/bit-team/backintime/archive/refs/tags/v1.3.2.zip (1.3.2) index=1.3.2-0
    [SNIPPED]

    uscan info: Looking at $base = https://github.com/bit-team/backintime/tags with
    $filepattern = .*/v?(\d.*)(?i)(?:\.(?:tar\.xz|tar\.bz2|tar\.gz|zip|tgz|tbz|txz)) found
    $newfile = https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.tar.gz
    $newversion = 1.4.0
    $lastversion = 1.3.3
    uscan info: Matching target for downloadurlmangle: https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.tar.gz
    uscan info: Upstream URL(+tag) to download is identified as https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.tar.gz
    uscan info: Filename (filenamemangled) for downloaded file: v1.4.0.tar.gz uscan: Newest version of backintime on remote site is 1.4.0, local version is 1.3.3
    uscan: => Newer package available from:
    => https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.tar.gz
    uscan info: Downloading upstream package: v1.4.0.tar.gz
    uscan info: Requesting URL:
    https://github.com/bit-team/backintime/archive/refs/tags/v1.4.0.tar.gz
    uscan info: Successfully downloaded package: v1.4.0.tar.gz

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c.buhtz@posteo.jp@21:1/5 to mechtilde@debian.org on Sun Sep 17 09:00:01 2023
    Dear Metchilde,

    thanks for reply.

    On 2023-09-17 08:51 Mechtilde Stehmann <mechtilde@debian.org> wrote:
    Am 17.09.23 um 08:35 schrieb c.buhtz@posteo.jp:
    Might it just be that "uscan" doesn't run every day on the Debian
    servers? :)

    I tried to reproduce it on my local machine. But there the new
    version is recognized without problems.

    You can find the right result under https://qa.debian.org/developer.php?email=fabi.wolff%40arcor.de

    To be more precise: First table, last column (header "Watch").

    OK, than what is about tracker.debian.org ? Then there must be a BUG?
    I assume I'm not the first one encountered it. Is there a bug tracker I
    can check or report that Issue?

    It is really frustrating when simple things like this do not work.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c.buhtz@posteo.jp@21:1/5 to All on Sun Sep 17 08:30:01 2023
    Hello together,

    do I get it right that the syntax of the debain/watch file do use regex?

    https://repo .*/v?(\d.*)@ARCHIVE_EXT@

    When an application do use version tages like "v1.4.0" and based on my knowledge and experiments on regex101.com this won't work. Am I right?

    There is also a capturing group in that example. What exactly should be captured?

    My proposal would be

    v+(\d.*)

    but I'm not sure what the system expect or what part of the system do
    use the watch file.

    Background: The tracker didn't recognized the latest release of
    backintime and I try to understand why and how to improve this myself.

    https://sources.debian.org/src/backintime/1.3.3-4/debian/watch/

    Thanks for your help.
    Christian
    Upstream maintenance team of Back In Time

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mechtilde Stehmann@21:1/5 to All on Sun Sep 17 09:00:02 2023
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------7rKSkg585VUo5poamWQHgxEg
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGVsbG8gQ2hyaXN0aWFuLA0KDQoNCkFtIDE3LjA5LjIzIHVtIDA4OjM1IHNjaHJpZWIgYy5i dWh0ekBwb3N0ZW8uanA6DQo+IE1pZ2h0IGl0IGp1c3QgYmUgdGhhdCAidXNjYW4iIGRvZXNu J3QgcnVuIGV2ZXJ5IGRheSBvbiB0aGUgRGViaWFuDQo+IHNlcnZlcnM/IDopDQo+IA0KPiBJ IHRyaWVkIHRvIHJlcHJvZHVjZSBpdCBvbiBteSBsb2NhbCBtYWNoaW5lLiBCdXQgdGhlcmUg dGhlIG5ldyB2ZXJzaW9uDQo+IGlzIHJlY29nbml6ZWQgd2l0aG91dCBwcm9ibGVtcy4NCg0K WW91IGNhbiBmaW5kIHRoZSByaWdodCByZXN1bHQgdW5kZXIgDQpodHRwczovL3FhLmRlYmlh bi5vcmcvZGV2ZWxvcGVyLnBocD9lbWFpbD1mYWJpLndvbGZmJTQwYXJjb3IuZGUNCg0KUmVn YXJkcw0KDQoNCi0tIA0KTWVjaHRpbGRlIFN0ZWhtYW5uDQojIyBEZWJpYW4gRGV2ZWxvcGVy DQojIyBQR1AgZW5jcnlwdGlvbiB3ZWxjb21lDQojIyBGMEUzIDdGM0QgQzg3QSA0OTk4IDI4 OTkgIDM5RTcgRjI4NyA3QkJBIDE0MUEgQUQ3Rg0K

    --------------7rKSkg585VUo5poamWQHgxEg--

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAmUGodsACgkQ8od7uhQa rX+ZoRAAja/S3bF267YVmwHBHpRdQx0B4ZmFYGtCEWphw017BFrLLfSk34K3u2eS 2U9W4tky0y00jpPQjMflgcqLPthiXIpdPFu4aJsNf8Jg1Ev4++zVgDZFpMHaJltE FurvL4xRO/0p1yxSu+syQrltUEWEWoXyLMzlFqfd1oa0CEGk3eSC4PQ/sxne67xA RMvtU0aItztCQV3yTviCIFnekCNc9NxtB+o52VnbAsjcFPh/hW2Sh/WP8LVhbLgy 8sC693MdTVge+v0dNrOyEvkD/MKJ/MbyyTQvjxAN1BAsT3IFxAFWuEx0IYfkpnKF P8afuSWaSj8WviPM74aKoPpzrcxuALNvOhdpux0BFFeQ5HqaQJfFDm8WPOzfOrq7 u0qZWqGZTaMd32bQKinjaIztRjV90AERAptKhv5Pqo7c1abT2tV+DnkaIP0eKkRM 9QiAuhoWF8r2Londm5ogcmCLJ+YWz4vrGGV04oWLhBAGLF1LIyF7OwEnaR6fg8wS KSjsE4pHcrDKEYW3sl9Bapq+JwwaHEVoBE7DlPKs4sxl1RBbbrmJJJ/a092NMM61 Qz8A1dxrm63rygdAMQoXAGv7gV6Mrv0NgpsH5Q+u+Ga6wQRlG/HPHIxScT2hNo0U Srkdy5yd16Z6qBOtpuf1fUCh4vY/4n80ykatiUZHHwgNBhitSQs=
    =m7/J
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c.buhtz@posteo.jp@21:1/5 to fzielcke@z-51.de on Sun Sep 17 09:50:01 2023
    Dear Felix,

    thanks for the reply.

    On 2023-09-17 09:13 Felix Zielcke <fzielcke@z-51.de> wrote:
    Tracker needs a bit of time to
    update all the infos shown. 1-2 days aren't unusual and not directly a
    bug in it.

    Is there a bug tracker for the tracker?

    The term "tracker" indicates just in time and not two days.
    A minimal improvement would be to give a timestamp at the tracker site
    to indicate the last update of all the information shown.

    I do think in interest of the Debian project. I assume it feels
    unprofessional to users if things like this happens.

    If the update interval can not be increased then it should be more
    transparent.

    Kind
    Christian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Mechtilde Stehmann@21:1/5 to All on Sun Sep 17 10:00:01 2023
    This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------MYmrxNYLgbQuPcJvLx04fLi0
    Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64

    SGVsbG8gQ2hyaXN0aWFuDQoNCkFtIDE3LjA5LjIzIHVtIDA5OjQ2IHNjaHJpZWIgYy5idWh0 ekBwb3N0ZW8uanA6DQo+IERlYXIgRmVsaXgsDQo+IA0KPiB0aGFua3MgZm9yIHRoZSByZXBs eS4NCj4gDQo+IE9uIDIwMjMtMDktMTcgMDk6MTMgRmVsaXggWmllbGNrZSA8ZnppZWxja2VA ei01MS5kZT4gd3JvdGU6DQo+PiBUcmFja2VyIG5lZWRzIGEgYml0IG9mIHRpbWUgdG8NCj4+ IHVwZGF0ZSBhbGwgdGhlIGluZm9zIHNob3duLiAxLTIgZGF5cyBhcmVuJ3QgdW51c3VhbCBh bmQgbm90IGRpcmVjdGx5IGENCj4+IGJ1ZyBpbiBpdC4NCj4gDQo+IElzIHRoZXJlIGEgYnVn IHRyYWNrZXIgZm9yIHRoZSB0cmFja2VyPw0KPiANCj4gVGhlIHRlcm0gInRyYWNrZXIiIGlu ZGljYXRlcyBqdXN0IGluIHRpbWUgYW5kIG5vdCB0d28gZGF5cy4NCj4gQSBtaW5pbWFsIGlt cHJvdmVtZW50IHdvdWxkIGJlIHRvIGdpdmUgYSB0aW1lc3RhbXAgYXQgdGhlIHRyYWNrZXIg c2l0ZQ0KPiB0byBpbmRpY2F0ZSB0aGUgbGFzdCB1cGRhdGUgb2YgYWxsIHRoZSBpbmZvcm1h dGlvbiBzaG93bi4NCj4gDQo+IEkgZG8gdGhpbmsgaW4gaW50ZXJlc3Qgb2YgdGhlIERlYmlh biBwcm9qZWN0LiBJIGFzc3VtZSBpdCBmZWVscw0KPiB1bnByb2Zlc3Npb25hbCB0byB1c2Vy cyBpZiB0aGluZ3MgbGlrZSB0aGlzIGhhcHBlbnMuDQoNCldoYXQgZG8geW91IGV4cGVjdD8N Cg0KVGhpcyBpcyBhIGRhc2hib2FyZCB0byBpbmZvcm0gbWFpbnRhaW5lciBhYm91dCBuZXcg dmVyc2lvbi4NCg0KV2hhdCBkbyB5b3UgbWVhbiBpcyB1bnByb2Zlc3Npb25hbD8NCg0KTW9z dCBvZiB0aGUgbWFpbnRhaW5lcnMgYXJlIHZvbHVudGVlcnMgYW5kIHdvcmsgb24gcGFja2Fn aW5nIGluIHRoZWlyIA0KZnJlZSB0aW1lLg0KDQo+IA0KPiBJZiB0aGUgdXBkYXRlIGludGVy dmFsIGNhbiBub3QgYmUgaW5jcmVhc2VkIHRoZW4gaXQgc2hvdWxkIGJlIG1vcmUNCj4gdHJh bnNwYXJlbnQuDQo+IA0KPiBLaW5kDQo+IENocmlzdGlhbg0KPiANClJlZ2FyZHMNCg0KLS0g DQpNZWNodGlsZGUgU3RlaG1hbm4NCiMjIERlYmlhbiBEZXZlbG9wZXINCiMjIFBHUCBlbmNy eXB0aW9uIHdlbGNvbWUNCiMjIEYwRTMgN0YzRCBDODdBIDQ5OTggMjg5OSAgMzlFNyBGMjg3 IDdCQkEgMTQxQSBBRDdGDQo=

    --------------MYmrxNYLgbQuPcJvLx04fLi0--

    -----BEGIN PGP SIGNATURE-----

    iQIzBAEBCgAdFiEE8ON/Pch6SZgomTnn8od7uhQarX8FAmUGsUMACgkQ8od7uhQa rX+Yog//eZeagdZfWgheJG4mjINaauKvbyVGPWqOj9uzZ2sxYtqcL7AarfHnzlDI VKHdGnrwRwoe/H1BdcJ726M1O7pENV706UmmGXlF5AacXyq7h3hmWjrvWC2brbx3 +679nHaOlTGLZOA0b2YWGhbXpW/xmKnwp86TMETjiEOPUcTyhgM6lE2dlCEpUMyT +tHvqBHRFu2ZCYU3Ebf6rbsZWnuxHf8cE2FaNmlGVmdQuQlo8DIeySOMeYqaKNv4 XYZ0C6jsd28nQTxcgzt0KqvZQWlwX975RfDamisjD8t7JzUhtmBlMTmIFDp2fx7u LtqMGI8cEAw+pxYWjeVC5zzAgFNWrbNmf+1UZM05ogK9W60JGcd8gCuAhArUnFYm Xc3N1rzk4oxIuIbVJYw40e1NktH+OiP6oo7I+Gcg/wzodKdsi7xxbhpDWuS2FPxU ox475F3Zes9ii4gumS4+n3WdOGDQdsZkwqmKF0xCDEtcidXooui7LD4B7USd7of7 RzACSI/Tm3cqLvp/gL2U6S8boSnoBlatDKeFqPkHsaZ+gYdMFfp1zxkeINhUHi9I FFJvO1a2qZ1lVzK491w66h6HrdvE6jMcbNzlBarvScZERBtBhSB/EvKbSKZ/F2uQ BQEtMnzHHpXxNTIePJ9z++EbeY8IMmnHuZbJul7Q0rqEB/mZ+UM=
    =TLHq
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?utf-8?Q?=C3=89tienne?= Mollier@21:1/5 to All on Sun Sep 17 11:00:01 2023
    Hello,

    c.buhtz@posteo.jp, on 2023-09-17:
    Why do we have to increase the volume of the list with that topic? Can
    we just discuss this on an issue tracker about the tracker? ;)
    Isn't this what a tracker is for?

    Bugs against the package tracker system can be reported against
    the pseudo package "tracker.debian.org" in the bug tracker
    system[0] using:

    $ reportbug tracker.debian.org

    You can see whether there could be a possibly duplicate issue on
    the corresponding web page[1].

    [0]: https://bugs.debian.org
    [1]: https://bugs.debian.org/tracker.debian.org

    Hope this helps,
    --
    .''`. Étienne Mollier <emollier@debian.org>
    : :' : gpg: 8f91 b227 c7d6 f2b1 948c 8236 793c f67e 8f0d 11da
    `. `' sent from /dev/pts/2, please excuse my verbosity
    `-

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEj5GyJ8fW8rGUjII2eTz2fo8NEdoFAmUGvo0ACgkQeTz2fo8N Edrsdg/8DRPmVpb+CUCAu6bCXXTQLxEnk1RGivtnErPA8jGSkmpHnc+U6JmI6Irr mAOdihv4e4gJcsZrUt0NiEIIybIiMw090PUsCj19pchuq+OOErFtLvU1PQaepbAH L9dH238SuVr0sRJ4zhz5IG0jx3NX+vfYTEdCtwKboW2p+CBkY1LvOIoOAGFOui8c 2QNQZj8Sy2tKEdX58Y4OfV4SMBBMYnDFzL7rR9g8KLR8jydPhLmDK8PZxyAejrx9 BCwEARTPpGns5e8MI3qhDwErKgkCDm5hNI66jxlOhLLBVqcCoREjEKcuxyFu6mlq 2J9Qh3zr33nNgGZFuW7DzLjVVFxEJbJKMf0koJ+lPXxRAz/2y8KD/sPY4vlOoJci XtP74DRtnzFIrarItQgvdEvfdSyVq/qxTitJ9Dq8HC7+Y3EWEyEGa9T4Uh3jUO2d O7938zb/dCsfQerEv+nDN0wVqDfWhBeexDvpfcmTbCLL/s06OHV2Aj+EoQR0zwzt jriXqeuMpVza4Coh0cexnuaoZpvDrYDLdGMXzDN43XStnFzdWSs+qIjwWWwC5sFc Gg7a4BDoXk+7E/zmJELSGIxiCm5kWbwAkG3RsITXgZI8D17Hm4HInHyB8bL9m1g9 EXrRyZ3conScpn7sE7qZfDq872Wy8Ev5eiPZFGpbx0H0F8Vg4PA=
    =57H9
    -----END PGP SIG
  • From c.buhtz@posteo.jp@21:1/5 to mechtilde@debian.org on Sun Sep 17 10:50:01 2023
    Hello,

    maybe it depends on my non-nativ English that I'm not able to make
    myself clear.

    On 2023-09-17 09:56 Mechtilde Stehmann <mechtilde@debian.org> wrote:
    What do you expect?

    As I told. Information just in time. Within in a delay of 1 or 2 hours
    the tracker/dashboard should inform about the new release.
    If this is not possible because of technical reasons (server load, etc)
    then indicate exactly that with a timestamp to make the reader able to
    validate the information in time.

    What do you mean is unprofessional?

    That the information the "Debian system" is out dated.
    Try to step into the role of a (new) user or a possible contributor.

    Most of the maintainers are volunteers and work on packaging in their
    free time.

    Why do we have to increase the volume of the list with that topic? Can
    we just discuss this on an issue tracker about the tracker? ;)
    Isn't this what a tracker is for?

    I also do this in my free time and try to improve Debian and not only
    my own workflow.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?UTF-8?Q?IOhannes_m_zm=c3=b6lnig_=@21:1/5 to c.buhtz@posteo.jp on Sun Sep 17 11:20:01 2023
    On 9/17/23 10:41, c.buhtz@posteo.jp wrote:
    Hello,

    maybe it depends on my non-nativ English that I'm not able to make
    myself clear.

    On 2023-09-17 09:56 Mechtilde Stehmann <mechtilde@debian.org> wrote:
    What do you expect?

    As I told. Information just in time. Within in a delay of 1 or 2 hours
    the tracker/dashboard should inform about the new release.

    hmm.
    how is "1 or 2 hours" more *just in time* than "1 or 2 days"?
    i get your point that you want the information fast, but it seems you
    are just using some arbitrary constraint that fits your personal need.
    it appears that for "most" Debian maintainers a lag of "1 or 2 days" is
    just as well (i assume that it is indeed "most" maintainers, as I don't
    see many complaints; for my *personal* workflow i'm very sure that I do
    not care to be informed about whether a new release has been made
    withing the last 2 hours, as I pretend that I like to let the dust
    settle a bit before starting *my* work).

    If this is not possible because of technical reasons (server load, etc)
    then indicate exactly that with a timestamp to make the reader able to validate the information in time.

    i find the suggestion to add a timestamp on when a given piece of
    information was updated last in the tracker very useful.
    possibly as a mouse-over or somesuch, in order to not clutter the
    already rather full page with even more information that is *usually*
    not important at all.


    What do you mean is unprofessional?

    That the information the "Debian system" is out dated.

    I personally feat at unease when people call other people
    "unprofessional" like this.
    such accusations just feel... unprofessional :-)



    Try to step into the role of a (new) user or a possible contributor.

    the tracker's audience is really Debian maintainers, not users.
    i don't know what the average user expects, but I assume that they are
    good enough with the information about what Debian actually *ships* (as
    in: what is packaged; and more likely: what is packaged in Debian/stable
    or even Debian/testing, and less so Debian/unstable) rather than whether "Debian" has been made aware that there is a new release minutes after
    it has been made available to the public.

    as for Debian maintainers: if they need super-short notice of a new
    package, then I do not see why they cannot track upstream themselves.
    after all, d/watch files tend to be buggy as well and give false
    information (or: upstream decided to switch to some new release scheme
    which simply breaks the existing d/watch) making them only so useful.

    in any case: why do *you* think it of utmost importance to be informed
    of a new release on this very page?



    Most of the maintainers are volunteers and work on packaging in their
    free time.

    Why do we have to increase the volume of the list with that topic? Can
    we just discuss this on an issue tracker about the tracker? ;)

    fair enough.
    however, it seems i cannot find your bug report (i checked both the BTS
    and your emails, but there is no indication of any existing bug report)

    gcmas
    IOhannes

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c.buhtz@posteo.jp@21:1/5 to emollier@debian.org on Sun Sep 17 13:20:01 2023
    Dear Étienne,

    On 2023-09-17 10:53 Étienne Mollier <emollier@debian.org> wrote:
    $ reportbug tracker.debian.org

    thanks for pointing this out.
    Sometimes it is to easy. I am not new to Debian but always forget about
    "pseudo packages".

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From c.buhtz@posteo.jp@21:1/5 to umlaeute@debian.org on Sun Sep 17 13:40:01 2023
    Dear IOhannes,

    thanks for your reply and your thoughts.

    On 2023-09-17 11:11 IOhannes m zmölnig (Debian/GNU)
    <umlaeute@debian.org> wrote:
    i get your point that you want the information fast, but it seems you
    are just using some arbitrary constraint that fits your personal need.
    it appears that for "most" Debian maintainers a lag of "1 or 2 days"

    I'm not a Debian maintainer.

    I do use that tracker page as an upstream maintainer.
    And I do use it as a usual user because the "usual" package pages (e.g. https://packages.debian.org/source/sid/backintime) are IMHO less
    comfortable to read.
    I like the dashboard character of the tracker.

    But I always try to take into account that there are a lot of different "flavors of users", especially in the context of our world ruling
    Debian. ;)

    I'm not the benchmark here. My benchmark is always all users in the
    world. Of course this is unrealistic. But it can be a goal. I mean, no
    matter that it is impossible to reach that goal, trying to reach it
    can improve Debian.

    I personally feat at unease when people call other people
    "unprofessional" like this.
    such accusations just feel... unprofessional :-)

    English as not my native language but to my understanding when
    scrolling back to my own messages I never addressed a person or group
    of person with that word. I addressed the feeling of users.
    I tried to be emphatic to "my" users and imagined that they would
    experience it as unprofessional.

    Please keep calm and step one step back.
    We all do love Debian and FOSS and most of us invest their free time in
    it. But please don't take everything personal.

    We may have different goals in context of usability and quality. But
    that is what the community is about. We need to talk about such things
    and evolve. The none-free-firmware thing is a very good (positiv!)
    example of that process no matter how the decision was at the end.

    How Debian "discuss" things and comes to conclusions is one thing that
    makes it so special compared to other distros and FOSS projects.

    the tracker's audience is really Debian maintainers, not users.

    We have no proof for that and I would disagree here.

    i don't know what the average user expects

    Me, too. I don't know. But I try to be empathic to them and also try to
    keep Debian in a good light to them.

    in any case: why do *you* think it of utmost importance to be
    informed of a new release on this very page?

    Because of my watch-file problem. First I thought the watch file is
    buggy and I invested time to understand what the problem is with it. In
    the end it was not buggy and I burned time.

    Kind
    Christian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andrey Rakhmatullin@21:1/5 to c.buhtz@posteo.jp on Sun Sep 17 14:10:01 2023
    On Sun, Sep 17, 2023 at 06:56:58AM +0000, c.buhtz@posteo.jp wrote:
    I assume I'm not the first one encountered it. Is there a bug tracker I
    can check or report that Issue?
    The footer of every tracker page says "Report problems to the tracker.debian.org pseudo-package in the Debian BTS."

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Michael Stehmann@21:1/5 to All on Sun Sep 17 17:00:02 2023
    Hello,

    "normal" users - like me - should use stable - like I do - neither
    testing nor unstable.

    So some days delay are ok for me, because it takes much more time until
    a new upstreanḿ version will reach stable (via backports) - if all.


    Kind regards
    Michael, who is also not a native speaker.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)