- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jan 8 2023
Oct 19 2022
Dec 22 2021
Package upgraded in T3705.
Dec 17 2021
Dec 15 2021
Sep 16 2021
And stable is good [2]
unstable build passed [1]
So now, back on plain old failures about missing deps.
olasd to the rescue:
In the end, that won't solve the problem mentioned by apt [1].
Well, D2676 should only take care of the warning about the missing key.
In the end, that won't solve the problem mentioned by apt [1].
Sep 2 2021
17:17 <+ardumont> just out of curiosity, not that i'm on that right now 17:20 <+ardumont> on an elastic node, we'd get 17:20 <+ardumont> ardumont@esnode1:~% apt-cache show journalbeat | grep Version | awk '{print $2}' | sort -V -r | head -1 17:20 <+ardumont> 7.14.1 17:20 <+ardumont> we'd have some choice 17:22 <+olasd> ardumont: no objections. the main concern is that the upstream mapping from journalctl fields to elasticsearch documents has changed, so we'd need to adapt the (overall, very few) filters we have 17:22 <+olasd> and probably some dashboard churn
Apr 27 2021
Apr 21 2021
Mar 25 2021
Feb 26 2021
Deployed and icinga check went fine.
whether mypy is happy is another matter though...
django version:
ii python3-django 1:1.11.29-1~deb10u1 all High-level Python web development framework (Python 3 version)
Feb 22 2021
At last, trigger back the puppet on worker3.internal.staging.swh.network:
root@worker3:~# puppet agent --test Info: Using configured environment 'staging' Info: Retrieving pluginfacts Info: Retrieving plugin Info: Retrieving locales Info: Loading facts Info: Caching catalog for worker3.internal.staging.swh.network Info: Applying configuration version '1613999976' Notice: /Stage[main]/Profile::Swh::Deploy::Worker::Indexer_fossology_license/Package[fossology-nomossa]/ensure: created Notice: /Stage[main]/Profile::Swh::Deploy::Worker::Indexer_fossology_license/Profile::Swh::Deploy::Worker::Instance[indexer_fossology_license]/File[/etc/softwareheritage/indexer_fossology_license.yml]/ensure: defined content as '{md5}71db8b37a3e1b963a2ec9f6e4a6a00c0' Notice: /Stage[main]/Profile::Swh::Deploy::Worker::Indexer_fossology_license/Profile::Swh::Deploy::Worker::Instance[indexer_fossology_license]/Service[swh-worker@indexer_fossology_license]/enable: enable changed 'false' to 'true' Notice: /Stage[main]/Profile::Swh::Deploy::Worker::Indexer_fossology_license/Profile::Swh::Deploy::Worker::Instance[indexer_fossology_license]/Systemd::Dropin_file[swh-worker@indexer_fossology_license/parameters.conf]/File[/etc/systemd/system/swh-worker@indexer_fossology_license.service.d]/ensure: created Notice: /Stage[main]/Profile::Swh::Deploy::Worker::Indexer_fossology_license/Profile::Swh::Deploy::Worker::Instance[indexer_fossology_license]/Systemd::Dropin_file[swh-worker@indexer_fossology_license/parameters.conf]/File[/etc/systemd/system/swh-worker@indexer_fossology_license.service.d/parameters.conf]/ensure: defined content as '{md5}bab06958a00a4880e94c5f20e82d8b50' Info: /Stage[main]/Profile::Swh::Deploy::Worker::Indexer_fossology_license/Profile::Swh::Deploy::Worker::Instance[indexer_fossology_license]/Systemd::Dropin_file[swh-worker@indexer_fossology_license/parameters.conf]/File[/etc/systemd/system/swh-worker@indexer_fossology_license.service.d/parameters.conf]: Scheduling refresh of Class[Systemd::Systemctl::Daemon_reload] Info: Class[Systemd::Systemctl::Daemon_reload]: Scheduling refresh of Exec[systemctl-daemon-reload] Notice: /Stage[main]/Systemd::Systemctl::Daemon_reload/Exec[systemctl-daemon-reload]: Triggered 'refresh' from 1 event Notice: Applied catalog in 8.41 seconds
Finally unstuck this.
Feb 16 2021
Package swh.storage 0.23.1 built both for stable and unstable.
Now stable build is stuck on storage tests, the one using a journal.
Status, unstable build is now ok.
For the previous tryout to work, we need to exclude all unwanted jres.
Tryout in progress
Another suggestion which sounds more standard, debian build wise:
13:05 <+olasd> I think you can just add a `Build-Conflicts: openjdk-17-jre-headless` 13:06 <+olasd> which should make the sbuild dependency resolver avoid it altogether 13:10 <+ardumont> ack, i'll try
Another solution (to prevent hard-coding JAVA_HOME) is to invert the dependency order
currently defined in debian/rules.
Forcing JAVA_HOME to a jdk11
What changed from the last unstable build ok [1] to the new failing one [2], the jdk
versions pulled for the build changed.
Feb 15 2021
Status: package mercurial needed to be backported for buster-swh [1]
Done pairing with olasd (as tutor ;) and vsellier.
Feb 11 2021
Note:
10:40 <+olasd> ardumont: btw, I've been looking for the fossology-nomossa package for stretch, and I don't have it on this laptop; I suspect I just pulled the previous source and just bumped the version and rebuilt the package with no changes 10:40 <+olasd> ardumont: you could debdiff the jessie and stretch versions to see what happened... 10:42 <+ardumont> i'm fuzzy on the command to actually rebuild it (i guess our gbp/sbuild stanza will work) 10:43 <+ardumont> til on debdiff, thx for the hints
Feb 10 2021
I guess the only way to fix the build will be to backport mercurial bullseye package to buster.
It seems new code recently introduced in the loader now directly uses the mercurial internal Python modules.
Feb 9 2021
I took a stab at it but i came up moot so far.
Feb 8 2021
Feb 4 2021
Feb 3 2021
Jan 6 2021
Nov 23 2020
Packages have been tagged and built.
So this can be closed now.
The second part, the actual clean up will be dealt with in T2808.
Nov 21 2020
Nov 20 2020
Nov 9 2020
grrr, come on, i already opened one... T2746...