Re: Fedora Atomic Host Two Week Release Announcement: 29.20190414.0

2019-04-16 Thread Robert Fairley
An example of the diff between this and the previous released version (for
x86_64) is:

rpm-ostree db diff
a39e99a72c80c9c4a8fce8a2092b2856f742a5c3ba5c9bedd59a9e76aa3e9924
3fa99cde65f41035e0a912643b64251cc84eec8fedd53ca42df2c4857d569639
ostree diff commit old:
a39e99a72c80c9c4a8fce8a2092b2856f742a5c3ba5c9bedd59a9e76aa3e9924
ostree diff commit new:
3fa99cde65f41035e0a912643b64251cc84eec8fedd53ca42df2c4857d569639
Upgraded:
  audit 3.0-0.5.20181218gitbdb72c0.fc29 -> 3.0-0.7.20190326git03e7489.fc29
  audit-libs 3.0-0.5.20181218gitbdb72c0.fc29 ->
3.0-0.7.20190326git03e7489.fc29
  cockpit-bridge 190-1.fc29 -> 191-1.fc29
  cockpit-docker 190-1.fc29 -> 191-1.fc29
  cockpit-networkmanager 190-1.fc29 -> 191-1.fc29
  cockpit-system 190-1.fc29 -> 191-1.fc29
  container-selinux 2:2.91-1.gitacc6941.fc29 -> 2:2.94-1.git1e99f1d.fc29
  containers-common 1:0.1.35-1.git404c5bd.fc29 -> 1:0.1.35-2.git404c5bd.fc29
  fuse 2.9.9-1.fc29 -> 2.9.9-2.fc29
  fuse-common 3.4.2-1.fc29 -> 3.4.2-2.fc29
  fuse-libs 2.9.9-1.fc29 -> 2.9.9-2.fc29
  fuse-overlayfs 0.3-5.dev.git8ec68ae.fc29 -> 0.3-8.dev.gita6958ce.fc29
  fuse3-libs 3.4.2-1.fc29 -> 3.4.2-2.fc29
  glibc 2.28-26.fc29 -> 2.28-27.fc29
  glibc-all-langpacks 2.28-26.fc29 -> 2.28-27.fc29
  glibc-common 2.28-26.fc29 -> 2.28-27.fc29
  hostname 3.20-6.fc29 -> 3.20-7.fc29
  kernel 5.0.4-200.fc29 -> 5.0.7-200.fc29
  kernel-core 5.0.4-200.fc29 -> 5.0.7-200.fc29
  kernel-modules 5.0.4-200.fc29 -> 5.0.7-200.fc29
  librepo 1.9.6-1.fc29 -> 1.9.6-2.fc29
  libsolv 0.7.4-1.fc29 -> 0.7.4-2.fc29
  linux-firmware 20190213-93.git710963fe.fc29 -> 20190312-94.fc29
  linux-firmware-whence 20190213-93.git710963fe.fc29 -> 20190312-94.fc29
  pcre2 10.32-8.fc29 -> 10.32-9.fc29
  podman 1:1.1.2-1.git0ad9b6b.fc29 -> 1:1.2.0-2.git3bd528e.fc29
  python2-audit 3.0-0.5.20181218gitbdb72c0.fc29 ->
3.0-0.7.20190326git03e7489.fc29
  python3 3.7.2-5.fc29 -> 3.7.3-1.fc29
  python3-audit 3.0-0.5.20181218gitbdb72c0.fc29 ->
3.0-0.7.20190326git03e7489.fc29
  python3-libs 3.7.2-5.fc29 -> 3.7.3-1.fc29
  rpm-ostree 2019.2-1.fc29 -> 2019.3-1.fc29
  rpm-ostree-libs 2019.2-1.fc29 -> 2019.3-1.fc29
  selinux-policy 3.14.2-51.fc29 -> 3.14.2-53.fc29
  selinux-policy-targeted 3.14.2-51.fc29 -> 3.14.2-53.fc29
  skopeo 1:0.1.35-1.git404c5bd.fc29 -> 1:0.1.35-2.git404c5bd.fc29
  sos 3.6-4.fc29 -> 3.7-1.fc29
  tzdata 2018i-1.fc29 -> 2019a-1.fc29
  vim-minimal 2:8.1.998-1.fc29 -> 2:8.1.1137-1.fc29
  zchunk-libs 1.0.4-1.fc29 -> 1.1.0-1.fc29
Added:
  fedora-repos-ostree-29-5.noarch
  libmodulemd1-1.8.6-2.fc29.x86_64

x86_64 AMIs are here:
Fedora-AtomicHost-29-20190414.0.x86_64eu-west-2
ami-0bd332308bc3eba3e hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64ap-northeast-1
 ami-08efa8173fff3eed5 hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64eu-central-1
 ami-0688e285ec827b754 hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64us-west-1
ami-08c7ed821cb1fd96e hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64us-west-2
ami-057420b7ffc1693d3 hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64ap-southeast-2
 ami-01bd4bfc033057635 hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64ca-central-1
 ami-0257477b2daa8537b hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64ap-southeast-1
 ami-0c65755f9d937d4ab hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64sa-east-1
ami-03e5ca1d15a5e905d hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64ap-northeast-2
 ami-0c74edb4ed48a1ea0 hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64eu-west-1
ami-006336604d5af77ef hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64ap-south-1
 ami-0a489967ae23505e1 hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64us-east-1
ami-06c265399b45b5603 hvm   gp2
Fedora-AtomicHost-29-20190414.0.x86_64eu-west-2
ami-0feb622c519791e60 hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64ap-northeast-1
 ami-020c6abfe8d647756 hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64eu-central-1
 ami-018e5f039cd07f4d2 hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64us-west-1
ami-0c19ed8ad28100504 hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64us-west-2
ami-04f9f2b66737c87f3 hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64ap-southeast-2
 ami-07b851fd42ae8530e hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64ca-central-1
 ami-0a101ac57cd320666 hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64ap-southeast-1
 ami-025ccb3a8083b11da hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64sa-east-1
ami-0bcc21570f1c10a54 hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64ap-northeast-2
 ami-0be3498a6852e800f hvm   standard
Fedora-AtomicHost-29-20190414.0.x86_64eu-west-1
ami-0140d503b655f2942 hvm   standard
Fedora-AtomicHost-29-201904

Re: `dnf system-upgrade download` throws RuntimeError: TransactionItem not found for key: rtkit

2019-04-16 Thread Christian Stadelmann
This was fallout from an older bug in rtkit's rpm scripts: 
https://bugzilla.redhat.com/show_bug.cgi?id=1637496. Thanks for the help!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


`dnf system-upgrade download` throws RuntimeError: TransactionItem not found for key: rtkit

2019-04-16 Thread Christian Stadelmann
I am running in a reproducible traceback which happens during `dnf 
system-upgrade download` as reported in 
https://bugzilla.redhat.com/show_bug.cgi?id=1700551. Does anyone know whether 
this will let me run into upgrade issues?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: fedora-img-dl: a tool for downloading Fedora iso's and images

2019-04-16 Thread Adam Williamson
On Tue, 2019-04-16 at 21:55 +0100, Richard W.M. Jones wrote:
> On Mon, Apr 15, 2019 at 09:57:26AM -0700, Adam Williamson wrote:
> > On Mon, 2019-04-15 at 17:22 +0800, Jens-Ulrik Petersen wrote:
> > > Hi, I made a small cli tool for downloading Fedora iso's etc.
> > > 
> > > It can download rawhide, branched, beta, and released isos (eg Workstation
> > > Live etc), and even WS Live respins (support for spins coming later).
> > > 
> > > You can try it now from <
> > > https://copr.fedorainfracloud.org/coprs/petersen/fedora-img-dl/>;;.
> > > 
> > > Feedback is welcome.
> > 
> > I already basically wrote this:
> > 
> > https://pagure.io/fedora-qa/fedfind
> > 
> > it has a lot more capabilities, and is used quite heavily in various
> > tools and processes the QA team uses.
> 
> Well I can go one better here and say there's a way to *not* download
> the ISOs :-)
> 
> https://rwmj.wordpress.com/2019/04/13/virt-install-nbdkit-live-install/#content

But you still need to know where the ISO you want to use *is*, which
fedfind can help you with ;)
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: fedora-img-dl: a tool for downloading Fedora iso's and images

2019-04-16 Thread Richard W.M. Jones
On Mon, Apr 15, 2019 at 09:57:26AM -0700, Adam Williamson wrote:
> On Mon, 2019-04-15 at 17:22 +0800, Jens-Ulrik Petersen wrote:
> > Hi, I made a small cli tool for downloading Fedora iso's etc.
> > 
> > It can download rawhide, branched, beta, and released isos (eg Workstation
> > Live etc), and even WS Live respins (support for spins coming later).
> > 
> > You can try it now from <
> > https://copr.fedorainfracloud.org/coprs/petersen/fedora-img-dl/>;.
> > 
> > Feedback is welcome.
> 
> I already basically wrote this:
> 
> https://pagure.io/fedora-qa/fedfind
> 
> it has a lot more capabilities, and is used quite heavily in various
> tools and processes the QA team uses.

Well I can go one better here and say there's a way to *not* download
the ISOs :-)

https://rwmj.wordpress.com/2019/04/13/virt-install-nbdkit-live-install/#content

Rich.

-- 
Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones
Read my programming and virtualization blog: http://rwmj.wordpress.com
Fedora Windows cross-compiler. Compile Windows programs, test, and
build Windows installers. Over 100 libraries supported.
http://fedoraproject.org/wiki/MinGW
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: What is a PDC branch?

2019-04-16 Thread Christoph Junghans
On Tue, Apr 16, 2019 at 7:21 AM Robert-André Mauchin  wrote:
>
> On Tuesday, 16 April 2019 04:40:22 CEST Jerry James wrote:
> > I had two packages pass review a couple of weeks ago.  However, my
> > requests for repos were closed as invalid because "The PDC branch
> > already exists".  I reopened the tickets with a request for more
> > information, but they just got closed again with the same message,
> > which tells me that humans are not reading these, so there's no point
> > in opening them again.  Here are the relevant tickets:
> >
> > https://pagure.io/releng/fedora-scm-requests/issue/10798
> > https://pagure.io/releng/fedora-scm-requests/issue/10799
> > https://pagure.io/releng/fedora-scm-requests/issue/10800
> > https://pagure.io/releng/fedora-scm-requests/issue/10801
> >
> > Could somebody please (a) tell me what on earth that means, and (b)
> > fix whatever generates that error message so that it says something
> > intelligible to us mere mortals?
> >
> > Thank you,
> > --
> > Jerry James
> > http://www.jamezone.org/
> > ___
> > devel mailing list -- devel@lists.fedoraproject.org
> > To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
> > https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
> It means your packages already exist in the Product Definition Center,
> For example:
> https://pdc.fedoraproject.org/rest_api/v1/component-branches/?
> active=true&global_component=gap-pkg-francy
>
> Most likely the script which creates them went wrong. Ask infra to solve the
> issues.
I had the same problem for the newly added kim-api package:
https://pagure.io/releng/fedora-scm-requests/issue/11076
https://pagure.io/releng/fedora-scm-requests/issue/11077
https://pagure.io/releng/fedora-scm-requests/issue/11078
https://pagure.io/releng/fedora-scm-requests/issue/11079

However I was able to create branches myself, by disabling
the "Prevent creating new branches by git push" hook and doing:
$ git push origin master:f30
$ git push origin master:f29
$ git push origin master:f28
$ git push origin master:epel7

Christoph
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org



--
Christoph Junghans
Web: http://www.compphys.de
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Maintainer test instances

2019-04-16 Thread Richard Shaw
Also, pertinent to the main topic... Any chance of getting a EL 8 test
instance?

I'm working on getting some preliminary builds done in COPR but having some
issues which are difficult to troubleshoot just with logs.

Thanks,
Richard
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Maintainer test instances

2019-04-16 Thread Dan Horák
On Tue, 16 Apr 2019 09:37:55 -0500
Dennis Gilmore  wrote:

> https://www.openmainframeproject.org/ has some information on getting
> access to mainframe resources. there is also some information at
> https://osuosl.org/services/ibm-z/ I believe both of them end up
> running on hardware at Marist brothers college. there is also some
> info on how to use Jenkins for ci on mainframe.
> 
> Dennis
> 
> On Thu, Apr 4, 2019 at 4:41 PM Neal Gompa  wrote:
> >
> > On Thu, Apr 4, 2019 at 3:27 PM Kevin Fenzi  wrote:
> > >
> > > On 4/4/19 1:16 PM, Neal Gompa wrote:
> > > > On Thu, Apr 4, 2019 at 10:02 AM Kevin Fenzi 
> > > > wrote:
> > > >>
> > > >> Greetings.
> > > >>
> > > >> This is a periodic reminder that we have some test instances
> > > >> setup for package maintainers. Please see:
> > > >>
> > > >> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
> > > >>
> > > >> for more information.
> > > >>
> > > >> Additionally, I have just added 2 aarch64 instances (running
> > > >> Fedora 29).
> > > >>
> > > >> I hope folks will find them useful.
> > > >>
> > > >
> > > > These are definitely awesome, thanks Kevin!
> > > >
> > > > Would it also be possible to get some s390x in here? It seems
> > > > like it's the only arch we support that we don't have here...
> > >
> > > I'd love to, but sadly the ones we have now are: limited in
> > > number, accessible only via a slowish link, and in a lab where we
> > > definitely do not want to allow unrestricted access.
> > >
> > > I think there may be some ibm resources that have instances
> > > available, but not sure of the details. I can try and look into
> > > getting us an instance somewhere that we could setup as a
> > > maintainer test one...
> > >
> >
> > That'd be super useful, as there are times when I have failures only
> > in s390x, and not having a way to debug them makes it very
> > painful. :(

Neal, seems I missed this email. If a shared host is sufficient, I can
make you an account there.


Dan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Stewardship SIG Meeting (2019-04-17; 17:00 UTC)

2019-04-16 Thread Fabio Valentini
Hi everybody,

Tomorrow we'll have the first meeting of the Stewardship SIG.
Non-SIG-members are of course welcome to participate, as well.

I considered both the final whenisgood survey results and the fedora
meeting calendar to find a good spot for this week (which is a bit of
a weird one due to the Easter holidays). We'll try to find a better
slot for future meetings.

- When: 2019-04-17, 17:00 UTC
- Where: #fedora-meeting on freenode

fedocal event:
https://apps.fedoraproject.org/calendar/location/fedora-meeting%40irc.freenode.net/#m9512

Current Agenda:

- Review broken dependencies and build failures
- Review Open RHBZ Bugs
- Review Open Pull Requests
- Review (SIG) Leaf Packages
- Discuss and agree upon future meeting schedule

Some helpful hyperlinks for these items are available in the ticket on
pagure. Also, SIG members, feel free to add further things to the
agenda:
https://www.pagure.io/stewardship-sig/issue/8

If you can't make it tomorrow, we will continue discussions on the
tickets that I'll be creating for every open issue that we come across
during the meeting.

Fabio
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora Atomic Host Two Week Release Announcement: 29.20190414.0

2019-04-16 Thread noreply

A new Fedora Atomic Host update is available via an OSTree update:

Version: 29.20190414.0
Commit(x86_64): 3fa99cde65f41035e0a912643b64251cc84eec8fedd53ca42df2c4857d569639
Commit(aarch64): 
4bf47dda2c658c4392fad85ed78cf563123dc7bd7a86dd644b2dfd252016d535
Commit(ppc64le): 
03469a10666f0b65428974bd610c926f5493ee7a76e2ceccd3abec84c4549e69


We are releasing images from multiple architectures but please note
that x86_64 architecture is the only one that undergoes automated
testing at this time.

Existing systems can be upgraded in place via e.g. `atomic host upgrade`.

Corresponding image media for new installations can be downloaded from:

https://getfedora.org/en/atomic/download/

Alternatively, image artifacts can be found at the following links:
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190414.0.aarch64.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190414.0.aarch64.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-ostree-aarch64-29-20190414.0.iso
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190414.0.ppc64le.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190414.0.ppc64le.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-ostree-ppc64le-29-20190414.0.iso
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190414.0.x86_64.qcow2
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190414.0.x86_64.raw.xz
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190414.0.x86_64.vagrant-libvirt.box
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/x86_64/images/Fedora-AtomicHost-Vagrant-29-20190414.0.x86_64.vagrant-virtualbox.box
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-ostree-x86_64-29-20190414.0.iso

Respective signed CHECKSUM files can be found here:
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/aarch64/images/Fedora-AtomicHost-29-20190414.0-aarch64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/aarch64/iso/Fedora-AtomicHost-29-20190414.0-aarch64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/ppc64le/images/Fedora-AtomicHost-29-20190414.0-ppc64le-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/ppc64le/iso/Fedora-AtomicHost-29-20190414.0-ppc64le-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/x86_64/images/Fedora-AtomicHost-29-20190414.0-x86_64-CHECKSUM
https://alt.fedoraproject.org/pub/alt/atomic/stable/Fedora-29-updates-20190414.0/AtomicHost/x86_64/iso/Fedora-AtomicHost-29-20190414.0-x86_64-CHECKSUM

For direct download, the "latest" targets are always available here:
x86_64:
https://getfedora.org/atomic_qcow2_x86_64_latest
https://getfedora.org/atomic_raw_x86_64_latest
https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest
https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest
https://getfedora.org/atomic_dvd_ostree_x86_64_latest

aarch64:
https://getfedora.org/atomic_qcow2_aarch64_latest
https://getfedora.org/atomic_raw_aarch64_latest
https://getfedora.org/atomic_dvd_ostree_aarch64_latest

ppc64le:
https://getfedora.org/atomic_qcow2_ppc64le_latest
https://getfedora.org/atomic_raw_ppc64le_latest
https://getfedora.org/atomic_dvd_ostree_ppc64le_latest

Filename fetching URLs are available here:
x86_64:
https://getfedora.org/atomic_qcow2_x86_64_latest_filename
https://getfedora.org/atomic_raw_x86_64_latest_filename
https://getfedora.org/atomic_vagrant_libvirt_x86_64_latest_filename
https://getfedora.org/atomic_vagrant_virtualbox_x86_64_latest_filename
https://getfedora.org/atomic_dvd_ostree_x86_64_latest_filename

aarch64:
https://getfedora.org/atomic_qcow2_aarch64_latest_filename
https://getfedora.org/atomic_raw_aarch64_latest_filename
https://getfedora.org/atomic_dvd_ostree_aarch64_latest_filename

ppc64le:
https://getfedora.org/atomic_qcow2_ppc64le_latest_filename
https://getfedora.org/atomic_raw_ppc64le_latest_filename
https://getfedora.org/atomic_dvd_ostree_ppc64le_latest_filenam

Re: Updating/rebuilding of coin-or packages

2019-04-16 Thread Andrew Lutomirski
On Mon, Apr 15, 2019 at 7:35 PM Jerry James  wrote:

> On Mon, Apr 15, 2019 at 12:00 PM Antonio Trande 
> wrote:
> > On 15/04/19 19:25, Andrew Lutomirski wrote
> > > Would one of you be interested in maintaining coin-or-lemon?  I
> packaged
> > > it because I thought I was going to use it, but I ended up not using
> it.
> >
> > Add me, please.
> > My FAS: sagitter
>
> I can comaintain too, if you like.  FAS: jjames.
>
>
Done.  Thanks!
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Donate 1 minute of your time to test upgrades from F29 to F30

2019-04-16 Thread Ankur Sinha
Hello,

I updated 2 systems today to F30 using dnf system-upgrade. Ran into a
few issues, but nothing major. I worked around them by removing the
offending packages and then proceeding with the upgrade. Here are the
bugs I filed:

- https://bugzilla.redhat.com/show_bug.cgi?id=1700307:
  package Mayavi-4.6.2-3.fc30.x86_64 requires python3-mayavi, but none
  of the providers can be installed

- https://bugzilla.redhat.com/show_bug.cgi?id=1674843:
  ekiga is FTBFS in F30

- https://bugzilla.redhat.com/show_bug.cgi?id=1700305:
  (Apparently fixed in testing, but I haven't been able to test yet.)
  package hamcrest-1.3-25.fc30.noarch requires hamcrest-core =
  1.3-25.fc30, but none of the providers can be installed -
  hamcrest-1.3-24.fc29.noarch does not belong to a distupgrade
  repository

- https://bugzilla.redhat.com/show_bug.cgi?id=1700310:
  package python2-envisage-4.6.0-1.fc29.noarch requires
  python2-ipykernel, but none of the providers can be installed

- https://bugzilla.redhat.com/show_bug.cgi?id=1700286:
  package ghc-hoopl-3.10.2.2-70.fc29.x86_64 requires
  libHSarray-0.5.2.0-ghc8.2.2.so()(64bit), but none of the providers can
  be installed

- https://bugzilla.redhat.com/show_bug.cgi?id=1686746:
  python3-fsleyes uninstallable because of missing deps: we're looking
  into this now.


-- 
Thanks,
Regards,

Ankur Sinha "FranciscoD"
https://fedoraproject.org/wiki/User:Ankursinha

Time zone: Europe/London


signature.asc
Description: PGP signature
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: rpmlint: new "executable stack" warnings on rawhide

2019-04-16 Thread Adam Williamson
On Tue, 2019-04-16 at 19:44 +0200, Fabio Valentini wrote:
> On Tue, Apr 16, 2019 at 6:11 PM Adam Williamson
>  wrote:
> > On Sun, 2019-03-17 at 12:07 +0100, Fabio Valentini wrote:
> > > Hi everybody,
> > > 
> > > I've noticed that as of some days ago, some packages I build on rawhide 
> > > are
> > > now triggering the "W: executable-stack" warning for all included
> > > executables and shared libraries.
> > > 
> > > I'm not sure which change might be the cause of this, but meson 0.50.0
> > > seems to be a good candidate, since all my affected packages are built 
> > > with
> > > meson and the new version landed six days ago.
> > > 
> > > Is that new warning something we should worry about?
> > 
> > Just to loop back on this...this wound up causing a release blocker
> > bug:
> > 
> > https://bugzilla.redhat.com/show_bug.cgi?id=1699099
> > 
> > mclasen, mcatanzaro and I investigated it and eventually worked out
> > that it is indeed caused by a bug in meson 0.50.0:
> > 
> > https://github.com/mesonbuild/meson/issues/5268
> > 
> > the offending meson change was actually later reverted for other
> > reasons. I have now backported the reversion to the Fedora meson
> > packages and am rebuilding everything that was built with meson 0.50.0
> > (it's likely that at least some of the rebuilds aren't strictly
> > necessary, but it's easier to rebuild everything than try to figure out
> > which packages did and didn't wind up with execstack marked bits).
> > 
> > Note meson 0.50.0 wound up in the buildroots for F29 and F30 as well as
> > Rawhide, so there are rebuilds for all three going through.
> > 
> > Once I've rebuilt everything (there are quite a lot of things) I'll
> > figure out a strategy for sending out updates.
> 
> Since you probably have a list of affected packages / builds, I can
> help by submitting updates for my own packages at least (once the
> rebuilds are finished), if that helps.

Thanks, but it's probably gonna be easier for one person just to do it,
so we don't have to spend cycles trying to co-ordinate :P I'll let you
know if I need help, though.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Module's package branch name to be aligned?

2019-04-16 Thread Jun Aruga
Hi Mikolaj

> I thought of using names in format "stream-${name}-${stream}" (eg.
stream-scala-2.10), but I can use "${name}-${stream}" (scala-2.10)
format too - consistency between modules is more important than
maintainer personal preferences.

I just checked current modules' situation in f29 module repository.
Maybe this list shows all the module or most modules in it.
The result is here.
https://pagure.io/jaruga-modules-branches

So, current package branch name patterns are

* "stream-${name}-${stream}": 2 (postgresql, varnish)
* "${name}-${stream}": 1 (ruby (but not created yet))
* Both "${name}-${stream}" and "${stream}": 1 (kubernetes)
* "${stream}": 11

Remarkable case is kubernetes module.
2 types of module stream names: 1.10, openshift-3.10
2 types of package branch names: 1.10, openshift-3.10
1.10 is maybe used like a kubernetes-1.10 branch.

There is no "${name}-${stream}" except ruby I thought I would create it.

As the examples of package branch names are defined explicitly
referring http://calver.org/ .
https://docs.fedoraproject.org/en-US/modularity/making-modules/naming-guidelines/#_package_branch_name
In the point of consistency of "current" modules, it might be better
to align with a kubernetes module's style.

That is
* As a first branch name: "${stream}"
* As a 2nd branch name: foo-${stream}

Jun
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: rpmlint: new "executable stack" warnings on rawhide

2019-04-16 Thread Fabio Valentini
On Tue, Apr 16, 2019 at 6:11 PM Adam Williamson
 wrote:
>
> On Sun, 2019-03-17 at 12:07 +0100, Fabio Valentini wrote:
> > Hi everybody,
> >
> > I've noticed that as of some days ago, some packages I build on rawhide are
> > now triggering the "W: executable-stack" warning for all included
> > executables and shared libraries.
> >
> > I'm not sure which change might be the cause of this, but meson 0.50.0
> > seems to be a good candidate, since all my affected packages are built with
> > meson and the new version landed six days ago.
> >
> > Is that new warning something we should worry about?
>
> Just to loop back on this...this wound up causing a release blocker
> bug:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1699099
>
> mclasen, mcatanzaro and I investigated it and eventually worked out
> that it is indeed caused by a bug in meson 0.50.0:
>
> https://github.com/mesonbuild/meson/issues/5268
>
> the offending meson change was actually later reverted for other
> reasons. I have now backported the reversion to the Fedora meson
> packages and am rebuilding everything that was built with meson 0.50.0
> (it's likely that at least some of the rebuilds aren't strictly
> necessary, but it's easier to rebuild everything than try to figure out
> which packages did and didn't wind up with execstack marked bits).
>
> Note meson 0.50.0 wound up in the buildroots for F29 and F30 as well as
> Rawhide, so there are rebuilds for all three going through.
>
> Once I've rebuilt everything (there are quite a lot of things) I'll
> figure out a strategy for sending out updates.

Since you probably have a list of affected packages / builds, I can
help by submitting updates for my own packages at least (once the
rebuilds are finished), if that helps.

Fabio

> Thanks for spotting this earlier, wish we'd worked out the cause at the
> time, it would've saved some pain!
> --
> Adam Williamson
> Fedora QA Community Monkey
> IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
> http://www.happyassassin.net
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora 30-20190416.n.0 compose check report

2019-04-16 Thread Fedora compose checker
Missing expected images:

Atomichost qcow2 x86_64
Atomichost raw-xz x86_64

Failed openQA tests: 9/146 (x86_64), 2/24 (i386), 1/2 (arm)

ID: 384350  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/384350
ID: 384354  Test: x86_64 Workstation-live-iso base_selinux
URL: https://openqa.fedoraproject.org/tests/384354
ID: 384357  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/384357
ID: 384360  Test: x86_64 Workstation-boot-iso memory_check@uefi
URL: https://openqa.fedoraproject.org/tests/384360
ID: 384364  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/384364
ID: 384375  Test: x86_64 KDE-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/384375
ID: 384380  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/384380
ID: 384383  Test: x86_64 Silverblue-dvd_ostree-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/384383
ID: 384412  Test: x86_64 universal install_cyrillic_language
URL: https://openqa.fedoraproject.org/tests/384412
ID: 384419  Test: x86_64 universal install_blivet_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/384419
ID: 384445  Test: x86_64 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/384445
ID: 384466  Test: i386 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/384466

Soft failed openQA tests: 2/146 (x86_64), 2/24 (i386)
(Tests completed, but using a workaround for a known bug)

ID: 384332  Test: x86_64 Server-dvd-iso server_realmd_join_kickstart
URL: https://openqa.fedoraproject.org/tests/384332
ID: 384340  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/384340
ID: 384341  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/384341
ID: 384359  Test: x86_64 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/384359

Passed openQA tests: 135/146 (x86_64), 20/24 (i386)

Skipped non-gating openQA tests: 1 of 172
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: environment variables LANGUAGE

2019-04-16 Thread mcatanzaro


My first thought is accountsservice, check that first.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: rpmlint: new "executable stack" warnings on rawhide

2019-04-16 Thread Adam Williamson
On Sun, 2019-03-17 at 12:07 +0100, Fabio Valentini wrote:
> Hi everybody,
> 
> I've noticed that as of some days ago, some packages I build on rawhide are
> now triggering the "W: executable-stack" warning for all included
> executables and shared libraries.
> 
> I'm not sure which change might be the cause of this, but meson 0.50.0
> seems to be a good candidate, since all my affected packages are built with
> meson and the new version landed six days ago.
> 
> Is that new warning something we should worry about?

Just to loop back on this...this wound up causing a release blocker
bug:

https://bugzilla.redhat.com/show_bug.cgi?id=1699099

mclasen, mcatanzaro and I investigated it and eventually worked out
that it is indeed caused by a bug in meson 0.50.0:

https://github.com/mesonbuild/meson/issues/5268

the offending meson change was actually later reverted for other
reasons. I have now backported the reversion to the Fedora meson
packages and am rebuilding everything that was built with meson 0.50.0
(it's likely that at least some of the rebuilds aren't strictly
necessary, but it's easier to rebuild everything than try to figure out
which packages did and didn't wind up with execstack marked bits).

Note meson 0.50.0 wound up in the buildroots for F29 and F30 as well as
Rawhide, so there are rebuilds for all three going through.

Once I've rebuilt everything (there are quite a lot of things) I'll
figure out a strategy for sending out updates.

Thanks for spotting this earlier, wish we'd worked out the cause at the
time, it would've saved some pain!
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: rpmlint: new "executable stack" warnings on rawhide

2019-04-16 Thread Fabio Valentini
On Sun, Mar 17, 2019 at 12:07 PM Fabio Valentini  wrote:
>
> Hi everybody,
>
> I've noticed that as of some days ago, some packages I build on rawhide are 
> now triggering the "W: executable-stack" warning for all included executables 
> and shared libraries.
>
> I'm not sure which change might be the cause of this, but meson 0.50.0 seems 
> to be a good candidate, since all my affected packages are built with meson 
> and the new version landed six days ago.
>
> Is that new warning something we should worry about?
>
> Fabio

Well, it turns out, it *was* a bug in meson 0.50.0 which, by now, has
affected a long list of packages and is starting to cause issues with
SELinux denials, etc.

The issue is tracked at [0] and meson has been fixed for all branches
of fedora, rebuilds of affected packages are running now.

Fabio

[0]: https://bugzilla.redhat.com/show_bug.cgi?id=1699099
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Can we maybe reduce the set of packages we install by default a bit?

2019-04-16 Thread Adam Williamson
On Tue, 2019-04-16 at 11:48 -0400, Matthias Clasen wrote:
> On Tue, Apr 9, 2019 at 12:08 PM Lennart Poettering 
> wrote:
> 
> > Heya,
> > 
> > today I installed the current Fedora 30 Workstation beta on my new
> > laptop. It was a bumpy ride, I must say (the partitioner (blivet?)
> > crashed five times or so on me, always kicking me out of anaconda
> > again, just because I wanted to undo something). But I don't really
> > want to discuss that. What I do want to discuss is this:
> > 
> > 
> > 
> > Ideally, the top 4 wouldn't be installed at all anymore (in case of
> > the first two at least on the systems which do not need them). But if
> > that's not in the cards, it would be great to at least not enable
> > these services anymore in the default boot so that they are only a
> > "systemctl enable" away for people who need them?
> > 
> > 
> I think all of these are good ideas. "No udev-settle" seems like a nice
> highlevel goal to shoot for.
> 
> Another one I might add: "No stuck stop jobs" - it annoys me every single
> time when I reboot and something like rngd or conmon holds up my reboot
> for several minutes for no reason at all.

I've seen the rngd stop thing, hadn't had time to investigate it yet as
more urgent fires keep showing up :/
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Can we maybe reduce the set of packages we install by default a bit?

2019-04-16 Thread Matthias Clasen
On Tue, Apr 9, 2019 at 12:08 PM Lennart Poettering 
wrote:

> Heya,
>
> today I installed the current Fedora 30 Workstation beta on my new
> laptop. It was a bumpy ride, I must say (the partitioner (blivet?)
> crashed five times or so on me, always kicking me out of anaconda
> again, just because I wanted to undo something). But I don't really
> want to discuss that. What I do want to discuss is this:
>
>
>
> Ideally, the top 4 wouldn't be installed at all anymore (in case of
> the first two at least on the systems which do not need them). But if
> that's not in the cards, it would be great to at least not enable
> these services anymore in the default boot so that they are only a
> "systemctl enable" away for people who need them?
>
>
I think all of these are good ideas. "No udev-settle" seems like a nice
highlevel goal to shoot for.

Another one I might add: "No stuck stop jobs" - it annoys me every single
time when I reboot and something like rngd or conmon holds up my reboot
for several minutes for no reason at all.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: auto-starting libvirtd on Workstation

2019-04-16 Thread Nicolas Mailhot
Le mardi 16 avril 2019 à 14:57 +, Matthias Clasen a écrit :
> I don't think we particularly need autostarting vms on the
> workstation. It would be very nice to get libvirtd activated. I know
> we've asked for this before...

I have autostarted vms on my other_os workstation and it is very
convenient. You set the hypervisor to save vm state on shutdown, and
autorestart all the vms that were running next boot, and you don't need
to bother about the hybernation vs sleep vs shutdown nonsense anymore.
It just works

-- 
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Donate 1 minute of your time to test upgrades from F29 to F30

2019-04-16 Thread Robert-André Mauchin
On Sunday, 14 April 2019 08:55:32 CEST Hirotaka Wakabayashi wrote:
> Hello
> 
> I tested upgrades from F29 to F30. I use the following images:
> https://download.fedoraproject.org/pub/fedora/linux/releases/29/Cloud/x86_64
> /images/Fedora-Cloud-Base-Vagrant-29-1.2.x86_64.vagrant-virtualbox.box
> https://download.fedoraproject.org/pub/fedora/linux/releases/29/Cloud/x86_6
> 4/images/Fedora-Cloud-Base-29-1.2.x86_64.qcow2
> 
> On the image for Vagrant, I failed upgrades  I usually use this image for
> rpm packaging.``` [vagrant@fedora29 ~]$ sudo dnf --releasever=30
> --setopt=module_platform_id=platform:f30 --enablerepo=updates-testing
> distro-sync Fedora Modular 30 -
> x86_64 
>650 kB/s | 2.3 MB
> 00:03 Fedora Modular 30 - x86_64 -
> Updates
>   219  B/s | 257  B 00:01 Fedora
> 30 - x86_64 - Test
> Updates
>  1.8 MB/s |  14 MB 00:07
> Fedora 30 - x86_64 -
> Updates
>   234  B/s | 257  B
> 00:01 Fedora 30 -
> x86_64 
>1.1 MB/s |  54
> MB 00:48 Error:
>  Problem 1: problem with installed package
> gofed-infra-1.0.0-0.21.rc1.fc29.noarch -
> gofed-infra-1.0.0-0.21.rc1.fc29.noarch does not belong to a distupgrade
> repository - nothing provides python2.7dist(git) needed by
> gofed-infra-1.0.0-0.22.rc1.fc30.noarch - nothing provides
> python2.7dist(hglib) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch -
> nothing provides python2.7dist(koji) needed by
> gofed-infra-1.0.0-0.22.rc1.fc30.noarch - nothing provides
> python2.7dist(python-gitdb) needed by
> gofed-infra-1.0.0-0.22.rc1.fc30.noarch - nothing provides
> python2.7dist(tarfile) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch -
> nothing provides python2.7dist(urllib2) needed by
> gofed-infra-1.0.0-0.22.rc1.fc30.noarch Problem 2: problem with installed
> package gofed-gofedlib-1.0.0-0.21.rc1.fc29.x86_64 -
> gofed-gofedlib-1.0.0-0.21.rc1.fc29.x86_64 does not belong to a distupgrade
> repository - nothing provides python2.7dist(jinja2) = 2.8 needed by
> gofed-gofedlib-1.0.0-0.22.rc1.fc30.x86_64 - nothing provides
> python2.7dist(markupsafe) = 0.23 needed by
> gofed-gofedlib-1.0.0-0.22.rc1.fc30.x86_64 Problem 3: problem with installed
> package gofed-1.0.0-0.21.rc1.fc29.x86_64 - package
> gofed-1.0.0-0.22.rc1.fc30.x86_64 requires gofed-infra =
> 1.0.0-0.22.rc1.fc30, but none of the providers can be installed -
> gofed-1.0.0-0.21.rc1.fc29.x86_64 does not belong to a distupgrade
> repository - nothing provides python2.7dist(git) needed by
> gofed-infra-1.0.0-0.22.rc1.fc30.noarch - nothing provides
> python2.7dist(hglib) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch -
> nothing provides python2.7dist(koji) needed by
> gofed-infra-1.0.0-0.22.rc1.fc30.noarch - nothing provides
> python2.7dist(python-gitdb) needed by
> gofed-infra-1.0.0-0.22.rc1.fc30.noarch - nothing provides
> python2.7dist(tarfile) needed by gofed-infra-1.0.0-0.22.rc1.fc30.noarch -
> nothing provides python2.7dist(urllib2) needed by
> gofed-infra-1.0.0-0.22.rc1.fc30.noarch Problem 4: problem with installed
> package gofed-resources-1.0.0-0.21.rc1.fc29.noarch - package
> gofed-resources-1.0.0-0.22.rc1.fc30.noarch requires gofed-gofedlib =
> 1.0.0-0.22.rc1.fc30, but none of the providers can be installed -
> gofed-resources-1.0.0-0.21.rc1.fc29.noarch does not belong to a distupgrade
> repository - nothing provides python2.7dist(jinja2) = 2.8 needed by
> gofed-gofedlib-1.0.0-0.22.rc1.fc30.x86_64 - nothing provides
> python2.7dist(markupsafe) = 0.23 needed by
> gofed-gofedlib-1.0.0-0.22.rc1.fc30.x86_64 (try to add '--skip-broken' to
> skip uninstallable packages)
> ```
> 
> On the image for OpenStack, dependencies are successfully resolved.
>  ```
> Transaction Summary
> 
> 
> == Install   20 Packages
> Upgrade  392 Packages
> 
> ...
> 
> Total download size: 282 M
> Is this ok [y/N]:
> Operation aborted.
> ```
> 
> Upgrades are successfully completed while I found scriptlets in dbus-daemon
> and systemd are failed because of "Failed to reload daemon: Access
> denied".```
> Transaction Summary
> 
> 
> == Install   20 Packages
> Upgrade  392 Packages
> 
> Total 

environment variables LANGUAGE

2019-04-16 Thread Sérgio Basto
Hi,
from this bug : 
https://bugzilla.redhat.com/show_bug.cgi?id=1574222#c35

I have my locale all set to en_US.UTF-8 but LANGUAGE=en_US:pt  ,
where  LANGUAGE is set ? 
I can't find it 

Thanks 
-- 
Sérgio M. B.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora 30 compose report: 20190416.n.0 changes

2019-04-16 Thread Fedora Branched Report
OLD: Fedora-30-20190415.n.2
NEW: Fedora-30-20190416.n.0

= SUMMARY =
Added images:2
Dropped images:  2
Added packages:  14
Dropped packages:8
Upgraded packages:   80
Downgraded packages: 0

Size of added packages:  1.77 MiB
Size of dropped packages:245.61 MiB
Size of upgraded packages:   4.00 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   -10.93 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Python_Classroom live i386
Path: Labs/i386/iso/Fedora-Python-Classroom-Live-i386-30-20190416.n.0.iso
Image: Workstation live i386
Path: Workstation/i386/iso/Fedora-Workstation-Live-i386-30-20190416.n.0.iso

= DROPPED IMAGES =
Image: Design_suite live x86_64
Path: Labs/x86_64/iso/Fedora-Design_suite-Live-x86_64-30-20190415.n.2.iso
Image: Astronomy_KDE live x86_64
Path: Labs/x86_64/iso/Fedora-Astronomy_KDE-Live-x86_64-30-20190415.n.2.iso

= ADDED PACKAGES =
Package: butt-0.1.17-3.fc30
Summary: Broadcast using this tool
RPMs:butt
Size:1.12 MiB

Package: golang-github-benbjohnson-clock-0-0.1.20190325git7dc7640.fc30
Summary: Go library for mocking time
RPMs:golang-github-benbjohnson-clock-devel
Size:14.78 KiB

Package: golang-github-codahale-hdrhistogram-0-0.1.20190318git3a0bb77.fc30
Summary: Go implementation of the High Dynamic Range (HDR) Histogram
RPMs:golang-github-codahale-hdrhistogram-devel
Size:16.38 KiB

Package: golang-github-ldap-v3-3.0.2-2.fc30
Summary: Basic LDAP v3 functionality for Go
RPMs:golang-github-ldap-v3-devel golang-gopkg-3-ldap-devel 
golang-gopkg-ldap-3-devel
Size:136.41 KiB

Package: golang-github-oklog-run-1.0.0-1.fc30
Summary: Universal mechanism to manage goroutine lifecycles
RPMs:golang-github-oklog-run-devel
Size:15.00 KiB

Package: golang-github-rainycape-unidecode-0-0.1.20190315gitcb7f23e.fc30
Summary: Replaces non-ASCII characters with their ASCII approximations
RPMs:golang-github-rainycape-unidecode-devel
Size:197.20 KiB

Package: golang-github-stack-1.8.0-1.fc30
Summary: Capture, manipulate and format Go call stacks
RPMs:golang-github-stack-devel
Size:16.18 KiB

Package: golang-github-teris-io-shortid-1.0-1.20190315git771a37c.fc30
Summary: Short, fully unique, non-sequential and URL friendly Ids
RPMs:golang-github-teris-io-shortid-devel
Size:17.16 KiB

Package: golang-github-unknwon-com-2-2.fc30
Summary: Commonly used functions for the Go programming language
RPMs:golang-github-unknwon-com-devel
Size:29.19 KiB

Package: golang-github-xorm-0.7.1-1.fc30
Summary: Xorm is a simple and powerful ORM for Go
RPMs:golang-github-xorm-devel
Size:126.85 KiB

Package: golang-github-xorm-builder-0.3.4-1.fc30
Summary: Lightweight and fast SQL builder for Go and XORM
RPMs:golang-github-xorm-builder-devel
Size:31.40 KiB

Package: golang-github-xorm-core-0.6.2-1.fc30
Summary: Lightweight Go sql.DB wrapper
RPMs:golang-github-xorm-core-devel
Size:26.96 KiB

Package: golang-github-yudai-gojsondiff-1.0.0-1.fc30
Summary: Go JSON format differences
RPMs:golang-github-yudai-gojsondiff-devel
Size:23.77 KiB

Package: golang-github-yudai-golcs-0-0.1.20190315gitecda9a5.fc30
Summary: Go Longest Common Subsequence
RPMs:golang-github-yudai-golcs-devel
Size:12.02 KiB


= DROPPED PACKAGES =
Package: mongodb-4.0.3-3.fc30
Summary: High-performance, schema-free document-oriented database
RPMs:mongodb mongodb-server mongodb-test
Size:214.75 MiB

Package: ruby-2.5.1-100.module_2208+c4843ca5
Summary: An interpreter of object-oriented scripting language
RPMs:ruby ruby-devel ruby-doc ruby-irb ruby-libs rubygem-bigdecimal 
rubygem-did_you_mean rubygem-io-console rubygem-json rubygem-minitest 
rubygem-net-telnet rubygem-openssl rubygem-power_assert rubygem-psych 
rubygem-rake rubygem-rdoc rubygem-test-unit rubygem-xmlrpc rubygems 
rubygems-devel
Size:25.12 MiB

Package: rubygem-abrt-0.3.0-5.module_2208+c4843ca5
Summary: ABRT support for Ruby
RPMs:rubygem-abrt rubygem-abrt-doc
Size:239.67 KiB

Package: rubygem-bson-4.3.0-4.module_2208+c4843ca5
Summary: Ruby Implementation of the BSON specification
RPMs:rubygem-bson rubygem-bson-doc
Size:701.66 KiB

Package: rubygem-bundler-1.16.1-4.module_2208+c4843ca5
Summary: Library and utilities to manage a Ruby application's gem dependencies
RPMs:rubygem-bundler rubygem-bundler-doc
Size:1.59 MiB

Package: rubygem-mongo-2.6.2-1.module_2208+c4843ca5
Summary: Ruby driver for MongoDB
RPMs:rubygem-mongo rubygem-mongo-doc
Size:1.60 MiB

Package: rubygem-mysql2-0.5.2-1.module_2208+c4843ca5
Summary: A simple, fast Mysql library for Ruby, binding to libmysql
RPMs:rubygem-mysql2 rubygem-mysql2-doc
Size:557.55 KiB

Package: rubygem-pg-1.1.3-1.module_2208+c4843ca5
Summary: A Ruby interface to the PostgreSQL RDBMS
RPMs:rubygem-pg rubygem-pg-doc
Size:1.08 MiB


= UPGRADED PACKAGES =
Package:  R-remotes-

Re: auto-starting libvirtd on Workstation

2019-04-16 Thread Matthias Clasen
I don't think we particularly need autostarting vms on the workstation. It 
would be very nice to get libvirtd activated. I know we've asked for this 
before...
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


FF v dnf needs-restarting

2019-04-16 Thread Bojan Smojver
I'm guessing most of you here probably observed this behaviour with dnf when FF 
is upgraded. Even after FF restarted, dnf needs-restarting reports that it 
needs restarting. Does that sound like a bug or is this somehow intentional?

I'm seeing this in f29 and previous releases are the same. Once I upgrade to 
f30, I'm planning to open a bug on this if it's still the same, unless someone 
tells me this is how it's supposed to work.

Thanks,
-- 
Bojan
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: fedora-img-dl: a tool for downloading Fedora iso's and images

2019-04-16 Thread Adam Williamson
On Tue, 2019-04-16 at 21:55 +0800, Jens-Ulrik Petersen wrote:
> On Tue, Apr 16, 2019 at 12:58 AM Adam Williamson 
> wrote:
> 
> > I already basically wrote this:
> > https://pagure.io/fedora-qa/fedfind
> 
> Wow, very cool, looks comprehensive, thanks.
> I see it even downloads composed images from Koji.

That's actually what it's mainly used for: it started when we (QA)
wanted to be running tests on both nightly image builds and TCs/RCs in
various places, and found ourselves writing big ugly lumps of
conditionals for where various bits turned up under different
circumstances into all these different places. I hated that, so I made
fedfind to be a sort of 'hey where the hell do I get these bits'
helper.

That was before Pungi 4, when there wasn't really a proper 'compose'
concept, so to find nightly lives it had to run Koji queries and all
sorts of nastiness like that. Since Pungi 4 things are better, but it
turns out fedfind is still useful for...various reasons (it provides a
bunch of helper features, it flattens image metadata into a more usable
form, it provides a sort of 'compatibility' implementation so you can
treat stable releases as if they were Pungi 4 composes even though they
actually either weren't built by Pungi 4 or have had their metadata
stripped and bits of themselves moved around...stuff like that).

fedfind does not actually implement downloading (you'd have to just
pipe the URLs it can give you to curl, or whatever) and doesn't
actually have a concept of 'the current rawhide' or 'the current
branched' exactly - that is, it can't find these for you:

https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/
https://dl.fedoraproject.org/pub/fedora/linux/development/30/

if you ask it for just 'branched' or 'rawhide' without any version
information, it will find the latest successful pre-mirroring compose
location for you, e.g. right now it would find:

https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190416.n.0/
https://kojipkgs.fedoraproject.org/compose/branched/Fedora-30-20190416.n.0/

it's quite a subtle difference - those things will usually be *the
same thing*, just in different places - but if it's important to you,
we could probably write that support into fedfind somehow.
-- 
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net
http://www.happyassassin.net
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora modularity and cyclic dependencies

2019-04-16 Thread Mat Booth
On Tue, 16 Apr 2019 at 14:14, Robert-André Mauchin 
wrote:
>
> On Tuesday, 16 April 2019 02:46:49 CEST Mat Booth wrote:
> >
> > Yes, there is a buildopts section in the yaml file where you can specify
> > rpm macros.
> >
> > Here is the documentation:
> >
> >
https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modu
> > les/#_build_macros_optional
> >
> > Here is an example where I needed to set --with bootstrap in my module:
> >
> >
https://src.fedoraproject.org/modules/tycho/blob/df837b8793fe460d2c7e72ab6d6
> > 38a0f6e9f47a7/f/tycho.yaml#_76
> >
>
>
> Thanks for the tip but that wouldn't work for Golang. When we bootstrap we
> disable certain codepath to workaround the cycle, but we still need to
> reenable them later to build the final binary. So we need to do both a
> bootstrap build, and then a non-bootstrap build to get all the
functionality.
>

Why wouldn't this work for you? You would just rebuild the module a second
time without the bootstrap flag set. This is fairly standard process for
packages that buildrequire themselves and not unique to golang.


--
Mat Booth
http://fedoraproject.org/get-fedora
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Maintainer test instances

2019-04-16 Thread Dennis Gilmore
https://www.openmainframeproject.org/ has some information on getting
access to mainframe resources. there is also some information at
https://osuosl.org/services/ibm-z/ I believe both of them end up
running on hardware at Marist brothers college. there is also some
info on how to use Jenkins for ci on mainframe.

Dennis

On Thu, Apr 4, 2019 at 4:41 PM Neal Gompa  wrote:
>
> On Thu, Apr 4, 2019 at 3:27 PM Kevin Fenzi  wrote:
> >
> > On 4/4/19 1:16 PM, Neal Gompa wrote:
> > > On Thu, Apr 4, 2019 at 10:02 AM Kevin Fenzi  wrote:
> > >>
> > >> Greetings.
> > >>
> > >> This is a periodic reminder that we have some test instances setup for
> > >> package maintainers. Please see:
> > >>
> > >> https://fedoraproject.org/wiki/Test_Machine_Resources_For_Package_Maintainers
> > >>
> > >> for more information.
> > >>
> > >> Additionally, I have just added 2 aarch64 instances (running Fedora 29).
> > >>
> > >> I hope folks will find them useful.
> > >>
> > >
> > > These are definitely awesome, thanks Kevin!
> > >
> > > Would it also be possible to get some s390x in here? It seems like
> > > it's the only arch we support that we don't have here...
> >
> > I'd love to, but sadly the ones we have now are: limited in number,
> > accessible only via a slowish link, and in a lab where we definitely do
> > not want to allow unrestricted access.
> >
> > I think there may be some ibm resources that have instances available,
> > but not sure of the details. I can try and look into getting us an
> > instance somewhere that we could setup as a maintainer test one...
> >
>
> That'd be super useful, as there are times when I have failures only
> in s390x, and not having a way to debug them makes it very painful. :(
>
>
>
> --
> 真実はいつも一つ!/ Always, there's only one truth!
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives: 
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Module's package branch name to be aligned?

2019-04-16 Thread Jun Aruga
On Tue, Apr 16, 2019 at 3:38 PM Igor Gnatenko
 wrote:
>
> Why?
>
> What is the problem with packages having branch "latest", "1.x" and such?

It's no problem.
Rather it might be better in the point of view of "minimal necessary
package branches for now".
I thought it again.

I considered below case of that a package is included in 2 different modules.
Then in the case, a module bar can not refer rpms/bar's 1.2 branch
because of specific issue of module bar.
But creating new branch "bar-1.2" on rpms/foo on that time might solve
the situation.

On modules/foo branch: 1.2
foo.yml
data:
components:
foo:
ref: 1.2

On modules/bar branch: 3.4
bar.yml
data:
components:
foo:
ref: bar-1.2

rpms/foo
  branch: 1.2
  branch: bar-1.2

--
Jun
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Module's package branch name to be aligned?

2019-04-16 Thread Mikolaj Izdebski
On Tue, Apr 16, 2019 at 3:26 PM Jun Aruga  wrote:
>
> Hi,
>
> I like to see "package branch name" of each modules to be aligned more.
>
> Here is a list of the current module, the module stream name, the
> package branch name, another package name. There are some patterns on
> the list.
>
> # module, the module stream name (module/foo's branch), the package
> branch name (rpms/foo's branch), another package name (rpms/bar's
> branch)
> mongodb3.6  3.6 None
> nodejs8 8 None
> perl5.24 fXX fXX
> python3 3.6   None  None
> python36   3.6   None  master
> ruby   2.5   ruby-2.5 master
> scala  2.10 javapackages javapackages
> varnish   6 stream-6 stream-6
>
> See more detail at https://pagure.io/jaruga-modules-branches
> I think "None" is same with "master" technically.
>
> In case of modules/ruby, we ruby team decided "the package branch
> name" as "ruby-X.Y" with a module name prefix against "X.Y" documented
> in the naming guideline.
> Because a package of a module A (ex. modules/ruby) can be used also in
> a module B (ex. modules/rubygem-rails, modules/vagrant and etc.
> In this case, a package branch name needs to have  "ruby-X.Y",
> "rubygem-rails-X.Y", "vargrant-X.Y".
>
> Do you like to see some alignments for the naming?

For my modules I also want component branch names to correspond to
module name/stream.
If the same component is used across different modules/streams then
there would simply be several branches pointing to the same commit.

I thought of using names in format "stream-${name}-${stream}" (eg.
stream-scala-2.10), but I can use "${name}-${stream}" (scala-2.10)
format too - consistency between modules is more important than
maintainer personal preferences.

--
Mikolaj
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora modularity and cyclic dependencies

2019-04-16 Thread Adam Samalik
On Tue, Apr 16, 2019 at 3:14 PM Robert-André Mauchin 
wrote:

> On Tuesday, 16 April 2019 02:46:49 CEST Mat Booth wrote:
> >
> > Yes, there is a buildopts section in the yaml file where you can specify
> > rpm macros.
> >
> > Here is the documentation:
> >
> >
> https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modu
> > les/#_build_macros_optional
> >
> > Here is an example where I needed to set --with bootstrap in my module:
> >
> >
> https://src.fedoraproject.org/modules/tycho/blob/df837b8793fe460d2c7e72ab6d6
> > 38a0f6e9f47a7/f/tycho.yaml#_76
> >
>
>
> Thanks for the tip but that wouldn't work for Golang. When we bootstrap we
> disable certain codepath to workaround the cycle, but we still need to
> reenable them later to build the final binary. So we need to do both a
> bootstrap build, and then a non-bootstrap build to get all the
> functionality.
>

This is quite common. One way to approach is is to have two modules, for
example:

* golang-bootstrap — with the bootstrap macros set, to build the first pass
* golang — the final one, it would build-require the golang-bootstrap module

Here is an example with Perl:

* perl-bootstrap:
https://src.fedoraproject.org/modules/perl-bootstrap/blob/5.26/f/perl-bootstrap.yaml
* perl: https://src.fedoraproject.org/modules/perl/blob/5.26/f/perl.yaml

Would that work for you?


>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>


-- 

Adam Šamalík
---
Senior Software Engineer
Red Hat
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: fedora-img-dl: a tool for downloading Fedora iso's and images

2019-04-16 Thread Jens-Ulrik Petersen
On Tue, Apr 16, 2019 at 12:58 AM Adam Williamson 
wrote:

> I already basically wrote this:
> https://pagure.io/fedora-qa/fedfind


Wow, very cool, looks comprehensive, thanks.
I see it even downloads composed images from Koji.

Jens
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora modularity and cyclic dependencies

2019-04-16 Thread Mikolaj Izdebski
On Tue, Apr 16, 2019 at 11:11 AM Petr Pisar  wrote:
>
> On 2019-04-16, Igor Gnatenko  wrote:
> > You can do something like:
> >
> > rpms:
> >   foo-bootstrap:
> > name: foo
> >   bar:
> > buildafter:
> >   - foo-bootstrap
> >   foo:
> > buildafter:
> >   - bar
> >
>
> How does foo.spec get to know that it should enable bootstrapping in
> foo-bootstrap component, but disable it in foo component?

You can use different refs (and therefore different spec files) for
foo and foo-bootstrap.

--
Mikolaj Izdebski
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora modularity and cyclic dependencies

2019-04-16 Thread Nicolas Mailhot

Le 2019-04-16 15:06, Robert-André Mauchin a écrit :

On Tuesday, 16 April 2019 02:46:49 CEST Mat Booth wrote:


Yes, there is a buildopts section in the yaml file where you can 
specify

rpm macros.

Here is the documentation:

https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modu
les/#_build_macros_optional

Here is an example where I needed to set --with bootstrap in my 
module:


https://src.fedoraproject.org/modules/tycho/blob/df837b8793fe460d2c7e72ab6d6
38a0f6e9f47a7/f/tycho.yaml#_76




Thanks for the tip but that wouldn't work for Golang. When we bootstrap 
we

disable certain codepath to workaround the cycle, but we still need to
reenable them later to build the final binary. So we need to do both a
bootstrap build, and then a non-bootstrap build to get all the 
functionality.


And that BTW is not Go specific at all. That's the usual bootstrap 
definition within Fedora.


--
Nicolas Mailhot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Module's package branch name to be aligned?

2019-04-16 Thread Igor Gnatenko
Why?

What is the problem with packages having branch "latest", "1.x" and such?

On Tue, Apr 16, 2019 at 3:35 PM Jun Aruga  wrote:

> Hi,
>
> I like to see "package branch name" of each modules to be aligned more.
>
> Here is a list of the current module, the module stream name, the
> package branch name, another package name. There are some patterns on
> the list.
>
> # module, the module stream name (module/foo's branch), the package
> branch name (rpms/foo's branch), another package name (rpms/bar's
> branch)
> mongodb3.6  3.6 None
> nodejs8 8 None
> perl5.24 fXX fXX
> python3 3.6   None  None
> python36   3.6   None  master
> ruby   2.5   ruby-2.5 master
> scala  2.10 javapackages javapackages
> varnish   6 stream-6 stream-6
>
> See more detail at https://pagure.io/jaruga-modules-branches
> I think "None" is same with "master" technically.
>
> In case of modules/ruby, we ruby team decided "the package branch
> name" as "ruby-X.Y" with a module name prefix against "X.Y" documented
> in the naming guideline.
> Because a package of a module A (ex. modules/ruby) can be used also in
> a module B (ex. modules/rubygem-rails, modules/vagrant and etc.
> In this case, a package branch name needs to have  "ruby-X.Y",
> "rubygem-rails-X.Y", "vargrant-X.Y".
>
> Do you like to see some alignments for the naming?
> Hopefully after the discussion here in this thread, below page will be
> updated.
>
> https://docs.fedoraproject.org/en-US/modularity/making-modules/naming-guidelines/#_package_branch_name
>
> Regards,
> Jun
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
>
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Module's package branch name to be aligned?

2019-04-16 Thread Jun Aruga
Hi,

I like to see "package branch name" of each modules to be aligned more.

Here is a list of the current module, the module stream name, the
package branch name, another package name. There are some patterns on
the list.

# module, the module stream name (module/foo's branch), the package
branch name (rpms/foo's branch), another package name (rpms/bar's
branch)
mongodb3.6  3.6 None
nodejs8 8 None
perl5.24 fXX fXX
python3 3.6   None  None
python36   3.6   None  master
ruby   2.5   ruby-2.5 master
scala  2.10 javapackages javapackages
varnish   6 stream-6 stream-6

See more detail at https://pagure.io/jaruga-modules-branches
I think "None" is same with "master" technically.

In case of modules/ruby, we ruby team decided "the package branch
name" as "ruby-X.Y" with a module name prefix against "X.Y" documented
in the naming guideline.
Because a package of a module A (ex. modules/ruby) can be used also in
a module B (ex. modules/rubygem-rails, modules/vagrant and etc.
In this case, a package branch name needs to have  "ruby-X.Y",
"rubygem-rails-X.Y", "vargrant-X.Y".

Do you like to see some alignments for the naming?
Hopefully after the discussion here in this thread, below page will be updated.
https://docs.fedoraproject.org/en-US/modularity/making-modules/naming-guidelines/#_package_branch_name

Regards,
Jun
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: What is a PDC branch?

2019-04-16 Thread Robert-André Mauchin
On Tuesday, 16 April 2019 04:40:22 CEST Jerry James wrote:
> I had two packages pass review a couple of weeks ago.  However, my
> requests for repos were closed as invalid because "The PDC branch
> already exists".  I reopened the tickets with a request for more
> information, but they just got closed again with the same message,
> which tells me that humans are not reading these, so there's no point
> in opening them again.  Here are the relevant tickets:
> 
> https://pagure.io/releng/fedora-scm-requests/issue/10798
> https://pagure.io/releng/fedora-scm-requests/issue/10799
> https://pagure.io/releng/fedora-scm-requests/issue/10800
> https://pagure.io/releng/fedora-scm-requests/issue/10801
> 
> Could somebody please (a) tell me what on earth that means, and (b)
> fix whatever generates that error message so that it says something
> intelligible to us mere mortals?
> 
> Thank you,
> -- 
> Jerry James
> http://www.jamezone.org/
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
> Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

It means your packages already exist in the Product Definition Center,
For example:
https://pdc.fedoraproject.org/rest_api/v1/component-branches/?
active=true&global_component=gap-pkg-francy

Most likely the script which creates them went wrong. Ask infra to solve the 
issues.

___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora 30 Final Freeze

2019-04-16 Thread Mohan Boddu
Hi all,

Today, April 16th 2019, is an important day on the Fedora 30
schedule [1], with significant cut-offs.

Today we have the Final Freeze [2]. This means that only packages
which fix accepted blocker or freeze exception bugs [3][4][5] will be
marked as 'stable' and included in the Final composes. Other builds
will remain in updates-testing until the Final release is approved, at
which point the Final freeze is lifted and packages can move to the
'updates' repository, pending updates will be pushed before final
release as zero day updates.

[1] https://fedoraproject.org/wiki/Releases/30/Schedule
[2] https://fedoraproject.org/wiki/Milestone_freezes
[3] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
[4] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
[5] https://qa.fedoraproject.org/blockerbugs/milestone/30/final/buglist

Regards,
Mohan Boddu
Release Engineering
___
devel-announce mailing list -- devel-annou...@lists.fedoraproject.org
To unsubscribe send an email to devel-announce-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fedoraproject.org
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Fedora modularity and cyclic dependencies

2019-04-16 Thread Robert-André Mauchin
On Tuesday, 16 April 2019 02:46:49 CEST Mat Booth wrote:
> 
> Yes, there is a buildopts section in the yaml file where you can specify
> rpm macros.
> 
> Here is the documentation:
> 
> https://docs.fedoraproject.org/en-US/modularity/making-modules/defining-modu
> les/#_build_macros_optional
> 
> Here is an example where I needed to set --with bootstrap in my module:
> 
> https://src.fedoraproject.org/modules/tycho/blob/df837b8793fe460d2c7e72ab6d6
> 38a0f6e9f47a7/f/tycho.yaml#_76
> 


Thanks for the tip but that wouldn't work for Golang. When we bootstrap we 
disable certain codepath to workaround the cycle, but we still need to 
reenable them later to build the final binary. So we need to do both a 
bootstrap build, and then a non-bootstrap build to get all the functionality.


___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


libiptcdata long-term FTBFS

2019-04-16 Thread Miro Hrončok

Hi libiptcdata-maintainers,

libiptcdata FTBFS for a long time. Please either fix it or oprhan the package if 
you don't have time to do it.


https://bugzilla.redhat.com/show_bug.cgi?id=1604602

Thanks,
--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora Rawhide-20190416.n.0 compose check report

2019-04-16 Thread Fedora compose checker
Missing expected images:

Atomichost raw-xz x86_64
Atomichost qcow2 x86_64

Compose FAILS proposed Rawhide gating check!
2 of 47 required tests failed
openQA tests matching unsatisfied gating requirements shown with **GATING** 
below

Failed openQA tests: 13/146 (x86_64), 4/24 (i386), 1/2 (arm)

ID: 384123  Test: x86_64 Server-dvd-iso modularity_tests
URL: https://openqa.fedoraproject.org/tests/384123
ID: 384149  Test: x86_64 Workstation-live-iso base_selinux
URL: https://openqa.fedoraproject.org/tests/384149
ID: 384152  Test: x86_64 Workstation-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/384152
ID: 384154  Test: x86_64 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/384154
ID: 384155  Test: x86_64 Workstation-boot-iso memory_check@uefi
URL: https://openqa.fedoraproject.org/tests/384155
ID: 384156  Test: x86_64 Workstation-boot-iso install_default@uefi 
**GATING**
URL: https://openqa.fedoraproject.org/tests/384156
ID: 384158  Test: i386 Workstation-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/384158
ID: 384159  Test: i386 Workstation-boot-iso memory_check
URL: https://openqa.fedoraproject.org/tests/384159
ID: 384172  Test: x86_64 KDE-live-iso apps_startstop
URL: https://openqa.fedoraproject.org/tests/384172
ID: 384175  Test: arm Minimal-raw_xz-raw.xz 
install_arm_image_deployment_upload
URL: https://openqa.fedoraproject.org/tests/384175
ID: 384178  Test: x86_64 Silverblue-dvd_ostree-iso install_no_user
URL: https://openqa.fedoraproject.org/tests/384178
ID: 384214  Test: x86_64 universal install_blivet_software_raid@uefi
URL: https://openqa.fedoraproject.org/tests/384214
ID: 384223  Test: x86_64 universal install_simple_free_space
URL: https://openqa.fedoraproject.org/tests/384223
ID: 384240  Test: x86_64 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/384240
ID: 384247  Test: x86_64 universal install_asian_language
URL: https://openqa.fedoraproject.org/tests/384247
ID: 384249  Test: x86_64 universal install_kickstart_user_creation 
**GATING**
URL: https://openqa.fedoraproject.org/tests/384249
ID: 384261  Test: i386 universal install_blivet_software_raid
URL: https://openqa.fedoraproject.org/tests/384261
ID: 384272  Test: i386 universal install_package_set_kde
URL: https://openqa.fedoraproject.org/tests/384272

Soft failed openQA tests: 2/24 (i386), 7/146 (x86_64)
(Tests completed, but using a workaround for a known bug)

ID: 384135  Test: i386 Server-boot-iso install_default
URL: https://openqa.fedoraproject.org/tests/384135
ID: 384136  Test: i386 Server-dvd-iso install_default
URL: https://openqa.fedoraproject.org/tests/384136
ID: 384145  Test: x86_64 Workstation-live-iso desktop_update_graphical
URL: https://openqa.fedoraproject.org/tests/384145
ID: 384195  Test: x86_64 universal upgrade_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/384195
ID: 384197  Test: x86_64 universal upgrade_server_64bit
URL: https://openqa.fedoraproject.org/tests/384197
ID: 384198  Test: x86_64 universal upgrade_server_domain_controller
URL: https://openqa.fedoraproject.org/tests/384198
ID: 384199  Test: x86_64 universal upgrade_realmd_client
URL: https://openqa.fedoraproject.org/tests/384199
ID: 384234  Test: x86_64 universal upgrade_2_server_64bit
URL: https://openqa.fedoraproject.org/tests/384234
ID: 384255  Test: x86_64 universal upgrade_2_minimal_64bit
URL: https://openqa.fedoraproject.org/tests/384255

Passed openQA tests: 126/146 (x86_64), 18/24 (i386)

Skipped non-gating openQA tests: 1 of 172
-- 
Mail generated by check-compose:
https://pagure.io/fedora-qa/check-compose
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Fedora rawhide compose report: 20190416.n.0 changes

2019-04-16 Thread Fedora Rawhide Report
OLD: Fedora-Rawhide-20190413.n.0
NEW: Fedora-Rawhide-20190416.n.0

= SUMMARY =
Added images:2
Dropped images:  4
Added packages:  18
Dropped packages:4
Upgraded packages:   194
Downgraded packages: 0

Size of added packages:  41.32 MiB
Size of dropped packages:555.92 MiB
Size of upgraded packages:   8.01 GiB
Size of downgraded packages: 0 B

Size change of upgraded packages:   263.80 MiB
Size change of downgraded packages: 0 B

= ADDED IMAGES =
Image: Mate live x86_64
Path: Spins/x86_64/iso/Fedora-MATE_Compiz-Live-x86_64-Rawhide-20190416.n.0.iso
Image: Python_Classroom live x86_64
Path: 
Labs/x86_64/iso/Fedora-Python-Classroom-Live-x86_64-Rawhide-20190416.n.0.iso

= DROPPED IMAGES =
Image: Container_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Base-Rawhide-20190413.n.0.ppc64le.tar.xz
Image: Container_Minimal_Base docker s390x
Path: 
Container/s390x/images/Fedora-Container-Minimal-Base-Rawhide-20190413.n.0.s390x.tar.xz
Image: KDE raw-xz armhfp
Path: Spins/armhfp/images/Fedora-KDE-armhfp-Rawhide-20190413.n.0-sda.raw.xz
Image: Container_Minimal_Base docker ppc64le
Path: 
Container/ppc64le/images/Fedora-Container-Minimal-Base-Rawhide-20190413.n.0.ppc64le.tar.xz

= ADDED PACKAGES =
Package: codemodel-2.6-26.fc31
Summary: Java library for code generators
RPMs:codemodel codemodel-javadoc
Size:333.20 KiB

Package: deepin-kwin-0.0.3.2-1.fc31
Summary: KWin configuration for Deepin Desktop Environment
RPMs:deepin-kwin deepin-kwin-devel
Size:1.13 MiB

Package: deepin-qt5dxcb-plugin-1.1.25-1.fc31
Summary: Qt platform integration plugin for Deepin Desktop Environment
RPMs:deepin-qt5dxcb-plugin
Size:1001.87 KiB

Package: erlang-mqtree-1.0.2-2.fc31
Summary: Index tree for MQTT topic filters
RPMs:erlang-mqtree
Size:178.72 KiB

Package: geronimo-jta-1.1.1-25.fc31
Summary: J2EE JTA v1.1 API
RPMs:geronimo-jta geronimo-jta-javadoc
Size:65.61 KiB

Package: glassfish-dtd-parser-1.2-0.19.20120120svn.fc31
Summary: Library for parsing XML DTDs
RPMs:glassfish-dtd-parser glassfish-dtd-parser-javadoc
Size:131.30 KiB

Package: glassfish-fastinfoset-1.2.13-11.fc31
Summary: Fast Infoset
RPMs:glassfish-fastinfoset glassfish-fastinfoset-javadoc
Size:690.23 KiB

Package: glassfish-jaxb-2.2.11-11.fc31
Summary: JAXB Reference Implementation
RPMs:glassfish-jaxb glassfish-jaxb-bom glassfish-jaxb-bom-ext 
glassfish-jaxb-codemodel glassfish-jaxb-codemodel-annotation-compiler 
glassfish-jaxb-codemodel-parent glassfish-jaxb-core 
glassfish-jaxb-external-parent glassfish-jaxb-javadoc glassfish-jaxb-jxc 
glassfish-jaxb-parent glassfish-jaxb-rngom glassfish-jaxb-runtime 
glassfish-jaxb-runtime-parent glassfish-jaxb-txw-parent glassfish-jaxb-txw2 
glassfish-jaxb-txwc2 glassfish-jaxb-xjc glassfish-jaxb1-impl
Size:4.56 MiB

Package: istack-commons-2.21-10.fc31
Summary: Common code for some Glassfish projects
RPMs:import-properties-plugin istack-commons istack-commons-buildtools 
istack-commons-javadoc istack-commons-maven-plugin istack-commons-runtime 
istack-commons-soimp istack-commons-test istack-commons-tools
Size:396.70 KiB

Package: jdepend-2.9.1-20.fc31
Summary: Java Design Quality Metrics
RPMs:jdepend jdepend-demo jdepend-javadoc
Size:244.16 KiB

Package: jsr-311-1.1.1-18.fc31
Summary: JAX-RS: Java API for RESTful Web Services
RPMs:jsr-311 jsr-311-javadoc
Size:155.17 KiB

Package: kim-api-2.0.2-2.fc31
Summary: Open Knowledgebase of Interatomic Models KIM API
RPMs:kim-api kim-api-devel kim-api-examples
Size:3.40 MiB

Package: ogr2osm-0.1-0.1.20190104git183e226.fc31
Summary: Convert ogr-readable files like shapefiles into .osm data
RPMs:ogr2osm
Size:28.05 KiB

Package: perl-Mail-AuthenticationResults-1.20180923-2.fc31
Summary: Object Oriented Authentication-Results Headers
RPMs:perl-Mail-AuthenticationResults
Size:59.97 KiB

Package: python-OBD-0.7.0-1.fc31
Summary: OBD-II serial module for reading engine data
RPMs:python3-OBD
Size:97.41 KiB

Package: rust-askalono-cli-0.3.0-1.module_f31+3935+a5a19355
Summary: Tool to detect the contents of license files
RPMs:askalono-cli
Size:14.54 MiB

Package: smoldyn-2.58-1.fc31
Summary: A particle-based spatial stochastic simulator
RPMs:smoldyn smoldyn-doc
Size:13.71 MiB

Package: xsom-0-21.20110809svn.fc31
Summary: XML Schema Object Model (XSOM)
RPMs:xsom xsom-javadoc
Size:693.64 KiB


= DROPPED PACKAGES =
Package: SimplyHTML-0.16.18-6.fc30
Summary: Application and a java component for rich text processing
RPMs:SimplyHTML SimplyHTML-javadoc
Size:510.53 KiB

Package: docker-2:1.13.1-66.git1185cfd.fc31
Summary: Automates deployment of containerized applications
RPMs:docker docker-common docker-devel docker-fish-completion 
docker-logrotate docker-lvm-plugin docker-novolume-plugin 
docker-rhel-push-plugin docker-vim docker-zsh-completion
Size:186.44 MiB

Package

Re: Fedora modularity and cyclic dependencies

2019-04-16 Thread Petr Pisar
On 2019-04-16, Igor Gnatenko  wrote:
> You can do something like:
>
> rpms:
>   foo-bootstrap:
> name: foo
>   bar:
> buildafter:
>   - foo-bootstrap
>   foo:
> buildafter:
>   - bar
>

How does foo.spec get to know that it should enable bootstrapping in
foo-bootstrap component, but disable it in foo component?

-- Petr
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org


Re: Orphaned packages need new maintainers

2019-04-16 Thread Miro Hrončok

On 15. 04. 19 18:52, Christopher wrote:

If nobody picks up the ones by my name (nodejs-path-exists,
nodejs-bluebird, nodejs-grunt-known-options), then I will probably
have to orphan js-jquery, because it probably needs those for its
build (I can't think of any other reason my name would be listed next
to those).


That is indeed the reason.

--
Miro Hrončok
--
Phone: +420777974800
IRC: mhroncok
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org