Rodney Baker composed on 2019-06-21 18:25 (UTC+0930):

If btrfs is installed, then btrfs-tools should be installed, that's expected - but if btrfs is not installed, it should be possible to uninstall btrfs-progs without breaking other packages (like gparted). User choice, etc.

I wholeheartedly agree with your philosophy about both propriety of hard requires, and btrfs in particular: # zypper ll | grep btrfs 8 | btrfsprogs | package | (any) Luckily for me, I'm not a gparted user. However, I am very particular about fonts, and find several so-called "required" fonts routinely interfering with zypper progress, forcing me to repeatedly "break" multiple packages because I don't want to see those fonts, don't want to waste space hosting those fonts, and don't want to waste bandwidth installing or updating those fonts: http://bugzilla.opensuse.org/show_bug.cgi?id=992519 onerous font package requirements IMO, "those that do" have too much power to bloat the distro to suit their personal fancies rather than best interest of the distro or its reputation. Break/require/depend should equate to functionality in absence of, not does not look the way developer/packager prefers it to look in absence of. I see the current condition of gparted requiring btrfsprogs no differently than if yast2-network was requiring yast2-tftp-server, yast2-dns-server or yast2-dhcp-server (which thankfully it does not). -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Friday, 21 June 2019 10:39:30 ACST Emanuel Castelo wrote:

Also using TW and current, I placed a lock ‘zypper al btrfs*’ after ‘zypper rm -u btrfs*’ execute, and I have not seen gparted complain.

No, gparted won't complain, but zypper does... # zypper dup -dl Retrieving repository 'Mozzilla Tumbleweed' metadata ............................................................................................................[done] Building repository 'Mozzilla Tumbleweed' cache .................................................................................................................[done] Retrieving repository 'Kernel HEAD' metadata ....................................................................................................................[done] Building repository 'Kernel HEAD' cache .........................................................................................................................[done] Loading repository data... Reading installed packages... Warning: You are about to do a distribution upgrade with all enabled repositories. Make sure these repositories are compatible before you continue. See 'man zypper' for more information about this command. Computing distribution upgrade... Problem: gparted-0.33.0-1.4.x86_64 requires btrfsprogs >= 4.1, but this requirement cannot be provided not installable providers: btrfsprogs-5.1-1.3.i586[download.opensuse.org-oss] btrfsprogs-5.1-1.3.x86_64[download.opensuse.org-oss] Solution 1: Following actions will be done: remove lock to allow installation of btrfsprogs-5.1-1.3.i586[download.opensuse.org-oss] install btrfsprogs-5.1-1.3.i586 despite the inferior architecture install libreiserfscore0-3.6.27-4.3.i586 despite the inferior architecture install libzstd1-1.4.0-2.1.i586 despite the inferior architecture Solution 2: deinstallation of gparted-0.33.0-1.2.x86_64 Solution 3: keep obsolete gparted-0.33.0-1.2.x86_64 Solution 4: remove lock to allow installation of btrfsprogs-5.1-1.3.x86_64[download.opensuse.org-oss] Solution 5: break gparted-0.33.0-1.4.x86_64 by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/3/4/5/c] (c): Naturally enough, I choose option 5, because I don't want btrfs on any of my systems due to past bad experiences involving unbootable systems and data loss, but for gparted IMHO it should be a "recommend", not a dependency. Others may disagree. I'll file the bug and see what happens. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ============================================================== -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Carlos E. R. composed on 2019-06-21 12:27 (UTC+0200):

Rodney Baker wrote:

...

Emanuel Castelo wrote:

...

...

Also using TW and current, I placed a lock ‘zypper al btrfs*’ after ‘zypper rm -u btrfs*’ execute, and I have not seen gparted complain.

...

No, gparted won't complain, but zypper does...

The only solution is to create an empty, mock btrfsprog.rpm, that satisfies zypper. rpm -i --justdb btrfsprogs-<version>.rpm zypper al btrfsprogs

Should work, until its dependencies require it be updated. -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Friday, 21 June 2019 21:36:52 ACST Carlos E. R. wrote:

On 21/06/2019 13.30, Felix Miata wrote:

...

Carlos E. R. composed on 2019-06-21 12:27 (UTC+0200):

...

Rodney Baker wrote:

...

Emanuel Castelo wrote:

...

Also using TW and current, I placed a lock ‘zypper al btrfs*’ after ‘zypper rm -u btrfs*’ execute, and I have not seen gparted complain.

No, gparted won't complain, but zypper does...

The only solution is to create an empty, mock btrfsprog.rpm, that satisfies zypper.

rpm -i --justdb btrfsprogs-<version>.rpm zypper al btrfsprogs

Should work, until its dependencies require it be updated.

Nice trick! I didn't know about it.

Nor did I - thanks, Felix. Looks like it needs to be downloaded and present first, though, because... error: open of btrfsprogs-5.1-1.3.x86_64.rpm failed: No such file or directory Oh well - at least it can be deleted immediately afterwards. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ============================================================== -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On Saturday, 22 June 2019 2:47:46 ACST Carlos E. R. wrote:

On 21/06/2019 16.10, Rodney Baker wrote:

...

On Friday, 21 June 2019 21:36:52 ACST Carlos E. R. wrote:

...

On 21/06/2019 13.30, Felix Miata wrote:

...

Carlos E. R. composed on 2019-06-21 12:27 (UTC+0200):

...

Rodney Baker wrote:

...

Emanuel Castelo wrote: > Also using TW and current, I placed a lock ‘zypper al btrfs*’ after > ‘zypper > rm -u btrfs*’ execute, and I have not seen gparted complain.

No, gparted won't complain, but zypper does...

The only solution is to create an empty, mock btrfsprog.rpm, that satisfies zypper.

rpm -i --justdb btrfsprogs-<version>.rpm zypper al btrfsprogs

Should work, until its dependencies require it be updated.

Nice trick! I didn't know about it.

Nor did I - thanks, Felix. Looks like it needs to be downloaded and present first, though, because...

error: open of btrfsprogs-5.1-1.3.x86_64.rpm failed: No such file or directory

Oh well - at least it can be deleted immediately afterwards.

Yes, the rpm command needs the rpm archive, to enter things from it on the database. But the files contained in it are not installed.

Bug #1139018. -- ============================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au CCNA #CSCO12880208 ============================================================== -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org