Re: [Spacewalk-list] Taskomatic : Debian repodata generation issue

2019-01-24 Thread Robert Paschedag
Am 24. Januar 2019 11:41:45 MEZ schrieb philippe bidault 
:
>Hi all,
>
>Something strange is happening on my Spacewalk 2.9: taskomatic is
>regenerating my Ubuntu repodatas some times to times:
>
>INFO   | jvm 1| 2019/01/24 03:34:00 | 2019-01-24 03:34:00,144
>[Thread-3446] INFO 
>com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter
>- File Modified Date:2019-01-24 03:05:24 CET
>INFO   | jvm 1| 2019/01/24 03:34:00 | 2019-01-24 03:34:00,144
>[Thread-3446] INFO 
>com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter
>- Channel Modified Date:2019-01-24 03:33:49
>CET
>INFO   | jvm 1| 2019/01/24 03:34:00 | 2019-01-24 03:34:00,374
>[Thread-3447] INFO 
>com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter
>- Generating new DEB repository for channel
>bionic-security
>INFO   | jvm 1| 2019/01/24 03:34:00 | 2019-01-24 03:34:00,544
>[Thread-3446] INFO 
>com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter
>- Generating new DEB repository for channel
>bionic-updates
>
>I know that this is the purpose of taskomatic, but this is really
>annoying
>as the "Packages" and "Release" files are "manually" generated, thus
>having
>taskomatic triggering their re-generation just break everything.
>
>I don't think remember having seen such behaviour in Spacewaok 2.8. Is
>there a way to force taskomatic to ignore the DEB repodatas ?
>
>Regards,
>Philippe.

This always happens. You have to make sure, that you keep (transfer) the 
timestamp of the original Packages and Packages.gz file after you modified 
them. See "touch -r ..."

Robert


-- 
sent from my mobile device

___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list


[Spacewalk-list] Taskomatic : Debian repodata generation issue

2019-01-24 Thread philippe bidault
Hi all,

Something strange is happening on my Spacewalk 2.9: taskomatic is
regenerating my Ubuntu repodatas some times to times:

INFO   | jvm 1| 2019/01/24 03:34:00 | 2019-01-24 03:34:00,144
[Thread-3446] INFO  com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter
- File Modified Date:2019-01-24 03:05:24 CET
INFO   | jvm 1| 2019/01/24 03:34:00 | 2019-01-24 03:34:00,144
[Thread-3446] INFO  com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter
- Channel Modified Date:2019-01-24 03:33:49
CET
INFO   | jvm 1| 2019/01/24 03:34:00 | 2019-01-24 03:34:00,374
[Thread-3447] INFO  com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter
- Generating new DEB repository for channel
bionic-security
INFO   | jvm 1| 2019/01/24 03:34:00 | 2019-01-24 03:34:00,544
[Thread-3446] INFO  com.redhat.rhn.taskomatic.task.repomd.RepositoryWriter
- Generating new DEB repository for channel
bionic-updates

I know that this is the purpose of taskomatic, but this is really annoying
as the "Packages" and "Release" files are "manually" generated, thus having
taskomatic triggering their re-generation just break everything.

I don't think remember having seen such behaviour in Spacewaok 2.8. Is
there a way to force taskomatic to ignore the DEB repodatas ?

Regards,
Philippe.
___
Spacewalk-list mailing list
Spacewalk-list@redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list