Hi,

What is DPT?

You are a bit too fast. The archive doesn't know about version
1:0.10.0-2 yet. What needs to happen on the UDD side is:
- UDD gets a mirror push notification from an archive mirror
- UDD updates its knowledge of the archive
- UDD runs the 'upstream' (= uscan data) importer (this happens every 30
mins)
+ it detects that there's a new version in Debian, updates the watch
file in the DB
+ it detects that the watchfile status needs to be refreshed, and
refreshes it

So in the normal case, approximately 30 mins after the mirror push, you
should have correct uscan information in UDD.

Since I don't know about DPT, I cannot help on that side.

Lucas


On 22/07/24 at 20:43 +0200, Patrice Duroux wrote:

sure, with the version column in UDD query output:

udd=> select source,version,watch_file,errors from upstream where source='xorgxrdp';
source | version |
watch_file | errors ----------+------------+-------------------------------------------------------------------------------------------+--------
xorgxrdp | 1:0.9.19-1 | version=4
+|
| |
https://github.com/neutrinolabs/@PACKAGE@/releases .*/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@+|
| |
|
xorgxrdp | 1:0.10.0-1 | version=4
+|
| |
https://github.com/neutrinolabs/@PACKAGE@/releases .*/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@+|
| |
|
(2 lignes)

Le lun. 22 juil. 2024 � 20:37, Patrice Duroux
<patrice.duroux@gmail.com> a �crit :

HI,

After the (very) recent upload of xorgxrdp (version1:0.10.0-2),
I was curious to check both DPT and UDD about it.
But currently DPT shows me:

Problems while searching for a new upstream version high
uscan had problems while searching for a new upstream version:

In debian/watch no matching files for watch line
https://github.com/neutrinolabs/xorgxrdp/releases .*/xorgxrdp(?:[-_]?[Vv]?(\d[\-+\.:\~\da-zA-Z]*))(?i)(?:\.(?:tar\.xz|tar\.bz2|tar\.gz|tar\.zstd?|zip|tgz|tbz|txz))

and UDD nothing special:

udd=> select source,watch_file,errors from upstream where source='xorgxrdp';
source | watch_file
| errors ----------+-------------------------------------------------------------------------------------------+--------
xorgxrdp | version=4
+|
| https://github.com/neutrinolabs/@PACKAGE@/releases .*/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@+|
|
|
xorgxrdp | version=4
+|
| https://github.com/neutrinolabs/@PACKAGE@/releases .*/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@+|
|
|

To me this is for the same d/watch file content but one reporting an error and the other one not, or do I have to check another UDD column than 'errors'?
In other words,how can I retrieve a list of packages with a watch
failure in DPT?

Best,
Patrice

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

Ah, I see what you mean.

I don't know where tracker.debian.org gets its data about upstream
status (and errors). I thought it was using UDD, but apparently it
isn't.

Lucas


On 22/07/24 at 23:12 +0200, Patrice Duroux wrote:

Sorry if I was not clear enough.

By DPT, I mean Debian Package Tracker.
The error shown there for this package correspond to a version <
1:0.10.0-2 and so to me UDD should be consistant no? (ie. having an error valoue and not null)
As d/watch is only fixed in -2.

Le lundi 22 juillet 2024, Lucas Nussbaum <lucas@debian.org> a �crit :

Hi,

What is DPT?

You are a bit too fast. The archive doesn't know about version
1:0.10.0-2 yet. What needs to happen on the UDD side is:
- UDD gets a mirror push notification from an archive mirror
- UDD updates its knowledge of the archive
- UDD runs the 'upstream' (= uscan data) importer (this happens every 30 mins)
+ it detects that there's a new version in Debian, updates the watch
file in the DB
+ it detects that the watchfile status needs to be refreshed, and
refreshes it

So in the normal case, approximately 30 mins after the mirror push, you should have correct uscan information in UDD.

Since I don't know about DPT, I cannot help on that side.

Lucas

On 22/07/24 at 20:43 +0200, Patrice Duroux wrote:

sure, with the version column in UDD query output:

udd=> select source,version,watch_file,errors from upstream where source='xorgxrdp';
source | version |
watch_file | errors ----------+------------+------------------------------------

-------------------------------------------------------+--------

xorgxrdp | 1:0.9.19-1 | version=4
+|
| | https://github.com/neutrinolabs/@PACKAGE@/releases .*/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@+|
| |
|
xorgxrdp | 1:0.10.0-1 | version=4
+|
| | https://github.com/neutrinolabs/@PACKAGE@/releases .*/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@+|
| |
|
(2 lignes)

Le lun. 22 juil. 2024 � 20:37, Patrice Duroux
<patrice.duroux@gmail.com> a �crit :

HI,

After the (very) recent upload of xorgxrdp (version1:0.10.0-2),
I was curious to check both DPT and UDD about it.
But currently DPT shows me:

Problems while searching for a new upstream version high
uscan had problems while searching for a new upstream version:

In debian/watch no matching files for watch line
https://github.com/neutrinolabs/xorgxrdp/releases .*/xorgxrdp(?:[-_]?[Vv]?(\d[\-+\.:\~\da-zA-Z]*))(?i)(?:\.(?:

tar\.xz|tar\.bz2|tar\.gz|tar\.zstd?|zip|tgz|tbz|txz))

and UDD nothing special:

udd=> select source,watch_file,errors from upstream where

source='xorgxrdp';

source | watch_file
| errors ----------+-------------------------------------------------

------------------------------------------+--------

xorgxrdp | version=4
+|
| https://github.com/neutrinolabs/@PACKAGE@/releases .*/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@+|
|
|
xorgxrdp | version=4
+|
| https://github.com/neutrinolabs/@PACKAGE@/releases .*/@PACKAGE@@ANY_VERSION@@ARCHIVE_EXT@+|
|
|

To me this is for the same d/watch file content but one reporting an

error

and the other one not, or do I have to check another UDD column than

'errors'?

In other words,how can I retrieve a list of packages with a watch failure in DPT?

Best,
Patrice

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

On Mon, Jul 22, 2024 at 11:35:13PM +0200, Lucas Nussbaum wrote:

I don't know where tracker.debian.org gets its data about upstream
status (and errors). I thought it was using UDD, but apparently it
isn't.

It is: https://salsa.debian.org/qa/distro-tracker/-/blob/master/distro_tracker/vendor/debian/tracker_tasks.py?ref_type=heads#L1402

don't know if there is any import error ongoing, though.

--
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
More about me: https://mapreri.org : :' : Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-

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

iQIzBAEBCgAdFiEEi3hoeGwz5cZMTQpICBa54Yx2K60FAmafYbYACgkQCBa54Yx2 K62zuA//YdgsBR16SBcd5wUPAf9IHsTf/AfYx2S9E+5ecZQ5CAQr5rSJgyFDygbJ RiWCpF4Ww0XozVu9BJq+xYG18XqY6bLjVZWGZQ1kv/nkko2qfrxotSk+0SvPj0Ai Ip5E+K9qGaDwVmRii9N1KTk+/iewWZ8qLquKL0RfSTbbefInDFiKLZoNowWaU8P5 JXrjOJzlKWE3a5rwRXv68Ypf8F+f5179SoseSiVk0BOdDwoi4e99MaeFL23QE175 pSY3n/WJwb8e2pn5uvqcWJtCGI6rVxcAJd89xsy8A7AjsE3WMod2OMd5fR9HbL/N FD65hurbgJcf/wfnRQNWk8YgmToTlchAwbSOk86D7w+wVuhK6UrHEXhnM4IeXjVY w/SlXeeCZlCPnLO70CNfJztwbMjgA9KsF5OwSp80qnunTcAursrDn9cDa+54gkdU SppyorAzUjfJv2j6E6D3k1PlxjKYk7F9M/eJCwQGxS2fGVuXbtZ5smEvAuUzY6Am Q74LLCD5s6RoJwBok4pC4I+cCfCqHYb97EdVLlPGb8wHWcC7YHH

On Tue, 23 Jul 2024, Mattia Rizzolo wrote:

On Mon, Jul 22, 2024 at 11:35:13PM +0200, Lucas Nussbaum wrote:

I don't know where tracker.debian.org gets its data about upstream
status (and errors). I thought it was using UDD, but apparently it
isn't.

It is: https://salsa.debian.org/qa/distro-tracker/-/blob/master/distro_tracker/vendor/debian/tracker_tasks.py?ref_type=heads#L1402

don't know if there is any import error ongoing, though.

I have no sign of error in the import process right now.
But https://tracker.debian.org/pkg/xorgxrdp now shows info about new
upstream release 0.10.1 so the problem (if any) is no longer visible.

Cheers,
--
⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hertzog@debian.org>
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/
⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS

-----BEGIN PGP SIGNATURE-----
Comment: Signed by Raphael Hertzog

iQEzBAABCgAdFiEE1823g1EQnhJ1LsbSA4gdq+vCmrkFAmafakQACgkQA4gdq+vC mrm0TQf+JFf0cII0N2yrzwsvMkmwFHZ9b+QENSGsC72DyNNf7jE2qyUdrrjsw/1L BCRWFZ3vuyMlG6C6hEJsRS92eDYvnbE5t7ObsBsZent9+JoimIkkxuHpefd7x0Ur I+x38eRm/659BMkXz+jcv24gsimRpJzXLIqDK375qmHTVqD+XhahpjV7+uJxcJKc eq3EEIu8T+tf2PmoGGOFIzxX/bIruLb2EzdfKBI6sDyAkPuCbyrQ6oAAa4f7BrBG OuoWuHdJdVjgVQzsaFZyanpmNdRNvuXM+/kMeKSzGUbEKwH57hfE7HQBzr7ks7ng MOpXE0UrFZokV0EdqnWQp09LW1Q4kQ==
=6OSh
-----END PGP SIGNATURE-----

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

Hi Patrice,

xorgxrdp at Salsa is still on the previous version and using a clone
here is what I am getting:

$ git clone https://salsa.debian.org/debian-remote-team/xorgxrdp.git
$ cd xorgxrdp
$ uscan
uscan warn: In debian/watch no matching files for watch line
https://github.com/neutrinolabs/xorgxrdp/releases .*/xorgxrdp(?:[-_]?v?(\d[\-+\.:\~\da-zA-Z]*))(?i)(?:\.(?:tar\.xz|tar\.bz2|tar\.gz|tar\.zstd?|zip|tgz|tbz|txz))

Indeed it took me a while to get the salsa repos updated for xorgxrdp
and xrdp.
That's done now.

Best,
Alex

so I think that DPT was right, isn't it?

Le mar. 23 juil. 2024 à 10:31, Raphael Hertzog <hertzog@debian.org> a
écrit :

On Tue, 23 Jul 2024, Mattia Rizzolo wrote:

On Mon, Jul 22, 2024 at 11:35:13PM +0200, Lucas Nussbaum wrote:

I don't know where tracker.debian.org gets its data about upstream
status (and errors). I thought it was using UDD, but apparently it
isn't.

It is:
https://salsa.debian.org/qa/distro-tracker/-/blob/master/distro_tracker/vendor/debian/tracker_tasks.py?ref_type=heads#L1402

don't know if there is any import error ongoing, though.

I have no sign of error in the import process right now.
But https://tracker.debian.org/pkg/xorgxrdp now shows info about new
upstream release 0.10.1 so the problem (if any) is no longer visible.

Cheers,
--
⢀⣴⠾⠻⢶⣦⠀ Raphaël Hertzog <hertzog@debian.org>
⣾⠁⢠⠒⠀⣿⡁
⢿⡄⠘⠷⠚⠋ The Debian Handbook: https://debian-handbook.info/get/
⠈⠳⣄⠀⠀⠀⠀ Debian Long Term Support: https://deb.li/LTS

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