Re: Bizzar error with dpkg-buildpackages

[Michelle Konzack]

Hello Harald Jenny,

Am 2011-04-06 00:01:20, hacktest Du folgendes herunter:
> I think you might find http://backports.debian.org/Contribute/#index5h3
> interesting, specifically point 4 - this would translate for you to:
> 
> 1.20-29   -> unstable (source included)
> 1.20-29~bpo60+1   -> stable/squeeze
> 1.20-29~bpo50+1   -> oldstable/lenny
> 
> This naming sheme will guarantee that you can update your package correctly.

Thank you for this hind.  I use it too

> Kind regards
> Harald Jenny

Thanks, Greetings and nice Day/Evening
Michelle Konzack

-- 
# Debian GNU/Linux Consultant ##
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsystems@tdnet France EURL   itsystems@tdnet UG (limited liability)
Owner Michelle KonzackOwner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France   77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

  
 

Jabber linux4miche...@jabber.ccc.de
ICQ#328449886

Linux-User #280138 with the Linux Counter, http://counter.li.org/


signature.pgp
Description: Digital signature

Re: Bizzar error with dpkg-buildpackages

[Harald Jenny]

Hi

On Tue, Apr 05, 2011 at 09:22:43PM +0200, Michelle Konzack wrote:
> I have this problem with 17 packages.
> 
> Can I use e.g.:
> 
> 1.20-29 ->  unstable (source included)
> 1.20-29b1   ->  stable/squeeze
> 1.20-29b2   ->  oldstable/lenny
> 

I think you might find http://backports.debian.org/Contribute/#index5h3
interesting, specifically point 4 - this would translate for you to:

1.20-29 -> unstable (source included)
1.20-29~bpo60+1 -> stable/squeeze
1.20-29~bpo50+1 -> oldstable/lenny

This naming sheme will guarantee that you can update your package correctly.

Kind regards
Harald Jenny


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20110405220120.ga19...@harald-has.a-little-linux-box.at

Re: Bizzar error with dpkg-buildpackages

[Didier Raboud]

Michelle Konzack wrote:

> Can I use e.g.:
> 
> 1.20-29 ->  unstable (source included)
> 1.20-29b1   ->  stable/squeeze
> 1.20-29b2   ->  oldstable/lenny
> 
> I was thinking there could be an upgrade problem later if I use this  or
> is there a special naming scheme for multi-release?  (I know, there  was
> a discussion some years ago, but I do not know its result)

Policy documents this, but…

You can use the "~" character as indicator of "sorts before". And using 
release codenames is often clearer (see e.g. the requirements for backports 
or stable updates.

In your case

> 1.20-29   -> unstable
> 1.20-29~squeeze1  ->  stable/squeeze
> 1.20-29~lenny1->  oldstable/lenny

1.20-29~lenny1 < 1.20.29~squeeze1 < 1.20-29

Note that this works because "squeeze" sorts alphabetically after "lenny". 
Now that we will release Wheezy, it will get harder to choose release 
codenames (as they should [for convenience] sort after "wheezy").

Cheers, 

OdyX


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/ing1qm$5ru$1...@dough.gmane.org

Re: Bizzar error with dpkg-buildpackages

[Michelle Konzack]

Hello Alexander,

Am 2011-04-05 19:51:23, hacktest Du folgendes herunter:
> Do you know what the +b1 means?  A +b1 never has an actual source
> package, therefore the b1 is cut off.

I was told it is used as NMU upload...  But how can I  provide  packages
for 3 releases in the same time without conflicting?

I have this problem with 17 packages.

Can I use e.g.:

1.20-29 ->  unstable (source included)
1.20-29b1   ->  stable/squeeze
1.20-29b2   ->  oldstable/lenny

I was thinking there could be an upgrade problem later if I use this  or
is there a special naming scheme for multi-release?  (I know, there  was
a discussion some years ago, but I do not know its result)

> Best Regards,
>   Alexander


Thanks, Greetings and nice Day/Evening
Michelle Konzack

-- 
# Debian GNU/Linux Consultant ##
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsystems@tdnet France EURL   itsystems@tdnet UG (limited liability)
Owner Michelle KonzackOwner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France   77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

  
 

Jabber linux4miche...@jabber.ccc.de
ICQ#328449886

Linux-User #280138 with the Linux Counter, http://counter.li.org/


signature.pgp
Description: Digital signature

Re: Bizzar error with dpkg-buildpackages

[Alexander Reichle-Schmehl]

Hi!

* Michelle Konzack  [110405 01:23]:

> Ehm, on the top, dpkg-deb say "signfile xmem_1.20-29+b1.dsc" and then at
> dpkg-genchanges I get "../xmem_1.20-29.dsc can't be read".   I  compiled
> the last two days 16 Packages and it was working and now not more.
> 
> Any suggestions what it can be that the "+b1" is cut off?

Do you know what the +b1 means?  A +b1 never has an actual source
package, therefore the b1 is cut off.


Best Regards,
  Alexander


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110405175123.gc...@melusine.alphascorpii.net

Re: Bizzar error with dpkg-buildpackages

[Michelle Konzack]

Thankyou Raphael,

> Because "+b1" means bin-nmu 1 and is never part of the source version.
> That's policy.
> 
> Don't put "+bX" at the end of your version and you'll be fine.

OK (it was working some ears ago...), but how to build the same Package
Version for different Releases (unstable, stable and oldstable)?

It seems it has a little bit changed in the last 5 years.

Thanks, Greetings and nice Day/Evening
Michelle Konzack

-- 
# Debian GNU/Linux Consultant ##
   Development of Intranet and Embedded Systems with Debian GNU/Linux

itsystems@tdnet France EURL   itsystems@tdnet UG (limited liability)
Owner Michelle KonzackOwner Michelle Konzack

Apt. 917 (homeoffice)
50, rue de Soultz Kinzigstraße 17
67100 Strasbourg/France   77694 Kehl/Germany
Tel: +33-6-61925193 mobil Tel: +49-177-9351947 mobil
Tel: +33-9-52705884 fix

  
 

Jabber linux4miche...@jabber.ccc.de
ICQ#328449886

Linux-User #280138 with the Linux Counter, http://counter.li.org/


signature.pgp
Description: Digital signature

Re: Bizzar error with dpkg-buildpackages

[Raphael Hertzog]

On Tue, 05 Apr 2011, Michelle Konzack wrote:
> Hello Mentors,
> 
> I am not compiling the package the first time, but today I got an  error
> on Squeeze which could be lead to the yesterdays "upgrade":

No, not related.

> Ehm, on the top, dpkg-deb say "signfile xmem_1.20-29+b1.dsc" and then at
> dpkg-genchanges I get "../xmem_1.20-29.dsc can't be read".   I  compiled
> the last two days 16 Packages and it was working and now not more.
> 
> Any suggestions what it can be that the "+b1" is cut off?

Because "+b1" means bin-nmu 1 and is never part of the source version.
That's policy.

Don't put "+bX" at the end of your version and you'll be fine.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Follow my Debian News ▶ http://RaphaelHertzog.com (English)
  ▶ http://RaphaelHertzog.fr (Français)


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110405092244.gc10...@rivendell.home.ouaza.com

Re: Bizzar error with dpkg-buildpackages

[Paul Wise]

Please re-post your message with English in the warning/error messages:

http://www.debian.org/MailingLists/#codeofconduct

-- 
bye,
pabs

http://wiki.debian.org/PaulWise


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/banlktik8amvbjnzpigw8_et-b3fbjvf...@mail.gmail.com