[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Problem with btrfs-progs package



On 31 May 2016 at 12:17, Gianfranco Costamagna <locutusofborg@debian.org> wrote:
> Hi Dimitri, Nicholas and backporters!
>
>
>>Thank you for getting in touch with me. Based on the version number
>
>>you appear to be running a backport package, which is not prepared /
>>uploaded / supported by me at all.
>
>
> It is supported by Nicholas, and by me as his sponsor.
>
> (Nicholas asked many times to have the possibility to maintain the package
> BTW)
>

I have accepted some, but not all patches from him. I disagree with
some of them, which i have clearly stated before =)
So far, I did not request nor require assistants with btrfs-tools
package maintenance in the distribution.

>>Packages should not be renamed in stable series, and when backporting,
>>package rename should not be included and/or backported correctly such
>>that one should still be able to install btrfs-tools & btrffs-progs
>>packages, together, from backports.
>
>
> I don't agree, package should be renamed, and should provide the old name
> (this is the mistake I can see here)
>

Old name is provided via an empty transitional package. At least in
unstable, I don't know what's the policy or convention for backports.

>>Please contact debian-backports and the backport uploader for further support.
>
>
> I'm here, and I'm sure Nicholas too :)
>

cool.

>
>>FYI - I strongly do not recommend to run backports. Are there>particular reasons and/or bugs that you do that on production systems?
>>Cause it's best to cherrypick fixes for bugs and ship a proper update
>>into debian updates stream without any incompatible packaging changes.
>
>
> I fully agree here, but when a kernel is backported, btrfs should follow it
> at least in my POV.
>
>>@ Debain Backports team
>>Could you please remove btrfs-progs / btrfs-tools backports until
>>instability issues are resolved, if the below bug report is valid?
>
>
> If you apply this patch on unstable
> @@ -20,6 +20,7 @@
> Depends: ${misc:Depends}, ${shlibs:Depends}
> Replaces: btrfs-tools (<< 4.4.1-1)
> Breaks: btrfs-tools (<< 4.4.1-1)
> +Provides: btrfs-tools

Horum, this seems odd to me. In unstable we have
https://tracker.debian.org/pkg/btrfs-progs btrfs-progs src package
which builds btrfs-progs binary package with most binaries, and
btrfs-tools dummy transitional package of high enough version number.
btrfs-tools (depends: btrfs-progs) & btrfs-progs should be
coinstallable in unstable. And this same property should be available
in backports, no? And "installing" btrfs-progs package from backports
should pull in the new btrfs-tools package from backports too. That is
the current intentions for any system doing stable->testing upgrade,
and should be the same for stable->backports and/or
stable+backports->testing.

Could this be a user error, that both updated btrfs-tools &
btrfs-progs binary package  are not pulled from the backports pocket?

> Description: Checksumming Copy on Write Filesystem utilities
> Btrfs is a new copy on write filesystem for Linux aimed at implementing
> advanced features while focusing on fault tolerance, repair and easy
>
>
> the problem will go away on the next backport.
>
>
> Nicholas is doing a great job here, even providing a btrfs-borg package
> (I like, as a borg maintainer :) )
>
> https://github.com/sten0/btrfs-borg/blob/master/btrfs-borg
>
> He as also a "fork" of the Debian packaging, where you might want to review and take his
> patches.
> https://github.com/sten0/btrfs-progs
>
> How do you want to proceed?
> fix unstable (adding the provide) and then ask us to backport?
> Add the missing Provides on backports alone?
>
> I understand you are running out of time, and we appreciate all the bits you can provide us, but
> please, accept some help :)
>

I'm not running out of time =) I just travel and spend a week cruising
in the Caribbean without any internet connectivity ;-)

> (BTW if you have a better solution than the provide, just ask, a renaming back should be out
> of scope, e.g. per backports policy).
>

btrfs-tools binary package is still built by the new src:btrfs-progs
package and should be available to satisfy relationships. Is that not
the case, and/or is buggy as per above?


> cheers!
>
> G.
>
>
> On 24 May 2016 at 15:18, Uher Marek <marek.uher@t-mobile.cz> wrote:
>>
>>
>> Hello Dimitri,
>>
>>
>>
>> I detected possible problem with btrfs-progs package on our Debian GNU/Linux
>> 8.4 (jessie) servers. The issue is that the new btrfs-progs doesn’t work
>> correctly with following packages:
>>
>>
>>
>> ·         Snapper
>>
>> ·         system-storage-manager
>>
>>
>>
>> When I tried to install new btrfs-progs package (4.4.1-1.1~bpo8+1) I got
>> this warning:
>>
>>
>>
>> root@xaero:~# apt-get -u install btrfs-progs
>>
>> Reading package lists... Done
>>
>> Building dependency tree
>>
>> Reading state information... Done
>>
>> The following packages will be REMOVED:
>>
>>   btrfs-tools libsnapper2 snapper system-storage-manager
>>
>> The following NEW packages will be installed:
>>
>>   btrfs-progs
>>
>> 0 upgraded, 1 newly installed, 4 to remove and 0 not upgraded.
>>
>> Need to get 525 kB of archives.
>>
>> After this operation, 1,498 kB disk space will be freed.
>>
>> Do you want to continue? [Y/n] n
>>
>> Abort.
>>
>> root@xaero:~#
>>
>>
>>
>> Simply, snapper and system-storage-manager packages depend on btrfs-tools
>> and therefore we are not able to install the new btrfs-progs package without
>> breaking package dependencies. I want therefore kindly ask you if you are
>> able to fix mentioned problem. Many thanks in advance for your answer or
>> help. Have a nice day.
>>
>>
>>
>> Best regards,
>>
>>
>>
>> Marek
>>
>> --
>>
>> Ing. Marek Uher
>>
>> Senior ICT Consultant
>>
>> Expert Solutions & Innovations Team
>>
>> B2B Service Delivery Management Department
>>
>> Business Segment Division
>>
>>
>>
>> T-Mobile Czech Republic a.s.
>>
>> Tomíčkova 2144/1
>>
>> Praha 4
>>
>> 149 00
>>
>> Czech Republic
>>
>> Mobile: (+420) 739 242 103
>>
>> Phone: (+420) 236 099 704
>>
>> Fax: (+420) 236 099 999
>>
>> E-mail: marek.uher@t-mobile.cz
>>
>> http://www.t-mobile.cz/
>>
>> http://www.t-systems.cz/
>>
>> http://www.gts.cz/
>>
>>
>>
>> T-Mobile Czech Republic a.s.
>>
>> Commercial Register: Municipal Court in Prague, Part B, Entry No. 3787
>>
>> Registered office: Tomickova 2144/1, Prague 4, 149 00
>>
>> Company ID: 64949681
>>
>> Tax ID: CZ64949681
>>
>>
>>
>> BIG CHANGES START SMALL - CONSERVE RESOURCE BY NOT PRINTING EVERY E-MAIL
>>
>>
>>
>> Tato zpráva a její přílohy mohou obsahovat interní nebo důvěrné informace.
>> Pokud nejste zamýšlený příjemce, tak prosím neprodleně oznamte odesílateli,
>> že jste obdrželi tuto zprávu omylem. Jakákoliv prohlížení, šíření nebo
>> kopírování této zprávy je přísně zakázáno. Neprodleně tuto zprávu a všechny
>> její přílohy smažte. Děkujeme.
>>
>>
>>
>> This transmittal and/or attachements may be privileged or confidental. It is
>> intended solely for addressee named below. Any dissemination, or copying is
>> strictly prohibited. If you received this transmittal in error, please
>> notify us immediately by reply and immediately delete this message and its
>> attachements. Thank you.
>>
>>
>>
>>
>> Zásady komunikace, které společnost T-Mobile Czech Republic a.s. užívá při
>> sjednávání smluv, jsou uvedeny zde. Není-li v zásadách uvedeno jinak,
>> nepředstavuje tato zpráva konečný návrh na uzavření či změnu smlouvy ani
>> přijetí takového návrhu. The communication principles which T-Mobile Czech
>> Republic a.s. applies when negotiating contracts are defined here. Unless
>> otherwise stated in the principles, this message does not constitute the
>> final offer to contract or an amendment of a contract or acceptance of such
>> offer.
>
>
>
> --
> Regards,
>
> Dimitri.



-- 
Regards,

Dimitri.


Reply to: