Re: Tracker bug for approved change proposals

[Parag Nemade]

Hi,

Is there any update on how bug tracking for Change proposals is going to be
handled for Fedora 39?

Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: %find_lang does not find locale files

[Parag Nemade]

Hi,


On Tue, May 23, 2023 at 11:58 PM Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:

> Hello,
>
> I know this has been asked before, more recently four years ago in
>
> https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/OQDWCHFDTBKCPHWF2VLPUF74WC76TCNY/#6VUBRYAAZMX6SOREM7ZENDV44MIPE7WH
>
> I'm not sure what the "right" way of dealing with this is, so I would
> really appreciate any advice.
>
> I've recently packaged input-remapper[1] and during the review[2],
> Zbigniew pointed out that I had forgotten to use the %find_lang macro
> for the localization files.
>
> The translations are placed in /usr/share/input-remapper/lang/ and
> apparently, %find_lang does not want to find them there. Is there a
> standard location that works across linux distributions? I guess that
> if the answer is yes, I should get upstream to move their files there.
> If not, is there something else to be done?
>
>
> 1. https://github.com/sezanzeb/input-remapper/
> 2. https://bugzilla.redhat.com/show_bug.cgi?id=2180418
> ___
>

I did a quick search and found this discussion
https://pagure.io/packaging-committee/issue/1058#comment-775111
Maybe this will not help you but will give some insights.

Regards,
Parag.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Re: List of long term FTBFS packages to be retired in March

[Parag Nemade]

On Wed, Feb 2, 2022 at 3:41 PM Miro Hrončok  wrote:

> On 02. 02. 22 10:41, Parag Nemade wrote:
> > I have submitted PR
> >
> https://src.fedoraproject.org/rpms/impallari-raleway-fonts/pull-request/2
> > <
> https://src.fedoraproject.org/rpms/impallari-raleway-fonts/pull-request/2>
>
> > which should fix that package building in Fedora releases.
>
> Thanks. I am afraid @nim is not going to respond.
>
> In case you won't use nonresponsive maintainer policy,
> the FTBFS policy says the packages will be orphaned and retired, so I
> assume in
> the spirit of the policy, I can just reassign the package to you when the
> time
> comes.
>

Sure no problem to assign me that package later on. I just don't want to
maintain all the packages that @nim owns.
I now also submitted
https://src.fedoraproject.org/rpms/sil-charis-fonts/pull-request/1 and am
sure Kevin will merge it.

Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: List of long term FTBFS packages to be retired in March

[Parag Nemade]

On Tue, Feb 1, 2022 at 7:39 PM Miro Hrončok  wrote:

> Dear maintainers.
>
> Based on the current fail to build from source policy, the following
> packages
> should be retired from Fedora 36 approximately one week before branching.
>
> However, 5 weekly reminders are required and I forgot to start this sooner,
> hence the retirement will happen in 5 weeks, i.e. March 1st 2022.
> Since this is after the Beta Freeze,
> I will skip retiring components with depending packages.
> Such components will be retired during the next release cycle,
> and are included in this report for completeness.
>
> Policy:
>
> https://docs.fedoraproject.org/en-US/fesco/Fails_to_build_from_source_Fails_to_install/
>
> The packages in rawhide were not successfully built at least since Fedora
> 33.
>
> This report is based on dist tags.
>
> Packages collected via:
>
> https://github.com/hroncok/fedora-report-ftbfs-retirements/blob/master/ftbfs-retirements.ipynb
>
> If you see a package that was built, please let me know.
> If you see a package that should be exempted from the process, please let
> me
> know and we can work together to get a FESCo approval for that.
>
> If you see a package that can be rebuilt, please do so.
>
>  Package  (co)maintainers
>
> 
> adf-tribun-fonts  frixxon, nim
> catharsis-cormorant-fonts nim
> chocolate-doomsundaram
> ecolier-court-fonts   frixxon, nim
> gfs-ambrosia-fontsfrixxon, nim
> gfs-artemisia-fonts   nim
> gfs-baskerville-fonts nim
> gfs-bodoni-classic-fonts  nim
> gfs-bodoni-fonts  nim
> gfs-complutum-fonts   nim
> gfs-decker-fonts  nim
> gfs-didot-classic-fonts   nim
> gfs-didot-display-fonts   nim
> gfs-didot-fonts   nim
> gfs-eustace-fonts nim
> gfs-fleischman-fonts  nim
> gfs-galatea-fonts nim
> gfs-garaldus-fontsnim
> gfs-gazis-fonts   nim
> gfs-goschen-fonts nim
> gfs-ignacio-fonts nim
> gfs-jackson-fonts nim
> gfs-neohellenic-fonts nim
> gfs-neohellenic-math-fontsnim
> gfs-nicefore-fontsnim
> gfs-olga-fontsnim
> gfs-orpheus-classic-fonts nim
> gfs-orpheus-fonts nim
> gfs-orpheus-sans-fontsnim
> gfs-philostratos-fontsnim
> gfs-porson-fonts  nim
> gfs-pyrsos-fonts  nim
> gfs-solomos-fonts nim
> gfs-theokritos-fonts  nim
> ht-alegreya-sans-fontsnim
> ibm-plex-fontssuraia
> impallari-dancing-script-fontsnim
> impallari-raleway-fonts   nim
> intel-clear-sans-fontsnim
> jetbrains-mono-fonts  nim
> kemie-bellota-fonts   nim
> libicu65  pwalter
> ndiscover-exo-2-fonts nim
> rubygem-cucumber-railsmmorsi, vondruch
> rubygem-selenium-webdrivermmorsi, ruby-packagers-sig, vondruch
> rubygem-supdcallagh, jaruga, ruby-packagers-sig,
> shreyankg
> sil-alkalami-fontsnim
> sil-andika-compact-fonts  nim
> sil-andika-fonts  nim
> sil-andika-new-basic-fontsnim
> sil-annapurna-fonts   nim
> sil-apparatus-fonts   nim
> sil-awami-nastaliq-fonts  nim
> sil-charis-compact-fonts  nim
> sil-charis-fonts  kevin, nim
> sil-dai-banna-fonts   nim
> sil-ezra-fontsnim
> sil-gentium-plus-compact-fontsnim
> sil-harmattan-fonts   nim
> sil-mondulkiri-extra-fontsnim
> sil-mondulkiri-fonts  nim
> sil-namdhinggo-fonts  nim
> sil-shimenkan-fonts   nim
> sil-sophia-nubian-fonts   nim
> sil-tagmukay-fontsnim
> sil-tai-heritage-pro-fontsnim
> symbian-m-yuppy-gb-fonts  nim
> tmux-top  ttomecek
> typesetit-great-vibes-fonts   nim
> uswds-public-sans-fonts   nim
> vernnobile-muli-fonts nim
> vernnobile-nunito-fonts   nim
> vernnobile-oswald-fonts   nim
> wagesreiter-patrick-hand-fontsnim
> weiweihuanghuang-work-sans-fonts  nim
> yanone-kaffeesatz-fonts   nim
>
> The following packages require above mentioned packages:
> Depending on: impallari-raleway-fonts (90)
> R-rmarkdown (maintained by: qulogic)
> R-rmarkdown-2.10-2.fc36.src requires
> impallari-raleway-fonts =
> 4.025-3.20200310git98add57.fc33
>
> sympa (maintained by: xavierb)
> sympa-6.2.68-1.fc36.src requires impallari-raleway-fonts =
> 4.025-3.20200310git98add57.fc33
> 

[rpms/perl-Text-SpellChecker] PR #1: Update hunspell directory path

[Parag Nemade]

pnemade commented on the pull-request: `Update hunspell directory path` that 
you are following:
``
Thank you
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Text-SpellChecker/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

[rpms/perl-Text-SpellChecker] PR #1: Update hunspell directory path

[Parag Nemade]

pnemade opened a new pull-request against the project: `perl-Text-SpellChecker` 
that you are following:
``
Update hunspell directory path
``

To reply, visit the link below
https://src.fedoraproject.org/rpms/perl-Text-SpellChecker/pull-request/1
___
perl-devel mailing list -- perl-devel@lists.fedoraproject.org
To unsubscribe send an email to perl-devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/perl-devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Orphaned packages looking for new maintainers

[Parag Nemade]

On Mon, Mar 8, 2021 at 9:25 PM Miro Hrončok  wrote:

> On 08. 03. 21 16:35, Parag Nemade wrote:
> >
> >
> > On Mon, Mar 8, 2021 at 5:58 PM Richard W.M. Jones  > <mailto:rjo...@redhat.com>> wrote:
> >
> > On Mon, Mar 08, 2021 at 11:52:10AM +0100, Miro Hrončok wrote:
> >  > The following packages are orphaned and will be retired when they
> >  > are orphaned for six weeks, unless someone adopts them. If you
> know for sure
> >  > that the package should be retired, please do so now with a
> proper reason:
> >  >
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> > <
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life>
> >  >
> >  > Note: If you received this mail directly you (co)maintain one of
> the affected
> >  > packages or a package that depends on one. Please adopt the
> affected
> > package or
> >  > retire your depending package to avoid broken dependencies,
> otherwise your
> >  > package will fail to install and/or build when the affected
> package gets
> > retired.
> >  >
> >  > Request package ownership via the *Take* button in he left column
> on
> >  > https://src.fedoraproject.org/rpms/
> > <https://src.fedoraproject.org/rpms/>
> >  >
> >  > Full report available at:
> >  > https://churchyard.fedorapeople.org/orphans-2021-03-08.txt
> > <https://churchyard.fedorapeople.org/orphans-2021-03-08.txt>
> >  > grep it for your FAS username and follow the dependency chain.
> >
> > A lot of problems caused by:
> >
> >XXX requires font(:lang=en)
> >
> > which seems to have been triggered by:
> >
> >> jomolhari-fonts   orphan, pnemade
> 2
> > weeks ago
> >
> > I don't really understand this one TBH.
> >
> >
> > I do not understand the reason behind this package getting orphaned. May
> I know
> > how it gets orphaned? I don't even remember now who was the previous
> owner of
> > this package? Does the orphaning of the package get recorded in the
> datagrepper log?
>
> Not sure if recorded, but I happen to have a backup of the metadata from
> ~20
> ages ago:
>
>
> https://github.com/fedora-python/portingdb/blob/3930184bdb/data/pagure_owner_alias.json
>
> It suggests it was frixxon who owned the packaged before it was orphaned.
>
>
Thank you.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Orphaned packages looking for new maintainers

[Parag Nemade]

On Mon, Mar 8, 2021 at 5:58 PM Richard W.M. Jones  wrote:

> On Mon, Mar 08, 2021 at 11:52:10AM +0100, Miro Hrončok wrote:
> > The following packages are orphaned and will be retired when they
> > are orphaned for six weeks, unless someone adopts them. If you know for
> sure
> > that the package should be retired, please do so now with a proper
> reason:
> > https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
> >
> > Note: If you received this mail directly you (co)maintain one of the
> affected
> > packages or a package that depends on one. Please adopt the affected
> package or
> > retire your depending package to avoid broken dependencies, otherwise
> your
> > package will fail to install and/or build when the affected package gets
> retired.
> >
> > Request package ownership via the *Take* button in he left column on
> > https://src.fedoraproject.org/rpms/
> >
> > Full report available at:
> > https://churchyard.fedorapeople.org/orphans-2021-03-08.txt
> > grep it for your FAS username and follow the dependency chain.
>
> A lot of problems caused by:
>
>   XXX requires font(:lang=en)
>
> which seems to have been triggered by:
>
>   > jomolhari-fonts   orphan, pnemade  2
> weeks ago
>
> I don't really understand this one TBH.
>

I do not understand the reason behind this package getting orphaned. May I
know how it gets orphaned? I don't even remember now who was the previous
owner of this package? Does the orphaning of the package get recorded in
the datagrepper log?

Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam on the list, report it: 
https://pagure.io/fedora-infrastructure

Re: Follow-up - Please BuildRequire python3-setuptools explicitly

[Parag Nemade]

Hi,

I think fontforge is a false positive. It's just one line which imports
setuptools and that is from third party sources in the pycontrib directory.
That file (or directory) is not installed by the fontforge package.

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

Orphaning my nodejs packages

[Parag Nemade]

Hi all,

As you know many nodejs packages have been removed recently but that has
created dependency issues. I maintain a few nodejs packages in Fedora but
those I added a few years back to learn nodejs packaging.
As more and more packages per release are getting retired it has become
difficult for me to keep maintaining my low package maintenance packages.
Hence instead of getting more and more bugzilla notifications for FTI or
FTBFS bugs and trying to figure out which dependency is present and which
not, I prefer to orphan them. I have orphaned them all so in case you need
it for your package please take the ownership.

Below is a list of packages(and their dependencies) which are owned by me
nodejs-ascii-tree
nodejs-buffer-shims
nodejs-caller-path
nodejs-caller-callsite
nodejs-callsites
nodejs-clear-required
nodejs-deep-extend
nodejs-error-ex
nodejs-freetree
nodejs-fs-ext
nodejs-ip
nodejs-is-arrayish
nodejs-from
nodejs-read-all-stream
nodejs-require-uncached
nodejs-statuses
nodejs-stream-combiner
nodejs-stream-spigot
nodejs-text-table

With the orphaning of nodejs-readdir-scoped-modules, I am orphaning
nodejs-debuglog

Other packages that I own but may share dependencies with other package
maintainers are
nodejs-core-util-is
nodejs-duplexer
nodejs-duplexify
nodejs-end-of-stream
nodejs-handlebars
nodejs-is-stream
nodejs-object-assign
nodejs-os-tmpdir
nodejs-pinkie
nodejs-pinkie-promise
nodejs-process-nextick-args
nodejs-readable-stream
nodejs-resolve-from
nodejs-safe-buffer
nodejs-split
nodejs-stream-shift
nodejs-through2
nodejs-util-deprecate
nodejs-xtend

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

Re: Fedora 32 System-Wide Change proposal: Move fonts language Provides to Langpacks

[Parag Nemade]

Hi,

Thank you Igor for your review.

On Thu, Jan 2, 2020 at 10:52 PM Igor Gnatenko <
ignatenkobr...@fedoraproject.org> wrote:

> I think it would be useful to mention in the change page that
> langpacks-core-* already depend on "good quality font". If that is
> already there, I apologize.
>
>
I think this is covered under "User Experience" section.

Another thing which is not mentioned on the change page is that you
> are going to drop Requires: font(:lang=…) from fontconfig (otherwise
> it is going to pull all langpacks-core-* packages).
>
>
Yes, once fontconfig updated, mass rebuild of all packages providing some
kind of "Provides: font(:lang=)" will drop that dependency.
I think this has been mentioned in Scope section.

Otherwise I'm happy with this change since this will finally solve the
> problem where you install some game like teeworlds, get some fonts
> pulled in and autoremove will never remove it since fontconfig depend
> on font(:lang=xx) and libsolv never auto-removes "alternative"
> packages. So you never remove fonts unless explicitly ask DNF to do
> so.
>
>
Regards,
Parag

On Thu, Jan 2, 2020 at 4:17 PM Ben Cotton  wrote:
> >
> > https://fedoraproject.org/wiki/Changes/FontLanguageProvidesToLangpacks
> >
> > == Summary ==
> > Move `Provides: font(:lang=...)` from fonts packages into the
> > `langpacks` package,
> > giving predictable default fonts for language scripts.
> >
> > === Motivation ===
> > Currently fonts packages has auto-generated `font(:lang=...)`
> > provides, which can be used as a dependency identifier to satisfy font
> > coverage required for a certain language requirement. This is used by
> > GTK application to install missing fonts via PackageKit for example.
> > However in practice it has not been very useful since usually there
> > are assorted multiple fonts that provide the language coverage and so
> > an arbitrary fonts of unknown quality would get selected, so the
> > mechanism is not unreliable.
> >
> > This change uses instead the default fonts chosen in `langpacks` for
> > each language, to give reliable predictable default fonts for each
> > language and improve the user application experience around fonts.
> >
> > == Owner ==
> > * Name: [[User:Tagoh| Akira TAGOH]], [[User:Pnemade| Parag Nemade]]
> > * Email: ta...@redhat.com, pnem...@redhat.com
> >
> >
> > == Detailed Description ==
> > The language based metadata for fonts packages was introduced in
> > Fedora 11.  The idea being to provide a mechanism to find and install
> > a font for missing glyphs through PackageKit and was useful for
> > minority languages which might be missing default installed fonts
> > packages.  But the user experience was generally not terribly good.
> >
> > Users cannot predict which fonts will be installed. This often leads
> > to poor fonts choices installed, particularly for languages with too
> > many available fonts such as English, since the first font found
> > lexically will be arbitrarily chosen with gurantee of quality or
> > expected style.
> > This random dependency resolution sometimes introduces highly
> > unexpected results too - for example a font from an external
> > repository may get chosen by chance. This would be particularly
> > problematic when composing ISOs, eg when including EPEL.
> >
> > So this Changes proposal aims to improve the user experience around
> > font dependencies by moving the meta-provides the `langpacks` package
> > instead. Langpacks contains various dependencies to use for certain
> > languages, including dependencies for default fonts. so it will
> > resolve the above issues.
> >
> > Specifically speaking, currently font provides are generated like this:
> > 
> > $ fc-query -f %{=pkgkit}  /usr/share/fonts/dejavu/DejaVuSans.ttf
> > font(dejavusans)
> > font(:lang=aa)
> > font(:lang=ab)
> > ...
> > 
> >
> > and at the build time, it is transformed to:
> > 
> > Provides: font(dejavusans)
> > Provides: font(:lang=aa)
> > Provides: font(:lang=ab)
> > ...
> > 
> >
> > After this proposal, the above result will be:
> > 
> > Provides: font(dejavusans)
> > 
> >
> > and then add `Provides: font(:lang=...)` line to corresponding
> > sub-packages langpacks-core-*.
> >
> > So asking for a font for a certain language through PackageKit will be
> > achieved by langpacks-core-* instead of a random font package.
> >
> > == Benefit to Fedora ==
> > This proposal will provide reliable, pr

Re: [Test-Announce] Fedora 31 Beta Freeze

[Parag Nemade]

On Tue, Aug 27, 2019 at 4:14 PM Mamoru TASAKA 
wrote:

> Mohan Boddu wrote on 2019/08/27 9:55:
> > Hi all,
> 
> >
> >
> > Today is also the Beta freeze[4]. This means that only packages which fix
> > accepted blocker or freeze exception
> > bugs[5][6] will be marked as 'stable' and included in the Beta composes.
> > Other builds will remain in updates-
> > testing until the Beta release is approved, at which point the Beta
> freeze
> > is lifted and packages can move to
> > 'stable' as usual until the Final freeze.
> >
> >
> > [1] https://fedoraproject.org/wiki/Releases/31/Schedule
> > [2] https://fedoraproject.org/wiki/Updates_Policy#Bodhi_enabling
> > [3] https://fedoraproject.org/wiki/Updates_Policy#Branched_release
> > [4] https://fedoraproject.org/wiki/Milestone_freezes
> > [5] https://fedoraproject.org/wiki/QA:SOP_blocker_bug_process
> > [6] https://fedoraproject.org/wiki/QA:SOP_freeze_exception_bug_process
> > [7] https://fedoraproject.org/wiki/ReleaseEngineering/StringFreezePolicy
> >
> >
>
> Well, the above [1] says 2019/08/27 is beta freeze, however python people
> seem to be saying that beta freeze is 2019/08/29, as said in [8] and [9]
> (and so I thought beta freeze was 2019/08/29 as such emails were repeatedly
>   sent to me). Which is correct?
>
>

I too got confused because I have already recorded 29th August as Beta
Freeze in my calendar. I see that Ben has edited the Schedule page[1] but I
am yet to see if there is any accompanying FESCo ticket approval for this
change.

Regards,
Parag

[1]
https://fedoraproject.org/w/index.php?title=Releases%2F31%2FSchedule=revision=550934=535832
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org

Re: Langpacks and the packages needed to display/input a language

[Parag Nemade]

Hi Jason,

On Sat, Jun 15, 2019 at 4:35 AM Jason L Tibbitts III 
wrote:

> I noticed that my F30 installs are coming out far larger than my F29
> installs (by 3GB or so) and did some digging into why.
>
> With F30 we switched away from having groups named like "korean-support"
> that you could install to get input methods and fonts needed to display
> a language and instead we have metapackages named like "langpacks-ko".
> These metapackages have (generally) weak dependencies on the fonts and
> input methods as before. But other packages have reverse weak
> dependencies on the langpacks, which causes far more to get pulled in
> than was previously installed.  For example, each libreoffice langpack
> has a "supplements" weak reverse dependency on the base "langpacks"
> metapackage.
>
> All of this seems fine, but my original goal was to be able to properly
> display, and perhaps input, various languages.  But now I get
> translations and help files and such as well.  Not just for libreoffice,
> but for eclipse, glibc, all of KDE as well.  And I also get
> autocorrection rules, spelling dictionaries, hyphenation rules, and
> terreract OCR recognition data as well.  Some of those aren't small, and
> the end result is that I need to bump up the size of / quite a bit.
>
> Note that turning off install_weak_deps is not an option because for
> most of the langpacks, _all_ of the langpack are weak.  (Some do have
> hard font dependencies, and I'm not sure if this inconsistency is
> intentional.)
>
> So it seems we lost the simple "here are our suggested Korean fonts and
> an input method" and instead the only thing you can say is "I want
> everything possible to be available in Korean".  Is there any way to
> improve the granularity here?  Perhaps by having "light" and "heavy"
> langpacks, or splitting them by usage (translations versus simple
> display of text)?
>
> For now I guess I will simply extract the list of fonts and input
> methods I want from the langpack specfile and stop installing the actual
> langpack packages.
>

Unfortunately this is the only option available for you. Remember langpacks
meta-packages are not pulling unnecessary language packages. You have
required base packages already installed on your system that is why when
you try to install langpacks-ko, you are getting all the respective Korean
language related packages. I never thought someone who want to use dekstop
in some language also will prefer not to have all language related packages
installed on his system.

If users think splitting (e.g.) langpacks-ko package into langpacks-i18n-ko
and langpacks-l10n-ko packages will make sense for them then someone please
report a bug against langpacks package and i18n group will discuss on it.

Regards,
Parag
___
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: Help needed for FTBFS in rawhide because of libraries order

[Parag Nemade]

On Mon, Feb 4, 2019 at 5:44 PM Mamoru TASAKA 
wrote:

> Guido Aulisi wrote on 2019/02/03 20:31:
> > Hi,
> > I'm trying to debug a FTBFS in rawhide:
> >
> > https://koji.fedoraproject.org/koji/taskinfo?taskID=32412101
> >
> > Apparently it fails because of library ordering, but it works in f29.
> > g_object_unref is defined in gobject-2.0 and it gets surely added by
> > the 'pkgconf  --libs cairo pangocairo pango' command.
> >
> > Did anything about gobject or glib change in rawhide recently?
> >
> > Thank you for any help.
> >
> > Guido
> >
> Apparently this is because rawhide pango.pc does not add -lglib-2.0
> when called with pkgconf --libs:
>
> F-29
> $ rpm -q pango
> pango-1.42.4-2.fc29.x86_64
> $ pkgconf --libs pango
> -lpango-1.0 -lgobject-2.0 -lglib-2.0
>
> F-30
> $ rpm -q pango
> pango-1.43.0-1.fc30.x86_64
> $ pkgconf --libs pango
> -lpango-1.0
>
> pango-1.43.0-1.fc30.x86_64 pango.pc shows:
> --
> Name: Pango
> Description: Internationalized text handling
> Version: 1.43.0
> Requires.private: glib-2.0 >=  2.38.0, gobject-2.0 >=  2.38.0, fribidi >=
> 0.19.7, libthai >=  0.1.9, harfbuzz >=  1.4.2, fontconfig >=  2.11.91,
> freetype2, xrender, xft >=  2.0.0, cairo >=  1.12.10
> Libs: -L${libdir} -lpango-1.0
> Libs.private: -lm
> --
> So -lglib-2.0 is moved to Requires.private.
>
> I guess this is due to this commit:
>
> https://gitlab.gnome.org/GNOME/pango/commit/86855b6a458fd9b82d246f723a7e3c9cdb37a8a0
> It seems to be doing some refactoring (with adding some fallback), and
> "requires: gobject_dep," line is deleted.
>
> Currently I am not sure if it is intentional or accidental.
>

I think this commit
https://gitlab.gnome.org/GNOME/pango/commit/d0cb6be7431d1a3c711bd45bcf05b34601604037
will revert it back but we need to wait for next upstream pango release.

Parag
___
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: F30 System-Wide Change proposal: Replace Comps Language Group With Langpacks

[Parag Nemade]

On Mon, Jan 21, 2019 at 1:29 PM Owen Taylor  wrote:

> If I understand the proposal, I'm slightly concerned that the proposed
> use of Supplements: means that there will be no longer any single
> place where we declare "this is our recommended font for LangX, this
> is our recommended input method for LangX" - the history of this will
> be collectively over all of dist-git and hard to extract. (And it will
> be necessary to go to packages we stop using and remove Supplemenets)
>
> What is the reason for the use of Supplements instead of just adding
> Recommends: to the langpacks packages?
>

Thanks. I have corrected it in the Change wiki page. Initially it was a
thought to use Supplements. You can see Recommends is used already in test
langpacks spec
<https://copr-dist-git.fedorainfracloud.org/cgit/pnemade/langpacks/langpacks.git/tree/langpacks.spec>
file.

Parag


>
> Owen
>
> On Wed, Jan 9, 2019 at 2:58 PM Ben Cotton  wrote:
> >
> > Congratulations to the last System-Wide Change proposal of F30!
> >
> >
> https://fedoraproject.org/wiki/Changes/Replace_Comps_Language_Group_With_Langpacks
> >
> > == Summary ==
> > Language support groups in Comps file will get replaced by langpacks
> > package. With this Change we want meta-packages like langpacks-ja to
> > also install required fonts and input-methods for the given language.
> >
> > == Owner ==
> > * Name: [[User:petersen| Jens Petersen]]
> > * Email:  petersen at fedoraproject dot org
> > * Name: [[User:pnemade| Parag Nemade]]
> > * Email: pnemade at fedoraproject dot org
> >
> > == Detailed Description ==
> > This change will remove the need of having the language specific comps
> > groups in Fedora.
> >
> > We already have ''langpacks-*'' packages in Fedora since F24.
> > Currently they are installing language packages for translations,
> > dictionaries etc. but not fonts or input-methods. With this Change we
> > will try to install fonts and input-methods as well.
> > E.g. if you net-install Fedora in Japanese language then installation
> > of any base package like libreoffice-core or man-pages are installing
> > automatically libreoffice-langpack-ja or man-pages-ja but langpacks-ja
> > is not installing any Japanese font or input-method.
> > But now with using RPM tags or weak dependencies like Supplements, we
> > can get font as well as input-method packages installed as well on the
> > system.
> > There is no need of language comps groups to exist, they will be
> > replaced by langpacks.
> >
> > This Change is originally submitted at https://pagure.io/i18n/issue/97
> >
> > == Benefit to Fedora ==
> > Users can install complete language support now using langpacks only.
> > This will also help to remove the language support groups from the
> > comps file.
> >
> > == Scope ==
> > * Proposal owners: Check all langpacks providing packages (like fonts,
> > input-methods) add Supplements tag in their SPEC file and build them.
> > We will track the progress of this Change in
> > [https://copr.fedorainfracloud.org/coprs/pnemade/langpacks/ Langpacks
> > Copr] project.
> > * Other developers: To all other developers of packages who provides
> > langpacks, they need to add the Supplements tag as given in this
> > [https://fedoraproject.org/wiki/Packaging:Langpacks Langpacks
> > guideline] to each langpack subpackage.
> > * Release engineering: none
> > * Policies and guidelines: none
> >
> > == Upgrade/compatibility impact ==
> > None.
> >
> > == How To Test ==
> >
> > * [[QA:Langpacks]]
> >
> > == User Experience ==
> > Currently users can get complete language support installed only using
> > "''dnf group install ''" command. After this Change gets
> > implemented end users can get language support installed using
> > meta-packages "''langpacks-"'' only
> >
> > == Dependencies ==
> > No Other Change depend on this.
> >
> > == Contingency Plan ==
> > * Contingency mechanism: If this change is not completed by final
> > development freeze then we need to target this for F31. We are just
> > proposing to add additional information in langpacks packages that is
> > Supplements tag. This should not affect individual langpacks packages
> > installation by dnf.
> > * Contingency deadline: I don't think we will need anything to revert
> > or apply any contingency plan here if this is not completed by beta
> > freeze.
> > * Blocks release? No
> > * Blocks product? N/A
> >
> > == Docu

Re: F30 System-Wide Change proposal: Replace Comps Language Group With Langpacks

[Parag Nemade]

On Fri, Jan 18, 2019 at 12:49 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Wed, Jan 09, 2019 at 02:56:59PM -0500, Ben Cotton wrote:
> > Congratulations to the last System-Wide Change proposal of F30!
> >
> >
> https://fedoraproject.org/wiki/Changes/Replace_Comps_Language_Group_With_Langpacks
> >
> > == Summary ==
> > Language support groups in Comps file will get replaced by langpacks
> > package. With this Change we want meta-packages like langpacks-ja to
> > also install required fonts and input-methods for the given language.
>
> What is the actual benefit of this change? It looks like a nice
> cleanup, but apart from that?


This Change will benefit to install all the possible language related
packages for a given language using langpacks- meta-package. First
this Change is important so that once we get single package installation
giving needed language support packages we can further work to use this
meta-package in gnome-software or in the required Gnome package to install
the language support automatically.

Also, This will benefit libreoffice package to remove following from its
specfile and only test the libreoffice UI rendering for the given default
language font(s) using langpacks

Requires: font(:lang=)



> It seems that 'dnf install group @lang-foo'
> is not different from 'dnf install langpack-bar'.
>
>
Right. Currently, the dnf group install command provides more language
support packages compared to langpacks- meta-package.

Regards,
Parag
___
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: F30 System-Wide Change proposal: Replace Comps Language Group With Langpacks

[Parag Nemade]

On Thu, Jan 10, 2019 at 5:37 PM David Tardon  wrote:

> Hi,
>
> On Wed, 2019-01-09 at 14:56 -0500, Ben Cotton wrote:
> > E.g. if you net-install Fedora in Japanese language then installation
> > of any base package like libreoffice-core or man-pages are installing
> > automatically libreoffice-langpack-ja or man-pages-ja but langpacks-
> > ja
> > is not installing any Japanese font
>
> Actually in this specific case a Japanese font is installed, because
> libreoffice-langpack-ja requires one :-)
>

Yes that is true. But I did some testing for this Change implementation in
F29 Container. If you only install libreoffice-langpack-ja then
adobe-source-han-code-jp-fonts package is getting installed because it
matches what libreoffice-langpack-ja is requiring that is "font(:lang=ja)"
whereas if langpacks-ja is installed then google-noto-sans-cjk-ttc-fonts
and google-noto-serif-cjk-ttc-fonts are getting installed.

Regards,
Parag
___
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: F30 System-Wide Change proposal: Replace Comps Language Group With Langpacks

[Parag Nemade]

On Thu, Jan 10, 2019 at 12:55 PM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Thu, Jan 10, 2019 at 12:31:38PM +0530, Parag Nemade wrote:
> > On Thu, Jan 10, 2019 at 4:23 AM Zbigniew Jędrzejewski-Szmek <
> > zbys...@in.waw.pl> wrote:
> > > Do you plan to remove the comps groups? And if yes, in F30 or later?
> >
> > Yes, Plan is to remove language support group entries from comps files
> for
> > F30+. Added same to Scope section of Change page now.
>
> > > > == Contingency Plan ==
> > > > * Contingency mechanism: If this change is not completed by final
> > > > development freeze then we need to target this for F31. We are just
> > > > proposing to add additional information in langpacks packages that is
> > > > Supplements tag. This should not affect individual langpacks packages
> > > > installation by dnf.
> > > > * Contingency deadline: I don't think we will need anything to revert
> > > > or apply any contingency plan here if this is not completed by beta
> > > > freeze.
>
> Contingency Plan needs to be changed too to revert the comps removal.
> (I'm mostly wondering when the best moment to trim comps is.)
>

Updated
https://fedoraproject.org/wiki/Changes/Replace_Comps_Language_Group_With_Langpacks#Contingency_Plan

Parag
___
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: F30 System-Wide Change proposal: Replace Comps Language Group With Langpacks

[Parag Nemade]

On Thu, Jan 10, 2019 at 4:23 AM Zbigniew Jędrzejewski-Szmek <
zbys...@in.waw.pl> wrote:

> On Wed, Jan 09, 2019 at 02:56:59PM -0500, Ben Cotton wrote:
> > Congratulations to the last System-Wide Change proposal of F30!
> >
> >
> https://fedoraproject.org/wiki/Changes/Replace_Comps_Language_Group_With_Langpacks
> >
> > == Summary ==
> > Language support groups in Comps file will get replaced by langpacks
> > package. With this Change we want meta-packages like langpacks-ja to
> > also install required fonts and input-methods for the given language.
> >
> > == Owner ==
> > * Name: [[User:petersen| Jens Petersen]]
> > * Email:  petersen at fedoraproject dot org
> > * Name: [[User:pnemade| Parag Nemade]]
> > * Email: pnemade at fedoraproject dot org
> >
> > == Detailed Description ==
> > This change will remove the need of having the language specific comps
> > groups in Fedora.
> >
> > We already have ''langpacks-*'' packages in Fedora since F24.
> > Currently they are installing language packages for translations,
> > dictionaries etc. but not fonts or input-methods. With this Change we
> > will try to install fonts and input-methods as well.
> > E.g. if you net-install Fedora in Japanese language then installation
> > of any base package like libreoffice-core or man-pages are installing
> > automatically libreoffice-langpack-ja or man-pages-ja but langpacks-ja
> > is not installing any Japanese font or input-method.
> > But now with using RPM tags or weak dependencies like Supplements, we
> > can get font as well as input-method packages installed as well on the
> > system.
> > There is no need of language comps groups to exist, they will be
> > replaced by langpacks.
> >
> > This Change is originally submitted at https://pagure.io/i18n/issue/97
> >
> > == Benefit to Fedora ==
> > Users can install complete language support now using langpacks only.
> > This will also help to remove the language support groups from the
> > comps file.
> >
> > == Scope ==
> > * Proposal owners: Check all langpacks providing packages (like fonts,
> > input-methods) add Supplements tag in their SPEC file and build them.
> > We will track the progress of this Change in
> > [https://copr.fedorainfracloud.org/coprs/pnemade/langpacks/ Langpacks
> > Copr] project.
> > * Other developers: To all other developers of packages who provides
> > langpacks, they need to add the Supplements tag as given in this
> > [https://fedoraproject.org/wiki/Packaging:Langpacks Langpacks
> > guideline] to each langpack subpackage.
> > * Release engineering: none
> > * Policies and guidelines: none
>
> Do you plan to remove the comps groups? And if yes, in F30 or later?
>

Yes, Plan is to remove language support group entries from comps files for
F30+. Added same to Scope section of Change page now.

Regards,
Parag


> Zbyszek
>
> > == Upgrade/compatibility impact ==
> > None.
> >
> > == How To Test ==
> >
> > * [[QA:Langpacks]]
> >
> > == User Experience ==
> > Currently users can get complete language support installed only using
> > "''dnf group install ''" command. After this Change gets
> > implemented end users can get language support installed using
> > meta-packages "''langpacks-"'' only
> >
> > == Dependencies ==
> > No Other Change depend on this.
> >
> > == Contingency Plan ==
> > * Contingency mechanism: If this change is not completed by final
> > development freeze then we need to target this for F31. We are just
> > proposing to add additional information in langpacks packages that is
> > Supplements tag. This should not affect individual langpacks packages
> > installation by dnf.
> > * Contingency deadline: I don't think we will need anything to revert
> > or apply any contingency plan here if this is not completed by beta
> > freeze.
> > * Blocks release? No
> > * Blocks product? N/A
> >
> > == Documentation ==
> > * Need to add about this in the Release notes
> >
> >
> > --
> > Ben Cotton
> > Fedora Program Manager
> > TZ=America/Indiana/Indianapolis
> > ___
> > 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.fe

Re: Intent to relicense fontpackages

[Parag Nemade]

Hi,

On Sun, Oct 28, 2018 at 9:14 PM Nicolas Mailhot 
wrote:

> Hi all,
>
> Just FYI, I intend to relicense fontpackages from LGPL3+ to GPL3+, to
> make sharing parts with go-macros easier.
>

Can it be possible for you to explain this further? I want to understand
how license change can help here.


> Since fontpackages only contains templates and scripts and is not linked
> anywhere there is no practical difference.
>
> If you see a problem with this change, or have contributed to
> fontpackages to the past and do not like this change, please say so now.
>
> Regards,
>
> --
> Nicolas Mailhot
>

Parag.
___
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: GNOME 3.30.0 megaupdate

[Parag Nemade]

On Wed, Sep 5, 2018 at 8:49 PM, Stephen Gallagher 
wrote:

>
>
> On Wed, Sep 5, 2018 at 11:12 AM Kalev Lember 
> wrote:
>
>> Hi all,
>>
>> As many of you know, I've been gone half the summer. I'm back now since
>> Monday though and just in time for GNOME 3.30.0 :)
>>
>> We are quite a bit behind with the builds, like half of GNOME is still
>> at 3.28.x or at various stages of 3.29.x snapshots, so there's quite a
>> bit of catching up to do.
>>
>> I just requested a f29-gnome side tag and will be commencing 3.30.0
>> builds shortly. When the builds are done, I'll try to collect all the
>> builds in a single Bodhi megaupdate as usual. Please use 'fedpkg build
>> --target f29-gnome' if you are helping with builds, and I'll pick up
>> anything that is tagged with f29-gnome in koji.
>>
>> Dunno what to do wrt the ongoing freeze and getting final 3.30 in F29
>> Beta, I guess it may be too late for that. Any opinions from QA here?
>>
>> There's also a few 3.30.0 builds already submitted separately into
>> Bodhi. I may try to collect those to the megaupdate as well, not sure
>> yet. Let's see how things go :)
>>
>>
>
> I'd be *strongly* disinclined to give a Freeze Exception for a GNOME
> mega-update. There's just far too much that could go wrong. Please plan to
> land the mega-update in updates-testing once the Freeze lifts. U-T is
> enabled by default on the Beta, so people will pick it up on their first
> post-install update anyway.
>
>

Please don't stop this update. There will be few required fixes in this
megaupdate which we need early to test.

Parag.
___
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

Orphaned many packages in Fedora

[Parag Nemade]

Hi,
I want to reduce my current package maintenance, hence orphaned below
packages now

Following packages have no bugs open against them and also not seen any
upstream release since imported in Fedora few years ago
aldusleaf-crimson-text-fonts
almas-mongolian-title-fonts
cf-sorts-mill-goudy-fonts
google-roboto-mono-fonts
impallari-lobster-fonts
moyogo-molengo-fonts
mph-2b-damase-fonts
oflb-brett-fonts
oflb-icelandic-fonts
oflb-roadstencil-fonts
oflb-sportrop-fonts
pagul-fonts
phetsarath-fonts
sarai-fonts
tabish-eeyek-fonts
tangerine-fonts
tharlon-fonts
trabajo-fonts
tuladha-jejeg-fonts
typemade-josefinsansstd-light-fonts

AFAIK, below packages have no dependency on any other packages in Fedora
nodejs-package-info
|-nodejs-got
  |-nodejs-create-error-class
|-nodejs-capture-stack-trace
  |-nodejs-into-stream
|- nodejs-from2
|- nodejs-p-is-promise
  |-nodejs-is-redirect
  |-nodejs-is-retry-allowed
  |-nodejs-lowercase-keys
  |-nodejs-timed-out
|-nodejs-prepend-http
|-nodejs-registry-url
  |-nodejs-duplexer3
|-nodejs-url-parse-lax

nodejs-http-server
|-nodejs-corser
|-nodejs-ecstatic
  |-nodejs-he
  |-nodejs-url-join
|-nodejs-http-proxy
  |-nodejs-eventemitter3
  |-nodejs-requires-port
|-nodejs-portfinder
|-nodejs-union

nodejs-as-number
nodejs-bluebird
nodejs-chainsaw
  |- nodejs-seq
nodejs-errs
nodejs-follow
  |- nodejs-browser-request
nodejs-filed
nodejs-gettext-parser
  |- nodejs-encoding
nodejs-infinity-agent
nodejs-json-parse-better-errors
nodejs-langdetect
nodejs-minstache
nodejs-native-or-bluebird
nodejs-nested-error-stacks
nodejs-node-print
nodejs-nsp-api
nodejs-nsp-audit-shrinkwrap
  |- nodejs-duplex

nodejs-node-status-codes
nodejs-pegjs
nodejs-pem
nodejs-silent-npm-registry-client
  |- nodejs-npm-registry-client
nodejs-stream-reduce
nodejs-strscanner
nodejs-ttembed-js
  |- nodejs-posix-getopt
nodejs-typedarray
nodejs-xmldom

Following packages have FTBFS since last two releases, hence I have retired
them from Fedora rawhide.
1) sfntly
2) ttname
3) nodejs-nano needs npm(cloudant-follow) package which is under review but
it further needs more packages to be packages in Fedora.
I have no time at all to keep adding newer dependencies getting added by
every new upstream release of this package.
Due to this package removal, I have retired below packages as well.
nodejs-npm-stats
nodejs-dependency-lister

Regards,
Parag
___
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/message/CLZ47LWS5WOTUXIO2EIILGLYP5AT5WQM/

Re: What to do when test gating in bodhi fails (no test results found)?

[Parag Nemade]

Hi,

On Wed, Mar 21, 2018 at 6:12 PM, Fabio Valentini 
wrote:
> On Wed, Mar 21, 2018 at 11:28 AM, Pierre-Yves Chibon
>  wrote:
>> On Mon, Mar 19, 2018 at 03:57:19PM +0100, Pierre-Yves Chibon wrote:
>>> waiverdb-cli should now support waiving missing results, I'm
double-checking it
>>> and see if we can document it at:
>>>
https://fedoraproject.org/wiki/Package_update_HOWTO#Handling_feedback_from_automated_tests
>>> next to the other examples.
>>
>>
>> The documentation on how to waive tests or missing tests have been
updated, same
>> url (above).
>>
>> Let us know if you need more or face issues with it!
>
> I've just "waived" the missing test results which blocked my 2
> packages, and it worked, I could push them to stable now.

I too created waiver for this case for 2 of my package updates
 for f27. I then directly go to bodhi and tried to find
the "push to batched/stable" link but could not. I then wait for 5 minutes.
Then I logout and login to bodhi but still did not get option to push to
batched/stable.

Now exactly after 12 hrs I logged into bodhi and can see that link to push
to stable. Is there any delay in getting that link? If so why is this much
delay?

Also, How can one know that waiver has been created for some update in
bodhi UI? Is there no log available to end user for his updates about how
this test gating system worked on his updates that resulted successful or
failed testing?

Regards,
Parag.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Mass Rebuild for Fedora 28

[Parag Nemade]

On Tue, Feb 13, 2018 at 4:36 AM, Dennis Gilmore  wrote:
> Hi All,
>
> We have now completed the automated part of the Fedora 28 mass rebuild,
> The details for the scheduled mass rebuild for Fedora 28 can be found
> here[1]. The failure page for the rebuilds can be found here[3] and the
> full list of packages that are needing rebuilding can be found here[4].
>  The needs rebuild list includes packages that failed to get submitted
> to koji for various reasons, things like the spec bumping failing due
> to incomplete or incorrect retirement
>
> Please quickly clean up all build failures as the schedule[5] has us
> branching next Tuesday, on the 20th of February and enabling Bodhi on
> the 6th of March, So expect to see a 28 branched compose in about a
> week from now.
>
> Many Thanks
>
> Dennis
>
> [1] https://fedoraproject.org/wiki/Fedora_28_Mass_Rebuild
> [2] https://kojipkgs.fedoraproject.org/mass-rebuild/f28-failures.html
> [3] https://kojipkgs.fedoraproject.org/mass-rebuild/f28-need-rebuild.ht
> ml

I think its better as releng already have above need-rebuild package
list so they can run mass-rebuild script and build all the missed
packages. Are there still any plans to use mass-rebuild script or its
upto individual maintainers to rebuild their packages for Fedora 28?

Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: [ACTION NEEDED] Missing BuildRequires: gcc/gcc-c++

[Parag Nemade]

On Sun, Feb 18, 2018 at 10:39 PM, Igor Gnatenko
 wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Over this weekend I've performed scratch-mass-rebuild without having gcc and
> gcc-c++ in buildroot of all Fedora packages, many of which failed due to 
> random
> reasons and I grepped all logs for some common errors found by analyzing
> hundreds of build logs.
>
> Guidelines: 
> https://fedoraproject.org/wiki/Packaging:C_and_C%2B%2B#BuildRequire
> s_and_Requies
>
> The grep output is located here:
> https://ignatenkobrain.fedorapeople.org/gcc-removal.txt
>
> Some packages might be missed due to short koji outage, broken dependencies 
> and
> so on, but majority of real failures is below.
>
> If you fixed package(s), found false positive, found missing packages in list
> or anything else -- please let me know.
>
> Note to packages which use CMake buildsystem. When you have project(xxx) in
> CMakeLists.txt it checks both for C and CXX compilers. So you might encounter
> packages where you have BuildRequires: gcc and it fails on CXX compiler (even
> you think you don't need it). Solution for this is to send patch to upstream
> switching to something like project(xxx C), or if problem is opposite to
> project(xxx CXX).
>
> List of packages and respective maintainers:
> https://ignatenkobrain.fedorapeople.org/gcc-removal-pkgs.txt

Thanks Igor for all this work. I have fixed my packages now in rawhide only.

Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Is there a seperate SOP for unblocking a package in koji?

[Parag Nemade]

Hi,

On Sun, Oct 1, 2017 at 8:02 PM, Alexander Ploumistos <
alex.ploumis...@gmail.com> wrote:

> Hello,
>
> About a couple of weeks ago, I went through the new
> adoption/unretirement procedure for scidavis and I also used
> fedrepo-req-branch to request that f25, f26 and f27 branches be
> created as well. A few days later I became the owner of the package in
> pagure, I can push to every branch, but whenever I try to build
> anything, koji complains that
>
> "BuildError: package scidavis is blocked for tag f2?-updates-candidate"
> or
> "BuildError: package scidavis is blocked for tag f28-pending"
>
> Do I need to file a new ticket or use another tool, so that I can
> build the package again?
>

Follow step 5 from
https://fedoraproject.org/wiki/Orphaned_package_that_need_new_maintainers#Claiming_Ownership_of_a_Retired_Package

Regards,
Parag.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Council Elections - July/August 2017 - Result announcement

[Parag Nemade]

Hi,

On Tue, Aug 15, 2017 at 6:38 PM, Langdon White 
wrote:

>
>
> On Tue, Aug 15, 2017 at 6:37 AM Kevin Kofler 
> wrote:
>
>> Jan Kurik wrote:
>> >   # votes |  name
>> > - +--
>> >  505  | Justin W. Flory (jwf / jflory7)
>> > - +--
>>
>> No wonder, he is the only candidate who bothered filling out the
>> questionnaire. It shows that answering voters' questions helps. (Though I
>> personally did not vote for him because the answers were not even close to
>> what I wanted to hear.) May this be a lesson for future candidates!
>>
>> Kevin Kofler
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>
> Personally, I find this to be pretty offensive. I care a lot about Fedora
> and between F26 being late & the short cycle for f27, not to mention
> $DAYJOB, I just didn't get to it. I am really sorry to have lost the seat
> and not campaigned hard enough.
>
> Congrats to Justin!
>
>

Just a suggestion, election wrangler can ask for submitting and preparing
the final questionnaires in advance maybe before the nomination period
starts so that probable candidate can know about them and they can start
preparing for their answers along with their nomination and submit it for
blog publishing review during nomination period. These blogs can be
published then in Campaign period. I am not sure but I guess publishing
these interviews also takes some amount time if no one is available to
review them.

Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: 610 emails for a branch import in dist git?

[Parag Nemade]

On Wed, Jun 28, 2017 at 12:29 PM, Michal Novotny  wrote:

> Can you, please, show the emails or just one of them?
>
>

https://lists.fedoraproject.org/archives/search?mlist=scm-commits%40lists.fedoraproject.org=audacious-plugins



> On Tue, Jun 27, 2017 at 11:34 PM, Michael Schwendt 
> wrote:
>
>> Whoever set up that service, seriously?
>>
>> Why would I receive 610 emails for activity in "epel7"? For packages with
>> a longer git history, it will likely be thousands of emails.
>> ___
>> devel mailing list -- devel@lists.fedoraproject.org
>> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>>
>
>
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to devel-le...@lists.fedoraproject.org
>
>
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Unresponsive packager process and reviews

[Parag Nemade]

On Mon, Mar 13, 2017 at 5:23 PM, Ralf Corsepius  wrote:
> On 03/13/2017 10:38 AM, Vít Ondruch wrote:
>>
>> Is this not enough [1] or you want to make the reviews part of orphaning
>> process?
>
>
>> [1] https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews
>
>
> The latter. [1] is not enough, because it leaves stalled reviews as
> "assigned" with most persons (esp. the package submitter) not noticing it.
>

From that page I think 1.1.2 is very much clear where I believe
reviewers are knowing all the policies that we have for Fedora
packaging and they can take actions given there but for 1.1.1 package
submitter need to know this policy page so that he can himself or
request someone to clear the fedora-review? flag. I don't think we
can/should enforce any criteria here to clear stalled reviews
automatically. Any packager can triage these stalled reviews as per
policy [1].

Is this policy page [1] not approved by Fedora Packaging Committee already?

Regards,
Parag

[1] https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews
[1.1.1] 
https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews#Reviewer_not_responding
[1.1.2] 
https://fedoraproject.org/wiki/Policy_for_stalled_package_reviews#Submitter_not_responding
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Orphaning zanata-parent, zanata-api, zanata-common, zanata-client

[Parag Nemade]

Hi,

On Thu, Mar 9, 2017 at 7:12 AM, Ding Yi Chen  wrote:
> As we merge our repositories into zanata-platform [1].
> so the new versions of Zanata client will be supplied by zanata-platform.
>
> The following repositories are depreciated:
>
> zanata-parent
> zanata-api
> zanata-common
> zanata-client
>
> Thus corresponding Fedora main packages are orphaned.

You need to retire those packages from F26+ branches.

Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Orphaning few very old packages

[Parag Nemade]

Hi,
   I am the the maintainer for following few packages since long time.
I got these packages from its previous owner who left its
maintainership. They have not seen any upstream releases since last
few years.

greadelf
elfinfo
rmanage

Also, I have been maintainer for following typesupply python modules
which I want to orphan now.

python-compositor
python-fontMath
python-robofab
python-ufo2fdk

Then I got few other packages which has not seen any upstream commits
since last 3 years and I also don't want to maintain them anymore

glyphtracer
perl-Lingua-EN-Alphabet-Shaw
perl-perlmenu
scholarsfonts-cardo-fonts
screenruler


Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Review swap

[Parag Nemade]

Hi,

I've got one nodejs module package in need of review. I will be happy
to review your package requests in return.

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

Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Wiki page subscription

[Parag Nemade]

On Wed, Nov 16, 2016 at 9:00 PM, Florian Weimer  wrote:
> On 11/16/2016 04:05 PM, Kevin Fenzi wrote:
>>
>> On Wed, 16 Nov 2016 12:03:42 +0100
>> Florian Weimer  wrote:
>>
>>> On the Fedora wiki, I can subscribe to certain pages.  I did that,
>>> but I did not receive any notifications when they were edited.
>>
>>
>> Odd. This definitely worked ok in the past.
>
>
> Does this work for *anyone* right now?

I remember before we moved to this new wiki ( I think sometime in
2008? ) I used to get notifications but after migration to this
current wiki I did not get notifications for years and did not pay
much attention there. I then realized that I didn't have those old
wiki page subscriptions in this current wiki account. I then
subscribed to some wiki pages but I never get any single email
notification for any changes to those pages. I can still see I have
few pages subscribed for my wiki account but their changes I can see
only online at https://fedoraproject.org/wiki/Special:EditWatchlist

Also, when you open any Fedora wiki page and click on "watch" the
message clearly says that
" The page  has been added to your watchlist. Future changes
to this page and its associated talk page will be listed there. "
This mean to me that notifications are not available and we need to go
to page https://fedoraproject.org/wiki/Special:EditWatchlist and check
if pages on watchlist has been changed in last few days.

Regards,
Parag.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-11-11)

[Parag Nemade]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting on
irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-11-11 16:00 UTC'


Links to all issues below can be found at:
https://pagure.io/fesco/report/meeting_agenda

= Followups =

none

= New business =
#topic #1641 F26 System Wide Change: Retire Synaptics Driver
.fesco 1641
https://pagure.io/fesco/issue/1641

#topic #1637 F26 System Wide Change: AARCH64 - 48-bit VA
.fesco 1637
https://pagre.io/fesco/issue/1637

#topic #1635 F26 Self Contained Changes
.fesco 1635
https://pagure.io/fesco/issue/1635
#link https://fedoraproject.org/wiki/Changes/AnacondaBlivetGUI


= Open Floor =

For more complete details, please visit each individual
issue.  The report of the agenda items can be found at
https://pagure.io/fesco/report/meeting_agenda

If you would like to add something to this agenda, you can
reply to this e-mail, file a new issue at
https://pagure.io/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Schedule for Friday's FESCo Meeting (2016-11-04)

[Parag Nemade]

On Fri, Nov 11, 2016 at 7:12 PM, Stephen Gallagher  wrote:
> On 11/11/2016 08:38 AM, Jared K. Smith wrote:
>>
>> On Fri, Nov 4, 2016 at 12:14 PM, Jared K. Smith > > wrote:
>>
>> For the second week in a row, we didn't have enough FESCo members to 
>> reach a
>> quorum.  We'll push the agenda to next week's meeting.
>>
>>
>>
>> I won't be able to make today's meeting, and since we haven't had a quorum 
>> for
>> the last two weeks, we don't have a volunteer to run today's meeting.  I'll 
>> vote
>> in the tickets from last week's agenda.
>>
>
> I have a conflicting appointment during the meeting as well. I think I've
> already voted in all of the tickets.


I think I can chair the meeting today. All other members please come
at usual time 16:00 UTC that is 2 hours from now.
We will have the same agenda that Jared posted in this thread.

Regards,
Parag
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Critpath flags on Emacs and Guile

[Parag Nemade]

Hi,

On Fri, Oct 21, 2016 at 2:13 PM, Jan Synacek  wrote:
> Why were critpath flags set on Emacs and Guile?

I think guile package was added because of @critical-path-base
@critical-path-base installs rpm-build -> gdb-headless -> guile

and emacs package was added because of @core group
@core group installs iputils -> libidn -> emacs-filesystem

Regards,
Parag.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Notifications on dependency retirement

[Parag Nemade]

On Wed, Oct 19, 2016 at 5:04 PM, Julien Enselme  wrote:
> Hi,
>
> I discovered this morning that a package I co-maintain was retired
> (ccnet [1]) because one of its dependency was retired (libzdb [2]). I
> learned it only because we have an open bug on it that change assigner
> because of this fact. I'll call this notification thanks to luck.
>
> Is there a way to be notified as soon as a dependency is orphaned so
> the (co-)maintainer can take action as soon as possible?
>
> I think the usual way is to send a notification message to devel but it
> relies on sending/reading the mail (I personally forgot ccnet relied on
> libzdb). In this case, I can't find one. But I may have missed it.
>
> Could this simply be because I am only a watcher and committer (neither
> POC nor admin) of this package or should we find a way to improve this?

Keep watching devel list for "Orphaned Packages in " emails.
The latest one[1] shows that libzdb is in orphaned state since last 15
weeks.

Regards,
Parag.

[1] 
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/UKET6ZEQY2YPLZ2XZUGRGGQBYV73YLXL/
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2016-10-14)

[Parag Nemade]

Hi,
   Thanks to Kevin for running this meeting.

===
#fedora-meeting: FESCO (2016-10-14)
===


Meeting started by paragan at 16:00:37 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-10-14/fesco.2016-10-14-16.00.log.html
.



Meeting summary
---
* init process  (paragan, 16:00:38)

* #1626 Release blocking deliverables for Fedora 25  (paragan, 16:03:56)
  * LINK: https://fedorahosted.org/fesco/ticket/1626   (paragan,
16:03:57)
  * AGREED: Accept the current status of Release blocking deliverables
as given on its wiki page and close the ticket (+6,0,0)  (nirik,
16:16:57)

* #1635 F26 Self Contained Changes  (nirik, 16:17:30)
  * AGREED: self contained changes approved (+5,0,0)  (nirik, 16:22:45)

* #1634 EOL and vulnerable software  (nirik, 16:23:07)
  * will discuss more on list/ticket and revisit next week  (nirik,
16:42:17)

* Next weeks chair  (nirik, 16:42:38)
  * maxamillion to chair next week  (nirik, 16:43:16)

* Open Floor  (nirik, 16:43:20)

Meeting ended at 16:46:49 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* nirik (52)
* mhroncok (24)
* kalev_ (18)
* zodbot (14)
* paragan (14)
* jwb (14)
* maxamillion (13)
* cstratak (5)
* nb (4)
* sgallagh (0)
* kalev (0)
* Rathann (0)
* jsmith (0)
* dgilmore (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Schedule for Friday's FESCo Meeting (2016-10-14)

[Parag Nemade]

On Fri, Oct 14, 2016 at 4:57 PM, Josh Boyer <jwbo...@fedoraproject.org> wrote:
> On Fri, Oct 14, 2016 at 4:03 AM, Parag Nemade <panem...@gmail.com> wrote:
>> Following is the list of topics that will be discussed in the
>> FESCo meeting Friday at 16:00UTC in #fedora-meeting on
>> irc.freenode.net.
>>
>> If needed any more topics to discuss we can discuss it in Open Floor.
>>
>>  To convert UTC to your local time, take a look at
>>   http://fedoraproject.org/wiki/UTCHowto
>>
>> or run:
>>   date -d '2016-10-14 16:00 UTC'
>>
>>
>> Links to all tickets below can be found at:
>> https://fedorahosted.org/fesco/report/9
>>
>> = Followups =
>>
>> #topic #1626 Release blocking deliverables for Fedora 25
>> .fesco 1626
>> https://fedorahosted.org/fesco/ticket/1626
>>
>> = New business =
>>
>> #topic #1635 F26 Self Contained Changes
>> .fesco 1635
>> https://fedorahosted.org/fesco/ticket/1635
>>
>> #topic #1634 EOL and vulnerable software
>> .fesco 1634
>> https://fedorahosted.org/fesco/ticket/1634
>>
>> = Open Floor =
>>
>> For more complete details, please visit each individual
>> ticket.  The report of the agenda items can be found at
>> https://fedorahosted.org/fesco/report/9
>>
>> If you would like to add something to this agenda, you can
>> reply to this e-mail, file a new ticket at
>> https://fedorahosted.org/fesco, e-mail me directly, or bring it
>> up at the end of the meeting, during the open floor topic. Note
>> that added topics may be deferred until the following meeting.
>
> Perhaps we could get an update on when the FESCo trac instance will be
> retired and replaced with pagure?

I think last week only I asked about this to Kevin and he said he
wanted to do first fedora-infra trac migration as it was having huge
number of tickets to check if the migration triggers any pagure bugs.

Parag.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-10-14)

[Parag Nemade]

Following is the list of topics that will be discussed in the
FESCo meeting Friday at 16:00UTC in #fedora-meeting onirc.freenode.net.

If needed any more topics to discuss we can discuss it in Open Floor.

 To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-10-14 16:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #1626 Release blocking deliverables for Fedora 25
.fesco 1626https://fedorahosted.org/fesco/ticket/1626

= New business =

#topic #1635 F26 Self Contained Changes
.fesco 1635https://fedorahosted.org/fesco/ticket/1635
#topic #1634 EOL and vulnerable software
.fesco 1634https://fedorahosted.org/fesco/ticket/1634

= Open Floor =

For more complete details, please visit each individual
ticket.  The report of the agenda items can be found
athttps://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can
reply to this e-mail, file a new ticket
athttps://fedorahosted.org/fesco, e-mail me directly, or bring it
up at the end of the meeting, during the open floor topic. Note
that added topics may be deferred until the following meeting.
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org

Re: Weak deps in updates

[Parag Nemade]

On Thu, Sep 8, 2016 at 7:21 PM, Christian Stadelmann
 wrote:
> So all packages have to be rebuilt to make their weak dependencies go into 
> repo metadata? This was not obvious from the first posting by  Kevin Fenzi 
> and probably should go into a separate post here and on devel-announce too.

I only provided my observation, I don't have access to bodhi server to
look whats happening there exactly. Wait for Kevin's reply on this
issue.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Weak deps in updates

[Parag Nemade]

On Thu, Sep 8, 2016 at 5:56 PM, Christian Stadelmann
 wrote:
> Still not working.
>
> The only file from updates-testing repo metadata¹ providing "recommends" XML 
> tags is the 
> 2b1dda391308bf7395f9890774b4d2d0692b615c2ad6a73fa378080d32c0c531-primary.xml 
> file, but it just has those tags for 6 packages.

I don't know why recommends tag for fedora-easy-karma is not appearing
in metadata but I can see recommends tag in the same metadata file for
the recently built packages like openqa. I think fedora-easy-karma
should be the only oldest built package in the f24 updates-testing
repository.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Unversioned and >/=/>= obsoletes

[Parag Nemade]

On Fri, Sep 2, 2016 at 7:21 PM, Igor Gnatenko  wrote:
> On Fri, Sep 2, 2016 at 3:34 PM, Michael Schwendt  wrote:
>> On Fri, 2 Sep 2016 13:14:13 +0200, Igor Gnatenko wrote:
>>
>>> All guidelines mandate the use of >> have some number of packages (179 source rpms -> 292 binary rpms) with
>>> unversioned Obsoletes or with >/=/>= Obsoletes.
>>>
>>> It is causing problems with upgrade (if package is getting re-added)
>>> or with 3rd-party repositories. Older package is obsoleting new
>>> package.
>>
>> Good luck with trying to get some packagers to fix such issues!
>> I appreciate the effort as I've reported similar things many times before,
>> but some packagers just don't respond in bugzilla or overwrite changes
>> applied to git after waiting months for a reply.
> Isn't this is a guidelines, so if packager ignores them - he should be 
> punished?

No, packager's sponsor will be contacted and he will guide the
packager for the correct usage of packaging guidelines.

Regards,
Parag
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Removing aliases on bugzilla

[Parag Nemade]

Hi,

On Sun, Aug 14, 2016 at 11:08 PM, Igor Gnatenko  wrote:
> Hi,
>
> Probably you've seen some strange activity from me like removing
> aliases from old (and new) bugs.
>
> Actually there is bug in bugzilla which prevents searching by text
> which is written in some bug's alias. Unfortunately I didn't realize
> when I ran script that it will send ton of notifications and that it's
> actual bug of buzilla (I thought it's a feature).

Can you let us know about what bug are you seeing in bugzilla? Have
you reported it already so that bugzilla maintainers can look at it?

Please don't remove aliases they are useful to many people.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Improvements of Fedora Sponsorship process

[Parag Nemade]

Hi,

On Sat, Aug 6, 2016 at 1:49 AM, Mikolaj Izdebski <mizde...@redhat.com> wrote:
> On 08/05/2016 10:31 AM, Parag Nemade wrote:
>>> b) fedora-review is run automatically by some bot/script just after review
>>> have been submitted.
>>
>>  Can a new utility be written for this as I don't think that long
>> fedora-review output is helpful? Most checks have no markings in them.
>> How can it be helpful to package submitter?
>
> You can configure which fedora-review checks are ran, for example
> exclude any non-automated checks.

I suppose then Generic group checks are sufficient here.

>
>>> c) Create wiki page with list of sponsors willing to accept new sponsoree.
>>> And list area of expertise of sponsors (e.g. java, python, IoT...). This
>>> will make for sponsoree easier to find right sponsor. Because we have some
>>> sponsors, who are active but are not willing to accept new sponsoree right
>>> now.
>>
>> This can be in addition to above, Why not run a script frequently and
>> check bugzilla and based on common naming CC the related SIG group?
>> e.g. if a package review is submitted whose name contains python then
>> add cc python SIG group that will notify actual group people and
>> someone can find interest and review the package. I know this is in
>> general suggestion but I suppose every SIG is also having some
>> Sponsors who can sponsor new contributor packages.
>
> This won't work for all SIGs. For example, Java packages don't have any
> common naming scheme. If you just search for "Java" in review requests,
> almost all results will be false-positives (eg. from "JavaScript") and
> you won't find most of relevant reviews this way.
>
> I think that wiki page could work for this purpose.

Right not for all SIGs but at least for those where its possible. Just
see there are many such common pattern named packages are waiting in
queue for their package review. I can think of some patterns like
perl, python, golang, nodejs, ruby, ghc, mingw, php etc.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Pending ACLs

[Parag Nemade]

Hi,

On Sat, Aug 6, 2016 at 11:07 PM,   wrote:
> Sometimes a maintainer doesn't want to approve ACLs for "reasons" but
> doesn't want to reject the request for various reasons including the
> requestor re-request of denied requests.
>

To add few things here,

1) Why do we need such "Pending ACLs" weekly emails? The package owner
already gets notifications when someone requests ACLs. Now if you say
people forgets then why not implement something in pkgdb only which
will keep sending weekly notification again to package owners that
someone has requested ACLs on their packages? What benefit will others
get by reading these emails that someone requested ACLs on some
package and its owner still not approving?

2) Sometime back I don't remember if I filed issue against pkgdb but I
discussed on IRC why not add some text entry box while requesting
ACLs. Not everyone knows everyother one here. Let the package owner
know why the ACL requestor need other package access. That will help
package owners to decide to approve or deny quickly. There can be some
people who want to have access/co-maintainer for some packages where
they really not needed to be.

3) I am not sure but I think there is some automation for something in
pkgdb which automatically grants package access to requstor if package
owner do not take action. Correct me if I am wrong here.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Improvements of Fedora Sponsorship process

[Parag Nemade]

Hi,

On Fri, Aug 5, 2016 at 1:02 PM, Miroslav Suchý  wrote:
> I had the talk [1] about Fedora Sponsorship process at Flock. And we had
> very interesting follow-up discussion.
>
> We come up with several improvements, which should be easy to implement and
> may improve the process a lot. I am posting it here so more people can see
> that and join the discussion.
>
> a) Sponsoree (who apply for package maintainer status) is required to create
> Copr project and maintain the package there until he get the package into
> Fedora. This should show his endurance to sponsors. It will improve the
> morale of the sponsoree as the package is immediately ready for other users.
> And it is not wiped after 14 days as scratch builds in Koji.

Few package submitter are using this currently, it will be good
improvement for new contributors to use Copr.

>
> b) fedora-review is run automatically by some bot/script just after review
> have been submitted.

 Can a new utility be written for this as I don't think that long
fedora-review output is helpful? Most checks have no markings in them.
How can it be helpful to package submitter?

> c) Create wiki page with list of sponsors willing to accept new sponsoree.
> And list area of expertise of sponsors (e.g. java, python, IoT...). This
> will make for sponsoree easier to find right sponsor. Because we have some
> sponsors, who are active but are not willing to accept new sponsoree right
> now.

This can be in addition to above, Why not run a script frequently and
check bugzilla and based on common naming CC the related SIG group?
e.g. if a package review is submitted whose name contains python then
add cc python SIG group that will notify actual group people and
someone can find interest and review the package. I know this is in
general suggestion but I suppose every SIG is also having some
Sponsors who can sponsor new contributor packages.

>
> d) When sponsors is not active for 2 years [*] - that means not just in
> sponsoring work, but there is no activity in BZ, koji, wiki and any other
> Fedora service at all (guessed by reading log of fedmsg), then his sponsor
> status is removed. We will assume that the sponsor is gone for good.

Well good information for other people or FESCo to take action and
orphan their packages as well ;-)

>
> e) When the package review is still not assigned to anybody after 3 months
> [*], then 3 [*] random sponsors are added to CC and asked to proceed with
> the review despite the fact that it likely doesn't belong to their area of
> expertise. This should helps us to get rid of stalled review, which are
> waiting for ages to get some sponsor.

Was there any discussion on what to do with existing stalled package
reviews? I think we should go and close stalled reviews where there is
no update from package review submitter for last six months at least.
Those where reviewer is not progressing, just remove the assignee and
any fedora-review? flag. The review queue I am considering here is
FE-NEEDSPONSOR queue and "tickets under review" queue.

> Those are the ideas which came up at Flock. Please comment this. And if we
> come to some conclusion, I can pass it to FeSCo for approval.
>
> [1] http://miroslav.suchy.cz/presentations/flock2016/sponsors/#/
>
>   Please note that the data in this presentation is based only on data I
> was able to gather and I am aware the it does not reflect 100% the reality.
> But it approximately gives us the order of magnitude of the reality and
> approximately ratio.
>
> [*] I just made up this number. Feel free to discuss appropriate interval.
>

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: finish retirement of sysvinit-only packages Re: Schedule for Friday's FESCo Meeting (2016-07-29)

[Parag Nemade]

Hi,

On Sun, Jul 31, 2016 at 10:53 AM, Sérgio Basto  wrote:
> On Sáb, 2016-07-30 at 22:29 -0600, Kevin Fenzi wrote:
>> On Sun, 31 Jul 2016 04:18:18 +0100
>> Sérgio Basto  wrote:
>>
>> >
>> > why we need retire sysvinit-only packages ?
>> Because they have had 10+ releases to adjust and haven't.
>>
>> >
>> > is not suppose systemd
>> > support sysvinit and why don't you fixed the packages like you will
>> > do
>> > for nagios ?
>> systemd does support sysvinit scripts, but it's a good deal less
>> optimal than a native systemd unit file for lots of reasons.
>>
>> nagios has a systemd unit file. It was setup/enabled in 2013, but
>> recent spec file changes caused it to ship the old sysvinit script
>> instead. Thats just a bug.
>>
>> >
>> > BTW I'd like keep 2 packages noip and tetrinetx.
>> > Shouldn't you give some time or open bug reports before do the
>> > retirement ?
>> >
>> > why such hurry ?
>> The orig ticket ( https://fedorahosted.org/fesco/ticket/615 ) was
>> opened 5 years ago.
>>
>> 9 months ago an announcement was made:
>> https://lists.fedoraproject.org/archives/list/devel-annou...@lists.fe
>> doraproject.org/thread/3XJN6JZ4S7SOG2KH2UT3GYY4K7LAJGGU/
>>
>> Then another 6 months ago:
>> https://lists.fedoraproject.org/archives/list/devel-announce%40lists.
>> fedoraproject.org/thread/ULPGRGI3OBFXWZISXRIX2S3Z35RBCMBN/
>>
>> We could keep putting it off, but it's had a long long ramp.
>
> But is so easy do the units files why you just don't add it ? it more
> work for volunteers, like me, now I will add 2 more packages just
> because nobody updates the initd :/

Kevin has already given a detailed information how longer it took to
retire these packages. Also see this
https://fedoramagazine.org/systemd-converting-sysvinit-scripts/

> OK maybe you are right, but maybe you may think in save work to
> volunteers, it is too many things, I think.

Why it is too many things? If you are a packager maintainer then you
need to follow the current development happening in Fedora. If
something is getting replaced by something else and your package is a
candidate of that change then I think its the maintainer's
responsibility also to make sure his/her package works with the
current development Changes.

> It is to get a better Fedora that we try keep the packages. If they
> still work, why not ? Even we have FTBFS you may help out or add
> appdata or even have people to migrate some software for example gtk2
> -> gtk3, SDL1 -> SDL2 , qt3 -> qt4 -> qt5 etc etc, teams that knows ,
> what are obsolete like asound or gnome2-vfs (this one is a guess). I
> think, have some people that can keep some software alive, will save
> much resources.


> Also I think this pre-alpha window is too small, I'd like have a bigger
> pre-alpha window, many things happens at same time, I think we should
> have more time between tasks and before branching. For example closing
> F22, I got lost of emails to check, at same time, happens mass rebuild
> of python, some soname bumps which may imply rebuilds, if not worst,
> and everything before branching. This tasks shouldn't be done almost at
> same time because volunteers will have many things to do at same time,
> IMHO.

Well, Fedora Project is a collaborative work. All teams need to work
together we can't stop releng from branching or FPM to stop closing
F22 bugs. Every participating team has their own work that need to be
carried within particular timeframe otherwise we will blocking each
other and endup with longer development cycle. Mass-rebuilds for any
Change is carried mostly by releng team or Change owners. All these
tasks are carried according to the that current Fedora development
schedule.

Regards,
Parag
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Fedora 25 Mass Branching

[Parag Nemade]

Hi,

On Wed, Jul 27, 2016 at 11:31 AM, Igor Gnatenko  wrote:
> I can't submit update in bodhi as it doesn't look for f25* tags.
>
> Builds : Invalid tag: scudcloud-1.31-1.fc25 tagged with
> [u'f24-updates-candidate', u'f22-updates-candidate',
> u'epel7-testing-candidate', u'dist-6E-epel-testing-candidate',
> u'dist-5E-epel-testing-candidate', u'f23-updates-candidate',
> u'f21-updates-candidate']
>
> On Tue, Jul 26, 2016 at 10:00 PM, Peter Robinson  wrote:
>> Hi All,
>>
>> Fedora 25 has now been branched, please be sure to do a git pull
>> --rebase to pick up the new branch, as an additional reminder
>> rawhide/f26 has been completely isolated from previous releases, so
>> this means that anything you do for f25 you also have to do in the
>> master branch and do a build there. There will be a Fedora 25 compose
>> ASAP and it'll appear
>> http://dl.fedoraproject.org/pub/fedora/linux/development/25/ once
>> complete. Please be sure to check it out.
>>


Please see Fedora 25 schedule [1] which shows bodhi will be enabled on
9th August.

Regards,
Parag

[1] https://fedoraproject.org/wiki/Releases/25/Schedule
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Retired dnf-langpacks in rawhide

[Parag Nemade]

Hi,
   Last release we implemented[1] new way of installing langpacks
packages using RPM's weak dependency feature. Therefore, I would like
to retire dnf langpacks plugin package called dnf-langpacks in
rawhide(f25+).

   Those who still want to know what is current way of installing
language packages please check this test case page[2].

   I have also submitted a pull request for fedora-comps to remove
dnf-langpacks package from "standard" as well as "workstation-product"
group.

Thanks.
Parag.

[1] 
https://fedoraproject.org/wiki/Changes/LangpacksInstallationWithRPMWeakDependencies
[2] https://fedoraproject.org/wiki/QA:Testcase_langpacks_packages
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Package Reviews Statistics

[Parag Nemade]

Hi,

On Mon, Jul 11, 2016 at 7:05 PM, Igor Gnatenko  wrote:
> On Mon, Jul 11, 2016 at 3:18 PM, Raphael Groner
>  wrote:
>> Can that information be used to award badges? There's an old open issue to 
>> implement badges for doing package reviews. Maybe get in contact with the 
>> badges team.
>> https://fedorahosted.org/fedora-badges/ticket/101
>
> whoa! would be happy to get some number of badges for this ;)

But this will not be a perfect thing. sometimes people make mistakes
and reset the flags so there are chances for other people to set the
fedora-review+ flag back and get the +1 fedmsg count as package
reviewed.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Package Reviews Statistics

[Parag Nemade]

Hi,

On Mon, Jul 11, 2016 at 3:00 PM, Igor Gnatenko  wrote:
> For me would be better some page with stats/links to weekly status,
> monthly status, yearly status and some nice graphics ;)
>
> On Mon, Jul 11, 2016 at 11:18 AM, Michal Novotny  wrote:
>> Hello,
>>
>> as a new Fedora Infrastructure apprentice, I am currently working on this
>> first infrastructure ticket
>> https://fedorahosted.org/fedora-infrastructure/ticket/3748.
>>
>> Basically, I updated an old script that collects stats on packages reviews
>> present on Bugzilla. I wonder if this information could actually be useful
>> (or at least interesting) to some people and if weekly automated updates (as
>> described in the ticket) are worth the effort :).
>>
>> To find this out, I ran the script manually to show you what kind of
>> information it provides. There are two different kind of stats the script
>> can collect - completed and in-progress reviews.
>>
>> 1) below are completed reviews (fedora-review+) from the last week + the
>> reviewers that approved the package + links and the package names
>>
>> Start Date: 2016-07-04 10:37:41.533674
>> End Date: 2016-07-11 10:37:41.533674
>>
>> punto...@libero.it : 4
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1352667licensecheck
>> https://bugzilla.redhat.com/show_bug.cgi?id=1352666
>> perl-Pod-Constants
>> https://bugzilla.redhat.com/show_bug.cgi?id=1331589multibit-commons
>> https://bugzilla.redhat.com/show_bug.cgi?id=1347987pasystray
>>
>>
>> ignate...@redhat.com : 3
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1352993python-args
>> https://bugzilla.redhat.com/show_bug.cgi?id=1352996python-zipstream
>> https://bugzilla.redhat.com/show_bug.cgi?id=1354184qhttpengine
>>
>>
>> tcall...@redhat.com : 2
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1317282bspwm
>> https://bugzilla.redhat.com/show_bug.cgi?id=1050744belle-sip
>>
>>
>> t...@compton.nu : 2
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1273526nodejs-tracejs
>> https://bugzilla.redhat.com/show_bug.cgi?id=1279127nodejs-each
>>
>>
>> admil...@redhat.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1308480wlc
>>
>>
>> anto.tra...@gmail.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1335278mame
>>
>>
>> athma...@gmail.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1349575python-multidict
>>
>>
>> jarodwil...@gmail.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1350029libi40iw
>>
>>
>> jar...@redhat.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1351575
>> rubygem-mime-types-data
>>
>>
>> lkund...@v3.sk : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1302876clatd
>>
>>
>> loganje...@gmail.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1335988giac
>>
>>
>> l...@redhat.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1333533bubblewrap
>>
>>
>> lupi...@mailbox.org : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1306353libunity
>>
>>
>> manisan...@gmail.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1346382picketlink
>>
>>
>> msima...@redhat.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1353572HikariCP
>>
>>
>> msu...@redhat.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1353469
>> python-marshmallow-enum
>>
>>
>> projects...@smart.ms : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1321687qpid-java
>>
>>
>> rdie...@math.unl.edu : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1270322chromium
>>
>>
>> williamjmore...@gmail.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1351097
>> python-uritemplate
>>
>>
>>
>> Total reviews modified: 26
>> Merge Reviews: 0
>> Review Requests: 26
>> This report by generated by bzReviewReport.py.
>> The source is available at:
>> https://fedorahosted.org/triage/browser/scripts/bzReviewReport.py
>> Please submit patches or bug reports at: https://fedorahosted.org/triage/
>>
>>
>> 2) below are in-progress reviews (fedora-review?) from the last week + the
>> reviewers that flagged the review with "?" + links and the package names
>>
>> start date: 2016-07-04 10:44:01.887148
>> end date: 2016-07-11 10:44:01.887148
>>
>> ignate...@redhat.com : 3
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1354202purple-hangouts
>> https://bugzilla.redhat.com/show_bug.cgi?id=1352408lasem
>> https://bugzilla.redhat.com/show_bug.cgi?id=1323214git-evtag
>>
>>
>> admil...@redhat.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1308561sway
>>
>>
>> athma...@gmail.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1324667python-locket
>>
>>
>> heg...@gmail.com : 1
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1347973
>> aries-blueprint-api
>>
>>
>> mizde...@redhat.com : 1
>>
>> 

Re: Too fast karma on Bodhi updates

[Parag Nemade]

Hi,

On Mon, Jul 11, 2016 at 2:19 PM, Kamil Paral  wrote:
>> Any kind of feedback after package gets into updates repository should
>> be denied, I can't think of a case where package moves to updates
>> repository and bodhi still allows to add comments/karma. Any feedback
>> after that can be either reported in bugzilla or to the package
>> maintainers directly. Its not like providing positive or negative
>> karma will make any changes to already pushed package to updates
>> repository.
>
> I do have valid use cases. We've had examples of important packages having 
> been pushed stable too quickly and breaking some computers (think kernel, 
> mesa). The bodhi comments can then be used to provide a description of the 
> problem, suggest any workarounds or fixes, and also link to more information 
> e.g. in the bugzilla or common bugs wiki, etc. The Bodhi pages are easy to 
> find (if I perform a system update and the computer breaks, I look at what 
> was included in the last update, and look at any bodhi feedback for those 
> packages), so it makes perfect sense to inform people there. It's much harder 
> to search bugzilla to find issues with a particular package.

In this case its better to disable karma and just let users provide
feedback. Its really annoying to get just +1 karma on your package
when that package is already stable.

>
> So, the ability to comment post-push should remain. However, it would make 
> sense to tweak email notifications somewhat (so that everyone is not spammed 
> with each new comment long after the package is pushed stable). That's what I 
> assume annoys people.
> --
> devel mailing list
> devel@lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Too fast karma on Bodhi updates

[Parag Nemade]

Hi,

On Mon, Jul 11, 2016 at 12:26 PM, Ville Skyttä  wrote:
> On Mon, Jul 11, 2016 at 9:37 AM, Raphael Groner
>  wrote:
>
>> Why is it possible to give +1 to stable packages? Bodhi may deny or at least 
>> impede such actions, -1 or neutral comments should be still possible though 
>> for users having issues.
>
> I disagree with allowing -1. At best, it's meaningless after a package
> is in stable, and may actually cause problems through confusion.
>
> I think disallowing *any* kind of comments after a package is in
> stable would be ok -- the comment field could be replaced with a link
> that points to a Bugzilla form prepopulated with the correct product,
> component, version, and a link to the update in the description.


Any kind of feedback after package gets into updates repository should
be denied, I can't think of a case where package moves to updates
repository and bodhi still allows to add comments/karma. Any feedback
after that can be either reported in bugzilla or to the package
maintainers directly. Its not like providing positive or negative
karma will make any changes to already pushed package to updates
repository.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2016-07-01)

[Parag Nemade]

===
#fedora-meeting: FESCO (2016-07-01)
===


Meeting started by paragan at 16:01:02 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-07-01/fesco.2016-07-01-16.01.log.html
.



Meeting summary
---
* init process  (paragan, 16:01:02)

* Next week's chair  (paragan, 16:11:17)
  * jsmith will chair for next week meeting (2016-07-08)  (paragan,
16:13:26)

* Open Floor  (paragan, 16:13:55)
  * no quorum today, postpone meeting to next week  (paragan, 16:14:48)

Meeting ended at 16:15:41 UTC.


Action Items



Action Items, by person
---
* **UNASSIGNED**
  * (none)


People Present (lines said)
---
* paragan (19)
* zodbot (8)
* jsmith (7)
* kalev (3)
* number80 (2)
* sgallagh (0)
* nirik (0)
* jwb (0)
* maxamillion (0)
* dgilmore (0)


Generated by `MeetBot`_ 0.1.4
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Schedule for Friday's FESCo Meeting (2016-07-01)

[Parag Nemade]

Hi,

On Fri, Jul 1, 2016 at 7:54 PM, Josh Boyer <jwbo...@fedoraproject.org> wrote:
> On Fri, Jul 1, 2016 at 4:08 AM, Parag Nemade <panem...@gmail.com> wrote:
>>
>> #topic #1592 Redefinition of what constitutes a secondary/alternate
>> architecture in Fedora
>> .fesco 1592
>> https://fedorahosted.org/fesco/ticket/1592
>
> I honestly don't think this is ready for a meeting yet.  While I'm
> mostly in support of it, the proposal needs more discussion both in
> the ticket and very likely on this list.  It is absolutely not ready
> to be voted on.

I agree with you but as ticket was filed with meeting keyword and
having only 2 easy tickets on Agenda, I thought to pick this and see
if we can discuss it a bit. I can see its not ready for voting.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-07-01)

[Parag Nemade]

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-07-01 16:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #1568 F25 Self Contained Changes
.fesco 1568
https://fedorahosted.org/fesco/ticket/1568

= New business =

#topic #1590 F25 System Wide Change: GHC 7.10
.fesco 1590
https://fedorahosted.org/fesco/ticket/1590

#topic #1592 Redefinition of what constitutes a secondary/alternate
architecture in Fedora
.fesco 1592
https://fedorahosted.org/fesco/ticket/1592


= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Changes to the scm-commits list

[Parag Nemade]

Hi Kevin,

On Thu, Jun 23, 2016 at 3:08 AM, Kevin Fenzi  wrote:
> Greetings.
>
> In the past the scm-commits list:
> https://lists.fedoraproject.org/archives/list/scm-comm...@lists.fedoraproject.org
>
> Contained not only git commit messages for packages and notification of
> uploads to lookaside cache, but also all changes in pkgdb acls.
>
> The volume of emails from pkgdb acl changes can be very high, and this
> prevented people from being able to use the scm-commits list as a way
> to review commits.
>
> In order to mitigate this problem, we have now created a new list:
> https://lists.fedoraproject.org/archives/list/scm-notificati...@lists.fedoraproject.org
> that will now get all pkgdb acl changes. The scm-commits list will
> continue to get commit messages and notification of source uploads
> only.
>
> We hope this change will help everyone more easily get the information
> they wish.


Thank you very much. I have been waiting for this change to happen for
scm-commits list since long time.

There are also some other kind of messages which generates lots of
notification emails like Koschei flag, pkgdb_updater script,
monitoring a package. Can some of them be moved to scm-notifications
list?

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: provenpackager request: fix keepassx for f24

[Parag Nemade]

Hi,

On Thu, Jun 9, 2016 at 8:43 AM, Andrew Lutomirski  wrote:
> See:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1338054
>
> Pushing a reasonable version of keepassx for f24 is apparently an accepted
> freeze exception, but it hasn't happened.  It would be rather unfortunate if
> f24 final was released before this was dealt with.
>
> Since fixing this is as simple as creating a bodhi update, can a
> provenpackager just do it, please?

The keepassx0 package review is approved already so I have requested
f24+ branches in pkgdb. I will wait for original package submitter to
build this package once its branches are created. Otherwise I can
build it tomorrow.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2016-05-27)

[Parag Nemade]

===
#fedora-meeting: FESCO (2016-05-27)
===


Meeting started by paragan at 16:01:04 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-05-27/fesco.2016-05-27-16.01.log.html
.



Meeting summary
---
* init process  (paragan, 16:01:04)

* #1568  F25 Self Contained Changes  (paragan, 16:04:15)
  * LINK: https://fedorahosted.org/fesco/ticket/1568   (paragan,
16:04:15)
  * AGREED: Approved all 3 Self Contained Changes (8, 0, 0)  (paragan,
16:08:58)

* #1573 Docker Layered Image maintainer guildelines, naming guidelines
  and review  (paragan, 16:09:18)
  * LINK: https://fedorahosted.org/fesco/ticket/1573   (paragan,
16:09:19)
  * AGREED: revisit this ticket next week.  (paragan, 16:19:05)

* #1576 Evaluate Workstation graphical upgrade Change status  (paragan,
  16:19:26)
  * LINK: https://fedorahosted.org/fesco/ticket/1576   (paragan,
16:19:26)
  * AGREED: tenative plan is to have this change implemented on release
day and update it monday with further details and revisit this
ticket next meeting (6, 0, 0)  (paragan, 16:31:25)

* #1578 F25 System Wide Change: Use /etc/repos.d as default reposdir
  (paragan, 16:31:50)
  * LINK: https://fedorahosted.org/fesco/ticket/1578   (paragan,
16:31:50)
  * AGREED: revisit this ticket next week so that kalev-afk can get
feedback on this  (paragan, 16:43:56)

* #1579 F25 System Wide Change: Parallel Installable Debuginfo
  (paragan, 16:44:25)
  * LINK: https://fedorahosted.org/fesco/ticket/1579   (paragan,
16:44:26)
  * AGREED: F25 System Wide Change: Parallel Installable Debuginfo (8,
0, 0)  (paragan, 16:47:19)

* Next week's chair  (paragan, 16:48:03)
  * kalev to chair for next week meeting  (paragan, 16:49:05)

* Open Floor  (paragan, 16:49:18)

Meeting ended at 16:55:28 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* paragan (63)
* nirik (32)
* kalev-afk (30)
* maxamillion (26)
* dgilmore (26)
* zodbot (17)
* sgallagh (16)
* jsmith (13)
* number80 (3)
* kalev (0)
* jwb (0)




Generated by `MeetBot`_ 0.1.4
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-05-27)

[Parag Nemade]

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-05-27 16:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #1568 F25 Self Contained Changes
.fesco 1568
https://fedorahosted.org/fesco/ticket/1568

#topic #1573 Docker Layered Image maintainer guildelines, naming
guidelines and review
.fesco 1573
https://fedorahosted.org/fesco/ticket/1573

#topic #1576 Evaluate Workstation graphical upgrade Change status
.fesco 1576
https://fedorahosted.org/fesco/ticket/1576

= New business =

#topic #1578 F25 System Wide Change: Use /etc/repos.d as default reposdir
.fesco 1578
https://fedorahosted.org/fesco/ticket/1578

#topic #1579 F25 System Wide Change: Parallel Installable Debuginfo
.fesco 1579
https://fedorahosted.org/fesco/ticket/1579

= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
--
devel mailing list
devel@lists.fedoraproject.org
https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Summary/Minutes for today's FESCo meeting (2016-05-20)

[Parag Nemade]

===
#fedora-meeting: FESCO (2016-05-20)
===


Meeting started by paragan at 16:00:27 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-05-20/fesco.2016-05-20-16.00.log.html
.



Meeting summary
---
* init process  (paragan, 16:00:27)
  * Cancelled today's meeting due to lack of quorum  (paragan, 16:10:27)
  * paragan to chair next week meeting  (paragan, 16:10:42)

Meeting ended at 16:11:35 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* paragan (13)
* zodbot (6)
* dgilmore (3)
* nirik (1)
* jwb (1)
* sgallagh (0)
* kalev (0)
* number80 (0)
* jsmith (0)
* maxamillion (0)




Generated by `MeetBot`_ 0.1.4
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-05-20)

[Parag Nemade]

Following is the list of topics that will be discussed in the FESCo
meeting Friday at 16:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-05-20 16:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #1444 updates deliverables
.fesco 1444
https://fedorahosted.org/fesco/ticket/1444

#topic #1568  F25 Self Contained Changes
.fesco 1568
https://fedorahosted.org/fesco/ticket/1568

#topic #1576 Evaluate Workstation graphical upgrade Change status
.fesco 1576
https://fedorahosted.org/fesco/ticket/1576

= New business =

#topic #1578 F25 System Wide Change: Use /etc/repos.d as default reposdir
.fesco 1578
https://fedorahosted.org/fesco/ticket/1578

= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: F25 System Wide Change: Use /etc/distro.repos.d as default reposdir

[Parag Nemade]

Hi,

On Thu, May 12, 2016 at 1:06 PM, Jan Kurik  wrote:
> = Proposed System Wide Change: Use /etc/distro.repos.d as default reposdir =
> https://fedoraproject.org/wiki/Changes/ReposInEtcDistroReposD
>
> Change owner(s):
> * Neal Gompa 
> * Jan Silhan 
>
>
> == Detailed Description ==
> For DNF 2.0 in Fedora 25, the DNF team would like to make the default
> repository configuration directory /etc/distro.repos.d. In contrast to
> /etc/yum.repos.d (current default path), /etc/distro.repos.d path is a
> package manager agnostic name and less misleading. The configuration
> files are currently used by DNF, PackageKit, and Yum. The proposed
> location more accurately reflects the nature of the repositories, and
> also implies that other tools can look there for repository
> information. Note: current default repository configuration directory
> /etc/yum.repos.d will still be supported by package managers but
> /etc/distro.repos.d would be preferred default path.
>

I will suggest /etc/package.repos.d that way we can be more neutral in
having repos directory using various different packaging formats.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Orphaned Packages in branched (2016-05-03)

[Parag Nemade]

Hi,

2016-05-03 21:53 GMT+05:30  :
> The following packages are orphaned and will be retired when they
> are orphaned for six weeks, unless someone adopts them. If you know for sure
> that the package should be retired, please do so now with a proper reason:
> https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life
>
> Note: If you received this mail directly you (co)maintain one of the affected
> packages or a package that depends on one. Please adopt the affected package 
> or
> retire your depending package to avoid broken dependencies, otherwise your
> package will be retired when the affected package gets retired.
>
>   Package(co)maintainers  Status Change
> ===
> nodejs-handlebars  orphan, group::nodejs-sig, 1 weeks ago
>mayorga, piotrp
>
> The following packages require above mentioned packages:
> Depending on: nodejs-handlebars (24), status change: 2016-04-26 (1 weeks ago)
> nodejs-istanbul (maintained by: piotrp, group::nodejs-sig)
> nodejs-istanbul-0.4.0-2.fc24.noarch requires npm(handlebars) 
> = 4.0.5
> nodejs-istanbul-0.4.0-2.fc24.src requires npm(handlebars) = 
> 4.0.5
>
> php-Assetic (maintained by: siwinski, jhogarth)
> php-Assetic-1.3.2-3.fc24.src requires npm(handlebars) = 4.0.5
>
> python-webassets (maintained by: kumarpraveen, dcallagh, pjp)
> python-webassets-0.10.1-5.fc24.src requires 
> /usr/bin/handlebars
>
> nodejs-camel-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-camel-case-1.2.0-2.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-change-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-change-case-2.3.0-2.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-constant-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-constant-case-1.1.1-2.fc24.src requires npm(istanbul) 
> = 0.4.0
>
> nodejs-dot-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-dot-case-1.1.1-3.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-error-ex (maintained by: pnemade, group::nodejs-sig)
> nodejs-error-ex-1.3.0-3.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-is-arrayish (maintained by: pnemade, group::nodejs-sig)
> nodejs-is-arrayish-0.3.0-1.fc24.src requires nodejs-istanbul 
> = 0.4.0-2.fc24
>
> nodejs-is-lower-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-is-lower-case-1.1.1-3.fc24.src requires npm(istanbul) 
> = 0.4.0
>
> nodejs-is-upper-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-is-upper-case-1.1.1-3.fc24.src requires npm(istanbul) 
> = 0.4.0
>
> nodejs-lower-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-lower-case-1.1.2-3.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-lower-case-first (maintained by: piotrp, group::nodejs-sig)
> nodejs-lower-case-first-1.0.0-2.fc24.src requires 
> npm(istanbul) = 0.4.0
>
> nodejs-native-or-bluebird (maintained by: pnemade, group::nodejs-sig)
> nodejs-native-or-bluebird-1.2.0-3.fc24.src requires 
> npm(istanbul) = 0.4.0
>
> nodejs-param-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-param-case-1.1.1-3.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-pascal-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-pascal-case-1.1.1-2.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-path-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-path-case-1.1.1-3.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-sentence-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-sentence-case-1.1.2-3.fc24.src requires npm(istanbul) 
> = 0.4.0
>
> nodejs-snake-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-snake-case-1.1.1-3.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-swap-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-swap-case-1.1.1-2.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-title-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-title-case-1.1.1-2.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-upper-case (maintained by: piotrp, group::nodejs-sig)
> nodejs-upper-case-1.1.2-3.fc24.src requires npm(istanbul) = 
> 0.4.0
>
> nodejs-upper-case-first (maintained by: piotrp, group::nodejs-sig)
> nodejs-upper-case-first-1.1.1-2.fc24.src requires 
> npm(istanbul) = 0.4.0
>
> nodejs-vow-fs (maintained by: group::nodejs-sig)
> 

Summary/Minutes for today's FESCo meeting (2016-04-08)

[Parag Nemade]

===
#fedora-meeting: FESCO (2016-04-08)
===


Meeting started by paragan at 17:00:07 UTC. The full logs are available
at
https://meetbot.fedoraproject.org/fedora-meeting/2016-04-08/fesco.2016-04-08-17.00.log.html
.



Meeting summary
---
* init process  (paragan, 17:00:07)

* #1518 Software packaged in Fedora should not be allowed to implement
  DRM schemes that cannot be disabled  (paragan, 17:03:11)
  * LINK: https://fedorahosted.org/fesco/ticket/1518   (paragan,
17:03:12)
  * AGREED: FESCo asserts that Firefox in its current incarnation meets
its standard for Free Software for inclusion in Fedora. Other
packages may be proposed on a case-by-case basis (5, 0, 0)
(paragan, 17:11:47)

* #1565 Fedora schedule must continue to track core library ABI or risk
  serious ABI implications  (paragan, 17:13:32)
  * LINK: https://fedorahosted.org/fesco/ticket/1565   (paragan,
17:13:33)
  * AGREED: Fedora Schedule should always schedule mass rebuilds (if
needed) after glibc final freeze. (5, 1, 0)  (paragan, 18:12:30)
  * LINK: https://fedoraproject.org/wiki/Fedora_Release_Life_Cycle
(nirik, 18:20:41)

* Next week's chair  (paragan, 18:28:46)
  * nirik to chair next week meeting  (paragan, 18:30:10)

* Open Floor  (paragan, 18:30:22)

Meeting ended at 18:34:44 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* sgallagh (94)
* dgilmore (71)
* paragan (65)
* codonell (61)
* nirik (34)
* number80 (19)
* zodbot (13)
* maxamillion (7)
* kalev (0)
* jwb (0)
* jsmith (0)

Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Schedule for Friday's FESCo Meeting (2016-04-08)

[Parag Nemade]

Hi,
   Please note that I feel only one ticket is there in this week that
need discussion. If any other existing open ticket need to be
discussed then we can discuss that in the meeting but I am adding only
one new ticket on the Agenda of this meeting.


Following is the list of topics that will be discussed in the FESCo
meeting Friday at 17:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2016-04-08 17:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= New business =

#topic #1565 Fedora schedule must continue to track core library ABI
or risk serious ABI implications
.fesco 1565
https://fedorahosted.org/fesco/ticket/1565

= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: glibc in Fedora rawhide now split by langpacks.

[Parag Nemade]

Hi,

On Fri, Feb 26, 2016 at 8:54 PM, Richard Hughes <hughsi...@gmail.com> wrote:
> On 26 February 2016 at 13:25, Parag Nemade <panem...@gmail.com> wrote:
>> Please have a look at New Langpacks Change[1] information.
>
> Thanks for the information -- this looks a lot better than the current
> logic and so a huge thanks for driving this. One more question: Would
> you be against me adding (translated) metainfo files to each of the
> langpack subpackages? This would allow me to add support in GNOME
> Software very easily without any hacky code. I'm happy doing the work
> if this sounds acceptable to you.

I am fine with you adding metainfo files to langpacks.spec file.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: glibc in Fedora rawhide now split by langpacks.

[Parag Nemade]

Hi Richard,

On Fri, Feb 26, 2016 at 5:55 PM, Richard Hughes  wrote:
> On 26 February 2016 at 09:47, Carlos O'Donell  wrote:
>> We have over 180 supported languages
>> in glibc, and those have been split into langpacks
>> for transparent install and support via dnf.
>
> What happens if the user isn't using DNF? For the workstation we have
> to support users using just the graphical tools, and we can't rely on
> command line tools for this kind of thing. I'm happy to add support
> for installing lang packs into gnome-software but need to know how the
> langpack plugin works so we can add proper support into the AppStream
> metadata file. The idea being if the user changes the per-session
> language we install the required langpacks automatically.
>
> Can someone explain how the dnf langpack plugin gets the data on what
> application subpackages to install? It would be easy if we could have
> a virtual package that we could install for each locale as then we can
> just put the metainfo file there for easy support in gnome-software.

Please have a look at New Langpacks Change[1] information. With this
change we are trying to remove the need of having dnf langpacks
plugin. The basic required things are already in F24+ but I have not
yet got time to add weak dependencies in all the required langpacks.
But I have modified basic required langpacks like hunspell, hyphen,
mythes. Then libreoffice, kde-l10n, gnome-getting-started-docs and
tesseract has been also built for this new langpacks change. I do have
created test page[2] for this new change.

I suppose all the langpacks changes will be complete by next week.
Please note that I specifically requested Workstation WG to add
dnf-langpacks package in comps but later on we decided to use weak
dependencies for langpacks. Now users need to just install
meta-packages like langpacks- to get all the required
langpacks installed on the system. If needed we can remove
dnf-langpacks from Fedora Workstation installation but I will say
better wait till Fedora 24 Alpha release and see if new langpacks
implementation has worked fine by that time.

Regards,
Parag

[1] 
https://fedoraproject.org/wiki/Changes/LangpacksInstallationWithRPMWeakDependencies
[2] https://fedoraproject.org/wiki/QA:Langpacks
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: glibc in Fedora rawhide now split by langpacks.

[Parag Nemade]

Hi,

On Fri, Feb 26, 2016 at 3:52 PM, Carlos O'Donell  wrote:
> On 02/26/2016 04:47 AM, Carlos O'Donell wrote:
>> The glibc in Fedora rawhide and F24 is now split by
>> language packs. We have over 180 supported languages
>> in glibc, and those have been split into langpacks
>> for transparent install and support via dnf. This
>> greatly reduces the size of a glibc install from 130MB
>> down to a couple of megs. It drops support for the hacky
>> %_inst_langs feature, and relies entirely on langpack
>> support (it was one or the other).
>
> Unfortunately we missed a piece of the puzzle here.
>
> Bug 1303034 - rpm macro expansion works incorrectly
>   when looping over a long list using lua
> https://bugzilla.redhat.com/show_bug.cgi?id=1303034
>
> We need this fixed in F24 and pushed into the buildroots
> to unblock building glibc.

I thought this is already fixed in F24. At least I remember I tested
langpacks glibc.spec from mfabian's some old private git repository on
F24 machine. The rpm build I tested was rpm-4.13.0-0.rc1.23.fc24. But
now I see that f24 glibc is failing while comparing the SUPPORTED file
in %prep.


Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

[EPEL-devel] Re: Mass rebuild of EPEL6 (2016-01-19)

[Parag Nemade]

Hi,

On Wed, Jan 20, 2016 at 9:46 AM, Jason L Tibbitts III  wrote:
> After spending far too much time playing with my mass rebuild script,
> and a whole lot of CPU time building packages, I've done another mass
> rebuild of EPEL6.  This involves an initial build of EPEL6 (with
> testing), another three builds of any failing packages, and then a final
> build of the current git of each failed package.  Packages which are
> excluded on x86_64 were skipped.
>
> The following packages are skipped because they take absolutely forever
> to build:
>
> elpa - Still building after two days on a rather fast machine!
> nwchem
> pypy
>
> This one's test suite appears to simply hang forever:
>
> rubygem-eventmachine
>
> Missing dependencies:
>
> dinotrace
> erlang-erlsom
> erlang-ibrowse
> freecad
> golang-github-endophage-gotuf
> golang-github-go-ldap-ldap
> golang-github-gonum-blas
> golang-github-gonum-floats
> golang-github-gorilla-sessions
> golang-github-hashicorp-serf
> golang-github-lsegal-gucumber
> golang-github-prometheus-client_golang
> golang-github-spf13-cast
> golang-github-spf13-viper
> gpredict
> jmtpfs
> nodejs-ascii-tree
> nodejs-duplexify
> nodejs-nsp-audit-shrinkwrap
> nodejs-nth-check
> nodejs-rc
> nodejs-registry-url
> nodejs-seq
> nodejs-silent-npm-registry-client
> nodejs-stream-spigot
> nodejs-test

I checked all above nodejs packages. I have already pushed
(epel-testing) most of them by replacing %{nodejs_arches} with its
actual definition and they are working fine. The only remaining
problematic package is nodejs-nsp-audit-shrinkwrap which I will get
fixed today. I am not sure about nodejs-nth-check which package needs
it.

Regards,
Parag.
___
epel-devel mailing list
epel-devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/epel-devel@lists.fedoraproject.org

redeclipse needs co-maintainers

[Parag Nemade]

Hi,

   The current maintainer has requested[1] that he has no time to work
on redeclipse package and requested if any co-maintainers can help
this package.
Can someone interested in this game package, 9co-maintain this package?

Regards,
Parag

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1204600#c8
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: How to create langpacks for a rpm package?

[Parag Nemade]

On Thu, Jan 7, 2016 at 8:34 PM, Mark Wielaard  wrote:
> Hi,
>
> I noticed one of my packages (elfutils libelf) installs a small library
> of 90K but also 1MB of .mo locale files. Given that this package will
> always be installed because it is on the critical path I thought it
> might be nice to split the locale files out into language packs so
> that you could create a smaller install. But I cannot find documentation
> on how to create langpacks. Is there a description of the conventions
> used for language packs and/or example rpm macros to help create them?

Generally langpack packages used to have their own separate sources, I
am not sure if you really require to create langpack packages for
elfutils.
But, if you want to create langpacks then just add subpackages per
available translation language which follows package naming guidelines
https://fedoraproject.org/wiki/Packaging:NamingGuidelines#Addon_Packages_.28langpacks.29

Then you need to add entry for your package in langpacks section which
is at the end of comps file.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Bodhi

[Parag Nemade]

On Tue, Dec 22, 2015 at 12:34 PM, Dmitrij S. Kryzhevich
 wrote:
> And now it is locked. I just can't drop it and redone (it is locked) and I
> can't do anything (it is locked).
> Any ideas?

Check this https://fedoraproject.org/wiki/Bodhi2#FAQ

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Summary/Minutes from today's FESCo Meeting (2015-12-02)

[Parag Nemade]

===
#fedora-meeting: FESCO (2015-12-02)
===


Meeting started by paragan at 18:00:15 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2015-12-02/fesco.2015-12-02-18.00.log.html
.



Meeting summary
---
* init process  (paragan, 18:00:15)

* #1504 F24 System Wide Change: Fedora 24 Boost 1.60 uplift  (paragan,
  18:08:13)
  * LINK: https://fedorahosted.org/fesco/ticket/1504   (paragan,
18:08:13)
  * AGREED: Approved F24 System Wide Change: Fedora 24 Boost 1.60 uplift
(8, 0, 0)  (paragan, 18:11:32)

* #1509 yarock package maintainer not respoding  (paragan, 18:12:58)
  * LINK: https://fedorahosted.org/fesco/ticket/1509   (paragan,
18:12:59)
  * AGREED: Based on jam3s email reply on fesco list, let's open yarock
package for new maintainer (5, 0, 0)  (paragan, 18:19:24)

* #1510 F24 System Wide Change: Livemedia Creator  (paragan, 18:21:10)
  * LINK: https://fedorahosted.org/fesco/ticket/1510   (paragan,
18:21:11)
  * AGREED: Approved F24 System Wide Change: Livemedia Creator (7, 0, 0)
(paragan, 18:23:04)

* #1505 Being able to prefer packages on distribution level  (paragan,
  18:23:18)
  * LINK: https://fedorahosted.org/fesco/ticket/1505   (paragan,
18:23:18)
  * AGREED: The use of Suggests: as a mechanism to resolve ambiguous
dependencies is approved. (7, 0, 0)  (paragan, 18:41:42)

* Next week's chair  (paragan, 18:45:12)
  * sgallagh to chair next week  (paragan, 18:46:54)

* Open Floor  (paragan, 18:47:09)
  * LINK: https://fedorahosted.org/fesco/ticket/1469   (jwb, 18:48:04)
  * LINK: https://pagure.io/pungi/issue/81   (nirik, 19:02:41)

Meeting ended at 19:06:31 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* paragan (52)
* sgallagh (48)
* dgilmore (45)
* nirik (35)
* jwb (32)
* ajax (18)
* thozza (17)
* zodbot (10)
* rishi (3)
* jkurik_mtg (1)
* number80 (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Schedule for Wednesday's FESCo Meeting (2015-12-02)

[Parag Nemade]

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2015-12-02 18:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= New business =

#topic #1504 F24 System Wide Change: Fedora 24 Boost 1.60 uplift
.fesco 1504
https://fedorahosted.org/fesco/ticket/1504

#topic #1505 Being able to prefer packages on distribution level
.fesco 1505
https://fedorahosted.org/fesco/ticket/1505

#topic #1509 yarock package maintainer not respoding
.fesco 1509
https://fedorahosted.org/fesco/ticket/1509

#topic #1510 F24 System Wide Change: Livemedia Creator
.fesco 1510
https://fedorahosted.org/fesco/ticket/1510


= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Package review skipped and straight to repos?

[Parag Nemade]

Hi,

On Sun, Nov 29, 2015 at 3:27 AM, Till Maas  wrote:
> On Sat, Nov 28, 2015 at 09:11:48 +, James Hogarth wrote:
>
>> I was flicking through package review requests to see if anything jumped
>> out as interesting when I saw this:
>>
>> https://bugzilla.redhat.com/show_bug.cgi?id=1280422
>>
>> Thought I'd take a look as I hadn't had time to review it when it first
>> appeared and the requester had fixed the github breaking fedora-review
>> issue ...
>>
>> I was very surprised to see :
>>
>> Package request has been approved:
>> https://admin.fedoraproject.org/pkgdb/package/rpg
>>
>> Given that there is no assignee, no review and no flags on the bug was
>> there just a mistake in an automated process or has policy changed on
>> actually needing a review?
>
> It looks like a mistake to me, therefore I retired rpg for now.

Is that because of missing validation check for fedora-review+ flag?
Good to add code to check if requested package review bug has
fedora-review+ flag set.

Regards,
Parag.
--
devel mailing list
devel@lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org

Re: Unresponsive maintainer and unupdated package

[Parag Nemade]

Hi Chaoyi,

On Mon, Oct 19, 2015 at 5:08 PM, Chaoyi Zha  wrote:
> Node.js v0.12 has since become outdated. The page about updating it to 0.12
> for F23 is likely outdated as well by now. We may want to create a new page
> if it is needed.
>
> Here is the latest "LTS" release:
> https://nodejs.org/en/blog/release/v4.2.1/
>
>

Have you checked any existing nodejs module packages if they
compile/build/run fine against this 4.2.1 version? Maybe try creating
Copr repo and rebuilding all the existing nodejs packages against it.

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Summary/Minutes for today's FESCo meeting (2015-10-14)

[Parag Nemade]

===
#fedora-meeting: FESCO (2015-10-14)
===


Meeting started by paragan at 18:01:15 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2015-10-14/fesco.2015-10-14-18.01.log.html
.



Meeting summary
---
* init process  (paragan, 18:01:15)

* #615 Strategy for services that do not have systemd native unit files
  (paragan, 18:04:01)
  * LINK: https://fedorahosted.org/fesco/ticket/615   (paragan,
18:04:01)
  * AGREED: to sgallagh's modified proposal based on
https://fedorahosted.org/fesco/ticket/615#comment:69 (7, 1, 0)
(paragan, 18:19:40)
  * sgallagh to work on updating SySV init packaging guidelines update
(paragan, 18:20:48)

* #1486 FESCo elections for F24/F25  (paragan, 18:21:42)
  * LINK: https://fedorahosted.org/fesco/ticket/1486   (paragan,
18:21:43)
  * AGREED: Have one ticket tracking elections for all governing bodies,
opened in Council's ticketing system as Council is the top-level
governance body. (9, 0, 0)  (paragan, 18:25:17)

* #1489 F24 System Wide Change: NetworkManager 1.2  (paragan, 18:25:49)
  * LINK: https://fedorahosted.org/fesco/ticket/1489   (paragan,
18:25:50)
  * AGREED: Approved F24 System Wide Change: NetworkManager 1.2 (8, 0,
0)  (paragan, 18:28:04)

* #1490 restore MPI Requires Provides as F23 change  (paragan, 18:28:16)
  * LINK: https://fedorahosted.org/fesco/ticket/1490   (paragan,
18:28:16)
  * AGREED: Mark the Change
https://fedoraproject.org/wiki/Changes/RpmMPIReqProv as completed
and include in https://fedoraproject.org/wiki/Releases/23/ChangeSet
(7, 2, 0)  (paragan, 18:34:26)

* #1491 clarifications/improvements for new bundling policy  (paragan,
  18:35:27)
  * LINK: https://fedorahosted.org/fesco/ticket/1491   (paragan,
18:35:28)
  * AGREED: defer ticket 1491 for next week meeting  (paragan, 18:38:27)

* Next week's chair  (paragan, 18:40:32)
  * rishi to chair next to next week  (paragan, 18:42:29)

* Open Floor  (paragan, 18:42:39)

Meeting ended at 19:00:16 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* paragan (61)
* dgilmore (51)
* nirik (46)
* sgallagh (42)
* number80 (17)
* ajax (15)
* jwb (14)
* rishi (13)
* zodbot (12)
* jkurik (3)
* zbyszek (2)
* gholms (1)
* thozza (0)



Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Schedule for Wednesday's FESCo Meeting (2015-10-14)

[Parag Nemade]

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2015-10-14 18:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#topic #615 Strategy for services that do not have systemd native unit files
.fesco 615
https://fedorahosted.org/fesco/ticket/615

= New business =

#topic #1486 FESCo elections for F24/F25
.fesco 1486
https://fedorahosted.org/fesco/ticket/1486

#topic #1489 F24 System Wide Change: NetworkManager 1.2
.fesco 1489
https://fedorahosted.org/fesco/ticket/1489

#topic #1490 restore MPI Requires Provides as F23 change
.fesco 1490
https://fedorahosted.org/fesco/ticket/1490

#topic #1491 clarifications/improvements for new bundling policy
.fesco 1491
https://fedorahosted.org/fesco/ticket/1491

= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: new package SCM requests change

[Parag Nemade]

Hi,

On Wed, Oct 7, 2015 at 6:27 PM, Kevin Fenzi <ke...@scrye.com> wrote:
> On Wed, 7 Oct 2015 18:23:01 +0530
> Parag Nemade <panem...@gmail.com> wrote:
>
>> Hi,
>>I was asked to follow "This SCM request method has been deprecated.
>> Please see
>> https://fedoraproject.org/wiki/PackageDB_admin_requests; on one of my
>> new package review bug.
>>I want to know is this process announced somewhere? This has been
>> asked on review bug also but as limb never gets cc'ed to review bugs
>> he never gets further comments from people working on review bug.
>
> I was planning on doing so monday, but got swamped.
>
> I'll try and get the announcement out today.
>
>> Also, does this mean that we can now remove fedora-cvs flag from
>> bugzilla?
>
> Sure. Time permitting on bugzilla admins.
>
>> What benefit we got with this process where we again require
>> some admin to process requests?
>
> It means you don't need to copy and paste some information using a
> template from one place to another place that gets scraped by a tool
> and attempted to be parsed, it's all in one app.
> Look for the announcement for more info.
>
>> How will I know that branches are
>> created? will that information be commented on review bugzilla as
>> well?
>
> The ones you request?
>

I just used pkgdb and requested new package branches. Here I would
like to suggest when someone requests branches associated with some
review bug then that bug should get notification that "your request
for branches has been submitted and someone will process in next 24
hours" and then when actually branches are created that thing also get
commented on bugzilla that "your branches are ready to import new
package".

Thanks,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

new package SCM requests change

[Parag Nemade]

Hi,
   I was asked to follow "This SCM request method has been deprecated.
Please see
https://fedoraproject.org/wiki/PackageDB_admin_requests; on one of my
new package review bug.
   I want to know is this process announced somewhere? This has been
asked on review bug also but as limb never gets cc'ed to review bugs
he never gets further comments from people working on review bug.

Also, does this mean that we can now remove fedora-cvs flag from
bugzilla? What benefit we got with this process where we again require
some admin to process requests? How will I know that branches are
created? will that information be commented on review bugzilla as
well?

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Removing packages that have broken dependencies in F23 tree

[Parag Nemade]

Hi Ralph,

On Thu, Sep 24, 2015 at 9:12 PM, Ralph Bean  wrote:
> On Thu, Sep 24, 2015 at 04:34:11PM +0200, Kalev Lember wrote:
>> nodejs-grunt-contrib-copy ralph

This package is missing needed dependency npm(file-sync-cmp) to be
packaged in Fedora.

>> nodejs-grunt-saucelabs  ralph, piotrp

This package is missing needed dependency npm(requestretry) to be
packaged in Fedora.

>> nodejs-proxy-agent  ralph, piotrp

I have just rebuilt the existing commit which is working fine for
Fedora 23 and submitted update, rawhide is using higher version so no
issues there.

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Help with a font package

[Parag Nemade]

Hi,

On Wed, Sep 23, 2015 at 8:43 AM, Jerry James  wrote:
> I've got a package that has started bundling a font, namely Roboto
> Slab.  I'd like to do things the right way and make this a separate
> package, but I've never done a font package before and could use a
> little hand holding.
>
> The home page for this font seems to be
> https://www.google.com/fonts/specimen/Roboto+Slab, but there are no
> download links anywhere that I can see.  I looked at the existing
> google-robot-fonts package to try to get some clues.  That one shows a
> download link from developer.android.com, but it requires knowing a
> version number, which isn't anywhere on the home page.  It also
> contains some mysterious fontconfig and xml files that I don't
> understand ... and I think I'm already in over my head.  I don't even
> know how to start with this.  If anybody has words of wisdom for me,
> I'd appreciate them very much.
>
> Or, better yet, someone with experience can package the font for me,
> and tell me what bribe I can send to you in the mail to make it worth
> your while. :-)

There is already a good documentation available on Fedora Wiki about
font packaging[1] [2] then we have Fedora fonts mailing lists then IRC
channel #fedora-g11n where you can get help.

I have packaged this font and submitted its review now ->
https://bugzilla.redhat.com/show_bug.cgi?id=1265484

You may want to review it ;-)

Regards,
Parag.

[1] https://fedoraproject.org/wiki/Packaging:FontsPolicy
[2] https://fedoraproject.org/wiki/Fontconfig_packaging_tips
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Can't push update to stable

[Parag Nemade]

Hi,

On Tue, Sep 8, 2015 at 8:32 AM, Jerry James  wrote:
> I tried this morning and tonight to push this update to stable:
>
> https://bodhi.fedoraproject.org/updates/FEDORA-2015-14375
>
> Both times, bodhi told me that this update has not yet met the minimum
> testing requirements defined in the Package Update Acceptance Criteria.  But
> why not?  It has been in testing for 10 days, and the minimum is only 7,
> right?  The depchecks passed.  http://status.fedoraproject.org/ says that
> all systems are go.  I don't understand what the problem is.
> --

I think problem is identified and explained in this ticket
https://github.com/fedora-infra/bodhi/issues/505

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: bodhi 2 now live

[Parag Nemade]

Hi,

On Tue, Aug 25, 2015 at 2:21 PM, Richard Marko rma...@fedoraproject.org wrote:
 On 08/20/2015 05:45 AM, Kevin Fenzi wrote:
 Greetings.

 After a longer than expected outage window, I'm happy to report that
 bodhi2 is now live in production at

 https://admin.fedoraproject.org/updates
 or
 https://bodhi.fedoraproject.org/

 The web interface should be available and working for adding and
 managing updates and build root overrides as well as karma.
 The command line tools should be available tomorrow in repos.

 'fedpkg update' should work provided you have the latest python-fedora
 (python-fedora-0.5.5-1).

 There will likely be oddities and bugs. Please file them in github so
 we can prioritize them and get them fixed up.

 https://github.com/fedora-infra/bodhi/issues

 A collection of known issues and more information can be found at:
 https://fedoraproject.org/wiki/Bodhi2

 Thanks for your patience as we roll out this new bodhi version.

 kevin


 Hi,

 I kind of miss the overview of supported releases that was available in
 old version.

 It would be nice if this overview was part of the landing page with
 links to the release detail pages:
 https://bodhi.fedoraproject.org/releases/F23

 This way one is immediately aware which releases are still supported or
 newly added.


I have filed it today - https://github.com/fedora-infra/bodhi/issues/350


Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Unable to submit update for F22 (was Re: bodhi 2 now live)

[Parag Nemade]

Hi,

On Sun, Aug 23, 2015 at 11:03 AM, Ralf Corsepius rc040...@freenet.de wrote:
 On 08/21/2015 06:02 PM, Kevin Fenzi wrote:

 On Fri, 21 Aug 2015 05:27:37 +0200
 Ralf Corsepius rc040...@freenet.de wrote:

 Upstreams, yes, but not Fedora. Fedora should be self-hosted.


 Can you please define Fedora and self-hosted as you use them above?


 A domain 100 operated and owned by Fedora (rsp. RH) and covered by the
 Fedora CLA. Whether github is popular does not matter all. It's third party
 out of Fedora's control.

 What you are doing, means pushing Fedora users around, in what I consider
 very rude ways.

 Fedora is part of the larger open source comunity.
 Fedora Infrastructure uses 100% open source software.

 All irrelevant.

 Bohdi is just a tool used by Fedora, like any other arbitrary tool.

 I.e. I am not interested in getting involved in bodhi, I am just using the
 bodhi instance Fedora has deployed and I am expecting to have a way to
 contact the Fedora personnel to report bugs.


 Anyhow, for the last time:

 github is currently the perferred way to report bodhi2 bugs.


 And for illiterate: github a legitimate way for upstream, but is not a way,
 which is acceptable to Fedora users.
 You guys, need to learn to distinguish your roles as upstream and as
 maintainers of an installation - These are *not* identical.

 If you have some objection to them, you can file a fedorahosted ticket
 or infrastructure fedorahosted ticket. Also, I have been trying to file
 tickets on issues I see in mailing lists that aren't filed.


 I am close to filing a ticket to FESCO and/or the Board/Council, to request
 to revert to bodhi one - bodhi2 has proven to suffer from very ugly bugs and
 to be close to being unusable.

I am sure moving to bodhi2 will have definitely some advantages that
is why this move happened but I also don't see any usage document for
bodhi2 before/when it went live. Also bodhi is really important
service for Fedora so when its deployed on staging server for testing,
testers should have been called at least to comment on any
functionality/UI related problem.

I have also seen developers have worked to fix/triage almost all the
filed issues against bodhi2. If there are any major issues in bodhi2
then let's provide as much as input to them and they will try to
quickly fix them. But as move has already happen let's use bodhi2 and
not to go back.

Regards,
Parag
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Sponsors - who does (not) work on FE-NEEDSPONSOR tickets

[Parag Nemade]

On Mon, Aug 17, 2015 at 6:48 PM, Josh Boyer jwbo...@fedoraproject.org wrote:
 On Mon, Aug 17, 2015 at 9:07 AM, Miroslav Suchý msu...@redhat.com wrote:
 Dne 17.8.2015 v 14:47 Josh Boyer napsal(a):
 I would recommend removing all of the above people from the sponsors group.

 -1
 There is nothing wrong on being inactive. At least as long as others are 
 active.
 If they would want, they can return any time they want.

 There is a problem though.  It makes the sponsors list larger than it
 actually is, and gives the impression that we have more people
 available for sponsoring than we actually do.  From a new packager
 perspective, it is even more frustrating to see a larger list and
 still have no sponsor.  It also lends itself to those people being
 contacted directly for sponsorship requests, which will then go
 ungranted because they are not active sponsors.

 At the very least, we need to have a way to mark these people as
 inactive so they are accurately reflected.

 We should *not* be like turned down lover If you leave me once, you are not 
 welcome any more.

 I didn't say or suggest that they aren't welcome.  I said we should
 remove them from the sponsors list.  Please do not elevate things to
 hyperbole.

 And as I said previously, the knowledge you proven to have as sponsor does 
 not disappear. The guidelines does not change
 too much. You can refresh your knowledge in few hours.

 Correct.  However, if they return it should be as simple and quick to
 get them granted access again.

+1 to what Josh said above.

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Sponsors - who does (not) work on FE-NEEDSPONSOR tickets

[Parag Nemade]

Hi,

On Sat, Aug 15, 2015 at 12:43 PM, Miroslav Suchý msu...@redhat.com wrote:
 Recently we had discussion here about the queue of package reviews with
 FE-NEEDSPONSOR flag.
 I suggested to write some script which would query db and reveal those
 sponsors who does not make his duty.

 Here comes this script:
https://github.com/xsuchy/guard-fedora-sponsors

 It is first version and I'm sure there will be some false negatives. The
 current logic is:
 1. query FAS to get all usernames from packager group who are sponsors
 2. for each such user get all bugs from past 365 day for Package Review
 component which are assigned to this sponsor
 3. give the sponsor some credit when he changed bug status (to whatever
 state) as this indicate some work on this bug
 4. give the sponsor some credit if he remove FE-NEEDSPONSOR from blocking
 bugs as this indicate finishing sponsor work

 This does not reflect if you sponsor somebody directly. E.g. because he want
 to be become co-maintainer and does not submit package review.

 This time I run it for past year. So this script reveals those who does not
 sponsor anybody for whole year. I hope that in future I can lower this
 constant to half year or even 3 months.

 Ideas, patches and comments about this script are welcome.


So, how are you going to address my issue?  I always work using my
email id which is associated with inactive/old FAS id but I never want
to use email in bugzilla which is associated with my newly migrated
FAS id. I have always kept a line between my fedora
development/packaging work and my voluntary package review work.

I know the intent behind this is to soon remove inactive sponsors from
sponsors group.

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Sponsors - who does (not) work on FE-NEEDSPONSOR tickets

[Parag Nemade]

On Sat, Aug 15, 2015 at 2:35 PM, Parag Nemade panem...@gmail.com wrote:
 Hi,

 On Sat, Aug 15, 2015 at 12:43 PM, Miroslav Suchý msu...@redhat.com wrote:
 Recently we had discussion here about the queue of package reviews with
 FE-NEEDSPONSOR flag.
 I suggested to write some script which would query db and reveal those
 sponsors who does not make his duty.

 Here comes this script:
https://github.com/xsuchy/guard-fedora-sponsors

 It is first version and I'm sure there will be some false negatives. The
 current logic is:
 1. query FAS to get all usernames from packager group who are sponsors
 2. for each such user get all bugs from past 365 day for Package Review
 component which are assigned to this sponsor
 3. give the sponsor some credit when he changed bug status (to whatever
 state) as this indicate some work on this bug
 4. give the sponsor some credit if he remove FE-NEEDSPONSOR from blocking
 bugs as this indicate finishing sponsor work

 This does not reflect if you sponsor somebody directly. E.g. because he want
 to be become co-maintainer and does not submit package review.

 This time I run it for past year. So this script reveals those who does not
 sponsor anybody for whole year. I hope that in future I can lower this
 constant to half year or even 3 months.

 Ideas, patches and comments about this script are welcome.


 So, how are you going to address my issue?  I always work using my
 email id which is associated with inactive/old FAS id but I never want
 to use email in bugzilla which is associated with my newly migrated
 FAS id. I have always kept a line between my fedora
 development/packaging work and my voluntary package review work.

 I know the intent behind this is to soon remove inactive sponsors from
 sponsors group.

Just found one thing while triaging needsponsor reviews that loveshack
is already sponsored but his one package submission was still blocking
177841. It will be good if either sponsorer or sponsoree will remove
blocking to 177841 from all the reviews when someone gets sponsored
his package in packager.



 Regards,
 Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Schedule for Wednesday's FESCo Meeting (2015-08-05)

[Parag Nemade]

Following is the list of topics that will be discussed in the FESCo
meeting Wednesday at 18:00UTC in #fedora-meeting on irc.freenode.net.

To convert UTC to your local time, take a look at
  http://fedoraproject.org/wiki/UTCHowto

or run:
  date -d '2015-08-05 18:00 UTC'


Links to all tickets below can be found at:
https://fedorahosted.org/fesco/report/9

= Followups =

#topic 1455 F23 System Wide Change: Standardized Passphrase Policy
.fesco 1455
https://fedorahosted.org/fesco/ticket/1455

#topic 1463 upgrades for F23 and beyond
.fesco 1463
https://fedorahosted.org/fesco/ticket/1463

#topic #1466 non-responsive maintainer exception process for skottler
.fesco 1466
https://fedorahosted.org/fesco/ticket/1466

= Open Floor =

For more complete details, please visit each individual ticket.  The
report of the agenda items can be found at
https://fedorahosted.org/fesco/report/9

If you would like to add something to this agenda, you can reply to
this e-mail, file a new ticket at https://fedorahosted.org/fesco,
e-mail me directly, or bring it up at the end of the meeting, during
the open floor topic. Note that added topics may be deferred until
the following meeting.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Summary/Minutes for today's FESCo meeting (2015-08-05)

[Parag Nemade]

===
#fedora-meeting: FESCO (2015-08-05)
===


Meeting started by paragan at 18:00:09 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2015-08-05/fesco.2015-08-05-18.00.log.html
.



Meeting summary
---
* init process  (paragan, 18:00:09)

* 1455 F23 System Wide Change: Standardized Passphrase Policy  (paragan,
  18:02:20)
  * LINK: https://fedorahosted.org/fesco/ticket/1455   (paragan,
18:02:20)
  * LINK: https://fedoraproject.org/wiki/Passphrase_policy   (nirik,
18:03:12)
  * AGREED: : Accept https://fedoraproject.org/wiki/Passphrase_policy
and use this for luks passwords also (+7, 0, 0)  (paragan, 18:13:07)

* 1463 upgrades for F23 and beyond  (paragan, 18:13:35)
  * LINK: https://fedorahosted.org/fesco/ticket/1463   (paragan,
18:13:35)
  * AGREED: : Accepted
https://fedoraproject.org/wiki/Changes/DNF_System_Upgrades (+7, 0,
0)  (paragan, 18:19:04)

* #1466 non-responsive maintainer exception process for skottler
  (paragan, 18:19:34)
  * LINK: https://fedorahosted.org/fesco/ticket/1466   (paragan,
18:19:35)
  * AGREED: : jwb to commit and build the 2.0.3 update to fix the CVEs
(+8, 0, 0)  (paragan, 18:32:56)

* #1467 F23 Changes - Progress at Change Checkpoint: Completion
deadline (testable)   (paragan, 18:34:27)
  * LINK: https://fedorahosted.org/fesco/ticket/1467   (paragan,
 18:34:29)
  * AGREED: : moving all them to f24 except these (two week
 atomic/layered docker images) Changes, (+5, 0, 0)  (paragan,
 18:53:29)

* Next week's chair  (paragan, 18:53:41)
  * no meeting next week  (paragan, 18:54:53)
  * LINK:
http://flock2015.sched.org/event/85fbdf579fa91c49ba13d45a9c1774eb
(nirik, 18:56:27)
  * sgallagh to chair next meeting  (paragan, 19:00:06)

* Open Floor  (paragan, 19:00:35)
  * LINK: https://fedoraproject.org/wiki/Cloud/Cloud_PRD?rd=Cloud_PRD
(dgilmore, 19:07:33)

Meeting ended at 19:18:04 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* paragan (63)
* nirik (53)
* number80 (40)
* jwb (40)
* sgallagh (36)
* dgilmore (34)
* adamw (18)
* rishi` (14)
* zodbot (10)
* jkurik (8)
* ajax (7)
* swilkerson (3)
* roshi (3)
* rishi (0)
* thozza (0)
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Review swap

[Parag Nemade]

Hi,

I have submitted a python package for review python-os-client-config,
https://bugzilla.redhat.com/show_bug.cgi?id=1247177

Appreciate if someone can review it and I can review your package :)

Regards,
Parag
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F-23 Branched report: 20150720 changes

[Parag Nemade]

Hi,

On Wed, Jul 22, 2015 at 10:38 AM, Milan Crha mc...@redhat.com wrote:

 On Wed, 2015-07-22 at 06:48 +0200, Milan Crha wrote:
  Furthermore, I run my rawhide machine today and tried `dnf update`,
  which didn't offer me the update of the evolution-data-server. I'd
  expect to have it offered after two days of the koji build.
 
  Maybe I missed some policy/update change?
 

 Hi again,
 it looks like a dnf issue, see below. Even manual update from
 dnf-1.0.1-3.fc23.noarch to dnf-1.0.2-2.fc24.noarch didn't help.
 Bye,
 Milan

 $ dnf list evolution
 Fedora - Rawhide - Developmental packages for t 792 kB/s |  43 MB 00:55
 Last metadata expiration check performed 0:00:47 ago on Tue Jul 21
 23:49:59 2015.
 Installed Packages
 evolution.x86_64  3.17.3-1.fc23
 @System
 Available Packages
 evolution.i6863.17.4-1.fc24
 rawhide
 evolution.x86_64  3.17.4-1.fc24
 rawhide
 $ su
 Password:
 # dnf update
 Fedora - Rawhide - Developmental packages for t 784 kB/s |  43 MB 00:55
 Last metadata expiration check performed 0:00:35 ago on Tue Jul 21
 23:51:51 2015.
 Dependencies resolved.
 Nothing to do.
 Complete!



You need to check broken dependencies as
 # dnf update evolution --best
Last metadata expiration check performed 0:01:32 ago on Thu Jul 23 05:44:09
2015.
Error: package gnome-shell-3.17.3-2.fc23.x86_64 requires
libcamel-1.2.so.53()(64bit), but none of the providers can be installed

I think you need to build gnome-shell update that will depend on new
evolution update.

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: Improving our processes for new contributors.

[Parag Nemade]

Hi,

On Tue, Jul 21, 2015 at 6:14 PM, Miroslav Suchý msu...@redhat.com wrote:

 Dne 11.7.2015 v 23:38 Jonathan Underwood napsal(a):
  Thoughts from the COPR folks?

 I like the idea of adding Copr as intermediate step for new contributors.
 Copr is outer ring of Fedora and it definitely
 make sense for newbies to go from outer ring to ring0. Step by step.

 Additionally we have in plan to run fedora-review consequently after each
 build, which hopefully will lead to better
 quality of spec files and resulting RPMs.


 Regarding long wait for sponsor: We have little over 120 sponsors right
 now. And there is little over 210 reviews
 waiting for sponsors.
 If every sponsor would take 2 reviews right now, the queue would be empty.
 So our current process still can work.
 However I am aware that sponsoring somebody is very irregular task. I am
 sponsor too. It happen that I sponsor 2
 contributors in one month, but sometimes there are months where I focus on
 something else and I forgot on my sponsor
 duties. I assume other sponsors have it similar.
 I would welcome if somebody can write cron script which would mine data
 from BZ and send me email that:

 Dear sponsor,
 it seems that you did not sponsor anybody for 3 months. We have 120 new
 contributors waiting for sponsor.
 Please consider taking some bug from:
   https://bugzilla.redhat.com/show_bug.cgi?id=177841

 Sincerely your Watchmen


What above is said is from sponsor side. I will suggest similar for
contributor side. Implement a script which search FE-NEEDSPONSOR package
review bugs where package has not already under review. This script will
check package submission date and then submit a comment every month till 3
months like

Dear contributor,
Its one/two/three month since this package review is submitted and you are
in need of a sponsor. Have you started reviewing other packages reviews? if
yes please post the link to your reviews in the next comment.
Have you also run fedora-review on your package submissions? if yes and
found any issues in review.txt then try to fix them or ask on devel list or
#fedora-devel irc channel for help.

something like this. This will make sure contributor realize what he need
to do next after his submission. Thus, contributor will not loose interest
in packaging.

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [ACTION REQUIRED] FTBFS Packages in rawhide (2015-07-13)

[Parag Nemade]

On Thu, Jul 16, 2015 at 2:41 AM, Michael Schwendt mschwe...@gmail.com
wrote:

 On Wed, 15 Jul 2015 21:53:46 +0200, Till Maas wrote:

   The email is hard to understand. It seems it looks at a dependency tree
   and somehow lists any leaf package maintainers in an unsorted list of
   dependencies.
 
  What is your proposal to display the information?

 To display the known dependency-chain (src.rpm names or binary rpm names)
 as in my reply to twoerner:

  twoerner: tuned - systemtap - prelink


Showing dependencies like above will be a nice improvement for this report.

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: [ACTION REQUIRED] FTBFS Packages in rawhide (2015-07-13)

[Parag Nemade]

Hi,

On Tue, Jul 14, 2015 at 4:10 AM, opensou...@till.name wrote:

 The following packages did not build for two releases and will be
 retired before the Alpha Freeze, unless someone takes care of them. If you
 know
 for sure that the package should be retired, please do so now with a proper
 reason:
 https://fedoraproject.org/wiki/How_to_remove_a_package_at_end_of_life

 According to https://fedoraproject.org/wiki/Schedule Alpha Freeze will
 occur on
 2015-07-28.

  Package(co)maintainers   Status Change
 ===
 UpTools sebelk60 weeks ago
 akkawillb, java-sig   60 weeks ago
 apt-maven-plugingoldmann  60 weeks ago
 bcfg2   fab, solj, zultron60 weeks ago
 clean   puiterwijk, pwouters  60 weeks ago
 clojure-compat  kushal, salimma   60 weeks ago
 clojure-contrib salimma   60 weeks ago
 clojure-maven-pluginsalimma   60 weeks ago
 clucy   salimma   60 weeks ago
 cpm mmahut60 weeks ago
 emacs-common-essalexlan   60 weeks ago
 epris   rtnpro60 weeks ago
 gdmap   mebourne  60 weeks ago
 honeyd  pvrabec   60 weeks ago
 ironjacamar ricardo, goldmann 60 weeks ago
 jabref  mef, tomspur  60 weeks ago
 jgroups212  orphan4 weeks ago
 lancet  kushal60 weeks ago
 libigtl mrceresa, peter   60 weeks ago
 mdsplib thias 60 weeks ago
 mojarra goldmann  21 weeks ago
 muleorphan, tspauld98 4 weeks ago
 nurbs++ mycae 60 weeks ago
 opengroklkundrak  60 weeks ago
 openuniversemmahut, astronomy-sig 60 weeks ago
 pfHandleredragon  60 weeks ago
 prelink jakub, mjw60 weeks ago
 prover9 tcolles, dwheeler 60 weeks ago
 publican-redhat rlandmann 60 weeks ago
 python-foolscap cicku, dcantrel   60 weeks ago
 python-sproxlmacken   60 weeks ago
 python-umemcacheyograterol60 weeks ago
 qtdbf   tieugene  60 weeks ago
 quarry  salimma   60 weeks ago
 robert-hookesalimma   60 weeks ago
 rubygem-activerecord-nulldb-ktdreyer  60 weeks ago
 adapter
 rubygem-git-up  jvcelak   60 weeks ago
 rubygem-icalendar   tremble   60 weeks ago
 rubygem-rgenskottler  60 weeks ago
 scala-stm   willb 60 weeks ago
 scalacheck  willb 60 weeks ago
 shrinkwrap-resolver goldmann, gil, mizdebsk   60 weeks ago
 spark   willb 60 weeks ago
 typesafe-config willb 60 weeks ago
 xmms-flac   thias 60 weeks ago

 The following packages require above mentioned packages:
 Depending on: clean (1), status change: 2014-05-14 (60 weeks ago)
 clean-extra-utils (maintained by: puiterwijk)
 clean-extra-utils-0.1-9.fc23.i686 requires clean =
 2.4-16.fc21


 Depending on: ironjacamar (26), status change: 2014-05-14 (60 weeks ago)
 narayana (maintained by: goldmann)
 narayana-5.0.0-3.fc21.src requires ironjacamar =
 1.1.3-2.fc21

 wildfly (maintained by: goldmann)
 wildfly-8.1.0-3.fc22.noarch requires
 mvn(org.jboss.ironjacamar:ironjacamar-common-api) = 1.1.3.Final,
 mvn(org.jboss.ironjacamar:ironjacamar-common-impl) = 1.1.3.Final,
 mvn(org.jboss.ironjacamar:ironjacamar-common-spi) = 1.1.3.Final,
 mvn(org.jboss.ironjacamar:ironjacamar-core-api) = 1.1.3.Final,
 mvn(org.jboss.ironjacamar:ironjacamar-core-impl) = 1.1.3.Final,
 mvn(org.jboss.ironjacamar:ironjacamar-deployers-common) = 

Re: [ACTION REQUIRED] FTBFS Packages in rawhide (2015-07-13)

[Parag Nemade]

Hi,

On Tue, Jul 14, 2015 at 8:15 PM, Vít Ondruch vondr...@redhat.com wrote:

 Dne 14.7.2015 v 00:40 opensou...@till.name napsal(a):
 
   Package(co)maintainers   Status
 Change
 
 ===
  rubygem-rgenskottler  60 weeks
 ago
 

 Fixed this one.


Thanks for helping with this package. This saved fontpackages package which
saved all the fonts in Fedora now :)

Regards,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Summary/Minutes for today's FESCo meeting (2015-07-08)

[Parag Nemade]

===
#fedora-meeting: FESCO (2015-07-08)
===


Meeting started by paragan at 18:00:02 UTC. The full logs are available
athttp://meetbot.fedoraproject.org/fedora-meeting/2015-07-08/fesco.2015-07-08-18.00.log.html
.



Meeting summary
---
* init process  (paragan, 18:00:02)

* #1445 F23 Self Contained Changes  (paragan, 18:01:34)
  * LINK: https://fedorahosted.org/fesco/ticket/1445   (paragan,
18:01:34)

* #1455 F23 System Wide Change: Standardized Passphrase Policy
  (paragan, 18:11:04)
  * LINK: https://fedorahosted.org/fesco/ticket/1455   (paragan,
18:11:04)
  * We need io.js change page updated with the information provided on
devel mailing list  (paragan, 18:18:39)
  * AGREED: let's revisit this next time when draft gets ready for
review  (paragan, 18:19:26)

* #1456 F23 System Wide Change: Node.js 0.12  (paragan, 18:19:38)
  * AGREED: F23 System Wide Change: Node.js 0.12 (+6, 1, -0)  (paragan,
18:26:45)

* #1457 F23 System Wide Change: jQuery  (paragan, 18:27:08)
  * AGREED: F23 System Wide Change: jQuery (+7, 0, -0)  (paragan,
18:34:05)

* #1458 F23 System Wide Change: IBus 1.5.11  (paragan, 18:34:09)
  * AGREED: F23 System Wide Change: IBus 1.5.11 (+7, 0, 0)  (paragan,
18:40:18)

* Next week's chair  (paragan, 18:40:32)
  * dgilmore to chair next week  (paragan, 18:41:42)

* Open Floor  (paragan, 18:41:49)

Meeting ended at 18:44:46 UTC.




Action Items






Action Items, by person
---
* **UNASSIGNED**
  * (none)




People Present (lines said)
---
* paragan (67)
* thozza (32)
* nirik (25)
* number80 (21)
* dgilmore (12)
* jwb (10)
* zodbot (9)
* ajax (7)
* lupinix (2)
* thozza2 (2)
* Southern_Gentlem (1)
* sgallagh (0)
* rishi (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct

Re: F23 Self Contained Change: io.js Technology Preview

[Parag Nemade]

Hi,

On Mon, Jul 6, 2015 at 2:47 AM, T.C. Hollingsworth 
tchollingswo...@gmail.com wrote:

 On Wed, Jul 1, 2015 at 12:41 PM, Stephen Gallagher sgall...@redhat.com
 wrote:
  So this was discussed at today's FESCo meeting[1]. Basically, we're not
  sure that it makes sense to have both interpreters in the distribution,
  particularly since they are merging back together in the future.
 
  Would you be willing to consider just packaging io.js *as* node.js in
  Fedora 23? Among other things, this would avoid the need to go through
  additional package reviews, rebuild nodejs-* packages to work with
  io.js, etc.
 
  My limited understanding of io.js is that it is essentially a superset
  of node.js functionality,

 This is correct.  It has additional features but is broadly compatible
 with the ecosystem of packages available via npm.

  so it seems like just moving to this instead
  of node.js 0.12.0 would make sense.

 I'm fine with moving the default engine in Fedora 23 to io.js.

 I'm not so fine with still calling the package we ship io.js in
 nodejs, since it's not node.js, and we can't be entirely sure the
 next version of node.js will be greater than the current version of
 io.js (although I believe that is the plan).

  Otherwise, will this Change require building NPM packages for iojs
  -module rather than (or in addition to) nodejs-module? Can this be
  avoided by running them with an alternatives-provided /usr/bin/node?

 No.  Only binary modules would require special iojs-foo cousins due to
 the different binary compatibility surface of the two engines.  These
 would be built from the SRPMS that already exist.  While binary module
 SRPMs would require changes, none would be necessary for
 pure-JavaScript modules.

 npm does not offer any ability to ship different code when different
 node.js/io.js versions are used, so it really isn't necessary for us
 to either.  The vast majority of all code in the ecosystem will either
 Just Work or detect and do the right thing at runtime.  We also don't
 really have the resources to maintain two separate stacks of
 JavaScript applications, as you're rightly concerned about.

 Therefore, we do not intend to support shipping different versions of
 pure-JavaScript nodejs software for different engines, though it of
 course will be possible to express that a particular package only
 works/doesn't work with a particular engine via Requires/Conflicts.

 Note that all of the above is a concern for the SIG even if we only
 ship io.js in Fedora, as I'd eventually like to get 0.12 into EPEL
 without leaving 0.10 users in the dust.  My intention was to design
 the binary SRPM build logic such that the same SRPM would build
 nodejs-foo and iojs-foo cousins on Fedora and nodejs0.10-foo and
 nodejs0.12-foo cousins on EPEL with no spec changes.

 So remember that some big changes are coming to nodejs-packaging and
 binary module SRPMs anyway, the only question is which branches
 they're landing in.  ;-)


Can you please add this information on change wiki page as well?

Thanks,
Parag.
-- 
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct