On Fri, Dec 20, 2019 at 08:12:26AM +1000, Jeff Fearn wrote:
>
> I think ATM the problem is there is one component for a module so if
> that module has 50 packages in it how do you report a bug against a
> specific package in it?
Well, since one person or group "owns" the module, I would just expe
On Thu, Dec 19, 2019 at 12:19:39PM -0800, Kevin Fenzi wrote:
On Wed, Dec 18, 2019 at 02:52:03PM -0500, Robbie Harwood wrote:
David Cantrell writes:
...snip...
> I would like to see modules have a stronger policy around tracking and
> handling CVEs. At the very least, what Fedora already do
On Wed, Dec 18, 2019 at 02:52:03PM -0500, Robbie Harwood wrote:
David Cantrell writes:
On Tue, Dec 17, 2019 at 11:21:45PM +0100, Miro Hrončok wrote:
On 17. 12. 19 21:57, David Cantrell wrote:
1) Are modules allowed to bundle packages that are provided by and
currently maintained in the base
On 20/12/19 06:22, Kevin Fenzi wrote:
> On Thu, Dec 19, 2019 at 09:29:36AM +1000, Jeff Fearn wrote:
>> On 19/12/19 01:00, David Cantrell wrote:
>>> On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote:
Just FTR, for Red Hat Software Collections, we are (ab)using "Version"
BZ field
On Thu, 2019-12-19 at 12:13 +, Petr Pisar wrote:
> On 2019-12-17, David Cantrell wrote:
> > 4) How can users determine what packages are installed from a module and how
> > can you see what, if any, module "owns" a package? I have been unable to
> > determine how to do this from dnf.
> >
> B
On Thu, Dec 19, 2019 at 09:29:36AM +1000, Jeff Fearn wrote:
> On 19/12/19 01:00, David Cantrell wrote:
> > On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote:
> >> Just FTR, for Red Hat Software Collections, we are (ab)using "Version"
> >> BZ field to track the SCL version (e.g. [1]), whic
On Wed, Dec 18, 2019 at 02:52:03PM -0500, Robbie Harwood wrote:
> David Cantrell writes:
...snip...
> > I would like to see modules have a stronger policy around tracking and
> > handling CVEs. At the very least, what Fedora already does for
> > regular packages.
>
> I would like this as well,
On 19. 12. 19 13:13, Petr Pisar wrote:
On 2019-12-17, David Cantrell wrote:
4) How can users determine what packages are installed from a module and how
can you see what, if any, module "owns" a package? I have been unable to
determine how to do this from dnf.
By asking dnf. perl-libs-5.30.1
Dne 19. 12. 19 v 10:36 Jeff Fearn napsal(a):
> On 19/12/2019 6:31 pm, Vít Ondruch wrote:
>> Dne 19. 12. 19 v 0:29 Jeff Fearn napsal(a):
>>> On 19/12/19 01:00, David Cantrell wrote:
On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote:
> Just FTR, for Red Hat Software Collections, w
On 2019-12-17, David Cantrell wrote:
> 4) How can users determine what packages are installed from a module and how
> can you see what, if any, module "owns" a package? I have been unable to
> determine how to do this from dnf.
>
By asking dnf. perl-libs-5.30.1-449.fc32.x86_64 is a non-modular pa
On 19/12/2019 6:31 pm, Vít Ondruch wrote:
>
> Dne 19. 12. 19 v 0:29 Jeff Fearn napsal(a):
>> On 19/12/19 01:00, David Cantrell wrote:
>>> On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote:
Just FTR, for Red Hat Software Collections, we are (ab)using "Version"
BZ field to track
On 18. 12. 19 15:53, David Cantrell wrote:
Maybe if a module bundles a package, the module maintainer also becomes a
co-maintainer on the bundled package?
How this appears to work now:
1. If one bundles a package in a module they need to create a stream branch
(unless they bundle form master/
Dne 19. 12. 19 v 0:29 Jeff Fearn napsal(a):
> On 19/12/19 01:00, David Cantrell wrote:
>> On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote:
>>> Just FTR, for Red Hat Software Collections, we are (ab)using "Version"
>>> BZ field to track the SCL version (e.g. [1]), which in module
>>> te
On 19/12/19 01:00, David Cantrell wrote:
> On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote:
>> Just FTR, for Red Hat Software Collections, we are (ab)using "Version"
>> BZ field to track the SCL version (e.g. [1]), which in module
>> terminology resembles stream. Maybe we could reuse so
David Cantrell writes:
> On Tue, Dec 17, 2019 at 11:21:45PM +0100, Miro Hrončok wrote:
>> On 17. 12. 19 21:57, David Cantrell wrote:
>>> 1) Are modules allowed to bundle packages that are provided by and
>>> currently maintained in the base system? Are there are restrictions
>>> to what a module
On ke, 18 joulu 2019, David Cantrell wrote:
On Wed, Dec 18, 2019 at 03:34:34PM +0100, Fabio Valentini wrote:
On Wed, Dec 18, 2019, 14:29 Alexander Bokovoy wrote:
On ke, 18 joulu 2019, Kevin Kofler wrote:
Vít Ondruch wrote:
Also, it is interesting that AFAIK, we have not yet dealt with issue
On Wed, Dec 18, 2019 at 03:29:14PM +0200, Alexander Bokovoy wrote:
On ke, 18 joulu 2019, Kevin Kofler wrote:
Vít Ondruch wrote:
Also, it is interesting that AFAIK, we have not yet dealt with issue
like this (i.e. reporting issues against specific streams) for RHEL8 yet.
How can Modularity hav
On Wed, Dec 18, 2019 at 03:34:34PM +0100, Fabio Valentini wrote:
On Wed, Dec 18, 2019, 14:29 Alexander Bokovoy wrote:
On ke, 18 joulu 2019, Kevin Kofler wrote:
>Vít Ondruch wrote:
>> Also, it is interesting that AFAIK, we have not yet dealt with issue
>> like this (i.e. reporting issues agains
On Wed, Dec 18, 2019 at 01:00:03PM +0100, Vít Ondruch wrote:
Dne 17. 12. 19 v 21:57 David Cantrell napsal(a):
With regard to the recent protobuf package issue and the eclipse
module, I
started wondering how bugs work with packages bundled in modules.
That is,
packages that exist outside module
On Tue, Dec 17, 2019 at 05:21:36PM -0700, John M. Harris Jr wrote:
On Tuesday, December 17, 2019 1:57:09 PM MST David Cantrell wrote:
With regard to the recent protobuf package issue and the eclipse module, I
started wondering how bugs work with packages bundled in modules. That is,
packages th
On Tue, Dec 17, 2019 at 11:21:45PM +0100, Miro Hrončok wrote:
On 17. 12. 19 21:57, David Cantrell wrote:
1) Are modules allowed to bundle packages that are provided by and currently
maintained in the base system? Are there are restrictions to what a module
can bundle (e.g., can a module bundle
On Wed, Dec 18, 2019, 14:29 Alexander Bokovoy wrote:
> On ke, 18 joulu 2019, Kevin Kofler wrote:
> >Vít Ondruch wrote:
> >> Also, it is interesting that AFAIK, we have not yet dealt with issue
> >> like this (i.e. reporting issues against specific streams) for RHEL8
> yet.
> >
> >How can Modulari
On ke, 18 joulu 2019, Kevin Kofler wrote:
Vít Ondruch wrote:
Also, it is interesting that AFAIK, we have not yet dealt with issue
like this (i.e. reporting issues against specific streams) for RHEL8 yet.
How can Modularity have been forced to production in both Fedora and RHEL
without somethin
Vít Ondruch wrote:
> Also, it is interesting that AFAIK, we have not yet dealt with issue
> like this (i.e. reporting issues against specific streams) for RHEL8 yet.
How can Modularity have been forced to production in both Fedora and RHEL
without something as basic as this figured out? Inability
Dne 17. 12. 19 v 21:57 David Cantrell napsal(a):
> With regard to the recent protobuf package issue and the eclipse
> module, I
> started wondering how bugs work with packages bundled in modules.
> That is,
> packages that exist outside modules (e.g., protobuf) that end up
> bundled with
> some m
On Tuesday, December 17, 2019 1:57:09 PM MST David Cantrell wrote:
> With regard to the recent protobuf package issue and the eclipse module, I
> started wondering how bugs work with packages bundled in modules. That is,
> packages that exist outside modules (e.g., protobuf) that end up bundled
>
On 17. 12. 19 21:57, David Cantrell wrote:
1) Are modules allowed to bundle packages that are provided by and currently
maintained in the base system? Are there are restrictions to what a module
can bundle (e.g., can a module bundle glibc)?
I am not aware of any policy against modularizing exi
27 matches
Mail list logo
