On Tue, Jan 24, 2017 at 03:12:10PM +0100, Michal Novotny wrote:
>Otherwise, in the fix that I am going to apply tomorrow, there will some
>additional fields for chroot.start and build.start messages.
>
>For chroot.start:
>- status (int)
>- version (str)
>For build.start:
>
On Tue, Jan 24, 2017 at 01:36:59PM +0100, Michal Novotny wrote:
>On Tue, Jan 24, 2017 at 11:44 AM, Pierre-Yves Chibon
>wrote:
>
> On Tue, Jan 24, 2017 at 11:30:33AM +0100, Michal Novotny wrote:
> >Â Â Yes, untested changes got into production. We are sorry. I am
> current
On Tue, Jan 24, 2017 at 03:08:52PM +0100, Pavel Raiskup wrote:
> On Tuesday, January 24, 2017 12:58:00 PM CET Michal Novotny wrote:
> > Hello, I will deploy fedmsg hotfix tomorrow at 7:30am UTC. I am very sorry
> > for the inconvenience.
>
> I'm very sorry too. I failed with testing this against
Otherwise, in the fix that I am going to apply tomorrow, there will some
additional fields for chroot.start and build.start messages.
For chroot.start:
- status (int)
- version (str)
For build.start:
- status (int)
- version (str)
- chroot (str)
The old fields will be all there with the same typ
On Tuesday, January 24, 2017 12:58:00 PM CET Michal Novotny wrote:
> Hello, I will deploy fedmsg hotfix tomorrow at 7:30am UTC. I am very sorry
> for the inconvenience.
I'm very sorry too. I failed with testing this against fedmsg because I was
even unable to connect to fedmsg. And I did not rea
On Tue, Jan 24, 2017 at 11:44 AM, Pierre-Yves Chibon
wrote:
> On Tue, Jan 24, 2017 at 11:30:33AM +0100, Michal Novotny wrote:
> >Yes, untested changes got into production. We are sorry. I am
> currently
> >working on a fix.
>
> If that made it up to production, then we'll need to adjust f
On Tue, Jan 24, 2017 at 11:30:33AM +0100, Michal Novotny wrote:
>Yes, untested changes got into production. We are sorry. I am currently
>working on a fix.
If that made it up to production, then we'll need to adjust fedmsg_meta to
support these messages as well.
fedmsg_meta should work fo
Hello, I will deploy fedmsg hotfix tomorrow at 7:30am UTC. I am very sorry
for the inconvenience.
clime
___
copr-devel mailing list -- copr-devel@lists.fedorahosted.org
To unsubscribe send an email to copr-devel-le...@lists.fedorahosted.org
Hi guys
I have standard mock building packages for RHEL with the following
configuration:
---
config_opts['root'] = 'rhel-7-x86_64'
config_opts['target_arch'] = 'x86_64'
config_opts['legal_host_arches'] = ('x86_64',)
config_opts['chroot_setup_cmd'] = 'install bash bzip2 cpio diff
Yes, untested changes got into production. We are sorry. I am currently
working on a fix.
On Tue, Jan 24, 2017 at 11:02 AM, Pierre-Yves Chibon
wrote:
> Hi all,
>
> We have recently been receiving emails about wrongly formatted fedmsg
> message
> coming from copr in stg.
> Has there been any chan
Thanks
That fixed it...
Right now I need to add the following to
/usr/lib/python2.7/site-packages/pyrpkg/__init__.py:
@@ -2381,6 +2381,9 @@
replace=replace)
gitignore = GitIgnore(os.path.join(self.path, '.gitignore'))
+oldpath = os.getcwd()
+
Hi all,
We have recently been receiving emails about wrongly formatted fedmsg message
coming from copr in stg.
Has there been any changes made to the structure of the messages sent in stg?
To give you an idea, this is what we received:
Traceback (most recent call last):
File "/usr/lib/python2.7
12 matches
Mail list logo
