Of the above ones, Martin already mentioned in bug #23357, comment #8 (about Mageia 6), that bittorrent, courier-imap-pop, imap, mydsn, and udhcpd don't come from rpmsrate.

Thierry, do you know where they come from?

I didn't check the other ones.

Source RPM: drakx,metatask ? => drakx-installer-stage2, metatask ?
Assignee: bugsquad => mageiatools
CC: (none) => marja11, thierry.vignaud
See Also: (none) => https://bugs.mageia.org/show_bug.cgi?id=23357

(In reply to Marja Van Waes from comment #1)
> Of the above ones, Martin already mentioned in bug #23357, comment #8 (about
> Mageia 6), that bittorrent, courier-imap-pop, imap, mydsn, and udhcpd don't
> come from rpmsrate.

tmb gave the answer, they come from drakfirewall in drakx-net for configuring ports and he already dropped them with this commit:
http://gitweb.mageia.org/software/drakx-net/commit/?id=1f3ce7010fe9b960257a61138821d11d437ff7b4


So those are left:

(In reply to Bit Twister from comment #0)

>  `gcc-java'
That was dropped in cauldron http://svnweb.mageia.org/packages?view=revision&revision=1138007 but it is still in rpmsrate

>  `gstreamer0.10-pulse'
Afaik we dropped all of gstreamer0.10*, so gstreamer0.10-pulse should be removed from rpmsrate.

>  `jovie'
Jovie is no longer maintained upstream (KDE) and not in cauldron.

>  `kaccessible'
Dead upstream (no commits since 4 years ago) and not in cauldron


>  `lesstif-mwm'

lesstif-mwm-0.95.2-14.mga7 should be in cauldron, but I can't find it. Maybe it didn't build or so? http://svnweb.mageia.org/packages?view=revision&revision=1215053 CC'ing kekepower.

The ones below still need to be looked into:

>  `php-mysql'
>  `postgresql9.4'
>  `python-django'
>  `rfkill'

CC: (none) => smelror

Lesstif submitted to Cauldron.

Cheers,
Stig

(In reply to Stig-Ørjan Smelror from comment #3)
> Lesstif submitted to Cauldron.
> 
> Cheers,
> Stig

Thanks that was very fast!

I had missed something, though :-(

Wally had added lesstif to task-obsolete
http://svnweb.mageia.org/packages?view=revision&revision=1235519
and had set all packages requiring it to require motif instead.

Would you have time to bump the release for those lesstif packages in task-obsolete
http://svnweb.mageia.org/packages/cauldron/task-obsolete/current/SPECS/task-obsolete.spec?r1=1235519&r2=1235518&pathrev=1235519

and to move the lesstif to svn obsolete?


=========================================

I suppose, since the motif package contains /usr/bin/mwm, that lesstif-mwm needs to be replaced with motif (without -mwm) in rpmsrate

(In reply to Marja Van Waes from comment #2)
> The ones below still need to be looked into:
> 
> >  `php-mysql'

Should be php-mysqli

> >  `postgresql9.4'

Should be postgresql9.6 (although will hopefully be postgresql10 by mga7).

> >  `python-django'

Should be python2-django or python3-django.  Philippe would know which would be better to suggest.  Historically it's been the python2 one which was recently renamed to follow Fedora's new convention.  I'm not sure if the python3 one is preferable going forward (obviously it will be at some point).

> >  `rfkill'

Not sure why that one disappeared.  tmb might know.

I think tv fixed all of those on september 13:

http://svnweb.mageia.org/packages/cauldron/meta-task/current/SOURCES/rpmsrate-raw?view=log

meta-task was pushed right after that, and stage2 two days later, so assuming this got FIXED.

Status: NEW => RESOLVED
Resolution: (none) => FIXED

(In reply to Marja Van Waes from comment #6)
> I think tv fixed all of those on september 13:
> 
> http://svnweb.mageia.org/packages/cauldron/meta-task/current/SOURCES/
> rpmsrate-raw?view=log
> 
> meta-task was pushed right after that, and stage2 two days later, so
> assuming this got FIXED.

Several were fixed. Some not. New ones have shown up.


#  grep 'unknown package' /root/drakx/ddebug.log
* unknown package `postgresql9.6'
* unknown package `postgresql9.6-server'
* unknown package `cdp'
* unknown package `postgresql9.6-devel'
* unknown package `postgresql9.6-pltcl'
* unknown package `postgresql9.6'
* unknown package `postgresql9.6'
* unknown package `mydsn'
* unknown package `udhcpd'
* unknown package `imap'
* unknown package `courier-imap-pop'
* unknown package `postgresql9.4'
* unknown package `postgresql9.6'
* unknown package `bittorrent'

# ls -l  /root/drakx/ddebug.log
-rw-r--r-- 1 root root 6132695 Oct  3 14:20 /root/drakx/ddebug.log

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Created attachment 10397 [details]
report.bug.xz

(In reply to Bit Twister from comment #7)
> * unknown package `postgresql9.6'
> * unknown package `postgresql9.6-server'
> * unknown package `postgresql9.6-devel'
> * unknown package `postgresql9.6-pltcl'
> * unknown package `postgresql9.6'
> * unknown package `postgresql9.6'
> * unknown package `postgresql9.4'
> * unknown package `postgresql9.6'

postgresql10 has been packaged, so they should be switched to that.

> * unknown package `cdp'

I believe the package was just dropped :o(

> * unknown package `udhcpd'

Maybe replace with dnsmasq?

> * unknown package `imap'

Should be dovecot.

> * unknown package `mydsn'

Not sure what that is.

> * unknown package `courier-imap-pop'
> * unknown package `bittorrent'

Should be removed from meta-task.

is this still relevant?

CC: (none) => mageia

#  grep 'unknown package' /root/drakx/ddebug.log
* unknown package `zemberek-server'
* unknown package `wine'
* unknown package `libmariadb-devel'
* unknown package `lsb-core-lib'
* unknown package `rgrep'
* unknown package `libalsa-plugins'
* unknown package `jed'
* unknown package `ufraw-gimp'
* unknown package `jed-xjed'
* unknown package `lsb-lib'
* unknown package `postgresql9.4'
* unknown package `postgresql9.6'

Version: Cauldron => 8

That can't be from a Mageia 8 installation...there's no references to those old postgresql versions anymore...

Anyway, jed (which includes rgrep) was mysteriously missing from the mirrors, so I'm rebuilding it.  zemberek-server is now zemberek and ufraw-gimp is gone, so I fixed both of those and rebuilt meta-task.  The other packages listed there do exist on i586, so I don't know why it's saying unknown package.  If you're installing on 64-bit, rpmsrate says !64bit for most of those, so it shouldn't be looking for them.

(In reply to David Walser from comment #12)
> That can't be from a Mageia 8 installation...there's no references to those
> old postgresql versions anymore...

What can I say, clean install, and doubled check that I was on the MGA8
system/install.

> 
> Anyway, jed (which includes rgrep) was mysteriously missing from the
> mirrors, so I'm rebuilding it.  zemberek-server is now zemberek and
> ufraw-gimp is gone, so I fixed both of those and rebuilt meta-task.  The
> other packages listed there do exist on i586, so I don't know why it's
> saying unknown package.  If you're installing on 64-bit, rpmsrate says
> !64bit for most of those, so it shouldn't be looking for them.


Well, some of your changes worked. Not so much on the others, picked up
a few new ones.

* unknown package `perl-Gimp'
* unknown package `lsb-core-lib'
* unknown package `wine'
* unknown package `libmariadb-devel'
* unknown package `libalsa-plugins'
* unknown package `lsb-lib'
* unknown package `postgresql9.4'
* unknown package `postgresql9.6'
* unknown package `vuze'

Created attachment 12212 [details]
ddebug.log

Forgot to add

#  urpmq --list-media active
Core Release
Core Updates
Nonfree Release
Nonfree Updates
Tainted Release
Tainted Updates

# cat /etc/release
Mageia release 8 (Official) for x86_64

New additions of unknown package may because I did not disable invictus-firewall
and postgresql database packages during package selection.

OK I just removed perl-Gimp too (and a duplicate database definition in compssUsers.pl), but the only postgresql in there is 13, and vuze isn't in there at all.  It looks like those show up in your log where it's enabling services.  I still don't know how it's getting in there.

I think I saw Martin recently fix something with regard to handling of the 64bit flag.  I wonder if there's still some package that needs to be rebuilt against updated meta-task.  I can't imagine old postgresql versions are hardcoded into some other part of the installer.

CC: (none) => luigiwalser, mageia

See bug 23357 comment 6. The "unknown package" message is printed before the flags are examined. That accounts for lsb-lib, lsb-core-lib, libalsa-plugins, libmariadb-devel, and wine.

postgresql9.4, postgresql9.6, and vuze come from drakfirewall. I've just fixed that in git.

Awesome work Martin.  Thank you.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

results from latest meta taks updates.

* unknown package `libalsa-plugins'
* unknown package `libmariadb-devel'
* unknown package `lsb-lib'
* unknown package `lsb-core-lib'
* unknown package `wine'

no idea why lsb failures.
lsb package group was selected.

Resolution: FIXED => (none)
Status: RESOLVED => REOPENED

Created attachment 12236 [details]
ddebug.log

(In reply to Bit Twister from comment #20)
> results from latest meta taks updates.
> 
> * unknown package `libalsa-plugins'
> * unknown package `libmariadb-devel'
> * unknown package `lsb-lib'
> * unknown package `lsb-core-lib'
> * unknown package `wine'
> 
> no idea why lsb failures.

See comment 18.

Martin already explained those ones, so we're in good shape now.

Resolution: (none) => FIXED
Status: REOPENED => RESOLVED