Hello Dominique,
Another rookie question (sorry for bothering) :-) Is there a way to make the
`unreserve` work in this command queue:
$ osc collab update --project GNOME:Next libsigc++3
# Then I found I just wanted to play with upstream build instead of
really
# reserving it, so I wanted to release it immediately:
$ osc collab todo --project GNOME:Next | grep 'libsigc++3' # it's
marked as reserved
libsigc++3 | 2.99.12 | 2.99.12 |
2.99.13 (r)
$ osc collab unreserve libsigc++3
Cannot unreserve package libsigc++3: Package not reserved # :-(
Best wishes,
Yifan
On Tue, Aug 27, 2019 at 09:22:36AM +0000, Yi Fan Jiang wrote:
> Hi Dominique,
>
> Thank you very much for working on the tool and fixing the cronjob. It works
> now and `osc collab todo --project GNOME:Next | wc -l` only gives 104 result,
> which was 113 or so yesterday :-)
>
> Best wishes,
> Yifan
>
> On Tue, Aug 27, 2019 at 10:53:03AM +0200, Dominique Leuenberger / DimStar
> wrote:
> > hi Yifan,
> >
> > On Tue, 2019-08-27 at 01:46 +0000, Yi Fan Jiang wrote:
> > > Hello good people,
> > >
> > > I am pretty new to the collab plugin and found something I did not fully
> > > understand. I am putting the mail here since I saw the collab plugin was
> > > heavily used by the GNOME project :-) Please let me know if this should
> > > go to
> > > the packaging list.
> >
> >
> > You're right in reaching out here - the plugin was originally created
> > by Vincent and now mainly under maintenance by myself (more or less
> > active).
> >
> > > As seen below, the version of GNOME:Next/libsigc++2 was given as 2.10.1,
> > > however the real version of the package is already 2.10.2. Is it expected?
> > >
> > > $ osc collab todo --project GNOME:Next | grep -e sig -e 'Package'
> > >
> > > Package | Parent Project | GNOME:Next |
> > > Upstream
> > > libsigc++2 | 2.10.1 | 2.10.1 |
> > > 2.10.2
> > > libsigc++3 | 2.99.12 | 2.99.12 |
> > > 2.99.13
> >
> > Grr.. that's my bad - just recently I fixed the collab server to show
> > stuff at all again (it was non-functional for a few months) and when I
> > did so, I disabled the cronjob catching up with he OBS live content
> > (originally we queried RSS feeds, but OBS no longer provides them, so
> > we have to be more aggressive in querying OBS)
> >
> > I have no re-enabled the cron job - and thins should settle withing 20
> > - 30 minutes. Let me know if there is something else you encounter.
- Yifan
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
